Thank you for the extensive overview! I wish you the best of luck and success
for this endeavour. Don't forget to let us know when a project website is up
and running :)
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Scala-Wicket-Help-and-Advice-tp3174601p3475536.html
STATUS
4/21/11
Waiting for final release of Wicket 1.5.
Status:
Scala-Wicket at Wicket version 1.5 RC3
About 50% of WicketStuff version 1.5 RC3 ported to Scala
(something to do while waiting for Wicket 1.5)
Scala-Wicket is about 1/2 the number of lines of code (or,
1
Is the port still in progress? Please write one or two lines about the
status.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Scala-Wicket-Help-and-Advice-tp3174601p3466499.html
Sent from the Forum for Wicket Core developers mailing list archive at
Nabble.com.
Yea, for a while now I have been concerned about taxing
the good graces of the dev mailing list with this thread;
going from pre-announcing and asking for advice, to
Scala IDEs, what Knuth meant, and whether or not Scala will
go main stream.
After porting 1.5 final over I will release the port,
pr
Don't get me wrong, I'm all about seeing a Wicket-like Scala-based
project (and would contribute to it), but that's not what we've been
debating here lately on this thread. If you guys want to talk about
coming up with a from-the-ground-up Scala-based, Wicket-inspired
project, then I'm all ears an
What about rewriting wicket into most wonderful tight functional scala style?
def : webserver {
homepage,
logoutpage,
onlinestore,
}
...
;)
**
Martin
2011/1/19 James Carman :
> I believe this conversation has gone enough off-course that it no
> longer belongs on this mailing list. We
I believe this conversation has gone enough off-course that it no
longer belongs on this mailing list. We're not discussing anything
related to Wicket anymore.
On Wed, Jan 19, 2011 at 11:57 AM, richard emberson
wrote:
>
>
> On 01/19/2011 07:22 AM, Martin Makundi wrote:
>>
>> The only thing that
On 01/19/2011 07:22 AM, Martin Makundi wrote:
The only thing that bugs me about scala is its flexibility of
accepting different kind of notation. It's that what was the
"downfall" of html: making complilers flexible to allow various human
input and as end result none of the browsers work correc
Yeah.. scala is like javazcribl ;)
2011/1/19 Gustavo Hexsel :
> Flexible syntax is a big part of it, but combined with operator override,
> it's a potential hole for understanding.
> They will never officially do that because one big use-case for scala is
> DSLs, in which this is an advantage (a
Flexible syntax is a big part of it, but combined with operator override,
it's a potential hole for understanding.
They will never officially do that because one big use-case for scala is
DSLs, in which this is an advantage (and the main scala team just got a
reasonably large funding from a gro
The only thing that bugs me about scala is its flexibility of
accepting different kind of notation. It's that what was the
"downfall" of html: making complilers flexible to allow various human
input and as end result none of the browsers work correctly because
the truth is only "in the eye of the b
Yea,
I have consistently advocated using Scala with strong coding
standards - standards that are actually believed in and enforced.
I have referred to it as OO Scala, Scala which is strong on the
Java-like Object-Oriented features plus functional programming
in-the-small, but refrains from using
Why people use C++ to facilitate making business a mess?
**
Martin
2011/1/19 Liam Clarke-Hutchinson :
> Hey mate,
>
> I code Java for my day job, and write my fun code in Scala. I just love the
> flexibility of Scala combined with the power to use all my existing Java
> libraries. That said,
> I
Hey mate,
I code Java for my day job, and write my fun code in Scala. I just love the
flexibility of Scala combined with the power to use all my existing Java
libraries. That said,
I don't see Scala overcoming Java anytime soon because it offers developers
_too much_ freedom. I had a real bad time
I originally mentioned the Kuhn book in the context of the politics of
change. Altering the focus, you brought up *the truth* as the view
held by those resisting change, which I believe is not the larger
insight to be gained from his book. It is still my contention that my
original interpretatio
One can always get better at following but tools must improve to be
better for building ;)
**
Martin
2011/1/11 Rodolfo Hansen :
> I guess Project Lombok could be extended for this.
>
> You would be inviting the same problems encountered by C++ with its
> multiple inheritance,
> and all that magi
I guess Project Lombok could be extended for this.
You would be inviting the same problems encountered by C++ with its
multiple inheritance,
and all that magic will probably make things harder to follow.
But; like all shotguns, it's everyone's responsibility where they aim,
lest they shoot the
On Tue, Jan 11, 2011 at 6:18 AM, Gustavo Hexsel wrote:
> Actually, in Scala it's idiomatic to skip the type on vals (unless they're
> complex structures or you NEED to declare the type as a higher-level, like
> it's a public val of a java collection and you want to enforce the
> interface).
>
I understand what you are saying, but I also think you are playing semantic
games here. By "truth", I was referring simply to objectively testable
results (the scientific method), not opening up a philosophical discussion
on the nature of truth. But in any case, there are certainly no objectively
Actually, in Scala it's idiomatic to skip the type on vals (unless they're
complex structures or you NEED to declare the type as a higher-level, like
it's a public val of a java collection and you want to enforce the
interface).
Also, if you type "new Model()" and do an insert-variable while i
I am sorry, but I can not disagree with you more about Kuhn's "The
Structure of Scientific Revolutions". Its about resistance to change
and not scientific truth and, as such, it has generally applicable.
At its crudest, its about the old, vested guard being unwilling and/or
unable to move with th
Biggest thing I miss in IntelliJ when coding Scala (I write Wicket in Java
for my dayjob) is my autocompletion of types. In Java you can type in
"IModel foo = new" and hit Ctrl + shift + space and it'll provide a
list of all types that subclass IModel, but for the time being (IntelliJ
10, build 99
>>> Either way, you have to put logic somewhere that tries to figure out
>>> what the heck you want to borrow and then figure out where the heck to
>>> get it.
>>
>> If it is done at compile time you don't need "messaging" logic. It
>> would be uniquely defined what you can get.
>
> Please explain.
On Sat, Jan 8, 2011 at 4:19 PM, Martin Makundi
wrote:
>>
>> Either way, you have to put logic somewhere that tries to figure out
>> what the heck you want to borrow and then figure out where the heck to
>> get it.
>
> If it is done at compile time you don't need "messaging" logic. It
> would be un
Hi!
> public T borrowObject(Class objectType)
>
> where you can do
>
> Pencil p = man.borrowObject(Pencil.class);
>
> Either way, you have to put logic somewhere that tries to figure out
> what the heck you want to borrow and then figure out where the heck to
> get it.
If it is done at compile t
On Sat, Jan 8, 2011 at 2:59 PM, Martin Makundi
wrote:
>
> It should be possible to say that "man will proxy by default all get
> methods of his belongings", It should be possible to say that "bag
> will proxy by default all get methods of his belongings". Same with
> pencil casing. In such situati
Hi!
> You would use a more domain-oriented design approach. Setters/getters
> are merely used because of all the frameworks that support (and
> expect) them. Why do you care where the man is carrying his pencil?
> Perhaps he's keeping it in his sock. All you want to do is ask the man
> object fo
On Sat, Jan 8, 2011 at 1:25 PM, Martin Makundi
wrote:
>>> What I hate about java is its one-dimensionality... ehh.. say you have:
>>>
>>> object man
>>> object man carrying bag
>>> bag carrying pencil case.
>>>
>> This isn't a Java problem. This is a design problem.
>
> How would you workaround t
>> What I hate about java is its one-dimensionality... ehh.. say you have:
>>
>> object man
>> object man carrying bag
>> bag carrying pencil case.
>>
> This isn't a Java problem. This is a design problem.
How would you workaround the design assuming you cannot change the
releations between the o
On Sat, Jan 8, 2011 at 1:07 PM, Martin Makundi
wrote:
>
> What I hate about java is its one-dimensionality... ehh.. say you have:
>
> object man
> object man carrying bag
> bag carrying pencil case.
>
> Now I want the man to hand me the pencil, I must implement:
> * man.getpencil->man.getbag.getpe
> Analysis is the a background process that parses the file and highlights
> errors, warnings, etc while you type. Eclipse has the same, though the name
> may be different. It's slow in Scala, like compilation is.
If it is slow then it is pain. Computer speeds might enhance faster than ides ;)
Analysis is the a background process that parses the file and highlights
errors, warnings, etc while you type. Eclipse has the same, though the name
may be different. It's slow in Scala, like compilation is.
Yes, it gives you context help. It's very helpful with a caveat: in
Scala, there a
Since scala is statically-typed, the ide can (and does) give you contextual
help very easily
On Jan 8, 2011 2:21 AM, "Martin Makundi"
wrote:
>> But it will do the right thing about 90% of the time. you'll
subconsciously
>> work around 4 or 5% of the rest that doesn't work, and the remaining 5-6%
> But it will do the right thing about 90% of the time. you'll subconsciously
> work around 4 or 5% of the rest that doesn't work, and the remaining 5-6%
> will irritate you.
I am used to coding 90% using context help with eclipse (ctrl+space).
I am a fast writer but that speeds up my coding by 1
it's not 100% of Java's level,mostly cause Scala is a much more complex
language.
But it will do the right thing about 90% of the time. you'll subconsciously
work around 4 or 5% of the rest that doesn't work, and the remaining 5-6%
will irritate you.
That's my perception, of course...
Among
Define complete.
On Sat, Jan 8, 2011 at 7:52 AM, Martin Makundi <
martin.maku...@koodaripalvelut.com> wrote:
> Nice or complete?
>
> **
> Martin
>
> 2011/1/7 Jonathan Locke :
> >
> > Have you checked out IDEA? My Scala friends tell me it has pretty nice
> Scala
> > support.
> >
> > Jon
> >
> > "L
Nice or complete?
**
Martin
2011/1/7 Jonathan Locke :
>
> Have you checked out IDEA? My Scala friends tell me it has pretty nice Scala
> support.
>
> Jon
>
> "Less is more."
> http://www.amazon.com/Coding-Software-Process-Jonathan-Locke/dp/0615404820/
>
> --
> View this message in context:
> htt
Have you checked out IDEA? My Scala friends tell me it has pretty nice Scala
support.
Jon
"Less is more."
http://www.amazon.com/Coding-Software-Process-Jonathan-Locke/dp/0615404820/
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Scala-Wicket-Help-and-Advice-tp3174
I would adopt scala immediately if it had all the IDE tools Java has
with equal reliability (amount of showstopper/awkward bugs).
So guess it's just a matter of time, if nobody comes up with something better.
Lots of people are taught into coding java (as if that helps ;), so
one day when people
Kuhn's "The Structure of Scientific Revolutions" has to do with people
denying *the truth* when there are radical paradigm shifts in knowledge. I
hardly think Scala qualifies for this analogy. Most of what Scala does has
already been done in one form or another. What it represents is the
applicati
That signature binds the function call to the function call expected in
the listview (i.e. the function itself is the parameter, not the results).
This means that the myService.list function is called only when the model
is evaluated, not when the listview is created.
On Thu, Jan 6, 2011 at
I know of several other Apache projects like Camel, ActiveMQ, ServiceMix that
happily look at projects like http://hawtdispatch.fusesource.org/ as well as
integrate Scala
and of course use them as they were written by Apache people, they just used
Scala to solve problems
in an elegant manner.
On Thu, Jan 6, 2011 at 7:24 PM, Gustavo Hexsel wrote:
> One of the cool things about scala is that you could have a model concept
> without a model class. You just need to receive 2 functions, a setter and a
> getter (or just a setter for read-only models). So for instance a ListView
> could ha
Everyone has opinions, myself included.
Curious the mention of Lift. It highlights Scala's
"functional goodies and type classes" which is certainly the
wrong approach - more in line with being less clear and less
simple. It is actually recommended that a Ruby programmer
would have a easier time
A sympathetic voice on the Wicket mailing list, greetings.
I don't know if you have followed it all but I have ported
Wicket to Scala, replaced the Java collections with Scala
collections, pushed the IModel[T] strong typing down to the
Component object and have plans for more changes. But,
I wante
I'll have to say I looked at Lift, and although it was greatly improved
since 1.0, it doesn't have the awesome separation of concerns that wicket
does. Even in the tutorial, the markup and the templates leak into each
other. Wicket's greatest asset was always IMO the fact that the HTML itself
c
Not so sure that doing a simple fork of Wicket into Scala is such a great
idea. And at the end of the day you probably couldn't call it Wicket without
Apache permission, which seems unlikely. But creating a Wicket-inspired
framework in Scala sounds like a good idea to me. Have you taken a look at
Richard,
This would effectively result in Java code translated directly to
Scala, pretty naively.
>From what you describe, you have already manually done much better than that.
As you have already hinted at in your previous posts, one of the key
points of this would be to take advantage of the f
I've got to try it!
On Jan 5, 2011 6:10 PM, "Gerolf Seitz" wrote:
>>
>> Is this in IntelliJ IDEA?
>>
>>
> yes
>
>
>> On Wed, Jan 5, 2011 at 6:04 PM, Gerolf Seitz
>> wrote:
>> > It's cmd+shift+G (OSX) and it works quite well ;)
>> >
>> > On Wed, Jan 5, 2011 at 11:55 PM, Justin Lee
>> wrote:
>> >
So there is an IDE that you can point at a directory tree and
tell it to convert all of the Java files to Scala files.
Does it do a 100% conversion, 90%, 50% or 10% (on average)?
Do you have a link to a page documenting this feature?
Thanks
Richard
On 01/05/2011 03:04 PM, Gerolf Seitz wrote:
It
>
> Is this in IntelliJ IDEA?
>
>
yes
> On Wed, Jan 5, 2011 at 6:04 PM, Gerolf Seitz
> wrote:
> > It's cmd+shift+G (OSX) and it works quite well ;)
> >
> > On Wed, Jan 5, 2011 at 11:55 PM, Justin Lee
> wrote:
> >
> >> You can paste a java class into a .scala file and it'll autoconvert.
> >> th
Is this in IntelliJ IDEA?
On Wed, Jan 5, 2011 at 6:04 PM, Gerolf Seitz wrote:
> It's cmd+shift+G (OSX) and it works quite well ;)
>
> On Wed, Jan 5, 2011 at 11:55 PM, Justin Lee wrote:
>
>> You can paste a java class into a .scala file and it'll autoconvert.
>> there's a shortcut keystroke, too
It's cmd+shift+G (OSX) and it works quite well ;)
On Wed, Jan 5, 2011 at 11:55 PM, Justin Lee wrote:
> You can paste a java class into a .scala file and it'll autoconvert.
> there's a shortcut keystroke, too, but i don't remember what it is.
>
> On Wed, Jan 5, 2011 at 10:40 AM, richard emberson
You can paste a java class into a .scala file and it'll autoconvert.
there's a shortcut keystroke, too, but i don't remember what it is.
On Wed, Jan 5, 2011 at 10:40 AM, richard emberson <
richard.ember...@gmail.com> wrote:
> No IDE, I use Vim. Also, my build environment is Ant-based
> using sca
No IDE, I use Vim. Also, my build environment is Ant-based
using scalac and javac.
Of course, what I was doing was porting from Java to Scala.
To that end I've got some 400 Vim scripts that aid in the
port. For instance,
:g/final \([a-zA-Z]\+\) \([a-zA-Z]\+\)\[\]\s*=/s//val \2: Array[\1] =/g
co
On Wed, Jan 5, 2011 at 9:38 AM, Juergen Donnerstag <
juergen.donners...@gmail.com> wrote:
> Cool. May I ask which tools (IDE) you've been using and what your
> experience with these tools has been.
>
#scala suggests IDEA 10 + SBT plugin as the most mature one.
>
> -Juergen
>
> On Wed, Jan 5, 20
Cool. May I ask which tools (IDE) you've been using and what your
experience with these tools has been.
-Juergen
On Wed, Jan 5, 2011 at 2:34 AM, Jeremy Thomerson
wrote:
> On Tue, Jan 4, 2011 at 5:15 PM, richard emberson > wrote:
>
>> Dev Wicketers,
>>
>> What: I have ported Wicket to Scala
>>
On Tue, Jan 4, 2011 at 5:15 PM, richard emberson wrote:
> Dev Wicketers,
>
> What: I have ported Wicket to Scala
>A couple of months ago I took a 1.5 snapshot and ported to Scala.
>This encompasses all of the source and test code. As successive 1.5
>snapshots were released, I ported t
I haven't had time to read all of this (hard to get through it all on
my phone), but I don't think that mere "port" of Wicket to Scala is
what is needed. I'd rather see a project built for Scala from the
ground up based on some of the concepts from Wicket. Wicket wasn't
designed with a functional
Richard,
This is an interesting idea that several people have discussed over
the last few years. I congratulate you on having taken it so far and
look forward to seeing your implementation.
As long as it can evolve in a way that can not do any harm to Wicket
(ie the quality is exceptional, the co
60 matches
Mail list logo
