I wish to preface this by saying the 0.8 release is a giant step beyond the previous 0.6 versions and Iannix now achieves much of its original promise.

However, there is one aspect of the current infrastructure that just seems to me architecturally misguided: the project management / file navigation, update, and-save mechanism. Integrating project management functions into an Inspector is a worthy goal, but this implementation is incomplete and fragmented. One of the deficiencies that must be overcome is the forced and awkward interaction between the File Inspector and the File Menu. The mechanism invites disaster in several ways. Just one example: Invoke « New script », and whatever Current Project score is selected in the Inspector (and one is always selected) will go dirty and a subsequent save will wipe out previous work. One must always ensure a new score or duplicate score has been created and selected before loading anything else or invoking a script. Simply loading an example can make a previous score go dirty.

There is much precedent out there and I suggest that this part of the Iannix infrastructure be modeled after a more conventional and intuitive design.

Thanks for hearing my blather,
–Bob