You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@clerezza.apache.org by "Reto Bachmann-Gmür (JIRA)" <ji...@apache.org> on 2011/01/26 00:01:50 UTC
[jira] Closed: (CLEREZZA-282) .ssp handling in Integrated
Development Environments (IDE)
[ https://issues.apache.org/jira/browse/CLEREZZA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Reto Bachmann-Gmür closed CLEREZZA-282.
---------------------------------------
Resolution: Not A Problem
Assignee: Reto Bachmann-Gmür
I think with typerendering.scala and the resolutio of CLEREZZA-410 it is no longer a problem, as renderlets written in scala offer the same advantages of ssp now and should be editable in every IDE that supports scala-
> .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
> Assignee: Reto Bachmann-Gmür
> 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.