question about implementing flexible media repository
|
View:
New views
18 Messages
—
Rating Filter:
Alert me
|
 |
question about implementing flexible media repository
by olafmolilink
::
Rate this Message:
Hello, in a CMS that some of our customers use (GX Webmanager) there is something called a Media Repository. This is a very powerfull, elegant and flexible way to manage data-objects with unstructered contents. Basically it's a repository that is much alike the website repository, where you can create articles (like webpages), which can have flexible content (like paragraphs added to the pages). You then can assign "terms" to the media repository items. You can then use a Media Repository item (like a specific media repository viewer/paragraph) in your webpages, where you can filter, sort and show content from the Media Repository, mainly filtered on terms. This way you can f.e. create news-items, vacancies, etc. which can have unstructured flexible content, and show these in pages, f.e. the latest X news items etc. In Magnolia this is a littlebit like how the news-items in STK are done, but more flexible, and especially more easy to use for a end-user, as they have a specific menu-tab out of the website pages tab to manage this kind of content. What would be the best approach to create something like this in Magnolia? Create a new repository, duplicate the website management admin interface settings to have a specific author menu button to access this new repository, and modify the latest news STK module/dialogue to add terms to look for, ordering, sorting, direction, and make it only look in the new media repository? cheers, Olaf ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by olafmolilink
::
Rate this Message:
here is some info about this functionality: http://www.gxdeveloperweb.com/documentation/GX-WebManager-9.8/Connectivity-Management/GXD0031_en-GX-WebManager-9.8-Media-Repository-20081014.pdf cheers, Olaf On Wed, Jun 24, 2009 at 7:26 PM, Olaf iLink<olaf@...> wrote: > Hello, > > in a CMS that some of our customers use (GX Webmanager) there is > something called a Media Repository. This is a very powerfull, elegant > and flexible way to manage data-objects with unstructered contents. > Basically it's a repository that is much alike the website repository, > where you can create articles (like webpages), which can have flexible > content (like paragraphs added to the pages). You then can assign > "terms" to the media repository items. You can then use a Media > Repository item (like a specific media repository viewer/paragraph) in > your webpages, where you can filter, sort and show content from the > Media Repository, mainly filtered on terms. This way you can f.e. > create news-items, vacancies, etc. which can have unstructured > flexible content, and show these in pages, f.e. the latest X news > items etc. > > In Magnolia this is a littlebit like how the news-items in STK are > done, but more flexible, and especially more easy to use for a > end-user, as they have a specific menu-tab out of the website pages > tab to manage this kind of content. > > What would be the best approach to create something like this in > Magnolia? Create a new repository, duplicate the website management > admin interface settings to have a specific author menu button to > access this new repository, and modify the latest news STK > module/dialogue to add terms to look for, ordering, sorting, > direction, and make it only look in the new media repository? > > cheers, Olaf > -- Met vriendelijke groet / Kind regards, Olaf Molenveld ---------------------------------------------- Interactive Link Keizerstraat 31 3512 EA Utrecht T +31 (0)30 634 32 66 F +31 (0)30 634 32 65 www.interactivelink.nl olaf@... INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL PANEL EN PARODOS DEEL UIT VAN DE HANSNEL GROEP ---------------------------------------------- De informatie in dit e-mail bericht is uitsluitend bestemd voor de geadresseerde. Verstrekking aan en gebruik door anderen is niet toegestaan. Door de elektronische verzending van het bericht kunnen er geen rechten worden ontleend aan de informatie. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by Boris Kraft-4
::
Rate this Message:
Why not simply use the data module? Look at the address book for an example; or, for a different example, check out the references section on magnolia-cms.com, which is completely powered by the data module. - Boris On Jun 24, 2009, at 7:26 PM, Olaf iLink wrote: > > Hello, > > in a CMS that some of our customers use (GX Webmanager) there is > something called a Media Repository. This is a very powerfull, elegant > and flexible way to manage data-objects with unstructered contents. > Basically it's a repository that is much alike the website repository, > where you can create articles (like webpages), which can have flexible > content (like paragraphs added to the pages). You then can assign > "terms" to the media repository items. You can then use a Media > Repository item (like a specific media repository viewer/paragraph) in > your webpages, where you can filter, sort and show content from the > Media Repository, mainly filtered on terms. This way you can f.e. > create news-items, vacancies, etc. which can have unstructured > flexible content, and show these in pages, f.e. the latest X news > items etc. > > In Magnolia this is a littlebit like how the news-items in STK are > done, but more flexible, and especially more easy to use for a > end-user, as they have a specific menu-tab out of the website pages > tab to manage this kind of content. > > What would be the best approach to create something like this in > Magnolia? Create a new repository, duplicate the website management > admin interface settings to have a specific author menu button to > access this new repository, and modify the latest news STK > module/dialogue to add terms to look for, ordering, sorting, > direction, and make it only look in the new media repository? > > cheers, Olaf > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <user-list-unsubscribe@...> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by olafmolilink
::
Rate this Message:
Hello Boris, because the data module has a fixed structure, The power of the Media Repository in GX is that it's flexible in it's content, like Magnolia webpages with their paragraph objects. Olaf On Fri, Jun 26, 2009 at 9:08 AM, Boris Kraft<boris.kraft@...> wrote: > > Why not simply use the data module? Look at the address book for an example; > or, for a different example, check out the references section on > magnolia-cms.com, which is completely powered by the data module. > > - Boris > > > On Jun 24, 2009, at 7:26 PM, Olaf iLink wrote: > >> >> Hello, >> >> in a CMS that some of our customers use (GX Webmanager) there is >> something called a Media Repository. This is a very powerfull, elegant >> and flexible way to manage data-objects with unstructered contents. >> Basically it's a repository that is much alike the website repository, >> where you can create articles (like webpages), which can have flexible >> content (like paragraphs added to the pages). You then can assign >> "terms" to the media repository items. You can then use a Media >> Repository item (like a specific media repository viewer/paragraph) in >> your webpages, where you can filter, sort and show content from the >> Media Repository, mainly filtered on terms. This way you can f.e. >> create news-items, vacancies, etc. which can have unstructured >> flexible content, and show these in pages, f.e. the latest X news >> items etc. >> >> In Magnolia this is a littlebit like how the news-items in STK are >> done, but more flexible, and especially more easy to use for a >> end-user, as they have a specific menu-tab out of the website pages >> tab to manage this kind of content. >> >> What would be the best approach to create something like this in >> Magnolia? Create a new repository, duplicate the website management >> admin interface settings to have a specific author menu button to >> access this new repository, and modify the latest news STK >> module/dialogue to add terms to look for, ordering, sorting, >> direction, and make it only look in the new media repository? >> >> cheers, Olaf >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <user-list-unsubscribe@...> >> ---------------------------------------------------------------- > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <user-list-unsubscribe@...> > ---------------------------------------------------------------- > > > -- Met vriendelijke groet / Kind regards, Olaf Molenveld ---------------------------------------------- Interactive Link Keizerstraat 31 3512 EA Utrecht T +31 (0)30 634 32 66 F +31 (0)30 634 32 65 www.interactivelink.nl olaf@... INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL PANEL EN PARODOS DEEL UIT VAN DE HANSNEL GROEP ---------------------------------------------- De informatie in dit e-mail bericht is uitsluitend bestemd voor de geadresseerde. Verstrekking aan en gebruik door anderen is niet toegestaan. Door de elektronische verzending van het bericht kunnen er geen rechten worden ontleend aan de informatie. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by Jan Haderka-2
::
Rate this Message:
On Fri, 2009-06-26 at 10:09 +0200, Olaf iLink wrote: > Hello Boris, > > because the data module has a fixed structure, The power of the Media Hi Olaf, I don't really understand what you mean when you say "data module structure is fixed". - You can have any kind of folder structure there, - you can even have multiple different types along in the same folder structure. - If you write your own tree configuration you can have even content to be child/parent to another content of the same or even of different type ... what is it missing that you still see the structure as "fixed"? Thanks, Jan > Repository in GX is that it's flexible in it's content, like Magnolia > webpages with their paragraph objects. > > Olaf > > On Fri, Jun 26, 2009 at 9:08 AM, Boris > Kraft<boris.kraft@...> wrote: > > > > Why not simply use the data module? Look at the address book for an example; > > or, for a different example, check out the references section on > > magnolia-cms.com, which is completely powered by the data module. > > > > - Boris > > > > > > On Jun 24, 2009, at 7:26 PM, Olaf iLink wrote: > > > >> > >> Hello, > >> > >> in a CMS that some of our customers use (GX Webmanager) there is > >> something called a Media Repository. This is a very powerfull, elegant > >> and flexible way to manage data-objects with unstructered contents. > >> Basically it's a repository that is much alike the website repository, > >> where you can create articles (like webpages), which can have flexible > >> content (like paragraphs added to the pages). You then can assign > >> "terms" to the media repository items. You can then use a Media > >> Repository item (like a specific media repository viewer/paragraph) in > >> your webpages, where you can filter, sort and show content from the > >> Media Repository, mainly filtered on terms. This way you can f.e. > >> create news-items, vacancies, etc. which can have unstructured > >> flexible content, and show these in pages, f.e. the latest X news > >> items etc. > >> > >> In Magnolia this is a littlebit like how the news-items in STK are > >> done, but more flexible, and especially more easy to use for a > >> end-user, as they have a specific menu-tab out of the website pages > >> tab to manage this kind of content. > >> > >> What would be the best approach to create something like this in > >> Magnolia? Create a new repository, duplicate the website management > >> admin interface settings to have a specific author menu button to > >> access this new repository, and modify the latest news STK > >> module/dialogue to add terms to look for, ordering, sorting, > >> direction, and make it only look in the new media repository? > >> > >> cheers, Olaf > >> > >> ---------------------------------------------------------------- > >> For list details see > >> http://www.magnolia-cms.com/home/community/mailing-lists.html > >> To unsubscribe, E-mail to: <user-list-unsubscribe@...> > >> ---------------------------------------------------------------- > > > > > > ---------------------------------------------------------------- > > For list details see > > http://www.magnolia-cms.com/home/community/mailing-lists.html > > To unsubscribe, E-mail to: <user-list-unsubscribe@...> > > ---------------------------------------------------------------- > > > > > > > > > Best regards, Jan Haderka Magnolia International Ltd. Meet us at the Magnolia Conference http:/www.magnolia-cms.com/conference Magnolia® - Simple Open Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by Will Scheidegger
::
Rate this Message:
On 26.06.2009, at 10:48, Jan Haderka wrote: > - If you write your own tree configuration you can have even content > to > be child/parent to another content of the same or even of different > type I wanted to do that for a long time now but never found the time to get into it. Do you think you could give me a few pointers to get a head start? Especially what do I have to do to have the tree open different dialogs depending on the node you're double-clicking? And of course also have a node specific context menu... Thanks! -will ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by Jan Haderka-2
::
Rate this Message:
On Fri, 2009-06-26 at 11:09 +0200, Will Scheidegger wrote: > On 26.06.2009, at 10:48, Jan Haderka wrote: > > > - If you write your own tree configuration you can have even content > > to > > be child/parent to another content of the same or even of different > > type > > I wanted to do that for a long time now but never found the time to > get into it. Do you think you could give me a few pointers to get a > head start? Especially what do I have to do to have the tree open > different dialogs depending on the node you're double-clicking? And of > course also have a node specific context menu... Hey Will, I think I can do better then that. :) I've got time to start it, but not to finish it. So, if you are willing to pick it up where I left and smooth out few rough edges still left there and contribute your changes back, I'll pack all the code I have with little of description on how it works and what still needs to be done and ship it your way (most likely I'll just expose it as a branch of Data module in the sandbox). The thing is basically working. What is still open is some fiddling about recognizing when there is only single type and dialog should be open directly for new items and where the dialog selection needs to be presented because multiple types are allowed in given place. And maybe few bugs here and there. Apart from that it is pretty much finished (if my memory serves me right :D). Just since you mentioned context menu above ... I don't think you need to do anything with it, really, since it is a DialogHandler that decides whether to show single dialog or selection similar to selecting from multiple paragraphs when adding new paragraph to the page. Same way on editing the dialog to be displayed is devised from the type you are trying to edit. Jan > > Thanks! > > -will > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <user-list-unsubscribe@...> > ---------------------------------------------------------------- Best regards, Jan Haderka Magnolia International Ltd. Meet us at the Magnolia Conference http:/www.magnolia-cms.com/conference Magnolia® - Simple Open Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by olafmolilink
::
Rate this Message:
Hello Jan, f.e. with a news item, i can lots of different types of paragraphs, some news items have a video item, some only text, some a combination of both etc. With the data-module this is not something i can do, i define the dialogue for a news data-module type, with it's properties, and this is what i have to use for that type. Maybe scanning the PDF makes it a littlebit more clear. Basically it's how the STK uses news and events, only the news and events items are managed from another tree in the repository, outside the website repository, and also have a different management-menu item in the authoring environment. I guess i can explain it best by saying that is a more generic version of news/events in STK, with filtering on terms, and displaying as a paragraph type using these terms, and a seperate management interface like the data modules in the authoring environment. I hope this makes it a littlebit more clear? :) Olaf On Fri, Jun 26, 2009 at 10:48 AM, Jan Haderka<jan.haderka@...> wrote: > > On Fri, 2009-06-26 at 10:09 +0200, Olaf iLink wrote: >> Hello Boris, >> >> because the data module has a fixed structure, The power of the Media > > Hi Olaf, > I don't really understand what you mean when you say "data module > structure is fixed". > - You can have any kind of folder structure there, > - you can even have multiple different types along in the same folder > structure. > - If you write your own tree configuration you can have even content to > be child/parent to another content of the same or even of different > type > > ... what is it missing that you still see the structure as "fixed"? > > Thanks, > Jan > >> Repository in GX is that it's flexible in it's content, like Magnolia >> webpages with their paragraph objects. >> >> Olaf >> >> On Fri, Jun 26, 2009 at 9:08 AM, Boris >> Kraft<boris.kraft@...> wrote: >> > >> > Why not simply use the data module? Look at the address book for an example; >> > or, for a different example, check out the references section on >> > magnolia-cms.com, which is completely powered by the data module. >> > >> > - Boris >> > >> > >> > On Jun 24, 2009, at 7:26 PM, Olaf iLink wrote: >> > >> >> >> >> Hello, >> >> >> >> in a CMS that some of our customers use (GX Webmanager) there is >> >> something called a Media Repository. This is a very powerfull, elegant >> >> and flexible way to manage data-objects with unstructered contents. >> >> Basically it's a repository that is much alike the website repository, >> >> where you can create articles (like webpages), which can have flexible >> >> content (like paragraphs added to the pages). You then can assign >> >> "terms" to the media repository items. You can then use a Media >> >> Repository item (like a specific media repository viewer/paragraph) in >> >> your webpages, where you can filter, sort and show content from the >> >> Media Repository, mainly filtered on terms. This way you can f.e. >> >> create news-items, vacancies, etc. which can have unstructured >> >> flexible content, and show these in pages, f.e. the latest X news >> >> items etc. >> >> >> >> In Magnolia this is a littlebit like how the news-items in STK are >> >> done, but more flexible, and especially more easy to use for a >> >> end-user, as they have a specific menu-tab out of the website pages >> >> tab to manage this kind of content. >> >> >> >> What would be the best approach to create something like this in >> >> Magnolia? Create a new repository, duplicate the website management >> >> admin interface settings to have a specific author menu button to >> >> access this new repository, and modify the latest news STK >> >> module/dialogue to add terms to look for, ordering, sorting, >> >> direction, and make it only look in the new media repository? >> >> >> >> cheers, Olaf >> >> >> >> ---------------------------------------------------------------- >> >> For list details see >> >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> >> To unsubscribe, E-mail to: <user-list-unsubscribe@...> >> >> ---------------------------------------------------------------- >> > >> > >> > ---------------------------------------------------------------- >> > For list details see >> > http://www.magnolia-cms.com/home/community/mailing-lists.html >> > To unsubscribe, E-mail to: <user-list-unsubscribe@...> >> > ---------------------------------------------------------------- >> > >> > >> > >> >> >> > -- > Best regards, > > Jan Haderka > Magnolia International Ltd. > > Meet us at the Magnolia Conference > http:/www.magnolia-cms.com/conference > > Magnolia® - Simple Open Source Content Management > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <user-list-unsubscribe@...> > ---------------------------------------------------------------- > > > -- Met vriendelijke groet / Kind regards, Olaf Molenveld ---------------------------------------------- Interactive Link Keizerstraat 31 3512 EA Utrecht T +31 (0)30 634 32 66 F +31 (0)30 634 32 65 www.interactivelink.nl olaf@... INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL PANEL EN PARODOS DEEL UIT VAN DE HANSNEL GROEP ---------------------------------------------- De informatie in dit e-mail bericht is uitsluitend bestemd voor de geadresseerde. Verstrekking aan en gebruik door anderen is niet toegestaan. Door de elektronische verzending van het bericht kunnen er geen rechten worden ontleend aan de informatie. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by Will Scheidegger
::
Rate this Message:
This sounds interesting. But be aware that I've only got started with trees and tree configurations. I also wanted to create a "ConfigurableTree" which would read almost its full configuration from the config repository instead of a tree configuration class... I do believe that Magnolia could still be improved a bit in this area. So sure, shoot, and I'll give it a try. -will On 26.06.2009, at 11:55, Jan Haderka wrote: > > > On Fri, 2009-06-26 at 11:09 +0200, Will Scheidegger wrote: >> On 26.06.2009, at 10:48, Jan Haderka wrote: >> >>> - If you write your own tree configuration you can have even content >>> to >>> be child/parent to another content of the same or even of different >>> type >> >> I wanted to do that for a long time now but never found the time to >> get into it. Do you think you could give me a few pointers to get a >> head start? Especially what do I have to do to have the tree open >> different dialogs depending on the node you're double-clicking? And >> of >> course also have a node specific context menu... > > Hey Will, > I think I can do better then that. :) > I've got time to start it, but not to finish it. So, if you are > willing > to pick it up where I left and smooth out few rough edges still left > there and contribute your changes back, I'll pack all the code I have > with little of description on how it works and what still needs to be > done and ship it your way (most likely I'll just expose it as a branch > of Data module in the sandbox). > The thing is basically working. What is still open is some fiddling > about recognizing when there is only single type and dialog should be > open directly for new items and where the dialog selection needs to be > presented because multiple types are allowed in given place. And maybe > few bugs here and there. Apart from that it is pretty much finished > (if > my memory serves me right :D). > Just since you mentioned context menu above ... I don't think you need > to do anything with it, really, since it is a DialogHandler that > decides > whether to show single dialog or selection similar to selecting from > multiple paragraphs when adding new paragraph to the page. Same way on > editing the dialog to be displayed is devised from the type you are > trying to edit. > > Jan > >> >> Thanks! >> >> -will >> >> ---------------------------------------------------------------- >> For list details see >> http://www.magnolia-cms.com/home/community/mailing-lists.html >> To unsubscribe, E-mail to: <user-list-unsubscribe@...> >> ---------------------------------------------------------------- > -- > Best regards, > > Jan Haderka > Magnolia International Ltd. > > Meet us at the Magnolia Conference > http:/www.magnolia-cms.com/conference > > Magnolia® - Simple Open Source Content Management > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <user-list-unsubscribe@...> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by Will Scheidegger
::
Rate this Message:
On 26.06.2009, at 11:55, Jan Haderka wrote: > [...] most likely I'll just expose it as a branch > of Data module in the sandbox). Hi Jan I tried to find the data module project you were talking about. Is this the right location: http://svn.magnolia.info/svn/community/sandbox/ Besides not finding the module I also have a general tree question: What exactly is the idea behind splitting the tree into a tree handler and a tree configuration? Well, doing so does make sense to me, but I don't get how things are split up. After all there are quite q few configuration possibilities in the tree handler class too, for instance in AdminTreeMVCHandler you can set the paht, browseMode etc. So what goes into the handler and what into the configuration class? Thanks for some explenations. -will ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by Jan Haderka-2
::
Rate this Message:
You could not find it because it was not there. Not that I have forgotten, but I have been out of town for while and had lost of other things to deal with since. The code was originally developed against Magnolia 3.0 and I wanted to make sure that it at least somehow still works. Here's the gist of it: http://wiki.magnolia-cms.com/display/WIKI/Magnolia+Data+Module +Extensions+-+Mixed+type+hierarchies If you have any issues let me know. Jan On Sun, 2009-07-12 at 22:49 +0200, Will Scheidegger wrote: > > On 26.06.2009, at 11:55, Jan Haderka wrote: > > > [...] most likely I'll just expose it as a branch > > of Data module in the sandbox). > > Hi Jan > > I tried to find the data module project you were talking about. Is > this the right location: > > http://svn.magnolia.info/svn/community/sandbox/ > > Besides not finding the module I also have a general tree question: > > What exactly is the idea behind splitting the tree into a tree handler > and a tree configuration? Well, doing so does make sense to me, but I > don't get how things are split up. After all there are quite q few > configuration possibilities in the tree handler class too, for > instance in AdminTreeMVCHandler you can set the paht, browseMode etc. > > So what goes into the handler and what into the configuration class? > > Thanks for some explenations. > > -will > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <user-list-unsubscribe@...> > ---------------------------------------------------------------- Best regards, Jan Haderka Magnolia International Ltd. Meet us at the Magnolia Conference http:/www.magnolia-cms.com/conference Magnolia® - Simple Open Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by olafmolilink
::
Rate this Message:
Hello everybody,
to bring my original question back to the attention :) I'm still not clear how i can bring the flexibility of a page, where a user can add different types of paragraphs to the page-content, and thus creates flexible content, to the data module? Cheers, Olaf On Fri, Jun 26, 2009 at 12:04 PM, Olaf iLink <olaf@...> wrote: Hello Jan, -- Met vriendelijke groet / Kind regards, Olaf Molenveld ---------------------------------------------- Interactive Link Keizerstraat 31 3512 EA Utrecht T +31 (0)30 634 32 66 F +31 (0)30 634 32 65 www.interactivelink.nl olaf@... INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL PANEL EN PARODOS DEEL UIT VAN DE HANSNEL GROEP ---------------------------------------------- De informatie in dit e-mail bericht is uitsluitend bestemd voor de geadresseerde. Verstrekking aan en gebruik door anderen is niet toegestaan. Door de elektronische verzending van het bericht kunnen er geen rechten worden ontleend aan de informatie. |
|
|
Re: question about implementing flexible media repository
by Brent McArthur
::
Rate this Message:
Hi olaf, We have a similar situation on one of our projects using the data module. I think the key to adding the flexability you're after is to write you're own tree configuration as the email trace says below. If you just define a new type and define a dialog for that type it won't automatically let you mix or choose data when creating new items. You can manually organise the data post creation using the ice browser but to imrpove the user experience I think you need a tree configuration? Cheers Brent
---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by Jan Haderka-2
::
Rate this Message:
On Wed, 2009-07-29 at 09:13 +0200, Olaf iLink wrote: > Hello everybody, > > to bring my original question back to the attention :) Yeah, it somehow got lost in the follow up discussions, didn't it? :) > I'm still not clear how i can bring the flexibility of a page, where a > user can add different types of paragraphs to the page-content, and > thus creates flexible content, to the data module? Taking if from what you explain below ... there are multiple ways how one can approach this. The most simple is to have one "newsItem" type with controls for all possible content - text, video, audio, images. When creating (or importing) news item, user (importer) fills only the fields for which values exist. In the website then, you create your own paragraph that (same as done for news and events in STK) this paragraph executes search query over Data Module repository and retrieves only the content that contains video or text or images or whatever combination of items you desire and renders it on the page. The more complex approach is to look at the extension to the data module I recently put in the sandbox [1] that allows creation of the multiple data types in same hierarchy and their display alongside in same tree. Then you can have multiple types e.g. videoNews, textNews, etc. still to show the items from the webpages you need to have a paragraph that retrieves the items and displays them. Only this time you will always search in same subpath and limit results by the node type ... there's no much difference here ... actually the former approach would yield better response time (shorter query) in case of big amounts (tens of thousands) of items of each type. The benefit of second approach is that editor can see what is the type of the news entry without having to ever open it, but on the other hand, editor has then choose type of the entry upfront before creating it and can't change it later (e.g. you can't add video to the textNews item, if you defined video content to exist only for videoNews). Of course with the extension to the data module, you can also choose 3rd approach and have generic "news" type and for the entry of this type editor would add sub entry of "textNews" or "videoNews" or whatever. There you gain flexibility and have nice hierarchical structure and make it easy to see what each item contain too, without having to open edit dialog (just need to expand the tree). In my experience, too fine grained approach later leads to very complex hierarchies which are then also cumbersome to work with. You need to find a balance, based on the experience of potential editors, need for searching, expected amount of items and need to extend the types in the future. Still whatever you do in the data module, you need to have something upfront to expose those entries on the website. The simplest is having paragraph that fetches the data from Data Module as I explained above. Other options are writing your own filter or servlet that would do so if you think that would be for some reason more appropriate in your case. Regards, Jan > > Cheers, Olaf > > On Fri, Jun 26, 2009 at 12:04 PM, Olaf iLink <olaf@...> wrote: > Hello Jan, > > f.e. with a news item, i can lots of different types of > paragraphs, > some news items have a video item, some only text, some a > combination > of both etc. > With the data-module this is not something i can do, i define > the > dialogue for a news data-module type, with it's properties, > and this > is what i have to use for that type. > Maybe scanning the PDF makes it a littlebit more clear. > > Basically it's how the STK uses news and events, only the news > and > events items are managed from another tree in the repository, > outside > the website repository, and also have a different > management-menu item > in the authoring environment. > > I guess i can explain it best by saying that is a more generic > version > of news/events in STK, with filtering on terms, and displaying > as a > paragraph type using these terms, and a seperate management > interface > like the data modules in the authoring environment. > > I hope this makes it a littlebit more clear? :) > > Olaf > > > On Fri, Jun 26, 2009 at 10:48 AM, Jan > Haderka<jan.haderka@...> wrote: > > > > On Fri, 2009-06-26 at 10:09 +0200, Olaf iLink wrote: > >> Hello Boris, > >> > >> because the data module has a fixed structure, The power of > the Media > > > > Hi Olaf, > > I don't really understand what you mean when you say "data > module > > structure is fixed". > > - You can have any kind of folder structure there, > > - you can even have multiple different types along in the > same folder > > structure. > > - If you write your own tree configuration you can have even > content to > > be child/parent to another content of the same or even of > different > > type > > > > ... what is it missing that you still see the structure as > "fixed"? > > > > Thanks, > > Jan > > > >> Repository in GX is that it's flexible in it's content, > like Magnolia > >> webpages with their paragraph objects. > >> > >> Olaf > >> > >> On Fri, Jun 26, 2009 at 9:08 AM, Boris > >> Kraft<boris.kraft@...> wrote: > >> > > >> > Why not simply use the data module? Look at the address > book for an example; > >> > or, for a different example, check out the references > section on > >> > magnolia-cms.com, which is completely powered by the data > module. > >> > > >> > - Boris > >> > > >> > > >> > On Jun 24, 2009, at 7:26 PM, Olaf iLink wrote: > >> > > >> >> > >> >> Hello, > >> >> > >> >> in a CMS that some of our customers use (GX Webmanager) > there is > >> >> something called a Media Repository. This is a very > powerfull, elegant > >> >> and flexible way to manage data-objects with > unstructered contents. > >> >> Basically it's a repository that is much alike the > website repository, > >> >> where you can create articles (like webpages), which can > have flexible > >> >> content (like paragraphs added to the pages). You then > can assign > >> >> "terms" to the media repository items. You can then use > a Media > >> >> Repository item (like a specific media repository > viewer/paragraph) in > >> >> your webpages, where you can filter, sort and show > content from the > >> >> Media Repository, mainly filtered on terms. This way you > can f.e. > >> >> create news-items, vacancies, etc. which can have > unstructured > >> >> flexible content, and show these in pages, f.e. the > latest X news > >> >> items etc. > >> >> > >> >> In Magnolia this is a littlebit like how the news-items > in STK are > >> >> done, but more flexible, and especially more easy to use > for a > >> >> end-user, as they have a specific menu-tab out of the > website pages > >> >> tab to manage this kind of content. > >> >> > >> >> What would be the best approach to create something like > this in > >> >> Magnolia? Create a new repository, duplicate the website > management > >> >> admin interface settings to have a specific author menu > button to > >> >> access this new repository, and modify the latest news > STK > >> >> module/dialogue to add terms to look for, ordering, > sorting, > >> >> direction, and make it only look in the new media > repository? > >> >> > >> >> cheers, Olaf > >> >> > >> >> > ---------------------------------------------------------------- > >> >> For list details see > >> >> > http://www.magnolia-cms.com/home/community/mailing-lists.html > >> >> To unsubscribe, E-mail to: > <user-list-unsubscribe@...> > >> >> > ---------------------------------------------------------------- > >> > > >> > > >> > > ---------------------------------------------------------------- > >> > For list details see > >> > > http://www.magnolia-cms.com/home/community/mailing-lists.html > >> > To unsubscribe, E-mail to: > <user-list-unsubscribe@...> > >> > > ---------------------------------------------------------------- > >> > > >> > > >> > > >> > >> > >> > > -- > > Best regards, > > > > Jan Haderka > > Magnolia International Ltd. > > > > Meet us at the Magnolia Conference > > http:/www.magnolia-cms.com/conference > > > > Magnolia® - Simple Open Source Content Management > > > > > > > ---------------------------------------------------------------- > > For list details see > > > http://www.magnolia-cms.com/home/community/mailing-lists.html > > To unsubscribe, E-mail to: > <user-list-unsubscribe@...> > > > ---------------------------------------------------------------- > > > > > > > > > > > > -- > > Met vriendelijke groet / Kind regards, > > Olaf Molenveld > ---------------------------------------------- > Interactive Link > Keizerstraat 31 > 3512 EA Utrecht > T +31 (0)30 634 32 66 > F +31 (0)30 634 32 65 > www.interactivelink.nl > olaf@... > > INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL > PANEL > EN PARODOS DEEL UIT VAN DE HANSNEL GROEP > ---------------------------------------------- > De informatie in dit e-mail bericht is uitsluitend bestemd > voor de > geadresseerde. > Verstrekking aan en gebruik door anderen is niet toegestaan. > Door de elektronische verzending van het bericht kunnen er > geen > rechten worden ontleend aan de informatie. > > > > > -- > > Met vriendelijke groet / Kind regards, > > Olaf Molenveld > ---------------------------------------------- > Interactive Link > Keizerstraat 31 > 3512 EA Utrecht > T +31 (0)30 634 32 66 > F +31 (0)30 634 32 65 > www.interactivelink.nl > olaf@... > > INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL PANEL > EN PARODOS DEEL UIT VAN DE HANSNEL GROEP > ---------------------------------------------- > De informatie in dit e-mail bericht is uitsluitend bestemd voor de > geadresseerde. > Verstrekking aan en gebruik door anderen is niet toegestaan. > Door de elektronische verzending van het bericht kunnen er geen > rechten worden ontleend aan de informatie. Best regards, Jan Haderka Magnolia International Ltd. Meet us at the Magnolia Conference http:/www.magnolia-cms.com/conference Magnolia® - Simple Open Source Content Management ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by olafmolilink
::
Rate this Message:
Hello Brent,
thanks for your reply. This flexible tree configuration for the data module is still not the way we envision this, and the way it's nicely implemented in GX. The thing is that we basically would like to see a page for the content-area, where the user can add and mix all the paragraph types that are available. This is not really the same as mixing different kinds of data module types. Olaf On Wed, Jul 29, 2009 at 3:36 PM, Brent McArthur <Brent.McArthur@...> wrote:
-- Met vriendelijke groet / Kind regards, Olaf Molenveld ---------------------------------------------- Interactive Link Keizerstraat 31 3512 EA Utrecht T +31 (0)30 634 32 66 F +31 (0)30 634 32 65 www.interactivelink.nl olaf@... INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL PANEL EN PARODOS DEEL UIT VAN DE HANSNEL GROEP ---------------------------------------------- De informatie in dit e-mail bericht is uitsluitend bestemd voor de geadresseerde. Verstrekking aan en gebruik door anderen is niet toegestaan. Door de elektronische verzending van het bericht kunnen er geen rechten worden ontleend aan de informatie. |
|
|
Re: question about implementing flexible media repository
by olafmolilink
::
Rate this Message:
Hello Jan,
thanks for your thoughts on this! I agree about the added complexity of a to granular control. Thats why i love the way it's implemented in GX Webmanager so much, basically when you create a new item in the mediarepository you create a new webpage, where you can add the content-paragraphs and re-order them just like you do with a regular webpage, only the pages in the mediarepository aren't displayed in the website and have a different management module where you can easily filter, browse and page through all the items. Is there a way to "frame" the front-end inline editor into the manager back-end interface to create new pages? Olaf On Wed, Jul 29, 2009 at 4:31 PM, Jan Haderka <jan.haderka@...> wrote:
-- Met vriendelijke groet / Kind regards, Olaf Molenveld ---------------------------------------------- Interactive Link Keizerstraat 31 3512 EA Utrecht T +31 (0)30 634 32 66 F +31 (0)30 634 32 65 www.interactivelink.nl olaf@... INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL PANEL EN PARODOS DEEL UIT VAN DE HANSNEL GROEP ---------------------------------------------- De informatie in dit e-mail bericht is uitsluitend bestemd voor de geadresseerde. Verstrekking aan en gebruik door anderen is niet toegestaan. Door de elektronische verzending van het bericht kunnen er geen rechten worden ontleend aan de informatie. |
|
|
Re: question about implementing flexible media repository
by Jan Haderka-2
::
Rate this Message:
On Wed, 2009-07-29 at 17:49 +0200, Olaf iLink wrote: > Hello Jan, > > thanks for your thoughts on this! I agree about the added complexity > of a to granular control. Thats why i love the way it's implemented in > GX Webmanager so much, basically when you create a new item in the > mediarepository you create a new webpage, where you can add the > content-paragraphs and re-order them just like you do with a regular > webpage, only the pages in the mediarepository aren't displayed in the > website and have a different management module where you can easily > filter, browse and page through all the items. > Is there a way to "frame" the front-end inline editor into the manager > back-end interface to create new pages? Hmm, I probably got your last sentence completely wrong ... do you mean FCK Editor by "front-end inline editor"? And how would adding ability to create new page to it solve your problem? When I wrote my original answer I assumed (and maybe that was wrong), that you first create the news items and only then you organize them in the pages. Or better that there are two different people doing the job. First job is someone I call web-editor (for the sake of the discussion), who organizes web content, create news page and defines where and what kind of the news entries will be displayed on this page. The second person is a news-editor who will be adding news entries independently of how/when/if those entries are being displayed on the web or not. The second person would be most likely (at least partially) replaces by periodically running ImportHandler fetching the news from other servers or from agencies providing such info in real news example. Anyway, reading what you wrote above, I have the feeling that you work this the other way around ... you prefer to create a webpage and paragraphs on this page as a news items, but want those to be stored in the data module as entries of special type ... is that correct? If so, this is also possible. all you have to do is write a custom SaveHandler for the paragraph, that would create new entry of given type in the Data Module repository and in the paragraph node itself store only location to the data entry ... honestly though, at this point i have problems to see any benefits in such an approach, except for ability to browse such entries later without having to go through the website tree ... maybe that's all you are after :) Cheers, Jan ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <user-list-unsubscribe@...> ---------------------------------------------------------------- |
|
|
Re: question about implementing flexible media repository
by olafmolilink
::
Rate this Message:
argh! I feel frustrated not being able to explain it good enough .... :)
I guess the best explanation is to be found in the media repository PDF manual of GX: http://www.gxdeveloperweb.com/documentation/GX-WebManager-9.8/Connectivity-Management/GXD0031_en-GX-WebManager-9.8-Media-Repository-20081014.pdf The process works like this: - you switch to the media repository tab, just like the data module tab - there you can create, filter, browse, page through all the items in the repository, this is a flat overview, no nested structures or whatever, just one big list - you create a new media repository item, which basically is the same as a regular GX webpage-type. The powerfull thing of a GX webpage type, just as wih magnolia's templates, that you are not forced into a fixed template of fields, but can add all the types of paragraphs, in the order you like, into the page, ie unstructured or composite content. - you assign some terms/categories to this item and now you can use them through a special component (= magnolia paragraph) where you can filter on terms/categories, order stuff, limit it, etc. (like Plone collections criteria) The powerfull thing here, and some of our customers have really big websites that are filled for 90% with media repository content, is that you don't need to define templates for all the content that is or will be available, it's up to the editors to mix and match the content-items (= paragraphs) in the way they see fit. If you look at it real simple, it's just like another main website tree that is not accessable from a browser, but only from a manager, with a more advanced interface for searching and filtering. The content is only 1 level deep, no structuring there, but the editing and creating of the content is done like a normal webpage, with 1 template type. Olaf On Thu, Jul 30, 2009 at 8:19 AM, Jan Haderka <jan.haderka@...> wrote:
-- Met vriendelijke groet / Kind regards, Olaf Molenveld ---------------------------------------------- Interactive Link Keizerstraat 31 3512 EA Utrecht T +31 (0)30 634 32 66 F +31 (0)30 634 32 65 www.interactivelink.nl olaf@... INTERACTIVE LINK MAAKT SAMEN MET HANSNEL COMMUNICATIE, CHANNEL PANEL EN PARODOS DEEL UIT VAN DE HANSNEL GROEP ---------------------------------------------- De informatie in dit e-mail bericht is uitsluitend bestemd voor de geadresseerde. Verstrekking aan en gebruik door anderen is niet toegestaan. Door de elektronische verzending van het bericht kunnen er geen rechten worden ontleend aan de informatie. |
| Free embeddable forum powered by Nabble | Forum Help |
