From: Kevin <ke...@dr...> - 2006-04-18 16:41:42
|
Andrew Turner wrote: > Roadmap: > Now that we're putting together the next major version of FoFRedux, I > wanted to gather people's ideas on what the next version should > include, and how we want to go about adding it all in a timely, and > constructive, manner. > > There are 3 major modifications happening (that I can think of): > 1) Code framework cleanup/pull-apart > 2) Multiple Users > 3) UI redesign implementation, and ajax > > Items 1 & 2 should happen together, as functions will need to receive > the user_id or session of the current logged in user requesting data. > Furthermore, a user table and several join tables will have to be > added to associate users with their: feeds, items, tags, and options. > > Beginning item 3 can be done largely independent of items 1 & 2, as it > is implementing Khaled's designs in CSS/HTML/JS. When it comes to > actually hooking in the UI into the code, that's where items 1 & 3 > will need to coordinate. > > The purpose of the Code cleanup is to separate the "View" logic from > the Controller logic (assuming we use some kind of MVC design idea), > so the View interface can be spec'd later. > > Katie & Kevin, can you you two handle items 1 & 2? You have the most > experience with modifying the db and logic. > > Sure, I can help with that. The code could definitely use some "spring cleaning". > PS > > Mapping: > I finally got a little bit of time to toss in basic mapping. As you > may remember/know, I'm a huge geo/mapping nut and this was one of the > reasons I originally picked up FoFRedux. I now have GeoRSS support of > the rss output and can display feed items on a GoogleMap. I'm planning > on adding better viewing/listing. The parameters in the map.php are > the same as view.php and rss.php. > > http://code.highearthorbit.com/fofredux/fofredux_head/map.php?feed=29 > > > That's pretty cool. I don't see myself using it. This might be a good candidate for a plugin. -Kevin |