[MGNLSTK-435] Paragraph for easy access to data in data module (or standard model classes for it) Created: 17/Aug/09  Updated: 25/Mar/13  Resolved: 25/Mar/13

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: paragraphs
Affects Version/s: 1.1.1
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Christian Ringele Assignee: Christian Ringele
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File SimpleDataObjectProviderModel.java     File templateExample.ftl    
Issue Links:
dependency
is depended upon by MGNLSTK-436 Make inplace templating more usable Closed
relation
is related to MGNLSTK-446 More complete method collection in ST... Closed
Template:
Acceptance criteria:
Empty

 Description   

I was asked in a presentation/mini workshop of STK how all 'categorization' values could be displayed.
This session was based on pure inplace templating.

So I saw the need of users, which want to use STK in a pure inplace templating mode, for easy accessing any stored data in the data module.
They don't want to code Java, and can not look into Java Model/Util classes to see if any method would fit their need.

In this use case the only need was, for being able to render all defined categorizations.
So spoken in a more technical matter, a Model Class was missing which delivers the chosen data folder objects into a paragraph template.
If the content object is deliver to the template, the properties and iterations on the content object/collection can be done freely in the template.

I could think of a paragraph on which you choose a folder in data module, and the model class just delivers the allChildren collection.



 Comments   
Comment by Christian Ringele [ 21/Aug/09 ]

I have attached a model class, that could be used by any paragraph as its model class within STK.
I customer was needing it for a POC.
This is a example, that with a set of such model classes you could do about anything only within the freemarker template.

The other idea what would scope the same use case would be:
To provide these getters of this class in the STKUtil class.
So it could be accessed in freemarker over ${stk.methodName}.
Like this you could use still your specific modelClass and can retrieve data from data module.
The STKUtil already provides possibility of generating a linkResolving, why not make the Util more complete in madder of retrieveing basic content from data/dms?

Comment by Christian Ringele [ 25/Mar/13 ]

M5 will change this by content apps, there for obsolete.

Generated at Mon Feb 12 07:27:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.