Re: [forge-dev] New Scaffolds

[gastaldi]

Exactly, I think I wasn't clear at first. Sorry about the confusion.

On 10-02-2014 10:14, Ivan St. Ivanov wrote:

Sorry, George, didn't get your original intention! You plan for

generating a scaffolding provider, not for scaffold[ed] project. My bad!

>

On Mon, Feb 10, 2014 at 2:13 PM, George Gastaldi <[e-mail]

<mailto:[e-mail]>> wrote:

    Hi Ivan,

    I'd expect it to generate a Maven project with a basic

    implementation of the

    org.jboss.forge.addon.scaffold.spi.ScaffoldProvider interface and

    also depending on the templates addon (with some basic templates

    available - perhaps JSF) . The idea is to that this generated

    addon project could be installed and used without modifications.

>

    On 10-02-2014 10:08, Ivan St. Ivanov wrote:

>>     Hi George,

>>

>>     What would you expect for this project type to generate besides

>>     the packaging type and maybe a couple of dependencies? Is this

>>     something like project-new-project+scaffold-setup?

>>

>>     BTW, not sure whether this is the right thread for the question:

>>     scaffold setup command is not available to my project, even

>>     though my ~/.forge/addons directory contains all the necessary

>>     scaffold jars.

>>

>>     Cheers,

>>     Ivan

>>

>>

>>     On Mon, Feb 10, 2014 at 12:02 PM, Vineet Reynolds Pereira

>>     <[e-mail] <mailto:[e-mail]>> wrote:

>>

>>

>>         Yeah, it might make sense. A bit too early to say if we need

>>         a scaffold project type in the New Project wizard.

>>

>>         We might support creation of new scaffold providers (like

>>         Aerogear) that extend existing scaffold providers (AngularJS),

>>         and I'm not sure if this can be supported via the wizard.

>>         Maybe it is better to revisit this once we've stabilized the

>>         programming model for scaffold providers sufficiently, to

>>         limit rewriting this wizard.

>>

>>         Vineet

>>

>>         -

---

Original Message -

---

>>         > From: "Sebastien Blanc" <[e-mail]

>>         <mailto:[e-mail]>>

>>         > To: [e-mail]

>>         <mailto:[e-mail]>

>>         > Sent: Monday, February 10, 2014 12:05:33 PM

>>         > Subject: Re: New Scaffolds

>>         >

>>         > On 02/10/2014 03:12 AM, George Gastaldi wrote:

>>         > > Hi everyone,

>>         > >

>>         > > I noticed an increasing demand in the scaffold usage

>>         (custom architectures,

>>         > > technologies,etc). I was thinking that it would be nice

>>         if we had a

>>         > > "Scaffold Project" type (similar to a maven archetype)

>>         allowing the

>>         > > creation of an addon project with available extension

>>         points to the

>>         > > scaffold addon.

>>         > > What do you guys think about it?

>>         > >

>>         > > Best Regards,

>>         > >

>>         > > George

>>         > > _______________________________________________

>>         > > forge-dev mailing list

>>         > > [e-mail] <mailto:[e-mail]>

>>         > > https://lists.jboss.org/mailman/listinfo/forge-dev

>>         > +1 Sounds good

>>         > We had some interesting discussions around this with Vineet

>>          last week

>>         > during JUDCon

>>         > _______________________________________________

>>         > forge-dev mailing list

>>         > [e-mail] <mailto:[e-mail]>

>>         > https://lists.jboss.org/mailman/listinfo/forge-dev

>>         >

>>         _______________________________________________

>>         forge-dev mailing list

>>         [e-mail] <mailto:[e-mail]>

>>         https://lists.jboss.org/mailman/listinfo/forge-dev

>>

>>

>>

>>

>>     _______________________________________________

>>     forge-dev mailing list

>>     [e-mail]  <mailto:[e-mail]>

>>     https://lists.jboss.org/mailman/listinfo/forge-dev

