Which is why google doesn't use tables for the event area. They create the rows and columns with absolutely positioned divs, and overlay absolutely positioned events on top.
I've recently created a similar tool for a project, but have the server calculate all the positions. The problem is that I have to rewrite those calculations on the client if I want real-time dragging/ resizing of events -- which I don't do now. The calculations get non- trivial when dealing with overlapping events. I couldn't find anything to better to start with, so If you do, let me know. Gareth Evans wrote: > I've written a Drag&Drop calendar before (without resizing) for another > project and the biggest problem was that it was created with table cells, so > when you had an appointment that was longer than a cell, we had to use row > span on the destination cell and 'pop off' the cells to the right so that > the calendar didnt get misaligned. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
