<![CDATA[ [Tip] Template Chunks - My Forums]]> https://forums.modx.com/thread/?thread=19674 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109188
Thanks for the good news!]]> zombiemx Jun 29, 2006, 11:12 AM https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109188 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109187 Considering all the announcements made for 1.0 I’m arguing whether you have planned more than can be achieved within a reasonable or predictable time. This could induce a high risk for the whole project, since it can undermine the motivation of the developers as well as the confidence of the users. That’s because you’ve not seen it actually working. The core is done and now it’s time to bolt on a new manager. smiley]]> rethrash Jun 29, 2006, 10:11 AM https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109187 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109186 It’s a pity, since the optimal situation for me - and others - would be to learn (=invest time) in a universal solution.
However, I understand quite well the conditions and limitations of an open-source, unfunded development project. But you have come so far with your excellent product, would be a shame to slow down.
Considering all the announcements made for 1.0 I’m arguing whether you have planned more than can be achieved within a reasonable or predictable time. This could induce a high risk for the whole project, since it can undermine the motivation of the developers as well as the confidence of the users.
Nevertheless: I will stay tuned and spend some weekends studying your code. This is more for fun than for productivity, though. smiley]]> zombiemx Jun 29, 2006, 04:37 AM https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109186 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109185 Quote from: ppaul at Jun 28, 2006, 08:32 PM

Yehyeh: almost every second reply from the core/foundation team mentions and promises GreatThingsToCome - either with 0.9.5 (overdue!) or 1.0 surmounting all my expectations.

Be honest: I’m currently considering moving from exploring/prototyping to the real stuff. Should I try it with the current version, or does it pay to wait some weeks (up to a month or so) for TheNextBigModxThing??
To be honest myself: I do not want to get involved into backward-compatibility issues, and all the promises make me think that there will be a lot of them!

I absolutely say try it with the current version. It does not pay to wait for anything, IMO. This is still a 100% volunteer-based open-source project; I’m deploying and building sites daily with the current code, working on 1.0 as I can afford to. That means I may plan on having it done in x amount of time, but these are merely estimates and things could change at anytime. Important thing is though, unless you are planning on hacking the core or writing a lot of direct to MODx core tables functionality in your efforts, there is no reason to fear what is coming. I simply mention it so people know there are efforts underway in certain areas and so maybe they’ll contact us if they are interested in contributing or just participating in the planning/implementation of these features by joining the discussion.

There will of course almost always be migration steps when making the kind of fundamental improvements and feature additions we’re talking about, but there will be a migration guide, and my vision includes handling a good portion of backwards compat issues via optional add-ons that can parse the old tag formats and properly translate the old API calls. Only components that directly access core data tables will require migration, and I’ve already done several component migrations against my early prototypes that took a matter of minutes with the new object-oriented API and data access layer.

In addition, I don’t see the 0.9.x line being forgotten about just because 1.0 is introduced, and hope that it will continue to receive bug fixes and possibly new features even after some have chosen to move on to 1.0.]]> opengeek Jun 28, 2006, 05:49 PM https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109185 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109184 And that functionality is already part of the 1.0 effort. Yehyeh: almost every second reply from the core/foundation team mentions and promises GreatThingsToCome - either with 0.9.5 (overdue!) or 1.0 surmounting all my expectations.

Be honest: I’m currently considering moving from exploring/prototyping to the real stuff. Should I try it with the current version, or does it pay to wait some weeks (up to a month or so) for TheNextBigModxThing??
To be honest myself: I do not want to get involved into backward-compatibility issues, and all the promises make me think that there will be a lot of them!
]]> zombiemx Jun 28, 2006, 03:32 PM https://forums.modx.com/thread/19674/tip-template-chunks?page=2#dis-post-109184 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109183 Quote from: ppaul at Jun 28, 2006, 02:59 PM

Really smart!
However, with this type of multi-level templating a rendering procedure might become smarter than its inventor and changing a template might get a re-engineering task laugh

True that, but if the snippet is authored in such a way as to only set placeholders for replacing dynamic values in external templates, leaving the markup to the external template (be it a chunk or TV or whatever), the only re-engineering tasks should be trivial, and using snippets to provide conditional output is trivial as well, should you want to have the template designer have a little more control over the rendering logic (a la Smarty or any other templating solution that allows logical rendering).

Only thing missing is being able to explicitly define relationships between snippets and their dependent chunks, TV’s, etc. And that functionality is already part of the 1.0 effort. This will make possible the creation of robust manager and/or quickedit features to deal with managing these related components in a more organized manner.]]> opengeek Jun 28, 2006, 01:58 PM https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109183 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109182 However, with this type of multi-level templating a rendering procedure might become smarter than its inventor and changing a template might get a re-engineering task laugh
]]> zombiemx Jun 28, 2006, 09:59 AM https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109182 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109181
I see now. Thanks for still answering my dumb (rookie) question.

Chuck]]> chucktrukk Jun 27, 2006, 05:54 PM https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109181 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109180 Quote from: ProWebscape at Jun 27, 2006, 12:49 PM

Jason,

What is your snippet [[SnippetSetsPlaceholderValues]]. How do you set this differently than Olaf did?

Not an actual snippet; I was just reinforcing Olaf’s example with one of my own, based on a project I had been working on last summer/fall.]]> opengeek Jun 27, 2006, 08:56 AM https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109180 <![CDATA[Re: [Tip] Template Chunks]]> https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109179
Jason,

What is your snippet [[SnippetSetsPlaceholderValues]]. How do you set this differently than Olaf did?

Thanks,
Chuck]]> chucktrukk Jun 27, 2006, 07:49 AM https://forums.modx.com/thread/19674/tip-template-chunks#dis-post-109179