[
https://issues.apache.org/jira/browse/CLEREZZA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935801#action_12935801
]
Henry Story commented on CLEREZZA-282:
--------------------------------------
[[
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
]]
I have asked around in NetBeans land to see how easy/difficult it is to get
SSPs supported there. Probably not that much.
I think dynamic compiling for proper Scala renderlets would be good idea
anyway, if it is easy to do. Then people who
use other IDEs can also participate more easily.
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.
On the other hand JSP, ASP and SSPs all suffer from the following problems, as
my colleague Tim Boudreau pointed out
[[
The fundamental problem with all of these is that as soon as it is possible to
mix together code and markup
- You have a security problem (witness the recent Apache attack which got
Bugzilla to run a malicious JSP uploaded as an attachment)
- You cannot use standard editors (e.g. Dreamweaver, etc.) for the markup
- It is nearly impossible to ever have a thriving reusable component market,
because components become inherently non-portable
]]
That is it would be quite interesting to see how one could do something
equivalent to http://wicket.apache.org/ for Clerezza. Perhaps
one can integrate parts of that? Perhaps with our RDF vision Wicket can be
improved? My guess is that it's probably best to start with
something like SSP to get a good understanding of how Clerezza works, and then
think of how best to seperate markup and logic.
Henry
> .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.
