You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2007/10/16 15:06:50 UTC
[jira] Created: (SLING-59) Make microsling code very easy to read
Make microsling code very easy to read
--------------------------------------
Key: SLING-59
URL: https://issues.apache.org/jira/browse/SLING-59
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: Bertrand Delacretaz
Priority: Minor
I think a big part of that is giving more importance to code that implements the basic concepts, as opposed to (possibly) boring support code that's here to make things work.
I have started moving stuff to subpackages named "helpers" in various parts to mark such support code.
We could also say that non-public classes are not "important", but that doesn't always work due to other constraints, classes sometimes have to be public even though they're not "interesting".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-59) Make microsling code very easy to read
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed SLING-59.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
Assignee: Bertrand Delacretaz
This issue can certainly be closed as many code submissions related to this issue have been done and placing helper classes in helper packages is now common habit. In addition microsling is now replaced by "full" Sling and the Launchpad.
> Make microsling code very easy to read
> --------------------------------------
>
> Key: SLING-59
> URL: https://issues.apache.org/jira/browse/SLING-59
> Project: Sling
> Issue Type: Improvement
> Components: microsling
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: 2.0.0
>
>
> I think a big part of that is giving more importance to code that implements the basic concepts, as opposed to (possibly) boring support code that's here to make things work.
> I have started moving stuff to subpackages named "helpers" in various parts to mark such support code.
> We could also say that non-public classes are not "important", but that doesn't always work due to other constraints, classes sometimes have to be public even though they're not "interesting".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.