Hi Christian,
for example Day Communiqué has something like this. They call it Designer.
Maybe it is a good idea to implement a Magnolia version. The idea is:
- define so-called design atoms just like you define content atoms and
use both
in your template/paragraph code. For example define a design atom holding the
column names of your table paragraph
- Access to the design atoms (your table columns) in your code could be like
-- Design design = MgnlContext.getDesign(...);
-- String columns = design.getAtom("columns");
- if you click "Edit" you get the dialog to edit the content atoms, typically
done by an editor
- if you change to "Design" mode and click "Edit" you get the dialog for the
design atoms. The table columns could be entries in a textfield
- The design is stored in the repository as a page
- You can connect a design to each content page
- the designs are inherited so typically if you have multiple sites running on
your instance you would have designs for each site and define the design only
in the root page of each site.
This is just the idea how it could work. In my opinion it is very powerful,
especially if we think about sharing configurable templates and paragraphs.
But of course we need a "Magnolia-version" of this which will be much smarter
than the Communiqué version ;-)
Ralf
Hi everyone,
I wondered if it was a good idea to create the dialog-configuration, which
is usually visually edited by some site-administrator via the admin-central,
programmatically, meaning within Java.
What I need is the following: A User defines in a list in the admin-view
some properties (e.g. what columns a table should have).
Then he gets a table with a nested new-bar (for each new row in the table).
When he presses the new(edit)-button, a Magnolia-Dialog should appear with
all the (column) values he previously added in the list as an individual
HTML-Input-Field.
(As if he just created this dialog himself via the Admin-Central-GUI)
E.g.: The List Provided (Textarea):
A
B
..
Becomes in the second (row) dialog:
A: [Textbox]
B: [Textbox]
...
Has anyone experience with something like this and if so would this be
possible without severely changing the info.magnolia.cms.gui.control.Save
class?
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
