I'll take a look at the archetype. Still, a simple page with some
example code would help a lot - Maven archetypes can be quite annoying
when the repository isn't directly available.

Also I don't know where to get the test-jars.

About that arrow character: Eclipse 3.4.x on Windows XP. Default
workspace characterset is set to UTF-8 and usually that works just
fine. It probably was only the class file viewer (with attached
source) that had troubles displaying the character. But worse, I still
don't know how to type that character, which makes it extremely
impractical.

Jörn

On Tue, Aug 18, 2009 at 3:40 PM, Antony Stubbs<[email protected]> wrote:
>
> Not sure how I missed this response.... Sorry!
>
> No there isn't, there's only the source code, the sample app, the archetype
> and the specification tests.
> But creating the Wicketstuff page is in the list of things to do, but it's
> not that close to the front of the queue unfort. If someone else wants to
> take a crack by my guess! Or even get me started with a template and I can
> fill in some details...
>
> The spec files are in the test-jars, but I guess wicketstuff projects aren't
> configured to deploy their test jars. Best thing to do is download the
> source, and have a look at the sample app.
>
> You should also be able to use the archetype by using a variation of (taken
> from the README for the archetype):
> "To use or test the archetype, run install, then either just run
> archetype:generate and select it from the list, or run a variant of:
>
> mvn archetype:generate -DarchetypeGroupId=org.wicketstuff.scala
> -DarchetypeArtifactId=wicket-scala-archetype -DgroupId=com.sharca
> -DartifactId=scalawicket-archetypetest -DarchetypeVersion=1.4-SNAPSHOT"
>
> note, if you have the wicketsuff repo in your settings.xml, you probably
> won't have to install the archetype yourself.
>
> The link to Nathan's page was only to give credit for the Fodel where credit
> was due - not as a source of documentation. Sorry for the confusion.
>
> Yes, the ⇒ is actually what the "=>" is supposed to be in Scala, and is a
> UTF8 character, which I'm sure would be supported by all modern editors. I'm
> surprised you can't see it properly. What OS and version of Eclipse are you
> viewing them with? I am toying around with ⇒ atm and haven't really reached
> a decision on which I prefer. But if it causes trouble for people, and it's
> an open library, then causing _less_ trouble for people is preferable :)
>
> Cheers,
> Antony.
>
> stubbisms.wordpress.com
> illegalargument.com
> sharca.com
>
>
> Jörn Zaefferer-2 wrote:
>>
>> Hi Antony,
>>
>> is there a website for the project with some documentation?
>>
>> You mention the specification files, but those aren't included in the
>> SNAPSHOT release. So all I have are some not-so-useful SDocs, your
>> hints here and a link to
>> http://technically.us/code/x/the-escape-hatch, which doesn't help
>> either.
>>
>> Also, when looking at the source files I see a lot of ⇒ icons, which
>> my Eclipse just displays as a little rectangle. That makes it somewhat
>> difficult to use those - could you stick with an ASCII charset?
>>
>> Jörn
>>
>> On Fri, Aug 14, 2009 at 6:53 PM, Antony Stubbs<[email protected]>
>> wrote:
>>> Hello People,
>>>
>>> Today, I am proud to announce that I have now uploaded the first version
>>> of
>>> the new Scala-Wicket Extensions.
>>>
>>> The project aims to be a central point for Scala related extensions to
>>> the
>>> Wicket framework.
>>>
>>> At the moment, the project consists of an Archetype, Sample application
>>> and
>>> Core libraries.
>>>
>>> The core libraries at this point consist of some useful implicit
>>> conversation functions (Scala -> Java list conversion, Closure -> Fodel
>>> conversion, etc... ScalaWicket.scala) a collection of simple extensions
>>> to
>>> existing components and the Fodel class. The Fodel class allows us to use
>>> closures and pass by name parameters in Scala to avoid some explicit
>>> construction of Models.
>>>
>>> For example:
>>> new SLabel("name", person.name )
>>> This actually constructs a Model which just like a Property Model looks
>>> up
>>> and re-evaluates the name property of the Person during each render time
>>> (i.e. this is a dynamic model, not a static model as it may appear to be,
>>> or
>>> would be if it were Java).
>>> Also:
>>> new SPropertyListView[String]("presentations", list, _.add(new
>>> SLabel("name", "asdp name")))
>>>
>>> There are a whole lot of examples in the Specification files, as the
>>> whole
>>> library as it stands is covered by Specs unit tests.
>>>
>>> It also includes SBT (simple build tool) code AND Maven build code (take
>>> your pick).
>>>
>>> I invite all those who are currently using Scala with Wicket to submit
>>> there
>>> odds and ends that make life easy for them - I'm sure there's a whole
>>> bunch
>>> of stuff out there!
>>>
>>> Special thanks to Stuq.nl
>>>
>>> P.s. it seems wicketstuff team city is stuck, so the SNAPSHOT won't be on
>>> the Wicket Stuff repo atm, but I'll try and get that sorted out asap.
>>>
>>> Maven signature:
>>>                <dependency>
>>>                        <groupId>org.wicketstuff.scala</groupId>
>>>                        <artifactId>wicket-scala</artifactId>
>>>                        <version>1.4-SNAPSHOT</version>
>>>                </dependency>
>>>
>>> Cheers,
>>> Antony Stubbs,
>>>
>>> sharca.com
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>
>
> -----
> ___________________________
>
> http://stubbisms.wordpress.com http://stubbisms.wordpress.com
> --
> View this message in context: 
> http://www.nabble.com/Announcing%3A-Scala-Wicket-Extensions-Project-tp24975011p25025121.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to