[
https://issues.apache.org/jira/browse/CLEREZZA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935825#action_12935825
]
Reto Bachmann-Gmür commented on CLEREZZA-282:
---------------------------------------------
[quote]
SSPs are on the whole really clever idea: they get the same functionality as
JSP or ASP for very cheap, given Scala.
So that's really nice.
[/quote]
JSP and ASP allow to implement arbitrary functionality in it (even though with
JSP Model 2 this is discoraged), the scope of SSP is much more restricted, its
just about rendering a graphnode to a format like HTML.
So I think the disadvantages Tim Boudreau point to do not apply to SSP and I
don't exactly see what wicket could offer, an additinal templatings format?
> .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.
