>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?
>
The matching criteria inside each template is defined as:
Server : 1/0 (Is this template used for SyncML server or client)
Name: comma separated list of strings using this template (eg. Funambol, google
or Nokia_7210c, Nokia_7210).
Description: A URL for SyncML service provider, a descriptive string for
devices (not used for matching, just ease the implementation of GetConfigs).
What we can expect from a phone is its Manufacture and Model name (either
guessing via Bluetooth SDP/SyncML DevInfo or asking the input from user).
The directory is like this:
templates
|-- README
|-- client
| |-- Funambol
| | |-- config.ini
| | `-- sources
| | |-- addressbook
| | | `-- config.ini
| | |-- calendar
| | | `-- config.ini
| | |-- memo
| | | `-- config.ini
| | `-- todo
| | `-- config.ini
| |-- ScheduleWorld
| | |-- config.ini
| | `-- sources
| | |-- addressbook
| | | `-- config.ini
| | |-- calendar
| | | `-- config.ini
| | |-- memo
| | | `-- config.ini
| | `-- todo
| | `-- config.ini
| |-- SyncEvolution
| `-- default
| `-- .internal.ini
`-- server
|-- default
`-- phone
|-- default
`-- nokia
|-- S40
| |-- 7210c
| `-- default
|-- S60
| `-- default
`-- default
--
Best Regards,
Congwu
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
