I’ve decided that instead of releasing a standalone version, it’ll become a hosted service/saas. This comes at a cost of more development time, to create the account management/etc. I’m going to allow custom CSS loading, and possibly some kind of online template editing. I’m not sure yet. Lots of ideas. I’m thinking that integrating a Zenfolio account will be the next major iteration.
Starting late on Monday carried over to a late night on Tuesday at work. It was an unexpected, but overall beneficial long day. I’ve managed to squeeze in a little time for refactoring the JavaScript portion of awFlickr app, which I plan to release into a private beta this weekend.
I’ll think of a better name once I get it out for testing. I’m planning on using this as a base for Spiral’s PHP version, and my tentatively named aw:Mail.
This past weekend I started working on a Flickr app that’s REST/JSON/JavaScript based (with a PHP back end generating the JSON). It’s a very old project I never really got started on, but was pretty easy to (almost) complete in under 2 days.
I discovered… a Flickr ID is too large for any web browser JavaScript engine to handle; they rounded up randomly. HTML comments on photos are very annoying from a programmatic point of view. I really like JavaScript.
I used the code base from my portfolio and hacked it up, by taking out the # operations and using events on all the dynamic objects/elements. I also corrected the JSON transportation. Now I’m left with a few visual effects to create, and some misc behavioral changes.
I’m hoping to have v1.0 released this week under the MIT license.
With the new employment at Maple Works Technology, working on Spiral has become very low priority due to other projects and having a fiance. I’m hoping to have a spring beta.
With Christmas having come and gone, and New Years just around the corner; development has slowed to a crawl on Spiral due to a lack of time for this project. It should pick up again in January, after I return from Jamaica where I’m shooting a wedding.
I’m hoping to have a beta up and running on the in-house dev server soon!
I’m using it for the first time with Spiral, and it’s slowing down my planned rapid development cycle. It’s definitely worth learning, and I’m sure it’s going to be worth while based on Spiral’s schema. I’m not sure if I’m a fan of CUD (CRUD?) though, because it complicates things and complains about FK relations sometimes.
Based on this Microsoft TechNet article I’ve refactored the Views used to access Spiral’s data via sproc . This is one of many changes which have allowed for a much broader role for the applicable. Spiral will be released as a community portal.
The database will be deployed as SQLExpress and be cluster ready if you attach it to SQL Server 2005 or newer.
Development of aw:Mail is being put on hold. Development of Spiral, a .Net MVC2 based blog is going forward.
I decided to make a small incremental upgrade to aw:Calendar and created a “weekend” class for the days that fall on Saturday or Sunday.
Today after noticing I had left the application/javascript type set on the aw:Browser demo, I noticed IE 8 wasn’t running the JavaScript properly after going a few directories deep. Putting try() into a few functions was all that was needed. I’m not surprised only IE needed this.