>

    _______________________________________________

    forge-dev mailing list

    [e-mail] <mailto:[e-mail]>

    https://lists.jboss.org/mailman/listinfo/forge-dev

>

>

_______________________________________________

forge-dev mailing list

[e-mail]

https://lists.jboss.org/mailman/listinfo/forge-dev

Sorry to bring that again, but, as a user, I don't see any difference

between code generation and scaffolding... so I don't understand why there

are several projects. If I want to create a n-tier architecture app with a

JSF and REST interface I would :

jpa-generate-entities-from-db

rest-generate-entdpoints-from-entity

jsf-generate-pages-from-entity

If I want to add a transactional EJB tier I would :

jpa-generate-entities-from-db

ejb-generate-services-from-entity

rest-generate-entdpoints-from-service

jsf-generate-pages-from-service

And if I want to see what an Angular front end looks like compare to JSF, I

would :

angular-generate-pages-from-service

Or if I quickly want to generate an Angular app from entities, I would :

angular-generate-pages-from-entity

I remember talking to Vineet and he had this idea of "you generate code"

and you "scaffold an entire project". If that could be the case, then we

would :

scaffold-ntier-architecture-from-db

or

scaffold-thin-client-from-db

....

My 2 cents

Antonio

2014-02-10 13:15 GMT+01:00 George Gastaldi <[e-mail]>:

Exactly, I think I wasn't clear at first. Sorry about the confusion.

>

On 10-02-2014 10:14, Ivan St. Ivanov wrote:

Sorry, George, didn't get your original intention! You plan for generating

a scaffolding provider, not for scaffold[ed] project. My bad!

>

On Mon, Feb 10, 2014 at 2:13 PM, George Gastaldi <[e-mail]>wrote:

>>  Hi Ivan,

>>

>> I'd expect it to generate a Maven project with a basic implementation of

>> the org.jboss.forge.addon.scaffold.spi.ScaffoldProvider interface and also

>> depending on the templates addon (with some basic templates available -

>> perhaps JSF) . The idea is to that this generated addon project could be

>> installed and used without modifications.

>>

>>

>>

>> On 10-02-2014 10:08, Ivan St. Ivanov wrote:

>>

>> Hi George,

>>

>>  What would you expect for this project type to generate besides the

>> packaging type and maybe a couple of dependencies? Is this something like

>> project-new-project+scaffold-setup?

>>

>>  BTW, not sure whether this is the right thread for the question:

>> scaffold setup command is not available to my project, even though my

>> ~/.forge/addons directory contains all the necessary scaffold jars.

>>

>>  Cheers,

>> Ivan

>>

>>

>> On Mon, Feb 10, 2014 at 12:02 PM, Vineet Reynolds Pereira <

>> [e-mail]> wrote:

>>

>>>

>>> Yeah, it might make sense. A bit too early to say if we need a scaffold

>>> project type in the New Project wizard.

>>>

>>> We might support creation of new scaffold providers (like Aerogear) that

>>> extend existing scaffold providers (AngularJS),

>>> and I'm not sure if this can be supported via the wizard. Maybe it is

>>> better to revisit this once we've stabilized the programming model for

>>> scaffold providers sufficiently, to limit rewriting this wizard.

>>>

>>> Vineet

>>>

>>> -

---

Original Message -

---

>>> > From: "Sebastien Blanc" <[e-mail]>

>>> > To: [e-mail]

>>> > Sent: Monday, February 10, 2014 12:05:33 PM

>>> > Subject: Re: New Scaffolds

>>> >

>>> > On 02/10/2014 03:12 AM, George Gastaldi wrote:

>>> > > Hi everyone,

>>> > >

>>> > > I noticed an increasing demand in the scaffold usage (custom

>>> architectures,

>>> > > technologies,etc). I was thinking that it would be nice if we had a

>>> > > "Scaffold Project" type (similar to a maven archetype) allowing the

>>> > > creation of an addon project with available extension points to the

>>> > > scaffold addon.

>>> > > What do you guys think about it?

