i'm not so sure about that. i really don't think cloning is good. i think undo is at least capable of doing everything cloning does only with better perf. in fact, if we cloned the component models when we stored the undo information, it would be exactly cloning but with better performance. also, undo is a controllable operation, whereas cloning is not. we could, for example, let the user control how certain models get assigned/checked/processed during undo. that's not possible with cloning.
is there /anything/ cloning can do that undo can't do or do better? maybe i missed something, but i'm stumped.
Martijn Dashorst wrote:
Jonathan Locke wrote:
yeah, johan and eelco and i were just IM'ing and we also like gili's undo thing better so far. we've got a fairly concrete idea of how to implement it as well. i think someone should be able to get to this before i get there in an new experimental branch.
Undo is not *the* solution... it creates other unwanted effects, see my reply to Gili's requst... I think it is one option from a palette. Perhaps cloning *is* another.
Martijn
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
