click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Schellink (JIRA)" <>
Subject [jira] Commented: (CLK-347) Module support
Date Mon, 12 Jul 2010 23:00:50 GMT


Bob Schellink commented on CLK-347:

> So, should we finalize the definition of modularity that we are talking here?

I don't know anymore. I think this question just solidifies that we are not trying to solve
real world problems here, and are instead speculating and theorizing about problems that could
fit into the modularity concept. Unfortunately this leads to bloatware eg. features added
to the framework that nobody uses or that is too hard to use.

Regardless here is what is already possible with the framework today:

- split a large project into multiple pieces (modules) and assemble all the parts when building
the final product (this is normally achieved with ANT, no need for "modularity")
- split a large UI into "reusable" pieces that can be reused. This is already possible through
multi package[1] support:

  <pages package="com.mycorp.mod1">
  <pages package="com.mycorp.mod2">

Granted this does not provide drop-in "module" support. Instead its a one-liner, so its pretty
close. It also doesn't address multiple configurations, however multiple configurations won't
work anyway eg: mod1 depends on Velocity and mod2 depends on Freemarker. Click only supports
one Template Engine at a time.


> Module support
> --------------
>                 Key: CLK-347
>                 URL:
>             Project: Click
>          Issue Type: Improvement
>          Components: core
>            Reporter: Bob Schellink
> Add module support to Click core. Some code has been committed here: 
> Note that with the recent work done on CLK-343 the module code wont compile anymore.
> A related issue is: CLK-328

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message