gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnumed-devel] About new login dialog task


From: Carlos Moro
Subject: [Gnumed-devel] About new login dialog task
Date: Fri, 12 Mar 2004 18:55:46 +0100
User-agent: KMail/1.6

Hi,

If you agree, i'll be glad to begin to work in the proposed login dialog. 
Please, excuse if at the moment i need some time to implement (my first cups 
of python  ;)  ):

> --------------------------------------
> Server profile   : ___________ | edit
> Password         : ___________
> workplace profile: ___________ | edit
>
>          Login         Cancel
> --------------------------------------

Just  a few doubts to have a precise idea of the task:
1. By clicking 'edit' in 'Server profile', the user would configure (similar 
to current 'options' dialog):
   Server profile name or identifier (listed in the 'server profile' combo)
   Database name
   Host
   Port
   Backend options
2. By clicking 'edit' in 'Workplace profile', the user would configure:
   Workplace profile name or identifier (listed in the 'workplace profile' 
combo)
   Help desk gnumed.conf parameter (contact data). What does this field 
exactly indicate or is used for?
   

> Yes. Pre-connection values are stored in ~/.gnumed/gnumed.conf

Current gnumed.conf file is structured in different sections (eg. hosts), 
containing a list of possible values that are displayed in the combo. If we 
create different 'section profiles',  i suppose it must reflect the new 
structure... so for example a concrete host  is associated to a profile 
(including port, db name,ect..)  rather than a list of possible hosts (as 
now). What could be the best approach to accomplish it?

   a) XML for configuration: it should be efficient and easy to mantain a XML 
based gnumed.conf.xml file. We could user pyxml ( http://
pyxml.sourceforge.net ):
              <serverProfile>
                        <dbName>
                        <host>
                        <port>
              <serverProfile>
               ...another server profiles....
               ...and so with <workspaces>...

   b) adapt current plain text based gnumed.conf file (Not sure how, ideas 
needed ;) ).:
              [backend]
              hosts = $hosts$
              anubis.homeunix.com , localprofile
              localhost , localprofile
              $hosts$

              server_profiles = $server_profiles$
              local_profile
              $server_profiles$

   c) other ideas...

Best regards

Carlos





reply via email to

[Prev in Thread] Current Thread [Next in Thread]