Chromecide.com

So I’ve been mad at it the last few weeks.  Outside of work, I have been spending any free time I have working on Flux Singularity and it’s really starting to come together.  I should probably give some in depth analysis of everything I’ve completed so far, and what is left, but I’m just going to summarise the updates and get back to getting the system done.

DockUI

The Messaging and request subsystem is finished.  It can handle both single instance requests, as well as poll based requests.  Single instance requests are things like retrieving the details of an object to display on an edit form, while a poll based request is more designed for things like lists of objects, where the information can change over time and needs to be updated.

Flux Singularity

On par with the development of the DockUI widgets, I’ve created the core framework for the Flux Singularity Server API.  This includes methods for sessions and user registration, authentication and data security, as well as object schema and content manipulation functionality.

The Twitter information retrieval has been integrated into the core communications engine, and updated to reflect the new methods for creating and validating objects.  I’ll be beginning testing with this hopefully this week, so keep an eye out for a couple of Twitter accounts that, well…quite frankly…appear totally normal, but that’s the point isn’t it?

Next Steps

In my original coding for the Twitter interaction, I had the sending of Tweets being performed by the event loop.  I want to move this into the Twitter process loop to bring the methods into line with the modularity of the system.  This would then limit the tasks of event loop to those of data modification only.   For example, the event loop would calculate if a Tweet is ready to be sent, and if so update the “NeedsToBeSent” flag in the database.  This tweet would then be picked up and sent upon the next iteratoin of the communications loop.

Updating the way that works would complete the Twitter module of the Communications system.  With that out of the way, I will be moving onto updating the Web Site Renderer to include support for Hierarchical navigation, web forms and web site statistics gathering. (At the moment, it only supports basic, flat structured static web sites.)

Once that is complete, it’s onto the Event Processor, although the work to get that finished would primarily be updating code to bring it in line with the recent modifications to the methods for creating and validating objects, and to expand the capabilities of the script engine.

While this may seem like quite a fair amount of work, I’m still on track for having the system ready for some major testing by the start of August.

The only real outstanding question mark over the timing is the arrival of our New Bubba, because nature has it’s it’s own timeline, and The Better Half is gonna need a well deserved break after 10 months!!