[
https://issues.apache.org/jira/browse/CLEREZZA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Story reopened CLEREZZA-282:
----------------------------------
Assignee: (was: Reto Bachmann-Gmür)
well it is still a problem for all the ssp in existence. For example debugging
an ssp is a big problem because one cannot set a stop point in the ssp from a
IDE. This issue cannot be closed (unless ssp are completely removed), but could
be pushed to "later". A few things that could happen:
- scala evolves some feature that allows templated
- IDEs find a way of integrating scala languages the way we would like
- ..
> .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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
