Wicket 'Mobile' Viewer

[Stephen Cameron <st...@gmail.com>]

Hi,

I am currently looking for more work with Apache Isis and some potential
clients all want a mobile version, or, the chance to have one down the
track.

I say to them its possible using the Restful Objects API as the basis of a
client layer, and I know AngularJS is popular for this now.

My question is to ask if it's maybe possible to make a Wicket 'Mobile'
Viewer?

The idea that I have is based on the layout.xml files being hierarchical
and so it would seem possible to be able to turn that into a 'drill-down'
mobile app kind of UI automatically too.

Maybe to add mobile specific elements in the layout.xml files.

Steve Cameron

Re: Wicket 'Mobile' Viewer

[Martin Grigorov <mg...@apache.org>]

Hi Stephen,


On Mon, May 29, 2017 at 2:58 AM, Stephen Cameron <steve.cameron.62@gmail.com
> wrote:

> Viewer Forecast is on the list for the Isis meetup.
>
> On Mon, May 29, 2017 at 10:17 AM, Stephen Cameron <
> steve.cameron.62@gmail.com> wrote:
>
> > Hi,
> >
> > I am currently looking for more work with Apache Isis and some potential
> > clients all want a mobile version, or, the chance to have one down the
> > track.
> >
> > I say to them its possible using the Restful Objects API as the basis of
> a
> > client layer, and I know AngularJS is popular for this now.
>

AngularJS was popular few years ago.
These days React and Vue.js are much more popular.
Tomorrow it might be something else...


> >
> > My question is to ask if it's maybe possible to make a Wicket 'Mobile'
> > Viewer?
>

The problem with Wicket is that it generates a complete HTML page and
writes it into the web response.
For mobile applications this might be a problem if the connection is slow.
If the network speed is good then there is no problem to use Wicket!
Bootstrap (the CSS framework used by the Wicket viewer) is mobile-first, so
it shouldn't be a problem to create responsive design.

The second problem is that Wicket is stateful, i.e. it will bind an HTTP
session as soon as you use a stateful component, like any Ajax
component/behavior.
This is a problem only if you have a LOT of simultaneous users.
For this kind of problem you can use:
1) session replication - i.e. several Tomcat/Jetty nodes could share a
common session storage (based on Hazelcast, Memcached, Redis, Cassandra,
...)
2) use stateless components and behaviors - since Wicket 7.4.0 it is very
easy to use stateless Ajax behaviors too


> >
> > The idea that I have is based on the layout.xml files being hierarchical
> > and so it would seem possible to be able to turn that into a 'drill-down'
> > mobile app kind of UI automatically too.
> >
> > Maybe to add mobile specific elements in the layout.xml files.
> >
> > Steve Cameron
> >
> >
>

Re: Wicket 'Mobile' Viewer

[Stephen Cameron <st...@gmail.com>]

Viewer Forecast is on the list for the Isis meetup.

On Mon, May 29, 2017 at 10:17 AM, Stephen Cameron <
steve.cameron.62@gmail.com> wrote:

> Hi,
>
> I am currently looking for more work with Apache Isis and some potential
> clients all want a mobile version, or, the chance to have one down the
> track.
>
> I say to them its possible using the Restful Objects API as the basis of a
> client layer, and I know AngularJS is popular for this now.
>
> My question is to ask if it's maybe possible to make a Wicket 'Mobile'
> Viewer?
>
> The idea that I have is based on the layout.xml files being hierarchical
> and so it would seem possible to be able to turn that into a 'drill-down'
> mobile app kind of UI automatically too.
>
> Maybe to add mobile specific elements in the layout.xml files.
>
> Steve Cameron
>
>