You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@isis.apache.org by Dairo Correa Ramirez <da...@ticxar.com> on 2016/05/24 19:34:06 UTC
Questions
Good afternoon,
How I can hide or show depending form part of a selection or action?
Is it possible to make a flow of consecutive windows. Is a button back next
several pages?
--
[image: Logo]
Dairo Correa Ramirez
*Junior Development Analyst*
Tel: (57) 1 703 17 77
Cel: (57) 301 6588966
E-mail: dairo.correa@ticxar.com
Calle 93 # 19b - 66 Ofc 202
Bogotá D.C., Colombia
www.ticxar.com
[image: facebook]
<http://www.facebook.com/pages/Ticxar/446503822192581> [image:
twitter] <http://twitter.com/ticxar> [image: linkedIn]
<http://www.linkedin.com/company/ticxar>
Re: Questions
Posted by Dan Haywood <da...@haywood-associates.co.uk>.
Hi Dairo,
On 24 May 2016 at 20:34, Dairo Correa Ramirez <da...@ticxar.com>
> wrote:
... and apologies not to have replied before now on this question.
> How I can hide or show depending form part of a selection or action?
>
>
Hm, it's an interesting question. The Wicket viewer currently doesn't have
an awful lot of support for dynamic updating. But you could get a
reasonable simulation by having an action that returns the same object, and
then using either hideXxx() supporting methods or a subscriber to
hide/display the appropriate parts of the object.
Simplified:
public class MyClass {
private int x
public int getX() { ... }
public void setX(int x) { ... }
private int y;
public int getY() { ... }
public void setY(int y) { ... }
public boolean hideY() { return x<0; }
public MyClass updateX(int newX) {
setX(x);
return this;
}
}
with the above, if the "updateX" action is invoked and the value set to <0,
then the y property would disappear.
> Is it possible to make a flow of consecutive windows. Is a button back next
> several pages?
>
>
Yes, you could emulate this, using either a single view model acting as a
wizard, and holding state to toggle properties on/off; or have a succession
of objects that follow on from each other.
One issue, though, is that to modify any given page of the wizard view
model would open up a prompt, so the UI experience would likely feel
somewhat clumsy.
And, in any case, such wizards are very much against the original naked
objects philosophy: "problem solver over process follower".
But if you really want a wizard, then the Wicket viewer can be extended,
and/or there's also the option of writing a custom viewer against the REST
API surfaced by the RO viewer.
HTH
Dan
>
> --
> [image: Logo]
>
>
> Dairo Correa Ramirez
> *Junior Development Analyst*
> Tel: (57) 1 703 17 77
> Cel: (57) 301 6588966
> E-mail: dairo.correa@ticxar.com
> Calle 93 # 19b - 66 Ofc 202
> Bogotá D.C., Colombia
> www.ticxar.com
>
>
> [image: facebook]
> <http://www.facebook.com/pages/Ticxar/446503822192581> [image:
> twitter] <http://twitter.com/ticxar> [image: linkedIn]
> <http://www.linkedin.com/company/ticxar>
>