Hi,
I think I explained it, maybe I crossed threads.
It would be based on a wall calendar, similar to Matt Kruse's calendar script, in look and feel, but with changes to make it more Links-like or GT interface compatible. Also, to be SQL back end, template driven, etc.
From the webmaster point of view, he can set up calendars, which would be automatically perpetual. They would show the current month, or day, etc, without any interventions.
You can add dates, events and such to them. Recurring events, single events, whatever.
The idea is to allow a webmaster to post events going on. In my case, I have a rock & bead shop, and I want to post events, classes, and other things going on.
In addition, a user who has an account, can log on, and add their own personal events to the calendar. Such as birthdays, gift days, whatever. These events are ONLY seen on that users calendar.
This is not a groupware calendar, it's not a project planning or scheduling calendar, just a "Community Events" type calendar.
I'm at about 80% of it. The last 10-20% is always a killer. And then I have to make it a plugin (but since it's not a part of Links, that shouldn't be hard).
It will need a lot of template work, if people want fancy features, since I don't do javascript.
Actually, Matt's calendar program is _far_ more complex than it has to be, because he has to include database routines, a template parser, etc, all of which, and more, are built into any Links SQL installation. The date routines are built into PerlCalc (and I'm trying to allow the use of either DateCalc (if it's available) or PerlCalc since PerlCalc can be installed into your Links SQL directory if necessary (see the other thread here on date calculations). There are also a few CPAN available perl modules for doing calendar output, and I'm trying to integrate them, and make this pure-perl and as standard as I can.
The "tricks" are all done from the admin interface, and all involve Links stuff.
My templates are pretty poor, admittedly (but since this is a PUGWARE license) you'll be able to contribute back by developing better ones <G>. Actually, that is part of what a PUGWARE license is. You *MUST* contribute back any changes you make, or you are in violation of the license. That makes it a cooperative license, where EVERYONE has to contribute unless they use just the stock program, and make no significant changes to it. Since templates are 90% of the effort here, unlike most programs, there should be a wealth of templates to chose from, and the "core" set should get better with all the group effort.
Right now, I'm "stuck" on a logic flow for recurring events. My needs are odder than other calendars, and there are subtle things I have not worked out yet. Maybe I'll release a pre-beta that only has single events. That might get other people interested?
I have logic for recurring "static" events, such as "3rd tuesday of every month". I think I released a working global for that (and it works for GForum too, if you want to add a notification of conferences, meetings, etc to certain forums <G>)
What I'm looking for is what other stuff people want in a calendar. I'd like to get the database set up, and at least the back-end logic pretty set in stone before the first release, to prevent compatibility issues. You can always add fields (I *LOVE* that about passing hash-refs <G>), but the core fields need to be set, as does the driving functionality.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
I think I explained it, maybe I crossed threads.
It would be based on a wall calendar, similar to Matt Kruse's calendar script, in look and feel, but with changes to make it more Links-like or GT interface compatible. Also, to be SQL back end, template driven, etc.
From the webmaster point of view, he can set up calendars, which would be automatically perpetual. They would show the current month, or day, etc, without any interventions.
You can add dates, events and such to them. Recurring events, single events, whatever.
The idea is to allow a webmaster to post events going on. In my case, I have a rock & bead shop, and I want to post events, classes, and other things going on.
In addition, a user who has an account, can log on, and add their own personal events to the calendar. Such as birthdays, gift days, whatever. These events are ONLY seen on that users calendar.
This is not a groupware calendar, it's not a project planning or scheduling calendar, just a "Community Events" type calendar.
I'm at about 80% of it. The last 10-20% is always a killer. And then I have to make it a plugin (but since it's not a part of Links, that shouldn't be hard).
It will need a lot of template work, if people want fancy features, since I don't do javascript.
Actually, Matt's calendar program is _far_ more complex than it has to be, because he has to include database routines, a template parser, etc, all of which, and more, are built into any Links SQL installation. The date routines are built into PerlCalc (and I'm trying to allow the use of either DateCalc (if it's available) or PerlCalc since PerlCalc can be installed into your Links SQL directory if necessary (see the other thread here on date calculations). There are also a few CPAN available perl modules for doing calendar output, and I'm trying to integrate them, and make this pure-perl and as standard as I can.
The "tricks" are all done from the admin interface, and all involve Links stuff.
My templates are pretty poor, admittedly (but since this is a PUGWARE license) you'll be able to contribute back by developing better ones <G>. Actually, that is part of what a PUGWARE license is. You *MUST* contribute back any changes you make, or you are in violation of the license. That makes it a cooperative license, where EVERYONE has to contribute unless they use just the stock program, and make no significant changes to it. Since templates are 90% of the effort here, unlike most programs, there should be a wealth of templates to chose from, and the "core" set should get better with all the group effort.
Right now, I'm "stuck" on a logic flow for recurring events. My needs are odder than other calendars, and there are subtle things I have not worked out yet. Maybe I'll release a pre-beta that only has single events. That might get other people interested?
I have logic for recurring "static" events, such as "3rd tuesday of every month". I think I released a working global for that (and it works for GForum too, if you want to add a notification of conferences, meetings, etc to certain forums <G>)
What I'm looking for is what other stuff people want in a calendar. I'd like to get the database set up, and at least the back-end logic pretty set in stone before the first release, to prevent compatibility issues. You can always add fields (I *LOVE* that about passing hash-refs <G>), but the core fields need to be set, as does the driving functionality.
PUGDOG� Enterprises, Inc.
The best way to contact me is to NOT use Email.
Please leave a PM here.
