webMyCal

The latest sources can be found @ http://sourceforge.net/projects/webmycal/
The latest documentation is located @ http://webmycal.sourceforge.net/documentation/

Currently webmycal.pl accepts data from stdin and generates an html calendar. Internally it fills an array AoH with references to hashes of the events.

While I was doing listevents() I tought that i will not need to calculate the reocurrance of the events for the monthly view. I was wrong. It turns out that I do need the reocurrance in all cases. So the next thing in the todo list is to parce the RRULE line in each event (if any) and use the informatin to build the events. I thing this is the last big milestone. Once reocurrance is implemented it will alow for generation of the different views of the calendar.
Stay tooned

OK, the problem was the following:
in the whie loop, at the end of each event, when a hash is pushed into the array, it is done by reference. At the end of the loop we have n references in the array, where n is the number of the events. The problem is that all n references point to the same place in memory because the hash is not reallocate on every iteration.
To solve the problem a deepcopy function was implemented. Now, insted of pushing a reference of the hash into the array, we send that reference to the function, it is deep copied (by values) into a new hash, and the new address is pushed into the array. At the end we have n different addresses in the array, which was the whole point of the game.

Hi everyone,
Current status of webMyCal:
We have implemented monthly() which generates a month of the calendar and calls listevents() for every day.
During listevents() implementation, a logical bug was found in @AoH (array of hashes) which holds the events, so currently we are working on that.
Soon we will have listevents() working and this will complete monthly().

Next step will be to get daily and weekly done.

here is the latest status presentation:
files/webMyCal_Presentation3.pdf in pdf format and
files/webMyCal_Presentation3.tar.gz in tar.gz keynote format.

CSS Demo

http://www.w3schools.com/css/demo_default.htm
Our CSS Styles

“day” -> class for table in daily view

“dailybody” -> class for in daily view

“week” -> class for table in weekly view

“weeklybody” -> class for in weekly view

“weeklyeven” -> class for event in weekly view

“month” -> class for table in montly view

“monthlybody” -> class for in montly view

While going trough the documentation on SF.net I noticed they now have mysql pre-approved. So I decided to move the blog over to sf.net.

The new URL is :http://webmycal.sourceforge.net

Thanks SF

There is a difference between ability to do something and the need to do something. Everyone should be capable of understanding of why records need to be kept.
Pros on Keeping Detailed Written Records

Written records are a way of having people who no longer exist to provide information. It also allows replication, it allows you have the same project be done by someone else and get done again. Ex. Good open source kits have step by step instructions. This allows people to have desirable variations. Same thing on construction, people have instruction on building a colonial and a ranch. With good instructions, they can create a combination of the two.
Cons of Keeping Written Records

There is a reason not to write detailed records, in business, there is something called business retention policy. Well run businesses destroy written records. There is liability for something that is done when you do not have records.

webmycal approved on Sourceforge!
http://sourceforge.net/projects/webmycal is the url.

For the presentation, we (Georgi and I) will present the needs Analysis, feasibility study, system design, and the timeline.
Needs Analysis

Feasibility Study

System Design

Timeline

The presentation can be found at: http://mcs.dowling.edu/~terahz/POCS2/files/webMyCal_Intro.html