Vaadin viewer

[Jeroen van der Wal <je...@stromboli.it>]

Hi Dan,

I came across a project on SourceForge for a Vaadin viewer for Naked
Objects and you were one of the the committers. I was wondering what
the status is, perhaps it's something to revive? We did some
prototypes with Vaadin in another project and were very impressed with
the richness of the components. When building polished business
applications I would choose Vaadin over Wicket, especially for the
fact that you don't have to deal with all the layout and CSS stuff.
Building websites I would probably choose Wicket for it's flexibility,
the drawback of Vaadin is that if you want to change the design you
have to do a lot of work. But personally I know very little developers
who are skilled designers too. I have to say that I have no experience
with Wicket so my opinion is biased and might be totally incorrect.

Cheers,
Jeroen

[1] http://sourceforge.net/projects/vaadinobjects/

Re: Vaadin viewer

[Jeroen van der Wal <je...@stromboli.it>]

I certainly don't want to distract you from your priorities and agree
to work from back to front. The project doesn't need another half
baked viewer now so I'll probably invest some time in learning Wicket
and the viewer.

Thanks,
Jeroen

On Fri, Jun 1, 2012 at 10:27 AM, Dan Haywood
<da...@haywood-associates.co.uk> wrote:
> Hi Jeroen,
>
> yes, I created that project a few years back, [coincidentally at the same
> conference that I met Oliver Gierke, cf the thread on querydsl], when I
> first encountered Vaadin.  There were some guys from Vaadin showing off
> their framework on a stand, and I was impressed too.  I agree with your
> comments that Vaadin probably does fit better with intranet-style apps
> rather than internet apps. I sort-of hoped that I'd get some of the Vaadin
> community to contribute to building that viewer; I did elicit a few commits
> from one of their guys, but not much more.
>
> So, that code on the sourceforge project is definitely a starting point,
> but there's very little to salvage there.  Since that work, I worked on the
> Wicket viewer, and if we were to have a Vaadin viewer then I think the
> internal design of the Wicket viewer (chain of responsibility of view
> factories) is probably the way to go.
>
> Perhaps a starting point might be to start a project either on
> apache-extras.org, or on github, and I'll spend a bit of time getting a
> tiny walking skeleton going.  Then yourself or whoever can contribute in
> there, with a view to moving the codebase into Apache Isis "proper" as and
> when.
>
> For myself, my priorities right now are the JPA objectstore, then the
> Restful viewer, then probably finish off the Wicket viewer (just because
> it's pretty close to being done).  After that its probably a toss-up
> between a JDO object store or a Vaadin viewer.  All of these are big enough
> mini-projects to keep me off the streets!
>
> Dan
> ~~~~~~~~~
>
>
> On 31 May 2012 23:59, Jeroen van der Wal
> <jeroen@stromboli.it<javascript:_e({}, 'cvml',
> 'jeroen@stromboli.it');>
>> wrote:
>
>> Hi Dan,
>>
>> I came across a project on SourceForge for a Vaadin viewer for Naked
>> Objects and you were one of the the committers. I was wondering what
>> the status is, perhaps it's something to revive? We did some
>> prototypes with Vaadin in another project and were very impressed with
>> the richness of the components. When building polished business
>> applications I would choose Vaadin over Wicket, especially for the
>> fact that you don't have to deal with all the layout and CSS stuff.
>> Building websites I would probably choose Wicket for it's flexibility,
>> the drawback of Vaadin is that if you want to change the design you
>> have to do a lot of work. But personally I know very little developers
>> who are skilled designers too. I have to say that I have no experience
>> with Wicket so my opinion is biased and might be totally incorrect.
>>
>> Cheers,
>> Jeroen
>>
>> [1] http://sourceforge.net/projects/vaadinobjects/
>>

Vaadin viewer

[Dan Haywood <da...@haywood-associates.co.uk>]

Hi Jeroen,

yes, I created that project a few years back, [coincidentally at the same
conference that I met Oliver Gierke, cf the thread on querydsl], when I
first encountered Vaadin.  There were some guys from Vaadin showing off
their framework on a stand, and I was impressed too.  I agree with your
comments that Vaadin probably does fit better with intranet-style apps
rather than internet apps. I sort-of hoped that I'd get some of the Vaadin
community to contribute to building that viewer; I did elicit a few commits
from one of their guys, but not much more.

So, that code on the sourceforge project is definitely a starting point,
but there's very little to salvage there.  Since that work, I worked on the
Wicket viewer, and if we were to have a Vaadin viewer then I think the
internal design of the Wicket viewer (chain of responsibility of view
factories) is probably the way to go.

Perhaps a starting point might be to start a project either on
apache-extras.org, or on github, and I'll spend a bit of time getting a
tiny walking skeleton going.  Then yourself or whoever can contribute in
there, with a view to moving the codebase into Apache Isis "proper" as and
when.

For myself, my priorities right now are the JPA objectstore, then the
Restful viewer, then probably finish off the Wicket viewer (just because
it's pretty close to being done).  After that its probably a toss-up
between a JDO object store or a Vaadin viewer.  All of these are big enough
mini-projects to keep me off the streets!

Dan
~~~~~~~~~


On 31 May 2012 23:59, Jeroen van der Wal
<jeroen@stromboli.it<javascript:_e({}, 'cvml',
'jeroen@stromboli.it');>
> wrote:

> Hi Dan,
>
> I came across a project on SourceForge for a Vaadin viewer for Naked
> Objects and you were one of the the committers. I was wondering what
> the status is, perhaps it's something to revive? We did some
> prototypes with Vaadin in another project and were very impressed with
> the richness of the components. When building polished business
> applications I would choose Vaadin over Wicket, especially for the
> fact that you don't have to deal with all the layout and CSS stuff.
> Building websites I would probably choose Wicket for it's flexibility,
> the drawback of Vaadin is that if you want to change the design you
> have to do a lot of work. But personally I know very little developers
> who are skilled designers too. I have to say that I have no experience
> with Wicket so my opinion is biased and might be totally incorrect.
>
> Cheers,
> Jeroen
>
> [1] http://sourceforge.net/projects/vaadinobjects/
>