Adding Max. On Wed, Jan 2, 2013 at 4:00 PM, Lincoln Baxter, III <lincolnbaxter(a)gmail.com&gt; wrote: Hey All, We've started working on the Forge 2 Eclipse UI integation - please see the latest work here: https://github.com/forge/forge2-eclipse-ui Forge is booting and running from Eclipse (currently rigged up through "New -> Forge Addon", just so we have an easy way to start the runtime.) Forge may then be queried for Addon services via: forge.getAddonRegistry().getRemoteInstance(MyServiceClass.class); Next step: • Get UICommand objects working to build Eclipse Wizards, see UI API here: https://github.com/forge/core/tree/2.0/ui/api/src/main/java/org/jboss/for... Addons may depend on the org.jboss.forge:ui addon and implement the UICommand interface and UIWizard interfaces to make functionality available to the host environment (like Eclipse or the CLI Shell.) These implementations are then retrieved via the AddonRegistry, as exampled above. Set<UICommand.class> commands = forge.getAddonRegistry().getRemoteInstances(UICommand.class); Questions: • How should the Forge integration in Eclipse look and feel? • Where should the UI interactions begin? Menu, hotkey, etc? (I personally favor the CTRL-4 shortcut to bring up a forge command selector menu, like what currently is done in JBoss Tools. That's all for now. This is all a prototype so now is the time to fix things if they need to chance. Please send your feedback! We want this to work as well as possible so are very open to feedback. -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better." -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

I can't see why you need to support both Forge 1 and Forge 2 in the same Eclipse plugin?

For an end user, we'll want to do a single cutover from one to the other.

For testing and development a separate Forge 2 plugin seems ok.

On 7 Jan 2013, at 09:29, Max Rydahl Andersen wrote: > I'm on forge-dev so don't worry ;) > > first comment - why isn't this a branch in jbosstools-forge eclipse repo instead of a separate repo tied to forge ? (I assume we'll need both Forge 1 and 2 support in the eclipse integration ?) > > And just hook the starting on forge into the same place as it is today would make sense would it not ? > > /max > > On 04 Jan 2013, at 19:05, "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com&gt; wrote: > >> Adding Max. >> >> >> On Wed, Jan 2, 2013 at 4:00 PM, Lincoln Baxter, III <lincolnbaxter(a)gmail.com&gt; wrote: >> Hey All, >> >> We've started working on the Forge 2 Eclipse UI integation - please see the latest work here: >> >> https://github.com/forge/forge2-eclipse-ui >> >> Forge is booting and running from Eclipse (currently rigged up through "New -> Forge Addon", just so we have an easy way to start the runtime.) Forge may then be queried for Addon services via: >> >> forge.getAddonRegistry().getRemoteInstance(MyServiceClass.class); >> >> Next step: >> >> • Get UICommand objects working to build Eclipse Wizards, see UI API here: >> >> https://github.com/forge/core/tree/2.0/ui/api/src/main/java/org/jboss/for... >> >> Addons may depend on the org.jboss.forge:ui addon and implement the UICommand interface and UIWizard interfaces to make functionality available to the host environment (like Eclipse or the CLI Shell.) These implementations are then retrieved via the AddonRegistry, as exampled above. >> >> Set<UICommand.class> commands = forge.getAddonRegistry().getRemoteInstances(UICommand.class); >> >> Questions: >> • How should the Forge integration in Eclipse look and feel? >> >> • Where should the UI interactions begin? Menu, hotkey, etc? (I personally favor the CTRL-4 shortcut to bring up a forge command selector menu, like what currently is done in JBoss Tools. >> That's all for now. This is all a prototype so now is the time to fix things if they need to chance. Please send your feedback! We want this to work as well as possible so are very open to feedback. >> >> >> -- >> Lincoln Baxter, III >> http://ocpsoft.org >> "Simpler is better." >> >> >> >> -- >> Lincoln Baxter, III >> http://ocpsoft.org >> "Simpler is better." > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev

> It would be an exception to drop support this early but with the current state it might be what we need to do. I don't really understand? You would keep the Forge 1 support for JBDS.current, and move to Forge 2 for JBDS.next. Forge is part of JBDS effectively from a product perspective.

> >> For testing and development a separate Forge 2 plugin seems ok. > > To avoid problems of p2 updates, build and version tracking and other osgi sanities its simpler if we just keep these under the same jbosstools forge repo. > > /max > > >> >> On 7 Jan 2013, at 09:29, Max Rydahl Andersen wrote: >> >>> I'm on forge-dev so don't worry ;) >>> >>> first comment - why isn't this a branch in jbosstools-forge eclipse repo instead of a separate repo tied to forge ? (I assume we'll need both Forge 1 and 2 support in the eclipse integration ?) >>> >>> And just hook the starting on forge into the same place as it is today would make sense would it not ? >>> >>> /max >>> >>> On 04 Jan 2013, at 19:05, "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com&gt; wrote: >>> >>>> Adding Max. >>>> >>>> >>>> On Wed, Jan 2, 2013 at 4:00 PM, Lincoln Baxter, III <lincolnbaxter(a)gmail.com&gt; wrote: >>>> Hey All, >>>> >>>> We've started working on the Forge 2 Eclipse UI integation - please see the latest work here: >>>> >>>> https://github.com/forge/forge2-eclipse-ui >>>> >>>> Forge is booting and running from Eclipse (currently rigged up through "New -> Forge Addon", just so we have an easy way to start the runtime.) Forge may then be queried for Addon services via: >>>> >>>> forge.getAddonRegistry().getRemoteInstance(MyServiceClass.class); >>>> >>>> Next step: >>>> >>>> • Get UICommand objects working to build Eclipse Wizards, see UI API here: >>>> >>>> https://github.com/forge/core/tree/2.0/ui/api/src/main/java/org/jboss/for... >>>> >>>> Addons may depend on the org.jboss.forge:ui addon and implement the UICommand interface and UIWizard interfaces to make functionality available to the host environment (like Eclipse or the CLI Shell.) These implementations are then retrieved via the AddonRegistry, as exampled above. >>>> >>>> Set<UICommand.class> commands = forge.getAddonRegistry().getRemoteInstances(UICommand.class); >>>> >>>> Questions: >>>> • How should the Forge integration in Eclipse look and feel? >>>> >>>> • Where should the UI interactions begin? Menu, hotkey, etc? (I personally favor the CTRL-4 shortcut to bring up a forge command selector menu, like what currently is done in JBoss Tools. >>>> That's all for now. This is all a prototype so now is the time to fix things if they need to chance. Please send your feedback! We want this to work as well as possible so are very open to feedback. >>>> >>>> >>>> -- >>>> Lincoln Baxter, III >>>> http://ocpsoft.org >>>> "Simpler is better." >>>> >>>> >>>> >>>> -- >>>> Lincoln Baxter, III >>>> http://ocpsoft.org >>>> "Simpler is better." >>> >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >> >