[
https://issues.apache.org/jira/browse/CLK-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12836405#action_12836405
]
Joseph Schmidt commented on CLK-347:
------------------------------------
Any news on this "module support"?
I know that it is partially implemented, but can we please have a "full" module
support for Click 2.2.0?
I believe this would be the most important feature regarding high productivity
for Click: to be able to reuse not just components, but "modules" - i.e.
pages+templates+logic as standalone modules parts.
Now that I have made several small projects with Click (with older versions), I
see that there's allot of common functionality that I rather not
maintain/upgrade in every project, but have it as modules, some of them would
be even suitable as open source, e.g.:
- registration
- authentication
- acl
- dashboard
- recent activity/audit
- tags
- license management
- etc.
I believe this could be more like the Django plugins, where the developer only
configures/enumerates them, and the application just has them, except that in
Click the modules work in standalone mode too if provided a border template.
Thank you,
Joseph.
> Module support
> --------------
>
> Key: CLK-347
> URL: https://issues.apache.org/jira/browse/CLK-347
> Project: Click
> Issue Type: Improvement
> Components: core
> Reporter: Bob Schellink
>
> Add module support to Click core. Some code has been committed here:
> http://click.svn.sourceforge.net/viewvc/click/trunk/sandbox/sabob/plugin/
> 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.
