[Gambas-devel] gb.gtk 05806 / qt bug

[Benoit Minisini]

On Sunday 07 August 2005 20:38, Daniel Campos wrote:
> Hi;
>
> >>Bad idea for GTK+:
> >>
> >>1) GTK+ has these icons included in the same library, so you're wasting
> >>memory
> >>having it twice in memory (and hard disk).
> >
> >So this is the reason I didn't find them! I waste hard disk, but not
> > memory as the picture files are memory mapped.
>
> True :-)
>
> >>2) Icons can change with the theme. What to do then? They will not look
> >>at the rest
> >>of applications.
> >
> >Do the stock icons included in the library change with the theme ? Are
> > icon themes a GTK+ feature or a Gnome feature ?
>
> They change as GTK+ looks in some paths (I suppose defined in the theme)
> to replace
> the original icons for the theme icons. However not all themes use that
> feature.
>
> It is a GTK+ feature: All themes for GTK+ are pure GTK+, not GNOME. In fact
> the GNOME project is moving all the graphic features to GTK+ (Almost all
> GNOME
> widgets are deprecated). It is the modular conceptof GNOME: graphics:
> GTK+ , xml: libxml,
> process communication: dbus, and so on...
>
> >OK. But please can you use the following syntax? Stock["XX/a/b/c"] where
> > XX is the size of the icon: 16, 32, ... and 'a/b/c' the path to the icon
> > - without any extension at the end. And can you simplify a bit the way
> > GTK+ name its icons, by using subdirectories: Stock["16/text/bold"] for
> > example, or Stock["16/device/harddisk"].
> >
> >If path is not found, Stock must find a icon of a different size, scale
> > it, and return it.
> >
> >This way, I will be able to make a gb.qt gambas part that will use the
> > same syntax, and equivalent icons. As for gb.qt.kde, I will override the
> > Stock class so that it uses the KDE icon themes.
>
> OK!
>
> Regards,
>
> D. Campos
>

Nothing related to what is above...

When you start to work on TreeView & all his family controls, tell me. 

Because, in QT 4, TrollTech did like the GTK+ guys. I mean now the view of 
TreeView widget is distinct from the data, like in GTK+.

Even if this is powerful, I finally find that complex for the average Gambas 
user. So I think that we must not make this distinction visible, i.e.:
- We must keep only one control for the view. 
- This view will create its own data structure internally.
- The view control will have a r/w property (named View ?) that will returns 
itself if the control has its own data, and that will be able to be set to 
another control of the same type so that it displays the same data.

I did all that in my new Editor control. It has a Document property, and if 
you do Editor1.Document = Editor2.Document, then Editor1 will display and 
edit the same text as Editor2.

What do you think about that ?

-- 
Benoit Minisini
mailto:gambas at ...1...