Re: [PHPiCalendar-DEV] vtodo

[Waitman C. G. <wa...@em...>]

oh yeah, i missed this part of your email regarding dates on the TODO.

normally they don't have dates, but they CAN. so i went ahead and added
the info just in case it did exist.

waitman

On Wed, 2002-10-16 at 12:18, Chad wrote:
    I'm not sure why we would need to re-write the parser, as its pretty 
    well tested at this point. Jared and I have already started cleaning up 
    and tweeking the file for more speed and flexability, trimming over 200 
    lines this morning.
    
    It should just be altered to handle the vtodo, which is fairly simple. 
    I agree with Dre on placing it in the master array as [-2]. I don't see 
    though that it has a date attached specifically, they just appear in 
    iCal no matter the date they were created. Not sure how mozilla handles 
    these.
    
    -C
    
    
    
    On Wednesday, October 16, 2002, at 08:43  AM, Waitman C. Gobble wrote:
    
    > I just noticed that some of the apple events have a "start" and
    > "duration" instead of "end time". this is easy to implement in my
    > previous parser script, i will update.
    >
    > thanks
    >
    > waitman
    >
    >
    > On Wed, 2002-10-16 at 08:26, Waitman C. Gobble wrote:
    >     hello
    >
    >     i am working on VTODO implementation. attached is my preliminary
    >     code for review. I am at a point where i really need your comments,
    >     etc.
    >
    >     basically, the parser is redone. currently weighing in at only 181
    >     or so lines instead of 740, but it is not yet complete. the
    >     overlapper thing needs some looking into.
    >
    >     i would appreciate it if you could give it a try, and let me know
    >     what you find.
    >
    >     IMO, worse case is to extract the portions that handle VTODO and
    >     integrate with existing ical_parser.php
    >
    >     i estimate the final result could be around 250-350 lines of code.
    >
    >     it appears to me to be fast, i would need to create and collect 
    > data
    >     with regards to performance to compare to previous ical_parser.
    >
    >     it also appears to create a master_array that is compatible with 
    > the
    >     existing master_array, well i have added some stuff however some
    >     things can easily be removed to make it compatible with the other
    >     scripts if need be.
    >
    >     also, there is basic VALARM support. the rfc specs out a bunch of
    >     stuff with regards to VALARM, like being able to call a program
    >     using a URI, and setting multiple alarms that continue for
    >     prescribed durations, and specifying the alarm time relative to the
    >     START or the END of the event BUT I don't think any software
    >     currently implements these features - it appears to me that most
    >     software just lets you say "warn me x amount of minutes (or
    >     days/weeks/months) ahead of time before i am supposed to do this"
    >     and that is all. Please note I have not seen Apple's program,
    >     perhaps it allows more sophisticated alarm settings.
    >
    >     but my feeling is that at least the beginning we can simply handle
    >     the basic "alert at a certain amount of time before the event" 
    > since
    >     it seems that is all that is currently implemented in the clients.
    >
    >     ALSO, with regard to VTODOs, how do you guys feel about keeping 
    > them
    >     in the master array, or would you like them in a different array.
    >     currently the thing sticks them in the master array, with enough
    >     info to segregate them in the content producing scripts.
    >
    >     ALSO, with regard to VTIMEZONE. the rfc specs out some stuff but it
    >     is labelled as "incomplete". Mozilla doesn't use it at all, how
    >     about the apple software? the samples on the apple site "half" use
    >     the timezone thing when indicating times, but the timezone data
    >     itself is not present so you can't really do anything with it (at
    >     least not by the standards in the spec). you could speculate the
    >     timezone label but you might run into trouble down the road with
    >     compatibility.
    >
    >
    >     best regards,
    >
    >     Waitman
    >
    >
    >
    >
    >
    >
    > -------------------------------------------------------
    > This sf.net email is sponsored by: viaVerio will pay you up to
    > $1,000 for every account that you consolidate with us.
    > http://ad.doubleclick.net/clk;4749864;7604308;v?
    > http://www.viaverio.com/consolidator/osdn.cfm
    > _______________________________________________
    > Phpicalendar-devel mailing list
    > Php...@li...
    > https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel
    
    
    
    -------------------------------------------------------
    This sf.net email is sponsored by: viaVerio will pay you up to
    $1,000 for every account that you consolidate with us.
    http://ad.doubleclick.net/clk;4749864;7604308;v?
    http://www.viaverio.com/consolidator/osdn.cfm
    _______________________________________________
    Phpicalendar-devel mailing list
    Php...@li...
https://lists.sourceforge.net/lists/listinfo/phpicalendar-devel