Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement web IDE for camel routes (silverspoon camel components) #13

Open
sbunciak opened this issue Feb 26, 2015 · 9 comments
Open

Implement web IDE for camel routes (silverspoon camel components) #13

sbunciak opened this issue Feb 26, 2015 · 9 comments
Milestone

Comments

@sbunciak
Copy link
Member

  • Investigate usage of hawt.io
  • Needs to output wiring diagram (fritzing)
  • Output mobile friendly user interface for deployable (camel) application
@sbunciak sbunciak changed the title Implement web ide for camel routes (silverspoon camel components) Implement web IDE for camel routes (silverspoon camel components) Feb 26, 2015
@sbunciak sbunciak modified the milestones: 0.3.0, 1.0.0 Apr 12, 2015
@hekonsek
Copy link

Do you plan to release this as a Plugin to Hawt.io? I think that would be the best approach.

@sbunciak
Copy link
Member Author

Yes, that's the plan ;-)

@hekonsek
Copy link

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. :)

@sbunciak
Copy link
Member Author

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.

@hekonsek
Copy link

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.

@hekonsek
Copy link

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!

@sbunciak
Copy link
Member Author

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 [email protected]:

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
#13 (comment).

@hekonsek
Copy link

hekonsek commented May 4, 2015

All Fuse-related plugins will be migrated to V2 anyway. :) I would definitely recommend to go with V2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants