click-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian A. (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CLK-421) Move SourceViewer from examples to utils
Date Wed, 01 Apr 2009 16:27:13 GMT

    [ https://issues.apache.org/jira/browse/CLK-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12694606#action_12694606
] 

Adrian A. commented on CLK-421:
-------------------------------

> -1 for including this in Click. It adds no value to the target audience, the corporate
developer. 
This is practical for demos in first place, but for for commercial applications "in developer
mode" too, to quickly look at the target sources (like click-examples does). 
New developers in an existing project like this because they very quickly can connect the
visual think with the code, thus reducing the learning time.
(It is also possible to connect this with "open source in IDE" plug-ins)

This component is also useful in CMSes, Blogs, eLearning - in Admin mode, or any webapplication
that allow branding. It is incredible, but many of them (I mean commercial an expensive) show
only simple text and the uses are quite unhappy.

I also saw that there are a few similar components in the sandbox ( e.g. syntax highlight
code editor). Combined with that, a CMS would be even better.

Also as the reporter points out correctly in the issue description, the concurrent frameworks
don't have such a thing.

So, I think for the reasons above, it should be included since it's quite simple.


> Move SourceViewer from examples to utils
> ----------------------------------------
>
>                 Key: CLK-421
>                 URL: https://issues.apache.org/jira/browse/CLK-421
>             Project: Click
>          Issue Type: Improvement
>            Reporter: Demetrios Kyriakis
>            Priority: Minor
>         Attachments: SourceViewerPanel.diff
>
>
> Please move the SourceViewer utility class from click-examples to some util package inside
click because:
> - it is usable in more places than just click-examples, and users duplicate it all the
time, by copy and paste.
> - it could be used even in error reporting to display nice source code where errors appear.
> - even ClickClick has a duplicated class for SourceViewer
> - it would be much simpler to make other example webapplications moredeveloper friendly
if this
> class would be present in utils.
> - other concurrent frameworks don't have such an utility and display pure text :).
> Thank you,
> Demetrios.

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


Mime
View raw message