>>> > >

>>> > > Best Regards,

>>> > >

>>> > > George

>>> > > _______________________________________________

>>> > > forge-dev mailing list

>>> > > [e-mail]

>>> > > https://lists.jboss.org/mailman/listinfo/forge-dev

>>> > +1 Sounds good

>>> > We had some interesting discussions around this with Vineet  last week

>>> > during JUDCon

>>> > _______________________________________________

>>> > forge-dev mailing list

>>> > [e-mail]

>>> > https://lists.jboss.org/mailman/listinfo/forge-dev

>>> >

>>> _______________________________________________

>>> forge-dev mailing list

>>> [e-mail]

>>> https://lists.jboss.org/mailman/listinfo/forge-dev

>>>

>>

>>

>>

>> _______________________________________________

>> forge-dev mailing [e-mail]://lists.jboss.org/mailman/listinfo/forge-dev

>>

>>

>>

>> _______________________________________________

>> forge-dev mailing list

>> [e-mail]

>> https://lists.jboss.org/mailman/listinfo/forge-dev

>>

>

>

_______________________________________________

forge-dev mailing [e-mail]://lists.jboss.org/mailman/listinfo/forge-dev

>

_______________________________________________

forge-dev mailing list

[e-mail]

https://lists.jboss.org/mailman/listinfo/forge-dev

--

Antonio Goncalves

Software architect and Java Champion

Web site <http://www.antoniogoncalves.org/> |

Twitter<http://twitter.com/agoncal>

| LinkedIn <http://www.linkedin.com/in/agoncal> | Paris

JUG<http://www.parisjug.org/>

| Devoxx France <http://www.devoxx.fr/>

[lincolnthree]

To address your concerns, Antonio. Perhaps you are right, and we should

forget about the UI commands provided with scaffold. Scaffold could merely

become the set of APIs that make it easier to develop and "generate" web

framework code for users.

On Tue, Feb 11, 2014 at 2:57 PM, Antonio Goncalves <

[e-mail]> wrote:

Sorry to bring that again, but, as a user, I don't see any difference

between code generation and scaffolding... so I don't understand why there

are several projects. If I want to create a n-tier architecture app with a

JSF and REST interface I would :

jpa-generate-entities-from-db

rest-generate-entdpoints-from-entity

jsf-generate-pages-from-entity

If I want to add a transactional EJB tier I would :

jpa-generate-entities-from-db

ejb-generate-services-from-entity

rest-generate-entdpoints-from-service

jsf-generate-pages-from-service

And if I want to see what an Angular front end looks like compare to JSF,

I would :

angular-generate-pages-from-service

Or if I quickly want to generate an Angular app from entities, I would :

angular-generate-pages-from-entity

I remember talking to Vineet and he had this idea of "you generate code"

and you "scaffold an entire project". If that could be the case, then we

would :

scaffold-ntier-architecture-from-db

or

scaffold-thin-client-from-db

....

My 2 cents

Antonio

>

>

>

2014-02-10 13:15 GMT+01:00 George Gastaldi <[e-mail]>:

Exactly, I think I wasn't clear at first. Sorry about the confusion.

>>

>>

>> On 10-02-2014 10:14, Ivan St. Ivanov wrote:

>>

>> Sorry, George, didn't get your original intention! You plan for

>> generating a scaffolding provider, not for scaffold[ed] project. My bad!

>>

>>

>> On Mon, Feb 10, 2014 at 2:13 PM, George Gastaldi <[e-mail]>wrote:

>>

>>>  Hi Ivan,

>>>

>>> I'd expect it to generate a Maven project with a basic implementation of

>>> the org.jboss.forge.addon.scaffold.spi.ScaffoldProvider interface and also

>>> depending on the templates addon (with some basic templates available -

>>> perhaps JSF) . The idea is to that this generated addon project could be

>>> installed and used without modifications.

>>>

>>>

>>>

>>> On 10-02-2014 10:08, Ivan St. Ivanov wrote:

>>>

