As I've mentioned in the past, I'm currently working on a new project that's been taking my time away from Spaz. While most details are still under wraps, I can say now that the new project is a version of Spaz for mobile devices. Rather than a port, this is a whole new codebase that takes advantage of all the stuff I've learned writing Spaz for AIR.
While I will still be working hard on the mobile app for at least another month, I have been thinking a lot about where the desktop app should be going. Here's the plan:
- Version 0.8 will be the last version of Spaz using the current codebase. We are currently being held back by the design decisions I made, and they need to be tossed. Versions 0.9 and later will be based on a complete rewrite of the codebase. It will use an MVC-style pattern, and will be powered by the SpazCore component library. SpazCore being worked on now, and is hosted on GitHub at <http://github.com/funkatron/spazcore/>.
- I may switch from the AIR platform to Titanium for the new Spaz codebase. I am still weighing this decision, but I'm very interested in TI, especially after having the opportunity to meet the development team last week. They have a very strong platform, and their approach is very much in line with the "Spaz philosophy." <http://titaniumapp.com>
- Feature-wise, I'm targeting all(*) existing features, plus: - multiple instances of the "main" windows (basically the current Spaz window, multiple times for multiple accounts) - custom tab panels in the main window that filter your main timeline by user, keyword, etc - multiple search windows with auto-updating results - less reliance on the web site for user and message details
Spaz should still be very suitable for average Twitter users (under 100 friends), but will also offer powerful search features for folks who need them. And of course, Spaz will still be completely open-source under a New BSD-style license.
* Actually, one feature of Spaz that may see a reduction in functionality is theming. Supporting multiple themes in the main release is an *enormous* pain whenever I need to make an interface change. While I expect it will still be possible to override most or all of the interface with CSS, I will likely shoot for a single good theme to ship with Spaz, and leave modifications as an exercise for the motivated user.
> As I've mentioned in the past, I'm currently working on a new project
> that's been taking my time away from Spaz. While most details are
> still under wraps, I can say now that the new project is a version of
> Spaz for mobile devices. Rather than a port, this is a whole new
> codebase that takes advantage of all the stuff I've learned writing
> Spaz for AIR.
> While I will still be working hard on the mobile app for at least
> another month, I have been thinking a lot about where the desktop app
> should be going. Here's the plan:
> - Version 0.8 will be the last version of Spaz using the current
> codebase. We are currently being held back by the design decisions I
> made, and they need to be tossed. Versions 0.9 and later will be based
> on a complete rewrite of the codebase. It will use an MVC-style
> pattern, and will be powered by the SpazCore component library.
> SpazCore being worked on now, and is hosted on GitHub at
> <http://github.com/funkatron/spazcore/>.
> - I may switch from the AIR platform to Titanium for the new Spaz
> codebase. I am still weighing this decision, but I'm very interested
> in TI, especially after having the opportunity to meet the development
> team last week. They have a very strong platform, and their approach
> is very much in line with the "Spaz philosophy."
> <http://titaniumapp.com>
> - Feature-wise, I'm targeting all(*) existing features, plus:
> - multiple instances of the "main" windows (basically the current
> Spaz window, multiple times for multiple accounts)
> - custom tab panels in the main window that filter your main
> timeline by user, keyword, etc
> - multiple search windows with auto-updating results
> - less reliance on the web site for user and message details
> Spaz should still be very suitable for average Twitter users (under
> 100 friends), but will also offer powerful search features for folks
> who need them. And of course, Spaz will still be completely
> open-source under a New BSD-style license.
> * Actually, one feature of Spaz that may see a reduction in
> functionality is theming. Supporting multiple themes in the main
> release is an *enormous* pain whenever I need to make an interface
> change. While I expect it will still be possible to override most or
> all of the interface with CSS, I will likely shoot for a single good
> theme to ship with Spaz, and leave modifications as an exercise for
> the motivated user.
> On Feb 21, 11:16 pm, Ed Finkler <funkat...@gmail.com> wrote:
>> As I've mentioned in the past, I'm currently working on a new project
>> that's been taking my time away from Spaz. While most details are
>> still under wraps, I can say now that the new project is a version of
>> Spaz for mobile devices. Rather than a port, this is a whole new
>> codebase that takes advantage of all the stuff I've learned writing
>> Spaz for AIR.
>> While I will still be working hard on the mobile app for at least
>> another month, I have been thinking a lot about where the desktop app
>> should be going. Here's the plan:
>> - Version 0.8 will be the last version of Spaz using the current
>> codebase. We are currently being held back by the design decisions I
>> made, and they need to be tossed. Versions 0.9 and later will be
>> based
>> on a complete rewrite of the codebase. It will use an MVC-style
>> pattern, and will be powered by the SpazCore component library.
>> SpazCore being worked on now, and is hosted on GitHub at
>> <http://github.com/funkatron/spazcore/>.
>> - I may switch from the AIR platform to Titanium for the new Spaz
>> codebase. I am still weighing this decision, but I'm very interested
>> in TI, especially after having the opportunity to meet the
>> development
>> team last week. They have a very strong platform, and their approach
>> is very much in line with the "Spaz philosophy."
>> <http://titaniumapp.com>
>> - Feature-wise, I'm targeting all(*) existing features, plus:
>> - multiple instances of the "main" windows (basically the current
>> Spaz window, multiple times for multiple accounts)
>> - custom tab panels in the main window that filter your main
>> timeline by user, keyword, etc
>> - multiple search windows with auto-updating results
>> - less reliance on the web site for user and message details
>> Spaz should still be very suitable for average Twitter users (under
>> 100 friends), but will also offer powerful search features for folks
>> who need them. And of course, Spaz will still be completely
>> open-source under a New BSD-style license.
>> * Actually, one feature of Spaz that may see a reduction in
>> functionality is theming. Supporting multiple themes in the main
>> release is an *enormous* pain whenever I need to make an interface
>> change. While I expect it will still be possible to override most or
>> all of the interface with CSS, I will likely shoot for a single good
>> theme to ship with Spaz, and leave modifications as an exercise for
>> the motivated user.
> As I've mentioned in the past, I'm currently working on a new project
> that's been taking my time away from Spaz. While most details are
> still under wraps, I can say now that the new project is a version of
> Spaz for mobile devices. Rather than a port, this is a whole new
> codebase that takes advantage of all the stuff I've learned writing
> Spaz for AIR.
> While I will still be working hard on the mobile app for at least
> another month, I have been thinking a lot about where the desktop app
> should be going. Here's the plan:
> - Version 0.8 will be the last version of Spaz using the current
> codebase. We are currently being held back by the design decisions I
> made, and they need to be tossed. Versions 0.9 and later will be based
> on a complete rewrite of the codebase. It will use an MVC-style
> pattern, and will be powered by the SpazCore component library.
> SpazCore being worked on now, and is hosted on GitHub at
> <http://github.com/funkatron/spazcore/>.
> - I may switch from the AIR platform to Titanium for the new Spaz
> codebase. I am still weighing this decision, but I'm very interested
> in TI, especially after having the opportunity to meet the development
> team last week. They have a very strong platform, and their approach
> is very much in line with the "Spaz philosophy."
> <http://titaniumapp.com>
> - Feature-wise, I'm targeting all(*) existing features, plus:
> - multiple instances of the "main" windows (basically the current
> Spaz window, multiple times for multiple accounts)
> - custom tab panels in the main window that filter your main
> timeline by user, keyword, etc
> - multiple search windows with auto-updating results
> - less reliance on the web site for user and message details
> Spaz should still be very suitable for average Twitter users (under
> 100 friends), but will also offer powerful search features for folks
> who need them. And of course, Spaz will still be completely
> open-source under a New BSD-style license.
> * Actually, one feature of Spaz that may see a reduction in
> functionality is theming. Supporting multiple themes in the main
> release is an *enormous* pain whenever I need to make an interface
> change. While I expect it will still be possible to override most or
> all of the interface with CSS, I will likely shoot for a single good
> theme to ship with Spaz, and leave modifications as an exercise for
> the motivated user.
On Sat, Feb 21, 2009 at 11:25 PM, James Marshall <louie...@me.com> wrote:
> Will Titanium allow you to make a version for the iPhone?
> Sent from my iPhone
> On Feb 21, 2009, at 8:16 PM, Ed Finkler <funkat...@gmail.com> wrote:
>> As I've mentioned in the past, I'm currently working on a new project
>> that's been taking my time away from Spaz. While most details are
>> still under wraps, I can say now that the new project is a version of
>> Spaz for mobile devices. Rather than a port, this is a whole new
>> codebase that takes advantage of all the stuff I've learned writing
>> Spaz for AIR.
>> While I will still be working hard on the mobile app for at least
>> another month, I have been thinking a lot about where the desktop app
>> should be going. Here's the plan:
>> - Version 0.8 will be the last version of Spaz using the current
>> codebase. We are currently being held back by the design decisions I
>> made, and they need to be tossed. Versions 0.9 and later will be based
>> on a complete rewrite of the codebase. It will use an MVC-style
>> pattern, and will be powered by the SpazCore component library.
>> SpazCore being worked on now, and is hosted on GitHub at
>> <http://github.com/funkatron/spazcore/>.
>> - I may switch from the AIR platform to Titanium for the new Spaz
>> codebase. I am still weighing this decision, but I'm very interested
>> in TI, especially after having the opportunity to meet the development
>> team last week. They have a very strong platform, and their approach
>> is very much in line with the "Spaz philosophy."
>> <http://titaniumapp.com>
>> - Feature-wise, I'm targeting all(*) existing features, plus:
>> - multiple instances of the "main" windows (basically the current
>> Spaz window, multiple times for multiple accounts)
>> - custom tab panels in the main window that filter your main
>> timeline by user, keyword, etc
>> - multiple search windows with auto-updating results
>> - less reliance on the web site for user and message details
>> Spaz should still be very suitable for average Twitter users (under
>> 100 friends), but will also offer powerful search features for folks
>> who need them. And of course, Spaz will still be completely
>> open-source under a New BSD-style license.
>> * Actually, one feature of Spaz that may see a reduction in
>> functionality is theming. Supporting multiple themes in the main
>> release is an *enormous* pain whenever I need to make an interface
>> change. While I expect it will still be possible to override most or
>> all of the interface with CSS, I will likely shoot for a single good
>> theme to ship with Spaz, and leave modifications as an exercise for
>> the motivated user.
We use odd point releases (like .1, .3, .5...) as testing releases,
kind of like the Linux kernel, so the idea is that the public release
of Spaz mk2 would be 1.0.
--
Ed Finkler
http://funkatron.com Twitter:@funkatron
AIM: funka7ron
ICQ: 3922133
XMPP:funkat...@gmail.com
|
