Chen, Congwu wrote:
Patrick wrote:
I suggest we organize our templates around manufacturer, class of
device (S40, S60, ...), and specific model:
Nokia/ default/ S40/ default/ 7120c/
This is just for organizing the files in a more user-friendly way.
The directory hierarchy itself has no meaning for our code. The
matching criteria (vendor, class, model) should better be encoded
in a more machine-readable format inside each directory.
Nokia/default/ config.ini - main config template file
internal.ini - matching criteria, only (?) used by code which
searches for a template sources/ - sub-directory with source
part of template
How to define and the matching criteria is the key problem that we
need to discuss - is that moved into the front-ends?
Do you mean each configuration template have a 'internal.ini' to
identify it's
matching criteria? Maybe better to record them as a global index
file? The templates is
intended
to be read only, so a index file looks more reasonable. It may looks
like this:
index.ini server: templates/server/default client:
templates/client/default SyncEvolution :
templates/client/SyncEvolution/default Phone:
templates/client/phone/default Nokia:
templates/client/phone/nokia/default
The front end will let the user input as much as possible (phone? OS
? Model?) and try to return a most matched configuration template.
Some UI comments:
I assume it will be possible to query the template hierarchy and the
selection/matching is done in client?
The system should scale to fair number of templates: It should be
possible to add "empty" templates, so we can show e.g. "Nokia N85" if it
is a tested device even if it actually just uses "default Nokia S60".
From a user POV the "device class" might or might not be useful: As an
example, most Nokia users probably don't know the difference between S60
and S40 and it is not really advertized on the phone. This doesn't mean
it's not useful in the implementation, just mentioning that it might not
be shown on UI.
- Jussi
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
