From: <fra...@us...> - 2009-03-23 15:31:00
|
Revision: 1315 http://javapathfinder.svn.sourceforge.net/javapathfinder/?rev=1315&view=rev Author: frankrimlinger Date: 2009-03-23 15:30:57 +0000 (Mon, 23 Mar 2009) Log Message: ----------- Fixed EZ bug, and MangoRCP came online. The entire functionality of mango is now accessible via the Rich Client Platform. For now this is just smoke and mirrors as the bulk of the gui is still pure Swing, but at least now there is a plausible path to deployment. It remains to have something to deploy. Here is guess of how this will play out: Must finish stable rewriting update, then complete the test sessions, rebuild the System library sessions. This really should be done in a few weeks. Then there will be a big effort to replace the java bytecode model with the superior version in the jpf code base. Three months Then the mango model has to be reworked to generate artifacts capable of guiding the jpf state transition mechanism. Six months Invariant detection needs to get a boost from the jpf backtracking mechanism. Three months Bundling as a distributable Eclipse plugin. Three months. Making mango "disappear" into the Eclipse debugging workflow. Don't quite know what this means yet because there are a few things that just won't go away, so six months to a year. At this point, the tool should be able to generate theorem prover artifacts and English language specification for input java code, requiring only a reasonable amount of human guidance. Modified Paths: -------------- branches/mango/MangoRCP/Mango/src/mango/workstation/Workstation.java This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |