[Architecture] Combining complex panels in the preferences framework
amilchev at asteasolutions.com
Mon Sep 2 12:32:17 UTC 2013
Thank you for the reply, but I'm afraid you got me wrong. Perhaps I should
explain myself better.
My ambition is to break a bigger panel so that each piece has its own
The question is relevant to the grade merging, discussed previously in this
thread. I've been working on the Speak Text adjuster group and I tried to
panels into this<https://gist.github.com/radmanovi4/6410696#file-example-js-L35-L43>
one, as Justin suggested. The important part of the auxSchema is that both
adjusters' panels' type is the big panel
, wordEcho <https://gist.github.com/radmanovi4/6410711#file-example2-js-L22>)
and all this<https://gist.github.com/radmanovi4/6410711#file-example2-js-L13-L15>
is overwritten by the last
so these <https://gist.github.com/radmanovi4/6410696#file-example-js-L8-L11>
are looked for in
instead of the appropriate
Is there an elegant way to work around this?
On Fri, Aug 30, 2013 at 10:27 PM, Cheetham, Anastasia <acheetham at ocadu.ca>wrote:
> On 2013-08-30, at 9:43 AM, Alexander Milchev wrote:
> > Hi everyone,
> > I tried out the grade merging today and a question popped up.
> > It seemed to me that no more than one html template could be shared
> between multiple users of the same panel. This would be the template of the
> adjuster, defined last in the auxSchema. For instance (in Justin's
> example), if the auxSchema relates the big panel
> "fluid.uiOptions.panels.linksControls" to both emphasizeLinks and
> imputsLarger adjusters and imputsLarger is defined second, then info for
> template, container and message for emphasizeLinks is neglected and
> overwritten by those of imputsLarger.
> > Does this mean that all templates must be stuffed in one big html file
> (hope it doesn't) and how can the templates be apportioned properly?
> > Thanks,
> > Alexander
> Hi, Alexander,
> It's possible I'm not quite understanding your question, and if so, please
> forgive me. But it is certainly possible for each panel to have its own
> The auxiliary schema for the starter panels shows how this is done:
> The root part of the schema defines the template that will contain all of
> the panels:
> This template contains an empty div for each panel.
> The root part of the schema also defines a root directory for the
> individual panels:
> Each of the panel blocks specifies its own template relative to the root
> (It isn't necessary to use the root directory prefix, that's just
> something you can use if it's helpful.)
> Alexander, does this answer your question, or am I confused?
> Anastasia Cheetham Inclusive Design Research Centre
> acheetham at ocadu.ca Inclusive Design Institute
> OCAD University
*The information in this e-mail and any accompanying files is intended only
for the recipients named above. This message may contain CONFIDENTIAL
INFORMATION THAT IS LEGALLY PRIVILEGED. If you are not an intended
recipient, you may not download, copy, disseminate, distribute or use in
any way the information in this e-mail. Any of these actions can be a
criminal offense. If you have received this e-mail in error, please notify Astea
Solutions AD immediately by reply e-mail, and delete this e-mail and any
copies of it.*
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fluid-work