Hello,
My problem is that I have multiple SortableListViews, all of them work fine,
but I want to have the ability to drag the items between the different ListView
also. I have tried to work with SortableListViews an DragTargets but then I
can't sort the list furthermore I don't know how to le
vov: adding this behavior doesn't solve the problem. with this behavior the
ddc never reaches the "getDataGrid().setRowsPerPage(newSelection);" line in
the code.
I've remove the filter-form and toolbar to see if they affect this
situation, sadly they dont.
When the rows-per-page DDC is outside the toolbar (and outside the grid
markup) choosing a value will correctly change the DDC's model object and
then the grid is rendered again using the correct DDC int
Hello.
I have a problem:
1.There are 3 forms on the Page: GroupsForm, UsersForm, DocumentsForm.
Each of them reflects a Dcorrespoding Domain object and supposed to have a
Model.
2.Functionality:
Selecting a Group in GroupsForm should
force other 2 forms to show a list of corresponding objec
Do you use hollywood principle?
**
Marti
2010/6/27 Andrei Razin :
>
> Hello.
>
> I have a problem:
>
> 1.There are 3 forms on the Page: GroupsForm, UsersForm, DocumentsForm.
> Each of them reflects a Dcorrespoding Domain object and supposed to have a
> Model.
>
> 2.Functionality:
> Selecting a Gr
Martin.
Thanks for reply.
1. Yes, I think I do use "Hollywood principle". The children do not call
Parent.
So, I do not call Form method from the other Form (through Parent hierarchy)
2. I also do not have references to the Parent (Page, Panel) inside the
Form.
3. I try to synchronize forms thro
Hi!
> 1. Yes, I think I do use "Hollywood principle". The children do not call
> Parent.
I think you have it the wrong way around. The dependants should call
the parent to ask status. Otherwise you have the parents running all
around trying to find all the dependants. It's easier for the
dependan
Martin.
Thanks for clarification.
This will solve the problem for sure and I'll continue this way.
The only problem I can envision is - it will make the children not reusable.
They will have the references to the parent (Page or/and Panel)
and to use them on another page I have to modify the Fo
One more thing.
Just forgot to mention:
If I implement the proper interfaces in Parent objects, that will help to
make children component reusable.
Thanks again for the idea.
Andrei.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Dependent-Models-tp2270083p2270188
