I offered to help with the documentation a couple of days ago on
radiant-docs and didn’t get a reply, maybe because no one looks at that
list. Anyhow, I’d still like to help with the docs.
Allen
On 11/10/06, Allen [email protected] wrote:
I offered to help with the documentation a couple of days ago on
radiant-docs and didn’t get a reply, maybe because no one looks at that
list. Anyhow, I’d still like to help with the docs.
Awesome!
John asked me to take an official role for documentation a couple of
weeks ago, as I’ve been putting stuff from the list into the wiki.
I’ve been busy working this month, but next month is quieter and I
hope to be productive then; the handbook is the first thing I want to
look at.
Sorry I missed the posts to the docs list,
–
Regards,
Dave
For a couple of weeks I’ve been hunting for the absolute best way to
extend Radiant to handle the presentation of an event calendar.
After much going back and forth I finally settled on implementing it
as a series of new global tags in a plugin a la: http://
radiantcms.org/blog/2006/09/14/how-to-create-global-tags-in-a-
plugin. I’ve copied my needed Event models into this plugin as well.
This has gotten me pretty far. I’ve got my <r:calendar… and child
<r:event… tag which allow me to pull any set of events and present
them in anyway I need anywhere throughout the site. Great! However I
have hit a couple of road blocks:
- I’ve created attributes to select a set of event based on a date
range, a number of days, etc. This will allow me to create separate
pages for different date time periods. However, I’d much prefer to
have a form which allow users to select the date range or categories
of events to display.
Is there a way to access form get parameters from within the
Behavior::Base.define_tags? Has anyone came-up with an elegant way to
handle this sort of thing?
- Currently I’m handling migrations on my own models by just
generating them directly in the Radiant app. I figure I’ll have to do
some migration re-numbering when a new Radiant release includes it’s
own migrations. Anybody have a better solution for handling
migrations of custom models from within a plugin or without
interfering with the Radiant installation?
*** I’m implementing this Calendar into Radiant in this hodge-podge
manner now with the educated assumption that I’ll eventually be able
to re-factor it and have it directly “plug-in” to Radiant (on the
admin tab) and that the incorporation of a custom data model will be
accomodated in some manner. Notice I didn’t ask for a custom view or
controler (yet). Am I assuming too much?
Thoughts and solutions embraced,
Loren J.
[email protected]
Hi Allen!
On 11/10/06, Allen [email protected] wrote:
I offered to help with the documentation a couple of days ago on
radiant-docs and didn’t get a reply, maybe because no one looks at that
list. Anyhow, I’d still like to help with the docs.
Awesome!
John asked me to take an official role for documentation a couple of
weeks ago, as I’ve been putting stuff from the list into the wiki.
I’ve been busy working this month, but next month is quieter and I
hope to be productive then; the handbook is the first thing I want to
look at.
Sorry I missed the posts to the docs list,
–
Regards,
Dave
While I don’t have any time to help right now, I’m very interested in
an event calendar for my own eventual use of Radiant (my car club’s
track days and such).
Having a ‘calendar view’ that can be called from this event calendar,
which has children that are the individual events, would be ideal.
Please keep the list posted on this!