Apps run in their own child Processes

[formula1]

Methods syntax remains the same however... you cannot define methods within the server scripts. They must be in an app script or we have to write a script that masks the server as a fork

I did my best to ensure it is completely backwards compatible so you don't feel like I'm making giant leaps

I installed async which I use in almost everything I do.

On the "todo" list, clean up the routing handler. Its very ugly and stores everything single request id inorder to ensure that whenever the process wants to send back it goes to the correct user. However, this expects a multiple user environment.

[formula1]

Don't this yet, I need to fix a few things

[formula1]

Ok, should work but a little messy. On my dev branch I made some drastic changes previously. Some of them I think are in line with your philosophy. App managers are in their own folder allowing you to switch between them rather than they be so intergrated with the core. However, I think we can take this a step further and just consider an app manager as if it was an application.

In my dev system I nearly completely removed methods in favor of direct communications. However, I think that goes against your philosophy so I avoided committing those changes

[zodern]

The changes look good, though I am getting an error when opening files. When it calls Silk/appDefaults, it returns the error method Silk/appDefaults does not exist.

I have been thinking about having the app manager as an app and I think it will be good.

In the dev branch, what are you doing for communication? I looked at the dev branch, and many of the changes are nice, though it will take me a while to figure out how everything works.

[formula1]

I apologize for that, I'll fix it

For Communication, I'm making most everything extend an event emitter of somekind. For clientside there is...

• DocumentHost (Type Server) - The server that delivered the document. If we are to allow remote applications such that would be on a different server, I'd like to implement a UserHost and DocumentHost Seperately
• Manager - Which is the manager directly in contact with the application, this is the manager that the application will deal with the most. This is if managers can host other managers
• RootManager - Can make calls to all applications directly underneath it including other managers. This is the topmost manager/application

For Serverside there is

• ClientEmitter - This is only interfaces with the server allowing us to still add routes in the core
• forkAssembler - This cannot be interacted with directly, they can only listen to events emitted by the ClientEmiter. Though we may need to make that available in the future

Within Forks there is

• methods - I'm going to try and keep a form of methods, however

I implemented a version of JSPath to do selections of applications on the server. Currently by calling

DocumentHost
    .get("applications",{jspath:'.{.category !== "manager" || !.category}'})
    .done(VueManager.load.bind(VueManager))

My hope is to also browserify this. As well as allow a variety of selectors in the future

[zodern]

There now is another problem. The app defaults is shown in the title bar. Would it work to not include it in the windows.json?

I like how you are doing communication.

[formula1]

Btw, thankyou for the feedback.

At some point I'd like to merge my dev branch as I have built a simple task monitor and WebRTC application (It uses similar syntax as our server to client communications). In addition I enabled backwards compatability so you don't have to feel overwhelmed when getting your feet wet. The reason why its better is

• Core functionality becoming abstract - This means that a change to the communications on one part means change to communications on all parts. Much easier to handle than each file having their own individual fixes.
• A manager Chooser at the Start - you can customize that as you choose. I just chose black, white and grey to show impartiality though I didn't spend too much time on it.
• Silk is in its own application - I made some heavy duty changes to the load.js however I tried my best to make it much easier

That being said, I'll need some feedback on what to call each event in order to have some sort of continuity/Sense/Rhythim

[zodern]

I will try the dev branch, but the changes sound great.

In addition I enabled backwards compatability so you don't have to feel overwhelmed when getting your feet wet.

Thank you.