Last post Jun 16, 2005 06:09 PM by ikamiksok
May 26, 2005 05:44 PM|favance|LINK
I have just released the PA and Source Code for the Event-Calendar module for DNN 3.0.13. There still may be a few issues...but hopefully the wonderful folks out there that have helped will take a look and maybe help resolve the remaining issues.
I have some other great news. I have signed a Sub-Project agreement with the DNN Core Team and hope to soon have a major project, supported by the team, to further extend and better integrate the calendar into DNN. If you like the module, please let me
and the core team know. Also, we're interested in your help! I am especially looking for those that want to use the multi-language features and to make sure it runs well for them. Please let me know if you have issues or corrects that we can integrate into
the Source code....
Also, please let us know the features you would most like to see added in the future.
You can download the PA and Source @:
Thanks so much for your support,
May 26, 2005 11:32 PM|mcsenow|LINK
May 27, 2005 12:36 PM|mcsenow|LINK
Jun 16, 2005 02:34 PM|chammock|LINK
Jun 16, 2005 06:09 PM|ikamiksok|LINK
I worked a lot on AVCalendar and would love to contribute but don't have the time. But I will make some suggestions from my experience w/ the DNN2.x version.
1 - If there is a major version upgrade to the new DNN subproject, I'd recommend renaming a lot of variables and cleaning up the code. There is some code not used and some things that don't make sense like objects named calendar that actually refer to an
2- Improve the signup and event approval system. It's not very user friendly or customizable (from the DNN2.x version I used). For my implementation, My event moderation section lists all the events and has drop down combo boxes next to each where you can
choose the state of the event such as submitted, cancelled, on schedule, updated, etc.... at the bottom you click on update to update the states of all events in the list. I also think the user signup list UI should be improved w/ a nicer UI too to show all
users signed up, users who unrsvp, users who have been approved, option to have a signup list for users not approved, etc.... i wrote my own signup system very similar to evite.com.
3 - Add an event list control. Make this a control and not a module. The event list module PA thus would have only one line. It could look something like this.... <dnn:eventlist runat="server" listItems=10 displayType="Standard" cssclass="blah" eventCategory="Sports"
timespan="Upcoming Events" eventType="FeaturedEvents"/>. This way, a developer can put an event list anywhere on their site. On my site, I have about 20 different configured event lists on various pages throughout it.
4. Add a locations database. I did this and it is nice. Users can choose from an old location or create a new location. If events repeat at the same place, then you don't have to retype it every time. For my implementation, the event view contains the event
info and the user must click on the location link to get info on the location.
5 - Change default calendar view - have option for a large view versus small view. I would think that more ppl would use it in the large view format as opposed to small view. And in my opinion those who do use the small view don't realize that it looks bad.
:) Also, in the large view keep the event window boxes standard size. When weeks 1 and 2 have no events and the row is thin but week 3 has an event and the row is big, it just looks bad. Compare to other professional calendars or websites with calendars on
how they keep the calendar format looking the same would be my recommendation.
Just some of my opinions. I wish I had more time and could volunteer, but I am crazy busy overcommitted as it is. :)