[Cosmo-dev] Refactor of cal_main.js

[Bobby Rullo]

Could you explain what this list means a little more? That is, are  
these separate files? Functions? Classes? Equally important is how  
they interact with each other - like "The GUI widget contains a foo  
bar service which is uses static functions in the BarUtils.js to do  
it's bar-processing"


On Aug 10, 2006, at 2:15 PM, Matthew Eernisse wrote:

> Here's my first pass at a proposed plan for breaking up the Cal  
> object in cal_main.js in the Web UI. I hope it can serve as a  
> jumping-off point for a bit of discussion.
>
> 1. GUI container-elem init
> 2. Lang-specific resource init
> 3. Rendering basic UI elem
> 4. Loading events
> 5. Event conflict calculations
> 6. Appending/rendering events on canvas
> 7. Save/remove events (deprecate)
> 8. Navigation / cal-switching
> 9. Dialog box (error, remove, etc.)
> 10. Time/position calculations on canvas
> 11. ID/datetime attribute extraction (deprecate)
> 12. App-specific date-calc funcs
> 13. Timeout/keepalive
>
> The only significant departure from the existing section divisions  
> in the file is breaking the conflict code out into its own chunk.
>
> The final organization will of course be influenced by the big  
> changes from (1) re-architecting to use Dojo topics and (2) changes  
> to accommodate other types of items than events. But it is already  
> clear that a lot of the code in the save/remove area and the  
> attribute-extraction area will eventually be deprecated.
>
>
> Matthew
>
>
>
>
>
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev