Xarchiver branch

[Stephan Arts]

On 4/25/06, Jani Monoses <jani.monoses at gmail.com> wrote:
>
> > Mem-usage with a tar archive containing 250.000 files.
> >
> > fileroller: 134.736 KB
> > xarchiver: 81.540 KB
>
> nice :)
> >
> > A remaining problem is performance with archives containing large files...
> > takes too long and xarchiver gui does not respond.
>
> It's your call eventually but would it not be better to make it work for
> the common case first (where did you find an archive with 250K files?!),

I tar my /usr/share ;)

> get more testers on it (via thunar plugin too), then optimize? Well
> unless optimizing affects the whole design and source code of xarchiver.

Not entirely sure where the bug is coming from yet, so don't yet know
if the optimizing affects the whole design. Once i have finished the
basics for the GUI, by that i mean all dialogs and such, i will fix
the command-line options.

Then it will be ready for testing via thunar plugin.

>
> Jani

Stephan

P.S.
The memory usage does fluctuate, sometimes it is exactly the other way around.
...Probably some memory-leaks that stumbled in the code... :(