Open sbunciak opened 9 years ago
Do you plan to release this as a Plugin to Hawt.io? I think that would be the best approach.
Yes, that's the plan ;-)
Do you target the Hawt.io v1 or v2? Do you have a GitHub repo with the work in progress anywhere? I'd love to take a look. :)
At first, we were targeting Hawt.io v1, however if you find more useful we can switch to Hawt.io v2 as the work has not been started, afaik. It's supposed to be mainly a project for University students, and we haven't received any outcome, yet. However, I expect them to start working on it in few weeks.
Are Hawt.io v1 plugins compatible with Hawt.io v2? If so, then I see no reason why to target v1 anymore.
V2 architecture is much different from V1. For example nodejs backend is used instead of Java. I highly recommend not to invest your time into V1 as it will have to perform aggressive and time consuming refactoring the near future anyway.
But Hawt.io 2 plugins architecture is much nicer than v1 :) Those are just Bower packages. It makes it much easier to add your plugin to any Hawt.io installation. Even at runtime!
My only concern is whether we could re-use existing plugins like http://hawt.io/plugins/camel/ if we decide to go for Hawt.io v2. If yes, then we definitely go that way :-)
2015-04-29 10:09 GMT+02:00 Henryk Konsek notifications@github.com:
But Hawt.io 2 plugins architecture is much nicer than v1 :) Those are just Bower packages. It makes it much easier to add your plugin to any Hawt.io installation. Even at runtime!
— Reply to this email directly or view it on GitHub https://github.com/px3/silverspoon/issues/13#issuecomment-97342566.
All Fuse-related plugins will be migrated to V2 anyway. :) I would definitely recommend to go with V2.