[Swoop] SWOOP default save - bug fixed...+ latest changes

[Dean Allemang]

Aditya Kalyanpur wrote:

>On 10/12/05, Bijan Parsia <bparsia at isr.umd.edu> wrote:
>  
>
>>On Oct 12, 2005, at 11:57 AM, Miles, AJ (Alistair) wrote:
>>
>>    
>>
>>>Hi all,
>>>
>>>Couple of quick comments on latest SWOOP releases:
>>>
>>>The 2.3 alpha3 release doesn't lose the asterix next to classes after
>>>you do a save.
>>>
>>>Both 2.3 alpha3 and 2.2.1 have the annoying feature that they remember
>>>the last filename you used to save the ontology, irrespective of which
>>>ontology you change to in your workspace.  So you can be working on
>>>multiple ontologies, and if you press Control-s at the wrong moment
>>>you end up overwriting one ontology with another on the file system.
>>>It would be better if SWOOP remembered a filename for each ontology,
>>>as the target for a default save operation.
>>>      
>>>
>>Ah yes. I just noticed that. It brutally sucks and will be a priority
>>fix.
>>    
>>
>
>This bug has been fixed in the latest Swoop version in the SVN.
>Besides this bug, other recent fixes include:
>
>- bookmarks use physical URLs of ontologies (instead of logical URIs).
>This allows local ontology files to be bookmarked as well.
>- change log UI is now different..a treeTable is used to list
>changes..options have been added to undo, clear (remove old changes),
>serialize (in RDF/XML) and attach changes to an Annotea annotation
>directly
>- Pellet reasoner results are now cached..so each time you revert back
>to a processed ontology, the classified hierarchies are loaded from
>the cache directly.
>- Anonymous individuals are now displayed in the Alphabetical List
>
>I'm currently working on bugs piled up in the issue tracker.
>
>-Aditya
>_______________________________________________
>Swoop mailing list
>Swoop at lists.mindswap.org
>http://lists.mindswap.org/mailman/listinfo/swoop
>  
>
Not to be /too/ picky, but I have been warned before of the dangers of 
using nightly builds (not to mention SVN most recent versions).  Is 
there a plan for publishing a stable version with these bugs fixed?  I 
actually use SWOOP in my classes now, and I have to choreograph the 
students' work very carefully to get around these bugs (espcially that 
one where you can accidentally save to the wrong file!).  But the known 
bugs are usually better than the unknown ones.

Even if you call it alpha4, can we have a build release?