Re: KArchive design changes

2012-11-21 Thread David Faure
On Sunday 28 October 2012 11:34:41 Pier Luigi wrote: > > > * applications need to know the format in advance, my implementation > > > > > > instead had a public generic API that lets you open a file then it > > > detects the mime type and load the appropriate plugin for you. > > > > For this poin

Re: KArchive design changes

2012-10-28 Thread Kevin Ottens
On Sunday 28 October 2012 10:48:47 Pier Luigi wrote: > 2012/10/12 Kevin Ottens > > I can't predict the future, but still, I doubt it will go in Qt itself to > > be honest. I don't see why that would force you to make your own github > > repository and your own copy though. > > To avoid the whole k

Re: KArchive design changes

2012-10-28 Thread Pier Luigi
2012/10/1 Mario Bensi > > I will use it of course, maintaining code already available in a larger > > codebase is not an option I would totally avoid it, although I hope it > will > > go in Qt 5.1+ because otherwise I will have to make my own github repo > > with a copy of it. > > > > What's you

Re: KArchive design changes

2012-10-28 Thread Pier Luigi
2012/10/12 Kevin Ottens > On Monday 24 September 2012 08:49:56 Pier Luigi wrote: > > I will use it of course, maintaining code already available in a larger > > codebase is not an option I would totally avoid it, although I hope it > will > > go in Qt 5.1+ because otherwise I will have to make my

Re: KArchive design changes

2012-10-12 Thread Kevin Ottens
On Monday 24 September 2012 08:49:56 Pier Luigi wrote: > I will use it of course, maintaining code already available in a larger > codebase is not an option I would totally avoid it, although I hope it will > go in Qt 5.1+ because otherwise I will have to make my own github repo > with a copy of it

Re: KArchive design changes

2012-10-01 Thread Mario Bensi
> I will use it of course, maintaining code already available in a larger > codebase is not an option I would totally avoid it, although I hope it will > go in Qt 5.1+ because otherwise I will have to make my own github repo > with a copy of it. > > What's you plan for pushing more kdelibs stuff i

Re: KArchive design changes

2012-09-23 Thread Pier Luigi
2012/8/24 Mario Bensi : > Hi, > > I have check the code and i think we have done a similar work on kde > framework. I think you can use this instead of your fork to avoid to work on 2 > base of code. If you have any questions to know how use karchive in framework, > don't hesitate to ask me. > > Be

Re: KArchive design changes

2012-08-24 Thread Mario Bensi
Hi, I have check the code and i think we have done a similar work on kde framework. I think you can use this instead of your fork to avoid to work on 2 base of code. If you have any questions to know how use karchive in framework, don't hesitate to ask me. Best Regards Mario On Wednesday, Aug

Re: KArchive design changes

2012-08-15 Thread Pier Luigi
2012/7/25 Mario Bensi : > Hi, > > Thanks to work on karchive. I need to take time to look your code and find how > to integrate it in karchive (in kde framework). For the moment, i haven't lot > of spare time, if you can wait, i could check this in 2 weeks ago. No problem I'm a bit busy myself rig

Re: KArchive design changes

2012-07-25 Thread Mario Bensi
Hi, Thanks to work on karchive. I need to take time to look your code and find how to integrate it in karchive (in kde framework). For the moment, i haven't lot of spare time, if you can wait, i could check this in 2 weeks ago. Mario On Sunday, July 22, 2012 10:55:49 AM Pier Luigi wrote: > Hi,

KArchive design changes

2012-07-22 Thread Pier Luigi
Hi, I'm working on alternative desktop environment based on Wayland and Qt5 mainly designer for Maui, my Linux distribution, and I would like to share some work with you. Some time ago I needed to create an API for accessing archive files that could be used by many programs. The code is here: ht