[forge-dev] [JBoss JIRA] Commented: (SEAMFORGE-164) Forge Plugins should be decoupled from the Shell Interface, run standalone in JBoss Tools
[
https://issues.jboss.org/browse/SEAMFORGE-164?page=com.atlassian.jira.plu...
]
Koen Aers commented on SEAMFORGE-164:
-------------------------------------
I think on the other hand it would be good to be able to query Forge for all kinds of
stuff *bypassing* the shell. But as Max indicates, when you run Forge in the same VM as
JBT we will probably need to tie two particular versions of both Forge and JBT together.
And then it will be more difficult to have multiple runtimes of Forge in JBT. But then
maybe this is something that is good?
I'm putting my thoughts together on communication between JBT and Forge and I will
open another issue to track that.
Forge Plugins should be decoupled from the Shell Interface, run
standalone in JBoss Tools
-----------------------------------------------------------------------------------------
Key: SEAMFORGE-164
URL: https://issues.jboss.org/browse/SEAMFORGE-164
Project: Seam Forge
Issue Type: Feature Request
Components: Brainstorming, JBoss Tools Integration
Reporter: Lincoln Baxter III
(01:41:28 PM) Lincoln: I'd like to start Forge in JBoss Tools, but instead of using
the Shell, use the PluginMetadata to build a GUI to run Plugins from the IDE itself.
(01:41:34 PM) Lincoln: Using windows and input fields, etc.
(01:41:45 PM) Koen Aers: hm
(01:42:07 PM) Lincoln: So workflow like this:
(01:42:46 PM) Lincoln: <CTRL-4> JBT pops up a window like <CTRL-3> where you
can type and it will search through the list of commands that are available
(01:42:48 PM) Lincoln: you can pick one
(01:42:51 PM) Lincoln: when you do
(01:43:06 PM) Lincoln: JBT generates a UI for that command, with a list of required and
optional fields, based on teh plugin metadata
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira