George wrote: > What I am thinking of is a single XSLT to be applied for all > phones by merging a general.xml file (defined per Phone > Group) with specific phone settings (so an acme phone > settings will be generated at build time by merging > general.xml and acme-model.xml). > Acme plugin developer will not have to modify the xslt nor to > write complicated ant tasks. I've attached a simple sample > for reference - unpack the archive and run ant generate task > - you will get phone1.xml and phone2.xml generated > representing final phone settings.
Looks great! And the phone-group.xml could show up as the "General" model under the Phone Groups setting, right? And the values you set under "General" would be carried into the corresponding settings of all phone models whose plug-ins use general.xml? Could acme-model.xml use some but not all of the settings in general.xml? i.e. Apply "hidden" to some settings, so they don't appear? The example I'm thinking about is a soft client, which has a lot of common SIP phone functionality, but wouldn't have Network Settings such as VLAD ID. -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
