Re: gnome-apt screenshot, more questions
On Fri, 27 Nov 1998, Lalo Martins wrote:
>
> I see. I'd think there is a better way to do this, but you
> surely researched before making the choice, so I'll shut up. :-)
>
Check the list archives - it's a speed and memory use issue. It works
pretty nice actually, I was surprised at how easy it was to write.
> > On the info panel...
>
> I see. This is where we have the package name and short
> description right?
>
Well, I don't know. It's where we have stuff that's not the package
description. :-) It's the gdeb-ish sort of thing.
> But logically (program-wise) it's nice to have it as a separate
> thing so you can choose to put it elsewhere when we want to go
> to customization (later). For example, in vertical view it looks
> better to have the name-and-short-description on the top,
> everything else (notebook or not) in the middle and the actions
> on the bottom (as I described with my ugly ASCII art).
>
Okie, it's fine with me to have it logically separate.
> I will. Just didn't have too much incentive for downloading
> something I won't be able to compile :-) But now I have, since I
> want your data structures and I want to make things "mesh well".
>
> Actually I think I'm going to switch to C++ like the rest of
> libapt, so I can use libapt's classes and overridden functions.
> I never liked C anyway. :-)
>
I basically need this interface (look at infopanes.h):
void set_selection(pkgCache::Package* pkg);
void set_cache (GAptCache* cache);
Both of these should handle 0 for the pointer.
My InfoPanes class right now provides a single widget, but it can be
changed to provide more, don't worry about that yet.
The real work is to get from the Package* and Cache* to a bunch of
strings; once we have those, we can play around with putting them all over
the screen in various configurations. Jason recently posted about how to
do this. You can let me worry about interfacing it to the rest of the app,
really...
If you come up with a patch send it along...
Havoc
Reply to: