Going through my hastily hand written notes from that day... while "inside" the entity command, Ctrl-C does not work - user had to stop forge (red button) and start up again. I can jira these things if needed. this ctrl-c one is an issue with the eclipse integration - just like in the written tutorial, we promote only the eclipse-based version of forge so I have not tried the pure command line version. On Jul 6, 2012, at 12:05 PM, Burr Sutter wrote: Last Friday, while in Boston, we ran a few dozen people through our "Getting Started Tutorial" - a hands-on lab http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/ I made several notes on "gotchas" that students struggled with and one of them was forge's "list-commands". In the tutorial, we instruct the student to use the "entity" command and one student said "hey, this list-commands is broken, entity is not listed". and my immediate response was "yes, list-commands rarely tells me what I want" and the students response was "then how do I know what Forge offers me" and my response was "you have to read a document, like this tutorial we provided". The light-bulb turns on - we must have a usability problem :-) At this time, People mostly wish to use Forge to: - new project - new entity (with bean validations) - rest endpoints - jsf scaffolding - reverse engineer a database So, we need a better list-commands and better docs that "list out the commands". Based on current "docs", Forge only does a few things - https://docs.jboss.org/author/display/FORGE/Samples :-) _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

Actually that would be a 2.x release if commands (therefore scripts) are changing :-) And that would mean JBDS 6 as the "support vehicle" Is it possible to keep the older command syntax in place while pushing the new "API" instead? Allow for a "backward compatibility layer"? On Jul 6, 2012, at 1:45 PM, Lincoln Baxter, III wrote: Hey Burr, Awesome feedback as always. Definitely please file JIRAs for these and put them under the "Usability" component; this would be a huge help. Thanks very much! We had a good meeting at JBW and discussed many of these issues, so hopefully we will have some good changes coming for you soon. One thing we need to consider, though, is that changing commands and the names of commands may technically be a breakage of API compatibility with some scripts, so we might need to go up to a 1.1.x release to address this. ~Lincoln On Fri, Jul 6, 2012 at 12:16 PM, Burr Sutter <bsutter(a)redhat.com&gt; wrote: > Going through my hastily hand written notes from that day... > > while "inside" the entity command, Ctrl-C does not work - user had to > stop forge (red button) and start up again. > > I can jira these things if needed. > > this ctrl-c one is an issue with the eclipse integration - just like in > the written tutorial, we promote only the eclipse-based version of forge so > I have not tried the pure command line version. > > > On Jul 6, 2012, at 12:05 PM, Burr Sutter wrote: > > Last Friday, while in Boston, we ran a few dozen people through our > "Getting Started Tutorial" - a hands-on lab > http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/ > > I made several notes on "gotchas" that students struggled with and one of > them was forge's "list-commands". > > In the tutorial, we instruct the student to use the "entity" command and > one student said "hey, this list-commands is broken, entity is not listed". > > and my immediate response was "yes, list-commands rarely tells me what I > want" and the students response was "then how do I know what Forge offers > me" and my response was "you have to read a document, like this tutorial we > provided". > > The light-bulb turns on - we must have a usability problem :-) > > At this time, People mostly wish to use Forge to: > - new project > - new entity (with bean validations) > - rest endpoints > - jsf scaffolding > - reverse engineer a database > > So, we need a better list-commands and better docs that "list out the > commands". Based on current "docs", Forge only does a few things - > https://docs.jboss.org/author/display/FORGE/Samples :-) > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > > > _______________________________________________ > forge-dev mailing list > forge-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/forge-dev > > -- 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 _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev

I think that the functionality that the students requested is exactly the stuff like 'hint in Roo' that we wanted to implement in 2.0. Cheers! Ivan On Fri, Jul 6, 2012 at 10:20 PM, Lincoln Baxter, III < lincolnbaxter(a)gmail.com&gt; wrote: > Yeah we can try to do that :) > > > On Fri, Jul 6, 2012 at 2:54 PM, Burr Sutter <bsutter(a)redhat.com&gt; wrote: > >> Actually that would be a 2.x release if commands (therefore scripts) are >> changing :-) >> >> And that would mean JBDS 6 as the "support vehicle" >> >> Is it possible to keep the older command syntax in place while pushing >> the new "API" instead? Allow for a "backward compatibility layer"? >> >> On Jul 6, 2012, at 1:45 PM, Lincoln Baxter, III wrote: >> >> Hey Burr, >> >> Awesome feedback as always. Definitely please file JIRAs for these and >> put them under the "Usability" component; this would be a huge help. Thanks >> very much! >> >> We had a good meeting at JBW and discussed many of these issues, so >> hopefully we will have some good changes coming for you soon. One thing we >> need to consider, though, is that changing commands and the names of >> commands may technically be a breakage of API compatibility with some >> scripts, so we might need to go up to a 1.1.x release to address this. >> >> ~Lincoln >> >> On Fri, Jul 6, 2012 at 12:16 PM, Burr Sutter <bsutter(a)redhat.com&gt; wrote: >> >>> Going through my hastily hand written notes from that day... >>> >>> while "inside" the entity command, Ctrl-C does not work - user had to >>> stop forge (red button) and start up again. >>> >>> I can jira these things if needed. >>> >>> this ctrl-c one is an issue with the eclipse integration - just like in >>> the written tutorial, we promote only the eclipse-based version of forge so >>> I have not tried the pure command line version. >>> >>> >>> On Jul 6, 2012, at 12:05 PM, Burr Sutter wrote: >>> >>> Last Friday, while in Boston, we ran a few dozen people through our >>> "Getting Started Tutorial" - a hands-on lab >>> http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/ >>> >>> I made several notes on "gotchas" that students struggled with and one >>> of them was forge's "list-commands". >>> >>> In the tutorial, we instruct the student to use the "entity" command >>> and one student said "hey, this list-commands is broken, entity is not >>> listed". >>> >>> and my immediate response was "yes, list-commands rarely tells me what >>> I want" and the students response was "then how do I know what Forge offers >>> me" and my response was "you have to read a document, like this tutorial we >>> provided". >>> >>> The light-bulb turns on - we must have a usability problem :-) >>> >>> At this time, People mostly wish to use Forge to: >>> - new project >>> - new entity (with bean validations) >>> - rest endpoints >>> - jsf scaffolding >>> - reverse engineer a database >>> >>> So, we need a better list-commands and better docs that "list out the >>> commands". Based on current "docs", Forge only does a few things - >>> https://docs.jboss.org/author/display/FORGE/Samples :-) >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >>> >>> >>> _______________________________________________ >>> forge-dev mailing list >>> forge-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/forge-dev >>> >>> >> >> >> -- >> 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 >> >> >> >> _______________________________________________ >> forge-dev mailing list >> forge-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/forge-dev >> >> > > > -- > 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 > > _______________________________________________ forge-dev mailing list forge-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/forge-dev