zodern
commented
10 years ago I never knew those libraries existed. They will be useful.
Pub Sub NameSpaces and priority
Do you mean that multiple apps could have the same method names? When I started Silk, I had expected each app would have it's own server and handle their own methods. Now that Silk handles methods for apps, it will be a problem. Right now if an app defines a method that already exists, the previous method is overwritten. It would be nice if a namespace is added automatically for each app, though that might be too much trouble.
Concept
I like the concept. The difficulty will be in priority or remembering defaults when there is multiple apps.
Applications
Those categories cover most apps related to files. Many apps will fall under multiple categories.
File creator - Can create new files File Reader - Reads and renders files specified File Update - Can update an existing file
Generally those are in the same app.
Some apps, like brackets, opens up a folder to work with. Maybe there could be an option to open a folder in an app.
File Creator/Deleter - Can Create Empty files or remove file
When would that be used except in a file explorer?
File Encoder is interesting. How will an app discover them and use them? Will they be dependencies apps need and installed if they aren't already?
Is File Indexer the file explorer or is it for indexing to search?
The app manager will probably get more responsibilities over time, but that is the basics.
an application can also define what it can accept similar to the W3C Standard.
That standard is much better than what the app defaults currently allows. The data could be stored in the window.json.
formula1
Its important to note that we are at very early stages so implementing all of this may not be beneficial in the long run. If we stick to play as we go, we may be better off. This may be a red herring
to be able to have events/requests/streams with a selector definition to choose where the event will go.
This may make it easier to code or may just be a lost cause.
Currently we have a pub/sub system up. Where applications listen to events and do the processing from there. This is excellent for the simple fact that some events are only for some applications. However, in some cases multiple applications will both listen to the same event (like file opening). We can leave this up to the application to decide whether or not it can handle it or we can open it in all or only the first. As a result, there also needs to be a priority mechanism to allow certian application to override others
For Example: If all applications fall under a few catagories, we already can limit our search.
Files can be anything however they generally have some sort of metadata that we can gather allowing us to know what to do with them.
As such, an application can also define what it can accept similar to the W3C Standard.
When it comes to communication, they may want to recieve objects from multiple locations and etc. However, those locations either should have compatible applications or have arbitrary files that we can gather data about. This can result in chat systems, games or pretty much anything.