incubator-clerezza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henry Story (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CLEREZZA-282) .ssp handling in Integrated Development Environments (IDE)
Date Thu, 25 Nov 2010 18:45:14 GMT

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

Henry Story commented on CLEREZZA-282:
--------------------------------------

Thanks for the clarification on JSP and ASPs. 

As I understand Wicket is a descendant of a tool I used in 2001 with the Enhydra application
 server called XMLC. 
XMLC compiled  XHTML into Dom trees. The DOM trees were then manipulated by java code. The
aim of that 
was to completely separate the html and the logic. The programmers ended up doing the logic
in Java by 
getting hold of named DOM elements, and transforming those DOMS.

As a result  the artists could develop their XHTML nicely inside tools such as Dreamweaver,

or even just a bog standard web browser. The HTML and CSS they wrote would have no code in
it allowing them to
really focus on aesthetics. They could then put mini demo sites together, and those demo sites
would 
be used as is for the main site.

With SSP there is a lot of logic inside the template. Perhaps that is acceptable enough in
fact. I don't know. I'll know 
when I use it more. Last time I looked at Wicket it seemed to have too much magic in it for
my taste and made it 
a bit easy to create non RESTful sites. I am just pointing out that there is a radically different
way of thinking of 
templating languages that people tend to miss. It took me some time to see the value of XMLC.
But in any case
it's probably easier to get going with SSP for most people. We already have RDF newness. In
fact that is also 
a reason we should allow people (like me) to develop renderlets because it allows me to understand
how that
leads to SSPs, which is also a good way to get to know the system.



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