On 03.10.2005, at 00:01, Alexandru Popescu wrote:
...
Usually a good naming will ease the adoption of a product. A dialog is
something that doesn't really describe what those nodes are meant to.
New users will be puzzled by this name - as I was too. The existing
users, being experienced will be able to immediately adapt and most
probably will agree if the names are fitting better their scope.
Concluding, this is only a proposal and I guess it may make sense at
least to some of the newbies and future users. Surely, the core
developers are the ones to decide if it is gonna be done or not ;-).
Alex,
when I first wrote the Quickstart, the connection between templates,
dialogs and paragraphs was most confusing to me and I hope that its
somewhat made clear how things connect in the current release, that was
reworked by Giancarlo.
Dialog: if you find a better name, please share it. I completely agree
that names are *very* important to undetsand what is being talked
about. In the context of this discussion, Dialog is really what the
user sees, and I think its not too bad to name it like that. Of course,
one can argue that the dialog is only a rendition of a declaration; we
can render other things out of the "dialog" definition.
Anyways, I hope that one day someone has the time to write an interface
to administer dialog/paragraph/template structures more easily. After
all, adminCentral config tree is only a beginning and a catch-all. We
have an interface for user-management, too, so why not for templating
definitions.
Regards
Boris Kraft
---------------------------
Magnolia Content Management
http://www.magnolia.info/
---------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
