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

[Daniel Campos]

Hi:

In fact I'm using GtkTreeView for ListBox, ListView and ColumnView. One of
the things I was thinking is to write only the more complex control in 
C++, and
then use the gambas-control feature to implement ListBox, ListView, TreeView
GridView and ColumnView, may be in the gb.gtk.gambas part, or even in 
the gb.form component
if you did the same.


I agree with you: this model is very complex for Basic programmers, but 
may be there could be
only a Widget written in C++, exposing all the complex of a TreeView 
model, for those who
want to use it (primarily us to implement the rest of widgets :-), and 
then cover it with
Gambas code so we had a simple ListBox, ListView... and may be the 
TableView control that, I don't
know why, is placed in the gb.qt.ext component. All these controls would 
take the look & feel from
QT or GTK+ depending on what component is in use, and we (specially me 
:-) could save a lot
of time and code.

I'd want to start that work as soon as possible, as I know there are 
some bugs in the current
ListBox and ListView implementations, and I would like to rewrite that 
code...

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 ?
>
>  
>