Hi Jan, Thanks for all. Good way to work on the project now, with all the smaller tasks. A client has finally agreed on the setup of a new part of their site, which ties my hands this week at least. So I will not have much time this week to get some work done. I will keep my eye on the dev-list though.
Bye, Bert -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jan Haderka Sent: vrijdag 2 oktober 2009 22:15 To: Magnolia Dev-List Subject: RE: [magnolia-dev] datamodule type activation issues Hey Bert, I've committed all the changes now. I've also logged all the things that remain to be solved before this can be released ... if I have forgotten anything, feel free to add another subtask. I'll keep the parent issue open until all subtasks are solved. Please let me know which of the tasks you feel comfortable with solving and which ones you find too difficult so we can divide the work. Hopefully we get get this done more quickly then the original patch as it will affect much smaller chunks of the code. Thanks, Jan On Tue, 2009-09-29 at 10:42 +0200, Bert Leunis wrote: > - In a project we are working on now, the data only exists on the public site > since it is data that a Public User (created using the PUR module) will > maintain. Of course the web editor needs access to this data also, and to > have the correct types, trees and dialogs is then very handy. > > - Ok, to have a specific activation mechanism for types seems a good choice. > > Jan, when will you apply the patch I delivered to the code in SVN? > > The way activation is configured now seems to force the user to work with > workflow. 'Direct' activation is not possible without config changes, am I > right? > > Bye, Bert > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Jan Haderka > Sent: dinsdag 29 september 2009 9:14 > To: Magnolia Dev-List > Subject: Re: [magnolia-dev] datamodule type activation issues > > > > > > > NOT created are the dialog and the tree for this type. Option: maybe > > the dialog can be activated too, together with the type. Not sure if > > this is really necessary. If the dialog is needed at public it can be > > I've always thought that no one need to see the data maintained by the > data module on public, but since this is not the first time i hear this > question, I'm probably wrong. > > > activated manually. The creation of the tree could be moved from the > > dialoghandler to the DataModule. This way the tree is created > > I'm very tempted to say, yes, let's move it since I don't like the > dialogHandler creating the tree. > In theory, even if you adapt the tree and/or the dialog you can always > activate it, but ... if they were generated on the public as well, > rather then activated, they would exist there with different uuids which > is something i would rather avoid. Also having user to activate the > dialog and tree explicitly (even if they modified it) is not very nice. > For this reason I would think that perhaps the best solution to the > issue is to have a custom activate command for the type that would in > same go activate also the tree, the menu and the dialog for given type > so it is treated as a bundle of related things which is what it really > is. > > Jan > > > automatically when the type is activated. It is not very likely that > > the tree definition was adapted at the author side. The dialog > > definition most likely has. > > > > > > > > Your views on this matter are appreciated, as always! > > > > > > > > Best regards, Bert > > > > > > > > > > > > > > > > ______________________________________________________________________ > > ---------------------------------------------------------------- > > For list details see > > http://www.magnolia-cms.com/home/community/mailing-lists.html > > To unsubscribe, E-mail to: <[email protected]> > > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
