Thu Jul 13 04:04:53 PDT 2000

Another day of hacking on everything. Mostly gnop, grapevine and gnome-libs. After the gnop release someone sent me an excellent idea. A command line tool for loading up gnop dialogs. This means that coupled with gconftool, you can now have shellscripts have gconf configuration dialog boxes. Plus you can run the dialog of any app that uses just the stock internal widget stuff or glade stuff, by just running gnop-tool on it's .gnop file. I still need to do the "many configuration" stuff for gnop so that I can have per applet dialog box for configurations. These needs some schema shuffling and stuff like that. Then I can get done more grapevine stuff. Also will have to test out gnop's support for gconf lists. Another thing that needs some ideas is internationalization of gnop. There are several possibilities:

• Put strings in a .c file and use gettext (disadvantage: only your program can really be translated then)
• Put strings using the xml:lang stuff or gconf like stuff into the .gnop file (disadvantage: incredibly messy large file, hard to edit)
• Put strings into separate files (disadvantage: incredible mess of files and problems with finding stuff etc...)

Right now I'm leaning towards the second one, though I think the third one is also good. The second one can be made much better if there is a good tool to edit .gnop files (meaning: improve gnop-edit). The advantage over the third one is, that having only one file makes it much more convenient. We get all the power of having all the config info inside the XML file. So you could pass files around even accross network to easily setup apps. I guess you can still do it with the third option, though somewhat more clumsily.

So I've managed to be an incredible geek today and not even leave the house and hack on stuff all day (except for watching tv for like 2 hours)