> -----Original Message----- > From: peter royal [mailto:[EMAIL PROTECTED] > > How about having Framework linking to a page describing what happened > with it (incomplete wrt full component lifecycle, etc, etc), and > directing the user to either the "completed" framework ( as part of > Merlin ), or the Avalon 4 version? > > That would mitigate the need to prematurely bump versions in my eyes. > -pete
This is what I had hoped to work on last night but other things (ie- wife) came up. :) Basically there would be an "overview" page that would explain the status and history of the framework and then links to at least 4.1 and 4.2. The 4.2 page could then summarize the changes to the framework between 4.1 and 4.2 and then point users to the Merlin component specification docs. Meanwhile, the 4.1 docs would have more traditional framework information which I listed in what is now an ancient email in that started the "Regarding the Avalon Framework" thread. This said, I'm still partial to a bump to 5 but not set on it. It may not be a necessary move, but I believe it would be the wise one. J. Aaron Farr SONY ELECTRONICS STP SYSTEMS (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
