On Fri, 2004-01-23 at 19:03, Benoit des Ligneris wrote: > I think we should move this discussion to the devel list so that > everyone can contribute ?
This is posted to oscar-devel. > I have installed the 'gaim' and the 'gnomemeeting' in my home here, > and you can find me under the '[EMAIL PROTECTED]' login (MSN). Until now, I > don't know how to use the gnomemeeting (we should enter the adress of the > machine that we want to talk to?), but it's configured and operacional. Most oscar developers seem to use yahoo messenger. Yahoo has nice clients for woth windows and linux. You probably should get a yahoo id and start using YM. As far as my opinion on an oscar CLI: In general, certain things should end up going through various CLI based programs. However, some things will just be done by the logic in the GUI. CLI based programs cannot do some of the things that a GUI can do. I also think that it's premature to define a CLI specification now. The CLI should be defined as we define the future of oscar through the changes we are all in the process of making now. We should be defining the CLI in portions, as we program parts of it. For instance, the nest package I am writing does not fit into the definitions I have seen so far. CLI type functions that only involve changing the database do not need any CLI, they can use either the ODA command or the ODA perl modules with the exact same command semantics, through the use of ODA shortcuts. The ODA shortcuts define the "CLI" in that case. They are defined as I or other package authors create them. CLI type functions that have to do other things than just read/write the database will use various commands that are part of oscar packages or are commands in the oscar "glue code". For example, the various things that the nest package does use the nest commands and command options as their CLI. The individual package or command authors will determine their portion of the oscar CLI, as they should since they are writing that portion of oscar. This is not something that should or can be effectively pre-determined as a collective design committee. As an author of various packages within oscar, I greatly value other developer's input on my packages, but ultimately I have and will continue to decide exactly what the commands and command options look like, and therefore I end up making all of the decisions on that portion of the oscar "CLI". I, and I suspect other oscar developers, don't generally code to someone else's design/description. I determine what my package/command needs to do, and using input from a subset of the oscar developers that are involved in my current work, decide how to implement my package/command. A few other points. ODA can use whatever database it wants, ODA hides details of the database. However, mysql is a widely accepted unix database, and switching to something else would require additional code in ODA. There is currently code in ODA just to handle different versions of mysql that have very different capabilities, adding support for another type of database would require more code still. Changing the ODA password before the oscar database is initialized requires simply writing the desired password to /etc/odapw, as the simple GUI tool does now. Changing it after the oscar database is initialized required some mysql commands to be executed. If people really want that capability, I can split out the code into another ODA command/module function to do that, but it seems like there are better ways to spend my time now. Package configuration is changing greatly, and in most cases will simply require using the proper ODA shortcuts to modify/read the configurations. -- Neil Gorsuch <[EMAIL PROTECTED]> NCSA ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
