Echo the sentiments as well Chad.
It's a shame because I really wanted to expand on the test file I've been working on with the new features in Beta 2. I guess the behind the scenes changes didn't allow you to have time to write an import from previous version function.
Still keep up the good work guys this is going to be a great app for us code shy designers.
I'm sorry about the frustration you're having with old projects no longer working--we feel the pain internally in the team as well. As you noted, there have been many changes to the underlying beta Flex framework as well as other aspects of Catalyst projects since beta 1, and it would be difficult to create a robust conversion tool. Over time, as the framework and the tool both settle down, we should be able to achieve better compatibility, and of course once we ship 1.0 we will be committed to supporting FXPs from the shipping product in future versions.
Sorry about that,
nj, thanks for the reply. Just is the cautionary tale of being involved with a beta I supose. As a heads up however, do you foresee any significant structural changes moving forward that would negate b2's fxp files with future versions? Trying to set expectations internally.
Many thanks again
While we're not making any guarantees at this point, we're very much hoping that the final release will be able to open beta 2 projects . If so, you would most likely still hit a few snags that require redoing limited parts of the project, but you would at least be able to carry forward most of your work.
Once we do release, Catalyst 1.0 projects will definitely be able to open in the next release of Catalyst (1.x, 2.0, etc.).