[JBoss JIRA] Created: (SEAMFORGE-164) Forge Plugins should be decoupled from the Shell Interface, run standalone in JBoss Tools
12:49 p.m.
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
4:04 p.m.
New subject: [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...
]
Max Rydahl Andersen commented on SEAMFORGE-164:
-----------------------------------------------
This is one of my big wishes too but since forge is running in an external process
wouldn't it be simpler that this metadata could be queryed via the shell and we can
parse it ?
also removes/reduces any binary hard dependencies between specific jbosstools / forge
versions?
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
4:06 a.m.
New subject: [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
5:09 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on SEAMFORGE-164:
-----------------------------------------------
Koen, do you mean when you run forge in the same VM or when you *do not* run forge in the
same VM ?
Running CDI/Forge classloading tricks in the same VM as Eclipse has serious implications -
needs to be extremely careful that no classes gets loaded/accessed in both forge and
eclipse to avoid alot of problems. Would have to at least be in different threads and
avoid sharing any state beyond trivial stable data classes.
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
7:44 a.m.
New subject: [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:
-------------------------------------
Max, I think indeed that running in the same VM will be tricky though maybe not impossible
if it happens in a thread of its own with an appropriate classloader. But in addition to
that there is the problem of supporting multiple Forge runtime versions that becomes way
more complicated or even impossible. This would probably implicate that the release cycles
of Forge and JBT would have to be aligned. We both know how easy that is ;-)
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
8:25 a.m.
New subject: [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...
]
Max Rydahl Andersen commented on SEAMFORGE-164:
-----------------------------------------------
yes, so we agree ;)
My thinking is that there should be a way in Forge (possibly a plugin) to either turn the
shell into sending more structured content then just a "semi-random" text stream
which we then could "render" independent on how the plugins are implemented.
Alternatively that plugin could open up a port (http even, bound to the local machine)
which would receive and send out commands that the IDE could react/query on.
Things like "Query for possible commands", "query for completions for a
specific property", "cd to this project", "run this command" and
likewise the plugin could ask the IDE "Open this file", "these resources
are to be created - please lock workspace" or "about to start command X",
"finshed command X, here are the resources added/created - and this one is the main
one that should be opened in the IDE" etc.
No matter what functionality we want to do we need to find the manner of communication and
what "level" it is done at "forge commands", "ide commands"
or more highlevel ones?
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
4757
days inactive
4758
days old
5 comments
3 participants
participants (3)
-
Koen Aers (JIRA) -
Lincoln Baxter III (JIRA)
-
Max Rydahl Andersen (JIRA)