Changes for page WebObjects with Scala
Last modified by Ravi Mendis on 2011/05/10 02:10
From version 467.1
edited by Ravi Mendis
on 2010/12/24 00:39
on 2010/12/24 00:39
Change comment:
There is no comment for this version
To version 464.1
edited by Ravi Mendis
on 2010/12/24 00:36
on 2010/12/24 00:36
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -31,7 +31,7 @@ 31 31 32 32 ===== Caveats ===== 33 33 34 -Legacy tool support is often cited as a weak point. The [[Eclipse Scala plugin>>http://www.scala-ide.org]] has been found to be slow at times and sometimes buggy. 34 +Legacy tool support is often cited as a weak point. If your Application class is in Scala then you will have to create an Eclipse launch configuration manually. The [[Eclipse Scala plugin>>http://www.scala-ide.org]] has been found to be slow at times and sometimes buggy. 35 35 36 36 = WebObjects In Scala = 37 37 ... ... @@ -198,10 +198,16 @@ 198 198 199 199 After that, you may access the typical Scala collection methods directly on NSArray. This employs a feature of Scala known as implicit conversions to automagically cast a NSArray (a Java Iterable) into a Scala Iterable while leaving the actual object unchanged. Alternatively, you could generate an actual new scala.List instance by calling myNSArray.toList. 200 200 201 -== How to Add Scala to a WO Project (in Eclipse)==201 +== How to Add Scala to a WO Project == 202 202 203 203 {{include value="WOL:Adding Scala Support to a WOLips Project"}}{{/include}} 204 204 205 +{{note}} 206 + 207 +This is for Eclipse/WOLips IDE 208 + 209 +{{/note}} 210 + 205 205 == WO Scala Example == 206 206 207 207 The following example is an almost 100% Scala WO app. In reality it is a mixed Java/Scala app: