<?xml version="1.0"?>
<html>
<head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type"/>
</head>
<body>
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>
</body>
</html>