JSoo progress.
It's been a turbulent few days since I first released JSoo to the public, but since then my ideas and vision towards JSoo expanded substantially. I'm personally quite excited in the direction I chose for JSoo, though I soon must take some time to write proper documentation, routemap and dump it all into an opensource repository/wiki for collaberation. In any case, if you look to the right, you can now see a text bit with the hours I've worked on JSoo, it's a simple way to see if JSoo is progressing 
For now, a little update/teaser:
A-synchronous property hash assignments
Assign inheritance from a non-existing property hash for later use, when defining the property hash later on, JSoo will synchronize inheritance and all methods will appear on instances drawn from the JSoo property hash reference. This grants powerful potential to JSoo#Externals.
JSoo#Externals
Load external .jsoo files where JSoo property hashes are declared for better property hash management and code reuse.
JSoo#Interface
Declare which methods a property hash MUST contain and use it to remove redundant inheritted methods from a property hash. This is taken from Classical OO, though I find Interfaces to be a rather useful tool for team collaberation. It will ofcourse be optional to use Interfaces.
JSoo#compile
At this point, JSoo is becoming rather bulky, while still a small size and up for further code refining, it would be nice to compile the code into a bare minimum needed to run the code. Turning JSoo into a development tool rather then an addhoc .js library. This extends my personal preference to mix and match .js libraries rather then using a full sized js framework. I have quite some hurdles to cross to achieve this and it might not be compatible with all browsers, but since in this case you'd use the compiled code rather then the original JSoo declarations, you can use a supported browser to build your applications.
Forking
I am considering in splitting JSoo up for 2 applications, one being development and the other being an addhoc library to use out of the box in your projects. This will depend on how bulky #Interface and #compile become.
In closing
JSoo is growing beyond being an alternative of creating "classes/prototypes", wether this is good or bad, time will tell. In any case, there are a lot of "Class/Protoype" builders out there, which fit certain purposes much better then JSoo on convenience or sheer size. It's silly to compete with them or boast my way is better, instead I'd rather build something new and potentially useful for developers while having fun doing it.
While other frameworks/libraries offer a lot of functionality and convenience methods, I like JSoo to be a tool to manage the code developers themselves write while using frameworks.