CharlesMx
Add option for normal resources!
Altough custom table for events display is nice, and suits the needs, i would really like to conect my normal modx resources into mxCalendar. Why isnt that possible? Maybe if you could add the swtich , where you could set to either use custom table or use default modResource?
Not sure I understand what exactly your trying to achieve, mxCalendar is not intended to replace resources however one feature item on the roadmap is to hook it up to pull in values from an assigned resource id. In the Evo version you can pulling resource items values for title,name,alias,TVs, etc. but that functionality has not been added at this time to Revo.
The thing i want is , at the moment mxcalendar has custom table for events.. but i am using normal modx resources already for my latest events display. So i have to add event again if i want to connect it with calendar. I would wish for option that i can use my normal modx resources to connect them with mxCalendar instead of creating new ones in custom table.
Just to clarify then, the ability to create resources and then associate an event (mxCalendar) to that resource so that the event can display content of the resource, correct?
yes , or just an option to choose wheter you just want existing modx resources connected to mxCalendar or use custom resources from mxCalendar custom table.
Example i already got 200 resources in news container in modx,they all got TV's for date\etc. now i for them to display on mxCalendar i would have to recreat all 200 resources manually into mxCalendar.. with this option i cold just switch and the mxCalendar would pull my normal resources!
Hope its more clear now!
Yes that is more clear, also brings up a good point to potentially support a migration from Resources to events, thus cleaning up the document tree.
Cheers
Major concern here is the TV's from the resource... thinking this one through maybe a different way to call mxcalendar with a "resource" ID of the parent of all resources that you'd like to use display, thus giving the same UI and switches but using resources vs. the actual mxcalendar database. This would provide a single input either way, no duplication and allow more flexibility in how you want to use mxCalendar.....
thoughts ??
My suggestion:
- &ids ( comma seperated list of id's of resources that want to be included)
- &parents (comma separated list of parents to look in(
- &excludeids ( comma seperated list of excluded resource id's)
Something like this would be perfect!
CharlesMX, are you thinking that this would this work as if 'attaching' an mxCalendar group of tv's to your own custom event template that would allow entering all mxCalendar info along with any resource? I had previously been thinking it would be great if the events worked this way... but I have not thought through if there would be any issues from doing so.
still pondering the best case on this; being the most flexible - I still view mxCalendar as an independent item outside of resources, so to me it's providing the ability to merge existing resources into mxCalendar
then on the other hand a few TV's that would allow you to tie a resource to any event would be nice, might have to do both
The crucial point is to retain flexibility - so that you can edit the event details either using the modx component itself (accessing via components menu), or from the resource it is associated with. Perhaps a plugin could determine if the resource had an event associated with it, and add a tab containing the event details, which would also allow editing. This would mean that any new event would have to be created first, and connected to a resource, before you could then edit the event details via the resource.
Imo , you could have both options available and make a parameter to disable one or another. Something like
&useNormal= 1/0 , if option is 1 then enable $id and $parent option to connect any resources in a given parent or by given id..
If one doesent want to use normal resources..then just put that on 0 and use mxCalendar as it is. Imo isn't that the most convinient solution?
Regards, Yuka.