<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div style="-webkit-text-size-adjust: auto; ">Hi Thomas,</div><div style="-webkit-text-size-adjust: auto; "><br></div><div style="-webkit-text-size-adjust: auto; "><span style="background-color: rgba(255, 255, 255, 0); ">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. </span></div><div style="-webkit-text-size-adjust: auto; "><span style="background-color: rgba(255, 255, 255, 0); "><br></span></div><div style="-webkit-text-size-adjust: auto; "><span style="background-color: rgba(255, 255, 255, 0); ">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.</span></div><div><p style="margin: 0px; padding: 0px; "><span style="-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 255, 0);"><br></span></p></div><div style="-webkit-text-size-adjust: auto; ">Besides that, I'd really love to hear your ideas about the scaffold. This is something we are really looking forward to improving. </div><div style="-webkit-text-size-adjust: auto; "><br></div><div style="-webkit-text-size-adjust: auto; ">Best Regards,</div><div style="-webkit-text-size-adjust: auto; "><br></div><div style="-webkit-text-size-adjust: auto; ">George Gastaldi<br><br>Em 18/12/2012, às 10:01, A-ON Puls Referenz-User <<a href="mailto:thomas.fruehbeck@aon.at">thomas.fruehbeck@aon.at</a>> escreveu:<br><br></div><blockquote type="cite" style="-webkit-text-size-adjust: auto; "><div><!--?xml version="1.0"?-->
<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
Hello George,
<br>
sorry for late question, what "UI" do you mean?
<br>
If you mean a new scaffold or scaffold supporting API, I have quite a lot of ideas.
<br>
If you are talking of a wizard for Forge I have none (I dislike/h...) wizards).
<br>
<br>
Thomas
<br>
<br>
----- Ursprüngliche Nachricht -----
<br>
Von: ""
<ggastald redhat.com="redhat.com">
<br>
Erhalten: 12.12.2012 21:14
<br>
An: "forge-dev List"
<forge-dev lists.jboss.org="lists.jboss.org">
<br>
<blockquote>
<!--?xml version="1.0"?-->
<br>
Hello all,
<br>
<br>
We're designing a UI API that will serve as the base for the Addons
<br>
UI layer in Forge 2.0
<br>
<br>
I'd like some thoughts about what would be the best design strategy
<br>
for it.
<br>
I've created a JIRA issue to keep track:
<a href="https://issues.jboss.org/browse/FORGE-719" mce="mce" target="_blank">https://issues.jboss.org/browse/FORGE-719</a>
<br>
<br>
I kindly ask you to add your comments as what would be a good
<br>
feature to have, and additional requirements if necessary.
<br>
<br>
Best Regards,
<br>
<br>
<div class="moz-signature">
--
<br>
<b>George Gastaldi</b>
|
<i>Senior Software Engineer</i>
<br>
JBoss Forge Team
<br>
Red Hat
<br>
</div>
</blockquote>
</forge-dev>
</ggastald>
</div></blockquote><blockquote type="cite" style="-webkit-text-size-adjust: auto; "><div><span>_______________________________________________</span><br><span>forge-dev mailing list</span><br><span><a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/forge-dev">https://lists.jboss.org/mailman/listinfo/forge-dev</a></span><br></div></blockquote></body></html>