On Wed, Dec 11, 2013 at 5:28 PM, Stephan Eggermont <stephan@stack.nl> wrote:
On 11 dec. 2013, at 21:09, Mariano Martinez Peck <marianopeck@gmail.com> wrote:

> I have a question. I think I reached a limitation. From what I understand, you put a div for the group and you use that ID for the AJAX. Since you use a close priotity between each description that belongs to the same group, then it is not a problem...all labels/controls end up inside that DIV for the group with the defined ID for the AJAX.
> I wonder....is there a way/workaround if I want to have the descriptions belonging to a group separated?  I know... probably I should use a better name since Group in magritte is for displaying them together etc. In my case is about "refresh connectivity" or "value dependency" or something like that, but not necessary they should be displayed one after the other one.

You can of course make the update much more complex, but we found (in what we build) simply refreshing either the whole page or a common parent sufficiently performant. If you connect arbitrary (nested) elements you need to avoid update cycles.


Ok, I understand. What I need is:

1) To not re-render all fields (I have many forms where I have many lists that are queried from a DB) for every single field modification.
2) I don't want to have to display some fields together in order to have them been re-rendered when one of them has been modified. 
3) I am not obligued to use #group: I can use something different, like #dependentsGroups or something like that

Any hint on how to implement that adapting your very cool stuff will be very much appreciated! 


 
Stephan


_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki



--
Mariano
http://marianopeck.wordpress.com