Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Wiki Markup
\[15:56:07 CDT(-0500)\] <span style="color: black"> &lt;Bosmon&gt; At least in this case, there is a kind of semi-natural way of using IoC createOnEvent to do the scheduling, but it still means pulling the template information up out into a separate component</span>

Wiki Markup
\[15:56:38 CDT(-0500)\] <span style="color: black"> &lt;Bosmon&gt; Which as you say, isn&#039;t completely satisfactory, since, as you say, a component should really be able to control which templates it has through its own resolution</span>

Wiki Markup
\[15:56:59 CDT(-0500)\] <span style="color: black"> &lt;Bosmon&gt; on the other hand, there are at least SOME benefits to this kind of system, since it means that all the templates in a tree are held in a single place where users can configure them easily</span>

Wiki Markup
\[15:57:01 CDT(-0500)\] <span style="color: black"> &lt;Justin_o&gt; Bosmon: is it bad practice for my top level component to need to fetch a template too.. should all those things be subcomponents</span>

Wiki Markup
\[15:57:22 CDT(-0500)\] <span style="color: black"> &lt;Bosmon&gt; Justin_o - well, do look at the UIOptions templateLoader - you should be able to reuse most of it</span>

Wiki Markup
\[15:57:26 CDT(-0500)\] <span style="color: black"> &lt;Justin_o&gt; the top level one is for the bits of markup for where the other templates render into.. maybe this can just be in the standard markup though</span>