Dev Log Date 01.11.06 - Aero 2.0 RC1 - Control Panel

For the past 6 or so hours I've been working on getting the updated Aero 2.0 Control Panel ready for RC1 which is due sometime next week.

So far it allows you to look at some stuff, but that's about all.  Completely AJAX, with a Community Server Control Panel style sidebar to reduce what's on the screen.

[photo:2121]

The updated control panel will have autoupdating textboxes again, so no need for a save button.  The save message will be set to stay longer, and to be bigger.

As well as textboxes, and buttons, there will also be some check/radio buttons, and some drop down boxes to make it just that little bit easier for you to configure Aero 2.0.

Currently Aero 2.0 is on build number: 2.5, build 2.6 will be the RC1 build, due early next week.  Mind if your lucky it'll be Sunday

Today has had a few issues, but they are all resolved now thankfully.  NB Development, should be loading a bit quicker now.

The aero2.config file has once again been changed, this time to something which will allow easy updates, hopefully [yn].

Current Aero 2.0 RTM is due on the week beginning November 20th, if things go well.  If RC1 runs past Monday, then this 20th November date will slip to December 1st or something like that.

The current set up allows the browser to cache images easier, compared to the last one where one change meant re-caching everything.

Aero now remembers 4 Guid's to identify your last change, these get automatically updated when you change a specific value.  Makes loading quicker if only one or 2 Guid's change at a time.

If you are using my site you will have also noticed that the Customize Menu doesn't actually do anything.  This is on purpose, as the customize menu is Thursday's planned job.

Once the Customize Menu is done, there will be a couple of days of testing aero 2.0 RC1 internally, bug fixing, and optimizing aero for speed.

So keep an eye out for Aero 2.0 RC1, the Aero 2.0 download location should be updated the first, tho keep an eye on Dev Log, because I usually post the word of the release here 2 minutes later.

Happy Customizing

/* end of log */