You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by Stephen Cameron <st...@gmail.com> on 2015/07/16 04:51:16 UTC

wicket page 'views'

Hi,

There are examples of use of different views in the todoapp (table,calendar
etc.). I would like to implement tabs in the Wicket Viewer and am wondering
if a similar views approach can be used at the top level?

That is, to have some standard view layouts that can be switched, maybe by
the user or by the developer alone.

Steve Cameron

Re: wicket page 'views'

Posted by Martin Grigorov <mg...@apache.org>.
Hi Steve,

I think you have discussed the same recently at
http://mail-archives.apache.org/mod_mbox/isis-users/201507.mbox/%3CCALJOYLFwqrDb5As4W51x1oVc=2-44EoaPrDZoQnqwD2_T2u7Mg@mail.gmail.com%3E
That's why I wasn't sure what is the difference with your new question.

As Dan explained there are ideas and tickets in JIRA about implementing
this but so far such functionality is not available.

Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Jul 16, 2015 at 11:03 AM, Stephen Cameron <
steve.cameron.62@gmail.com> wrote:

> Hi Martin,
>
> Thanks for the pointers, I will start my learning. But the suggestion was
> for a new feature of allowing views to be easly switched, either by the
> user in the way that 'Views' are within Eclipse, or by the developer via an
> attribute on the entity (a parameter of @DomainObjectLayout maybe?).
>
> So the views are merely layout views with the hierarchy of the class placed
> into parts of the view. (I am coming from XForms where parts of the view
> are bound to parts of the (data) model via 'group' elements (and group
> within group)).
>
> There is already an automatic layout process that assigns properties to
> groups, maybe this can be enhanced further?
>
> I should understand the present details and come back with more clarity.
>
> Steve C
>
>
>
> On Thu, Jul 16, 2015 at 4:48 PM, Martin Grigorov <mg...@apache.org>
> wrote:
>
> > Hi,
> >
> > Everything is possible!
> >
> > I do not understand what exactly you need, so here are some options:
> > - you can setup your own version of EntityPage that will be used for any
> > entity.
> > - if you need to have the tabs only for some specific entity types then
> you
> > could use a ViewModel and custom Panel that visualize them in the page's
> > content.
> > - you say "top level", so may be you want to provide a custom header for
> > the page with a tabbed panel under the menu. This is possible too.
> >
> > Martin Grigorov
> > Freelancer. Available for hire!
> > Wicket Training and Consulting
> > https://twitter.com/mtgrigorov
> >
> > On Thu, Jul 16, 2015 at 5:51 AM, Stephen Cameron <
> > steve.cameron.62@gmail.com
> > > wrote:
> >
> > > Hi,
> > >
> > > There are examples of use of different views in the todoapp
> > (table,calendar
> > > etc.). I would like to implement tabs in the Wicket Viewer and am
> > wondering
> > > if a similar views approach can be used at the top level?
> > >
> > > That is, to have some standard view layouts that can be switched, maybe
> > by
> > > the user or by the developer alone.
> > >
> > > Steve Cameron
> > >
> >
>

Re: wicket page 'views'

Posted by Stephen Cameron <st...@gmail.com>.
Hi Martin,

Thanks for the pointers, I will start my learning. But the suggestion was
for a new feature of allowing views to be easly switched, either by the
user in the way that 'Views' are within Eclipse, or by the developer via an
attribute on the entity (a parameter of @DomainObjectLayout maybe?).

So the views are merely layout views with the hierarchy of the class placed
into parts of the view. (I am coming from XForms where parts of the view
are bound to parts of the (data) model via 'group' elements (and group
within group)).

There is already an automatic layout process that assigns properties to
groups, maybe this can be enhanced further?

I should understand the present details and come back with more clarity.

Steve C



On Thu, Jul 16, 2015 at 4:48 PM, Martin Grigorov <mg...@apache.org>
wrote:

> Hi,
>
> Everything is possible!
>
> I do not understand what exactly you need, so here are some options:
> - you can setup your own version of EntityPage that will be used for any
> entity.
> - if you need to have the tabs only for some specific entity types then you
> could use a ViewModel and custom Panel that visualize them in the page's
> content.
> - you say "top level", so may be you want to provide a custom header for
> the page with a tabbed panel under the menu. This is possible too.
>
> Martin Grigorov
> Freelancer. Available for hire!
> Wicket Training and Consulting
> https://twitter.com/mtgrigorov
>
> On Thu, Jul 16, 2015 at 5:51 AM, Stephen Cameron <
> steve.cameron.62@gmail.com
> > wrote:
>
> > Hi,
> >
> > There are examples of use of different views in the todoapp
> (table,calendar
> > etc.). I would like to implement tabs in the Wicket Viewer and am
> wondering
> > if a similar views approach can be used at the top level?
> >
> > That is, to have some standard view layouts that can be switched, maybe
> by
> > the user or by the developer alone.
> >
> > Steve Cameron
> >
>

Re: wicket page 'views'

Posted by Martin Grigorov <mg...@apache.org>.
Hi,

Everything is possible!

I do not understand what exactly you need, so here are some options:
- you can setup your own version of EntityPage that will be used for any
entity.
- if you need to have the tabs only for some specific entity types then you
could use a ViewModel and custom Panel that visualize them in the page's
content.
- you say "top level", so may be you want to provide a custom header for
the page with a tabbed panel under the menu. This is possible too.

Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Thu, Jul 16, 2015 at 5:51 AM, Stephen Cameron <steve.cameron.62@gmail.com
> wrote:

> Hi,
>
> There are examples of use of different views in the todoapp (table,calendar
> etc.). I would like to implement tabs in the Wicket Viewer and am wondering
> if a similar views approach can be used at the top level?
>
> That is, to have some standard view layouts that can be switched, maybe by
> the user or by the developer alone.
>
> Steve Cameron
>