We're trying to design the next Plugin API - as we call it in Forge 1. So we need a
programming model that lets people declare interactions in a manner that is agnostic of
the UI it will eventually be presented in.
One of our ideas is to have a visual UI representation for a plugin, so people could
easily write Forge addons with the input being prompted as a Window running from an
Eclipse plugin for example.
Besides that, I'd really love to hear your ideas about the scaffold. This is something
we are really looking forward to improving.
Em 18/12/2012, às 10:01, A-ON Puls Referenz-User <thomas.fruehbeck(a)aon.at>
sorry for late question, what "UI" do you mean?
If you mean a new scaffold or scaffold supporting API, I have quite a lot of ideas.
If you are talking of a wizard for Forge I have none (I dislike/h...) wizards).
----- Ursprüngliche Nachricht -----
Erhalten: 12.12.2012 21:14
An: "forge-dev List"
We're designing a UI API that will serve as the base for the Addons
UI layer in Forge 2.0
I'd like some thoughts about what would be the best design strategy
I've created a JIRA issue to keep track: https://issues.jboss.org/browse/FORGE-719
I kindly ask you to add your comments as what would be a good
feature to have, and additional requirements if necessary.
George Gastaldi | Senior Software Engineer
JBoss Forge Team
forge-dev mailing list