No there's no appropriate construct for this. I'm thinking I should add it,
something like this:
I was wondering if it could simply work annotating the class with spring
@Component or @Service...
Anyway, yes, any annotation is fine if does the job :-) Is there already
a jira issue?
Or have a post create callback on classes annotated with @DialogFactory.
I don't know if this would work right with the paragraph annotation.
IMHO the cleanest way should be to have an annotation at class level
(which works for paragraphs and as standalone) and an annotation at
level method for initialization (which works on templates, paragraphs
and classes annotated with the other annotation).
Can you tell me about the use case, will the number of tabs differ depending on
where the dialog is used, who the user is or something else?
"Basic" use case is simply the possibility to hide tabs depending on
user roles, just like what you can do with permissions in the usual
configuration.
Making the dialog "location-depenedent" is not a good policy, at least
from my point of view (two dialogs are not that expensive :-) ), but you
can have a dialog which is "data-dependent": after the user sets or
selects some value on the first tab, the dialog reloads and may have an
extra tab.
The latter is more or less my current use case.
Regards, Danilo.
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
