From: Andreas A. <a.a...@th...> - 2001-10-01 10:07:23
|
Hi Alex, the BccModuleCompiler does work now, but only for static module output. But what about templates containing "load_ordered" output? I thought of this: <bc:module> <group>content</group> <index>0</index> </bc:module> short one: <bc:module group="content" index="0" /> Will be transformed to: $Page->output['content'][0] or for the whole group: <bc:module group="content" /> = $Page->output['content']; Andi |
From: Alex B. <en...@tu...> - 2001-10-01 16:46:58
|
> Hi Alex, > > the BccModuleCompiler does work now, but only for static module output. But > what about templates containing "load_ordered" output? Static modules won't support load order (at least initially) - the StaticModule() method in page runs the module and sends the output all in one go. I like the 'group' tag, it's a nice alias... but I don't see how we can elegantly support full load-ordered module arrays that are defined in the markup they will be presented in :) _a > I thought of this: > > <bc:module> > <group>content</group> > <index>0</index> > </bc:module> > > short one: > <bc:module group="content" index="0" /> > > Will be transformed to: $Page->output['content'][0] > > or for the whole group: > > <bc:module group="content" /> = $Page->output['content']; > > Andi > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
From: Andreas A. <a.a...@th...> - 2001-10-01 18:27:32
|
Hi Alex, Yes, mybe you misunderstood my question. I was thinking of people that want to use the load_ordered modules, define them in their page def and echo the output in the master/layout template. Of course one can do it with pure PHP "echo $Page->output[..][..]" but it would be nice to have bc:tags in the source for that. Andi >Static modules won't support load order (at least initially) - the >StaticModule() method in page runs the module and sends the output all in >one go. > >I like the 'group' tag, it's a nice alias... but I don't see how we can >elegantly support full load-ordered module arrays that are defined in the >markup they will be presented in :) > >> I thought of this: >> >> <bc:module> >> <group>content</group> >> <index>0</index> >> </bc:module> >> >> short one: >> <bc:module group="content" index="0" /> >> >> Will be transformed to: $Page->output['content'][0] >> >> or for the whole group: >> >> <bc:module group="content" /> = $Page->output['content']; >> >> Andi >> >> >> _______________________________________________ >> binarycloud-dev mailing list >> bin...@li... >> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev >> > > >_______________________________________________ >binarycloud-dev mailing list >bin...@li... >https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
From: Alex B. <en...@tu...> - 2001-10-01 19:04:44
|
ohohoho ok, yes, of course that makes sense. :) in which case what you were talking about makes perfect sense... maybe I should assume that in the future :) -a > Hi Alex, > > Yes, mybe you misunderstood my question. I was thinking of people that want > to use the load_ordered modules, define them in their page def and echo the > output in the master/layout template. Of course one can do it with pure PHP > "echo $Page->output[..][..]" but it would be nice to have bc:tags in the > source for that. > > Andi > > > >> Static modules won't support load order (at least initially) - the >> StaticModule() method in page runs the module and sends the output all in >> one go. >> >> I like the 'group' tag, it's a nice alias... but I don't see how we can >> elegantly support full load-ordered module arrays that are defined in the >> markup they will be presented in :) > >> >>> I thought of this: >>> >>> <bc:module> >>> <group>content</group> >>> <index>0</index> >>> </bc:module> >>> >>> short one: >>> <bc:module group="content" index="0" /> >>> >>> Will be transformed to: $Page->output['content'][0] >>> >>> or for the whole group: >>> >>> <bc:module group="content" /> = $Page->output['content']; >>> >>> Andi >>> >>> >>> _______________________________________________ >>> binarycloud-dev mailing list >>> bin...@li... >>> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev >>> >> >> >> _______________________________________________ >> binarycloud-dev mailing list >> bin...@li... >> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev >> > > > _______________________________________________ > binarycloud-dev mailing list > bin...@li... > https://lists.sourceforge.net/lists/listinfo/binarycloud-dev > |
From: Andreas A. <a.a...@th...> - 2001-10-02 11:30:49
|
Hi Alex, nono, don't assume everything I talk about is right - this could be catastrophic :) Andi >ohohoho > >ok, yes, of course that makes sense. > >:) > >in which case what you were talking about makes perfect sense... maybe I >should assume that in the future :) > |