Submitted by covingto on Fri, 06/03/2011 - 16:03
Today we tackled several issues in Core.
First changes were made to facilitate loading of older pipelines into the new core using the refined widget API. We are still making changes but in general hope that we will be able to allow users to have some fail-safes that will keep older schemas working. These fail-safes will likely be in place for some time, but we will encourage users to at least open all old schemas and resave to the new settings. Doing this will greatly help us to keep from being overwhelmed by legacy code.
Also there seemed to be a persistent error with the save load functions to load required packages. This was caused by the adoption of a package manager class instead of a module. This has been fixes so that loading will ask users to update their packages to match those in the saved session. The versioning system should work on a floating point system such that versions are compared as increasing values instead of static comparisons of equivalence. Doing this really helps with keeping everyone clear with what the most current version is especially if a person receives or is testing a version of a package that is not yet on the repository.
There is still a bit of an issue with templates on developer systems in that templates generated with the new version will not be compatible with older versions. I'll continue to work on this and there shouldn't be too much of a problem with updating all of the templates once we have the new version out.
We added the ability to set several template directories in the options menu and these are searched when the user refreshes the registry. A name tag was also added to the template dialog and this will allow template makers to add a more informative name than simply the file name (so any characters will be permitted).
We hope that these changes will help users to better interact with Red-R and to use templates.