1 |
> we can do plugable applications. in GTK, you can plug an application in another |
2 |
> one. It's very simple to do. I'ts used in the mandrake control center, and |
3 |
> differently in the gnome control center. |
4 |
> |
5 |
> It's important to keep in mind that those config tools will be available in |
6 |
> console mode, where the gui takes a lot more space (newt/ncurses). So the |
7 |
> screen should be simple with only few gui widget to be able to display fine in |
8 |
> both mode. Or we do two seperate tools for each mode. There are technical |
9 |
> solutions to have one code that works in gtk and ncurses. Maybe the same exists |
10 |
> for other toolkits. Anyway it's maybe a little soon to talk about that |
11 |
|
12 |
As you said, it is too soon to be talking about this. But I want to say |
13 |
this :). I think that the tools should be seperate, and that the tool |
14 |
itself should determine wether to use GTK or ncurses. Something like |
15 |
this could be used, if we use python: |
16 |
|
17 |
try: |
18 |
import gtk |
19 |
except RuntimeException, e: |
20 |
""" no gui, using ncurses """ |
21 |
... |
22 |
|
23 |
An ofcourse we offer two options, for instance -g and -n to force GTK or |
24 |
ncurses (if available). |
25 |
|
26 |
Yet another argument against a precompiled language like c or c++ but it |
27 |
is really too soon to be talking about this :) |
28 |
|
29 |
Groeten, |
30 |
Tiemo |
31 |
|
32 |
-- |
33 |
Gentoo Linux Documentation developer & Desktop Research member |
34 |
Dutch Documentation: http://www.gentoo.org/doc/nl/index.xml |
35 |
Desktop Research: http://www.gentoo.org/proj/en/desktop/research/ |
36 |
blubber@g.o | http://dev.gentoo.org/~blubber/ |
37 |
|
38 |
Public key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE3E9E3A6 |
39 |
Key fingerprint = 6749 CD77 B577 D615 4B3C A082 C430 0ACD E3E9 E3A6 |
40 |
|
41 |
|
42 |
-- |
43 |
gentoo-desktop-research@g.o mailing list |