>>> Hi George,

>>>

>>>  What would you expect for this project type to generate besides the

>>> packaging type and maybe a couple of dependencies? Is this something like

>>> project-new-project+scaffold-setup?

>>>

>>>  BTW, not sure whether this is the right thread for the question:

>>> scaffold setup command is not available to my project, even though my

>>> ~/.forge/addons directory contains all the necessary scaffold jars.

>>>

>>>  Cheers,

>>> Ivan

>>>

>>>

>>> On Mon, Feb 10, 2014 at 12:02 PM, Vineet Reynolds Pereira <

>>> [e-mail]> wrote:

>>>

>>>>

>>>> Yeah, it might make sense. A bit too early to say if we need a scaffold

>>>> project type in the New Project wizard.

>>>>

>>>> We might support creation of new scaffold providers (like Aerogear)

>>>> that extend existing scaffold providers (AngularJS),

>>>> and I'm not sure if this can be supported via the wizard. Maybe it is

>>>> better to revisit this once we've stabilized the programming model for

>>>> scaffold providers sufficiently, to limit rewriting this wizard.

>>>>

>>>> Vineet

>>>>

>>>> -

---

Original Message -

---

>>>> > From: "Sebastien Blanc" <[e-mail]>

>>>> > To: [e-mail]

>>>> > Sent: Monday, February 10, 2014 12:05:33 PM

>>>> > Subject: Re: New Scaffolds

>>>> >

>>>> > On 02/10/2014 03:12 AM, George Gastaldi wrote:

>>>> > > Hi everyone,

>>>> > >

>>>> > > I noticed an increasing demand in the scaffold usage (custom

>>>> architectures,

>>>> > > technologies,etc). I was thinking that it would be nice if we had a

>>>> > > "Scaffold Project" type (similar to a maven archetype) allowing the

>>>> > > creation of an addon project with available extension points to the

>>>> > > scaffold addon.

>>>> > > What do you guys think about it?

>>>> > >

>>>> > > Best Regards,

>>>> > >

>>>> > > George

>>>> > > _______________________________________________

>>>> > > forge-dev mailing list

>>>> > > [e-mail]

>>>> > > https://lists.jboss.org/mailman/listinfo/forge-dev

>>>> > +1 Sounds good

>>>> > We had some interesting discussions around this with Vineet  last week

>>>> > during JUDCon

>>>> > _______________________________________________

>>>> > forge-dev mailing list

>>>> > [e-mail]

>>>> > https://lists.jboss.org/mailman/listinfo/forge-dev

>>>> >

>>>> _______________________________________________

>>>> forge-dev mailing list

>>>> [e-mail]

>>>> https://lists.jboss.org/mailman/listinfo/forge-dev

>>>>

>>>

>>>

>>>

>>> _______________________________________________

>>> forge-dev mailing [e-mail]://lists.jboss.org/mailman/listinfo/forge-dev

>>>

>>>

>>>

>>> _______________________________________________

>>> forge-dev mailing list

>>> [e-mail]

>>> https://lists.jboss.org/mailman/listinfo/forge-dev

>>>

>>

>>

>>

>> _______________________________________________

>> forge-dev mailing [e-mail]://lists.jboss.org/mailman/listinfo/forge-dev

>>

>>

>>

>> _______________________________________________

>> forge-dev mailing list

>> [e-mail]

>> https://lists.jboss.org/mailman/listinfo/forge-dev

>>

>

>

--

Antonio Goncalves

Software architect and Java Champion

Web site <http://www.antoniogoncalves.org/> | Twitter<http://twitter.com/agoncal>

| LinkedIn <http://www.linkedin.com/in/agoncal> | Paris JUG<http://www.parisjug.org/>

| Devoxx France <http://www.devoxx.fr/>

_______________________________________________

forge-dev mailing list

[e-mail]

https://lists.jboss.org/mailman/listinfo/forge-dev

--

Lincoln Baxter, III

http://ocpsoft.org

"Simpler is better."