Douglas wrote:
> On Mon, Jun 14, 2010 at 11:35 AM, Mossman, Paul (Paul)
> <[email protected]> wrote:
> > My suggestion is this. Let's not put any effort into build
> building framework capabilities and/or specific phone xslt
> files in order to have velocity files iterate over the
> elements of the UI layout.
>
> can you explain what you mean here a little more.
It's possibly a non-issue, but I'll clarify anyway.
The phone.xml and line.xml structure define the page, section, and setting UI
layout for plug-ins.
The new simplified plug-ins will use a generalized mechanism, as we've been
discussing. Generalized and vendor-specific settings will be mashed together
as follows (pardon the ASCII art):
general.xml --\
-- via general.xslt OR <vendor>.xslt --> (vendor) phone.xml
<vendor>.xml --/
In existing plug-ins, the UI layout largely mirrors the configuration file
structure. The velocity templates exploit this inherent mapping, by looping
over the settings in sections (and sometimes sections in pages) during
generation.
In order to deliver a refined UI layout, the simplified plug-ins will not be
required to mirror the configuration file structure. The velocity templates
can easily maintain the mapping between the configuration file and the
phone.xml/line.xml settings. i.e. No more looping through sections and pages.
We _could_ developing a mashing capability that allows the mapping to be
maintained in <vendor>.xslt, and then encoded in the generated
phone.xml/line.xml, so that the velocity templates can exploit it with looping.
I'm suggesting that we _not_ waste any effort developing such a capability. It
will be less work and far simpler to just maintain the mapping in the velocity
templates.
Does that make sense?
-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/
