Update - Sorry

Yep, Sorry I have not updated the blog lately. I have been working alot on Screens that even my sleeps are short. Screens is becoming more realistic and although I have my long design ideas, I am making Safire be more about being a 'stable release' then a full feature release. You can see this because Safire is targeted as a launcher and not as an environment. This allows me to not only release some build sooner but it allows it to be a perfectly valid release and not some demo. I have cut down the object storage inheritence, but made objects smaller, faster and simpler. What does this mean to the average user? Probably nothing. This is one of the reasons I have not posted lately... its just boring technical information. I hope to write some interesting post as soon as I can ;)

Update

I am still writing the tiny details for implementation of the object storage however I will not be including Services in the Safire release. The good news is that the object storage becomes less complex and I can finish coding it quicker, however the bad news is that no constructor/deconstructor for objects and no other dynamic abilities apart from inheritence. This means that an object wont notify you when it has changed, so untill I implement Services, polling or a refresh command will have to do. I am trying my best to be realistic about this project, so I am cutting off anything in the base which can be implemented later in the release cycle. This is so I can release it first and update it afterwards. I think its got to a stable stage where I can start coding and wont hit the wall after a few hundred lines of code.