Re: Object Class Violation
"scientica (GMail)" <[email protected]> Thu, 04 Aug 2005 19:49:35 +0200
| Newsgroups | gmane.network.directoryadmin |
|---|---|
| Message-ID | <[email protected]> |
Manuel Amador (Rudd-O) wrote: >El mi=C3=A9, 03-08-2005 a las 10:29 -0700, Neil Schneider escribi=C3=B3: > > =20 > >>I think the idea of using XML is a good one. >> =20 >> > >and the gnome stack already provides for interesting libraries to >manipulate XML! > >(by the way, how's that gtk2 port coming?) > =20 > Just a question, 'gnome stack' as in "you need all of gnome" or "you only need a libray (or two) that is used mainly by gnome". (I hope the later as other wise we'd endup depending on gnome (ie KDE,IceWM,etc users would have to install all of gnome to beable to use DA)). Any XML API that works and is fairly simple to use, extend (if needed) and doesn't pull too much depencies would be nice, imho. >> It makes config files >>easier to read, and if done right, you can add features into the xml >>set, that aren't reflected in the gui. Think of it as a hidden feature >>set. The tags exist in the DTD, the parser recognises them, but the >>gui would never use them. Thus you can code in "expert" options that >>might be needed, but wouldn't be available to the >>faint-of-heart/newbie user. >> >>A firewall I use, M0n0wall, has some "hidden" config options that you >>can't access through the gui. >> =20 >> Sounds good to me, maybe some of the 'hidden' options could be configured via GUI when some "expert mode" option is set, eg an extra menu item under Settings is enabled (or present at all times - eg naming it "Expert Preferences" or "Advanced Preferences" would probably scare away some of those who shouldn't be poking in them ;). >>I think templates would add a lot of functionality to DA. I would >>suggest default templates, similar to the current functionality, but >>add a preferences dialog, to allow custom templates for advanced >>configuration. Also I would like to see some color coding for required >>fields so errors would be easier to prevent. >> =20 >> Color coding also seems like an good idea, eg light green background in the fields for required and bright yellow for optional would be a good start? --=20 After all, if you are in school to study computer science, then a professor saying:=20 "use this proprietary software to learn computer science" is the same as English professor handing you a copy of Shakespeare and saying: "use this book to learn Shakespeare without opening the book itself." -- Bradley Kuhn