Quickstart - CLK-531

[Bob Schellink <sa...@gmail.com>]

Hi Adrian,

Do you have any technical detail (or code) on the ClickStart project you mention on the wiki[1] and
in Jira[2]?

Are you planning  to build a command line tool (ala Roo) or Ant or something else?

Kind r3gards

Bob

[1]: https://cwiki.apache.org/confluence/display/CLICK/Click+2.4+Wishlist
[2]: https://issues.apache.org/jira/browse/CLK-531

Re: Quickstart - CLK-531

[Bob Schellink <sa...@gmail.com>]

On 4/10/2010 22:25, Adrian A. wrote:
> One questions that remains is where to host it?

This is a good fit for a Click subproject, similar to EclipseIDE and Velocity tools. There is
certainly enough development scope. This allows the project to have its own documentation,
versioning and release cycle and evolve independently without being constrained by Click itself.

I suggest developing in:

http://svn.apache.org/repos/asf/click/trunk/tools/clickstart/

> in:
> http://svn.apache.org/repos/asf/click/trunk/click/template/
> (where the actual quickstart is located)


Once ClickStart matures we can remove 'quickstart'.

Kind regards

Bob

Re: Quickstart - CLK-531

["Adrian A." <a....@gmail.com>]

> Just be careful with JAG as it's GPL and viral, so best not to look at their source code.
Of course. I just gave it as an example as a tool that allows custom 
templates too, that are grouped as a "project", so that at generation, 
the user needs to give as input only very few values if it's using the 
"defaults" (but many other tools allow this concept too).

E.g. CayenneModeler allows this too, but it's a little bit complicated 
to deal with custom code generation, and improve it to allow directly 
from CM to simply generate a Click based project.

So, the main idea Qu(/Cl)ickStart is to have a generic tree like 
structure of objects for the default values and for input values (for 
custom values too) in order to greatly simplify the template creation, 
thus allowing a quick and easy creation of custom templates too (e.g. 
from existing and successful project structures).

One questions that remains is where to host it?
in:
http://svn.apache.org/repos/asf/click/trunk/click/template/
(where the actual quickstart is located)
or in:
http://svn.apache.org/repos/asf/click/trunk/tools/standalone/
?

Since it has several small(except the first) modules:
/clickstart
/clickstart-cli
/clickstart-ant
?/clickstart-maven?
/clickstart-gui


Adrian.

Re: Quickstart - CLK-531

[Bob Schellink <sa...@gmail.com>]

Sounds good. Just be careful with JAG as it's GPL and viral, so best not to look at their source code.

Regards

Bob


On 3/10/2010 22:42, Adrian A. wrote:
>> Are you planning  to build a command line tool (ala Roo) or Ant or something else?
> Similar to AppFuse[1] and JAG[2] but Roo too, i.e. it should be possible to generate more than one
> project type from templates.
> There will be an API that will have wrappers to start the generation process from the command line,
> from ANT but from a Swing GUI too.
> 
> The main advantage of this approach would be that the API could be used from IDEs as well, to have a
> uniform generation among all solutions with minimal effort. Also when changes to the templates are
> needed (due to updates of libraries, or deprecation), having these changes in only one place could
> save allot of time.
> 
> Unfortunately it looks like I won't be able to release it for 2.3 final, but this issue it's on my
> top priority since it could save so much time when starting a new click based project.
> 
> Adrian.
> [1] http://appfuse.org/display/APF/Home
> [2] http://jag.sourceforge.net/
> 
> 

Re: Quickstart - CLK-531

["Adrian A." <a....@gmail.com>]

> Do you have any technical detail (or code) on the ClickStart project you mention on the wiki[1] and
> in Jira[2]?
>
> Are you planning  to build a command line tool (ala Roo) or Ant or something else?
Similar to AppFuse[1] and JAG[2] but Roo too, i.e. it should be possible 
to generate more than one project type from templates.
There will be an API that will have wrappers to start the generation 
process from the command line, from ANT but from a Swing GUI too.

The main advantage of this approach would be that the API could be used 
from IDEs as well, to have a uniform generation among all solutions with 
minimal effort. Also when changes to the templates are needed (due to 
updates of libraries, or deprecation), having these changes in only one 
place could save allot of time.

Unfortunately it looks like I won't be able to release it for 2.3 final, 
but this issue it's on my top priority since it could save so much time 
when starting a new click based project.

Adrian.
[1] http://appfuse.org/display/APF/Home
[2] http://jag.sourceforge.net/