From: Mark U. <ma...@cs...> - 2012-01-29 20:34:14
|
Leo, Good luck! This is really tricky, for Z. I remember that Petra and I had 3-4 different attempts at designing a section manager that kept track of versions of Z sections, or the dependencies between Z sections, so that you could update one section without reparsing the whole spec. But none of the designs we tried were both sound and efficient, so we eventually put that problem in the too-hard basket, and did something that only cached the standard toolkits, which we assumed would not change within a session. Some of this is documented in: trunk/session/src/main/java/net/sourceforge/czt/session/package.html It refers to several classes that have presumably since been deleted, but should be in the history of the SVN repository. It would have been more useful if we'd recorded the use cases of the situations that are difficult to handle! Cheers Mark On 28 January 2012 02:50, Leo Freitas <leo...@ne...> wrote: > Hi guys, > > we've been working in a way to start using the section manager > dependencies in order to avoid duplicated work (e.g., as is, we have > section manager per buffer in Eclipse and jEdit). > obviously, the trouble is that invalidation of "dirty" sections is crucial > in order to trust that the manager is in a correct state. This is necessary > mostly for large specs, given that rework > gets in your way (e.g., Mondex has about 20 sections; you would get 20 > section managers like a onion-layer of duplicated information - quite a > waste!). > > we started adding the various dependency relationships between various > parts of CZT. This is experimental and we will come to it soon. At the > moment, since no tool is using such > dependency information, it will make no difference. Andi n the end, if > there is any issue on trusting the dependency results, one can just return > to the (inefficient) section manager > per buffer approach. > > We will summarise soon what think the dependencies for each element > involve are. There is also the issue of which directions of dependency > should we worry about (upwards to > parents or downwards to children or both; as well as mutual dependencies > like ZSect and its OpTable). > > In the past, I come across a Z spec of a similar database of information > management, and ideally an implementation should have such a origin. > Are you aware of this spec? I couldn't find it.... Also, if you have any > thoughts or comments, please let us know ... > > Best, > Leo & Andrius > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > CZT-Devel mailing list > CZT...@li... > https://lists.sourceforge.net/lists/listinfo/czt-devel > |