I want to migrate from Flex 3.1 to Flex 3.5, but I can't find any useful release notes on the differences between the two. I found the official Adobe website but it is more focused on the difference between 2 and 3, and not different versions of 3. Can someone help me out?
Thanks
In theory there isn't a lot of difference. Have you tried to just change the SDK on your project(s) and then see what works or doesn't?
Msot of the issues you'll run into, I expect, will relate to your custom component development that extend the existing components. The Flextras AutoCompleteComboBox, for example, had issues because the way the drop down is handled in the Flex ComboBox changed from 3.4 to 3.5. Since our component is a highly customized ComboBox; we inherited this change which "Broke".
However, my experience is probably a fringe case as in the course of normal development you wouldn't be customizing things so heavily.
Try it and see.
Related
Is angulartics2 compatible with angular1.6
OR
Is angulartics compatible with angular2
Because I'm currently working with angular 1.6 and I plan to migrate to angular2 in the future, and I'm searching for a solution that is compatible with both
There's two "versions" available:
angulartics
and
angulartics2
As you can see, the first one is for Angular 1.x, where as the second one is for Angular 2/4/5.
I have not worked with either version, but my guess is that migrating your entire app from Angular 1.6 to Angular 2/4/5 will take a good amount of work anyways, so exchanging these plugins with one another shouldn't be that much of a problem.
So, in a way, no. This plugin isn't exactly the solution you need considering it is supposed to work in both versions. I highly doubt there's a solution available that will just work out of the box for both versions to be all honest.
I'm enjoying the Bootstrap tutorials here, but after the first two, I realize that it's working off a V1 version of Bootstrap, where the layout worked as a 16-column grid and things like the span-one-third class were still active.
I know I could download and use an old version of Bootstrap, but (a) I'm not that smart, and (b) I'm trying to adopt best practices early on by using a github fork.
I'm not sure what else this tutorial will differ on. I can kind of figure out the differences between a 16- and a 12-column grid, but is there anything in Bootstrap between 1.4 and 2.0 that will completely screw me up while I follow these tutorials?
Super crucial. There were a significant amount of changes from 1.4 to 2.0, as summarized here: http://twitter.github.com/bootstrap/upgrading.html
I would highlight being almost fully responsive as the most important change, but just about any other component has changed, providing better support for mobile devices and keeping up to date with new standards and changes in the industry.
By not upgrading to 2.0 you are limiting yourself from future updates to your framework, as most of the changes will break your current progress. Some of the tutorials are good to follow as a "get the idea and implement yourself" tutorial.
Don't stay behind technology just because you are comfortable. You won't be when you have no support for the issues you run into, which are probably fixed in 2.0 or some later version. Save your time now!
I know there is a built-in update framework inside AIR but finding valid code samples for the latest versions proves to be hard. Some code for simple updating (assuming ActionScript 3, AIR 2.7 and Flex 4.5) would be deeply appreciated (nothing fancy, default styles etc).
This is the code I used to get this working: http://www.adobe.com/devnet/air/articles/air_update_framework.html. It's a good overview (even down to doing a custom update window), and is trivial to implement.
I had many issues found in migration from Flex 3 to Flex 4. I had done some logic in flex 3 but while migrating the same code to flex4 it is not working. Please help me out how to do the exact migrating or have any tool for migrating the code from flex3 to flex 4.
There are many advantages of Flex 4, one of which is Skinning, which is a huge plus for code reuse but also separation of concerns (separate the view/styling from the component behavior). There's also FXG (mxml based vectors) that can be used with Catalyst to easily skin components from illustrator.
Flex 4 is definitely the future and what you should strive for, but it does bring forth a lot of changes, so the con here is that it's very hard to convert a Flex 3 app to Flex 4 without redoing some code. It's a different mentality altogether and it needs to be adhered.
There are no quick tool to convert your component logic.
On my expirience most of the things I had to fix on my project when migrated to Flex 4 were related to parts of code that were actually work arounds for some strange behaviour with scaling/resizing of components in Flex 3, which was resolved in Flex 4. Overly it wasn't hard, there are no major changes in logic, just improvements and some bugs fixed, and possibly few new bugs made :)
When migrating to Flex 4 it's not neccessary to change your components to Spark ones, you can still use your MX structure.
New components use a different layout, you build them a bit differently
* you cant use Spark's ComboBox/DropDownList as in MX, since you need IList objects as data provider
* Resize/Scale and measures work as they should now, in both MX and Spark components
* you can't add directly some of MX components to Spark containers as you could in Flex 3
* you use addElement instead addChild for Spark components
* in Flex 4 they introduced FTE, with superior text render quality, lifting the limit of 127px font size, but now if you embed fonts on runtime (I do) you have to use CFF flag
I think that migrating to Flex 4 worth the hassle, just if you decide to use the latest SDK build (4.5) you may encounter some issues, 4.1 is a safer call at the moment, tho I'm using 4.5 knowing of the risks.
I have an app built in flex 3.2, and would like to start using some spark components within that same app. Are there any pitfalls to look out for.
Is it possible to use the old 3.2 components in the same app or Will I have to rebuild them.
Would like to get the heads up from anyone that has done the same, before I make the plunge.
Thanks
This post has some pretty good info - Migrating to Flex 4
You may run into some small issues with mixing and matching Halo/Spark components when it comes to some of the layouts, but in general they work pretty well together side by side.
The major issue is CSS because the Spark components are less CSS-friendly than Halo.
=Ryan
AFAIK, custom components extending / based on Halo components of Flex 3.2 will continue to work as will the default Halo components.