incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Reto Bachmann-Gmür (JIRA) <j...@apache.org>
Subject [jira] Commented: (CLEREZZA-282) .ssp handling in Integrated Development Environments (IDE)
Date Mon, 13 Sep 2010 13:01:42 GMT

    [ https://issues.apache.org/jira/browse/CLEREZZA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908771#action_12908771
] 

Reto Bachmann-Gmür commented on CLEREZZA-282:
---------------------------------------------

SSP are to Scala what JSP is to Java. Becaue of scala support for XML literal an SSP is closer
to the Scala class than with the java counterparts, in fact you only need to add some lines
on top of the ssp and some at the end to have a valid Scala class.

You can achieve everything you can do with SSP (and some more) also writing renderlets directly
in Scala rather than in SSP, this is possible with CLEREZZA-278 (to which I'll now add some
documentation and close it).

The main advantage of ssp compared with scala renderlets are:
- dynamic compilation (you can edit the ssp at runtime, no need to redeploy or manually compile)
- it's like a template: in most cases a valid xhtml page without doctype decalaration is a
valid SSP, you can star from add and add the actual contents inserting section between braces


What could be done for this issue:
- We could offer dynamic compiling also to proper scala renderlets
- we could offer a netbeans or eclipse plugin for SSP

> .ssp handling in Integrated Development Environments (IDE)
> ----------------------------------------------------------
>
>                 Key: CLEREZZA-282
>                 URL: https://issues.apache.org/jira/browse/CLEREZZA-282
>             Project: Clerezza
>          Issue Type: Wish
>         Environment: Netbeans, but other IDEs probably too
>            Reporter: Henry Story
>         Attachments: screenshot-1.jpg
>
>
> SSP stands for Scala Server Pages. The advantage of Scala Server Pages should be that
they are Scala. But they are not. As a result IDEs don't really work
> correctly with them as shown in the picture. This means that the IDE cannot function
as powerfully as it should. One should be able to jump to documentation
> for classes used for example, have completion working etc... Instead we have a very non
standard language, which does not even have the advantage of being
> XML (for which many editor modes exist), and for which there are very few developers
available.
> So either one should make the Scala be proper Scala or ...? 
> Btw.
> The hint for the red lines here say "Expected Class or Object definition"

-- 
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