[ https://issues.jboss.org/browse/FORGE-2516?page=com.atlassian.jira.plugin... ] Antonio Goncalves updated FORGE-2516: ------------------------------------- Description: {quote} agoncal Last week I gave 2 talks only in Forge and 2 talks on CDI using Forge agoncal The interesting feedbacks I had were : agoncal * not enough scaffolding strategy agoncal As we've already talked, being able to scaffold different architecture is important gastaldi yes agoncal But also (and that was an interesting feedback) having more "business" scaffolding gastaldi you mean scaffolding for a homegrown architecture? gastaldi what do you mean? agoncal Typically, you want to scaffold an app, you go faces-scaffold agoncal But if you want an app with login, you could go faces-scaffold --with-login agoncal (that's a common use case) agoncal And the good old shopping cart came along : agoncal faces-scaffold --with-shopping-cart agoncal And of course : gastaldi hm agoncal faces-scaffold --with-shopping-cart --with-login gastaldi this looks very specific agoncal The idea is to be able to scaffold common use case (a bit like what you did with generating design patterns, but in a larger scale) gastaldi interesting gastaldi maybe we could split these use cases into scripts gastaldi run shopping-cart-faces.sh agoncal Yes. In fact what Forge does is generate a CRUD app based on Entities, but that could be just another option : agoncal faces-scaffold --with-crud agoncal Yes but how do we integrate it nicelly in the top menu bar ? gastaldi or something like: faces-scaffold --featuring LOGIN, SHOPPING_CART, CRUD agoncal Yes, "feature" is good naming agoncal And features would be available for a specific scaffolding : agoncal faces-scaffold --featuring LOGIN, SHOPPING_CART, CRUD gastaldi and we can make that pluggable agoncal rest-scaffold --featuring LOGIN, SECURITY {quote} was: agoncal Last week I gave 2 talks only in Forge and 2 talks on CDI using Forge 15:59:01 agoncal The interesting feedbacks I had were : 15:59:11 agoncal * not enough doc/tutorial 15:59:20 gastaldi yeah, that's a shame :( 15:59:21 agoncal * not enough scaffolding strategy 15:59:47 agoncal As we've already talked, being able to scaffold different architecture is important 15:59:53 gastaldi yes 16:00:07 agoncal But also (and that was an interesting feedback) having more "business" scaffolding 16:00:24 gastaldi you mean scaffolding for a homegrown architecture? 16:00:34 gastaldi what do you mean? 16:00:40 agoncal Typically, you want to scaffold an app, you go faces-scaffold 16:01:06 agoncal But if you want an app with login, you could go faces-scaffold --with-login 16:01:11 agoncal (that's a common use case) 16:01:20 agoncal And the good old shopping cart came along : 16:01:32 agoncal faces-scaffold --with-shopping-cart 16:01:35 agoncal And of course : 16:01:44 gastaldi hm 16:01:45 agoncal faces-scaffold --with-shopping-cart --with-login 16:01:45 kopcheski joined the channel. 16:02:44 gastaldi this looks very specific 16:02:45 agoncal The idea is to be able to scaffold common use case (a bit like what you did with generating design patterns, but in a larger scale) 16:02:53 gastaldi interesting 16:03:24 gastaldi maybe we could split these use cases into scripts 16:03:32 gastaldi run shopping-cart-faces.sh 16:03:48 agoncal Yes. In fact what Forge does is generate a CRUD app based on Entities, but that could be just another option : 16:03:56 agoncal aces-scaffold --with-crud 16:04:30 agoncal Yes but how do we integrate it nicelly in the top menu bar ? 16:04:30 gastaldi or something like: faces-scaffold --featuring LOGIN, SHOPPING_CART, CRUD 16:04:46 agoncal Yes, "feature" is good naming 16:05:09 agoncal And features would be available for a specific scaffolding : 16:05:15 agoncal faces-scaffold --featuring LOGIN, SHOPPING_CART, CRUD 16:05:21 gastaldi and we can make that pluggable 16:05:24 agoncal rest-scaffold --featuring LOGIN, SECURITY -- This message was sent by Atlassian JIRA (v6.4.11#64026)