schedule

Hey all, I'm getting ready to geek out at boston2008... here's "the track" I think I'm going to follow... if you're going, look out for me,,, if not, hope to share an interesting note when I get back.

<

table>

Check out the schedule of conferences for our next Drupalcon Barcelona 2007. We have 84 conferences on a variety of topics, from showcases to API workshops, for any type of Drupal user, from evaluator to core programmer.

Any one can find a topic of interest at any time. There will be 4 rooms which can hold from 70 to more than 200 people plus 7 special spaces for BoFs. Any attendee will be able to propose a Bof at any time.

To get the ball rolling,

for all of you interested in attending meetup-type events in Hamilton, how often would you be interested? Would this be something you are interested in weekly? Monthly? Bi-Monthly?

Sorry i havent posted in while been busy with so many different things, so much to learn/do so little time hehe :D.

Anyways for past few weeks i have been attempting to create a plan of how go about each stage of the project. But because of what i need to learn and acheive the project just seemed bigger everytime i had a look at it :(.

After a session with drupals SoC pyschiatrist (webchick ;P), I do believe i have it figured out, well the first part anyways (first lesson learnt; dont think about the whole project, take it a chunk at a time).

I spoke to earls about it aswell and this is what i i think is the best way to get moving and seeing some progress will probably help,so to begin with i think its best if I got a list of exactly what i need from the schedule.module, whats missing.

This basicly means see if code is hijackable and what is needed on top of that code to make a ideal schedule module for our use.
Btw this could also be approached from the other end figuring out what i need form the views and whats missing etc.

From the views point, whats missing is an ID, an Entry point, and way to control the schedule.

now taking into consideration the schedule.module db design which i see as: