> I'm beginning to learn and use GTK+. Here is the steps that I
> believe are needed to build an GTK+ application:
> 1. Initialize the library.
Generally happens in main...
> 2. Create widgets and set attributes.
> 3. Register callback routines.
Those two go together... Either load a glade UI
Thanks for all your inputs.
My project:
I have many math solvers which are written in command line
mode, using data files for the inputs. The programs then
plot out the variable relationships. Older clients are
accustomed to a command line structure, the newer clients are
GUI only. So I wa
Hi Mike,
MEA-MikeFriedrichs wrote:
> List,
>
> Accidentally hit the send button too soon.
>
> I'm beginning to learn and use GTK+.
>
> Here is the steps that I believe are needed to build an GTK+ application:
>
> 1. Initialize the library.
> 2. Create widgets and set attributes.
> 3. Register call
MEA-MikeFriedrichs wrote:
[...]
I can see an application becoming very large in one module. So I would
like to break the program into modules, where each module can be managed
and compiled independently and finally link all the modules together.
But I don't see any divisions because of inter
If what you mean by "widget hierarchy" is what I think you mean --
namely, the parent-child relationships between container widgets and
the stuff they contain -- then I would recommend modularizing
according to this hierarchy. That is, steps 2, 3, and 5 in your list
can go together in a single mod
List,
Accidentally hit the send button too soon.
I'm beginning to learn and use GTK+.
Here is the steps that I believe are needed to build an GTK+ application:
1. Initialize the library.
2. Create widgets and set attributes.
3. Register callback routines.
4. Define widget hierarchy.
5. Show wi
List,
I'm begining to learn and use GTK+.
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
