On 2 May 2007, at 0:22, James Kebinger wrote: > I would think we should concentrate on the next release for two > reasons - 1) the current release is ancient and 2) that will mean > more features to run on slingshot. > > On 5/1/07, Luke Melia <[EMAIL PROTECTED]> wrote:Far out!!! This is > very cool. > > How do we decide how much time to spend on this versus the next > release?
I agree that we shouldn't delay the next release to do a full integration, but I certainly think that we should release an offline version for Mac/Windows people alongside the usual server release. That would solve the biggest single problem that Tracks has always had, which is that it's daunting for non-technical people (who just want to use it on their own computer) to install. I wasn't kidding when I said it took 5 minutes to do (and that was when I didn't know what I was doing). You don't need to modify the Tracks code at all - you just dump the code inside the app package, change a few config files (which could easily be scripted) and provide an SQLite3 db (which is easily done via rake db:migrate). So we can just carry on working on Tracks, then produce a standalone version when we're done in a few minutes. Then, for the release after next, we could get sync going, drag and drop and so on, so we'd connect the offline (Slingshot) and online (standard Tracks) parts so that people could get the best of both worlds. So for 1.050 we'd have: Online Tracks (all platforms) Offline Tracks for Mac (Intel only ATM, I had to build Slingshot on my Intel iMac at work) Offline Tracks for Windows Then for 1.051 (or whatever) As above, but also Online + Offline Tracks for syncing (Mac and Windows) What do you think? bsag -- but she's a girl - the weblog of a female geek http://www.rousette.org.uk [EMAIL PROTECTED] _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
