Re: gdselect alpha 3 [libapt]
On Fri, 6 Nov 1998, Havoc Pennington wrote:
> Urgh, this is not going to work in Gtk+ unless we write a fairly complex
> custom widget. I think we'll just have to eat the overhead for now, unless
> it turns out to be really bad, and if it ever bothers someone a lot they
> can write the custom widget.
Thought exercise:
There are 2200 packages in slink, lets say you display them all. Lets say
you use a string containing about 50 characters. That is 110k of ram or
about 10% of the total memory usage.
Furthermore, everytime someone does an operation you have to go and
rebuild ALL of that data which will lead to a very clunky and slow feeling
GUI.
The version I have been fiddling with is highly optimized in this regard
and uses about 15k of ram for the tree and never regenerates it.
> This is going to fight over argc/argv with the Gtk/Gnome arg parser, that
> is an issue to resolve. Any chance your class removes the args it
> understands and ignores the others?
Hrm, I presume it's important for gtk to have command lines.. Does its
code leave out ones it does not understand? If so you could just call mine
on the result.
If that's not possible then maybe I could do something..
Jason
Reply to: