I've been tasked with maintaining some existing flex 4.6 projects and am wanting to future proof them for the latest browsers. Should I move the projects over to Apache flex? If so what do I need to do to make these existing projects compatible with Apache flex?
No, you don't need to migrate these projects to Apache Flex.
Flex 4.6 projects can still be built and deployed; they just don't have the latest SDK changes. Your projects will remain compatible with future Flash Player versions.
The only reason to update to Apache Flex at this point is if you need features introduced in a later version of the Flex SDK.
Recent versions of the Apache Flex SDK have newer features, a large number of bug fixes, have been tested with the latest version of Flash Player, and in general have better performance and consume less memory than Adobe Flex 4.6.
So while Apache Flex is not required to run in the latest browsers you stil may want to consider moving to Apache Flex for these reasons.
My experience is with Flex/AIR desktop apps, I migrated using the Apache Flex installer to download latest SDK and AIR, then in the IDE you need to add the new SDK and select it. I did not had bugs or problems when I upgraded to latest versions(but you may encounter bugs or differences so you need to do some testing)
Related
I was looking for some NuGet updates about my project libraries. I see that there are a lot of Microsoft libraries update to v5.0.0.
Based on my knowledge I think these are new dependencies released with .Net 5.0 and I'm not sure that I can update these libraries to latest version using .Net Core 3.1 project.
Can I update to v5.0.0 libraries even if I'm using/building a .Net Core 3.1 project?
Unfortunately, you cannot update many of these newest Nuget packages to 5.0. The reason being is that the newest Nuget package versions are written primarily for .NET 5, and often times Nuget Package Manager will even prevent you from installing them since there are differences in the APIs. With that said, there may be a few spots where it will allow the installation, but I wouldn't recommend it if you plan to keep the application on .NET Core 3.1. Most likely it could cause some inconsistencies that would be hard to debug. Proceed with caution, or upgrade your projects to .NET 5.
I just finished the same. I had 3.1 core application with a lot of 3.1 and NET Standard2.0 libraries projects and just updated all these libraries to the version 5. All libraries were working ok, I could compile them. But I couldn't compile my main Web application. It started to give some strange errors that some staff needs .net5. Maybe it could be fixed but I didn't see much sense to waste my time since in any case I was planning to move to net5 in a couple of days. So I just decided to move to net5 immediately. I had installed net 5.0 SDK and change target framework of my application to net5.0. Now everything is working fine and I am happy with my net5.0 application. I have some Net 4.8 projects that use the same common libraries that I am using for Net Core. So these common libraries are targeted to netstandard2.0. and can't change them to Net5. Now all these Standard2.0 projects still work with my net5.0 web application without any problem. Since I didn't have any problems with my previous version 3.1.9 I DON'T RECOMEND to update libraries to 5.0 if YOU DON'T PLAN to move your application to Net5.0. You can get more problems after this then you can gain from this update.
You should report such (VS for Mac and VS for Windows) as product defects to Microsoft, as many of the new 5.0 packages are targeting net5 solely, and not applicable to netcoreapp3.1.
Try to use outdated tool to check package updates, which is much more reliable,
https://github.com/dotnet-outdated/dotnet-outdated
I have been throught a lot of reading and the whole thing is becoming only more confusing so I decided to ask you some stuff about Flex.
So, Flex can run in a webpage if you have Flash plugin in your browser, in an AIR container (on pc/android/IOS, but on OSX ?) and also can compile to Native IOS/Android app.
I am not sure about the last point.
If it is possible, how can I build a flex app that would run in browser with flash plugin and also be compiled to Android and IOS (and maybe Windows RT) ?
Adobe gives you Flash builder, do you also need the Flex SDK ? Is it doable with the Eclipse Flex plugin ?
Thank you for your help and sorry if it is a bit messed up.
So, Flex can run in a webpage if you have Flash plugin in your
browser, in an AIR container (on pc/android/IOS, but on OSX ?) and
also can compile to Native IOS/Android app. I am not sure about the
last point.
This is mostly correct. Flex can run in a web page using the Flash Plugin, which is widely available on desktop browsers. For all intents and purposes, you should assume your mobile users do not have a Flash Plugin installed on their mobile browsers.
It is true using AIR you can create desktop applications for PC and Mac; OSx is indeed supported. You can also use AIR to create Mobile applications on Android, iOS, and Blackberry Playbook. So, iOS is indeed supported. Windows 8 UI/Metro support for AIR is expected 1st quarter of this year. I suspect we'll also see AIR support for Blackberry 10; but nothing has been formally announced that I'm aware of.
Update: 3/2014
Adobe has abandoned plans for Windows 8 UI / Metro support. Windows Phone 8 support is a very common feature request, though, so vote for it if you want it.
BlackBerry 10 does indeed support Adobe AIR. Here is a link to the SDK.
If it is possible, how can I build a flex app that would run in
browser with flash plugin and also be compiled to Android and IOS (and
maybe Windows RT) ?
Flex is primarily a framework for creating business applications. A slightly different component set is offered for desktop applications and mobile applications. Part of this is due to screen size; and part due to performance. A big DataGrid with dozens of columns, for example, is not conducive to the screen size of your mobile phone.
Update 3/2014:
A mobile optimized DataGrid was donated to the Apache Flex Team, and it should be available in current versions of the SDK.
In the end; you should not plan on using the same exact application for both your Desktop/browser app and the mobile app. But, you can share some amount of code. I would target to share 80% of the code. Move the shared code into a library project; which you can then use on both your mobile application, your desktop application, and your browser based application.
Adobe gives you Flash builder, do you also need the Flex SDK ? Is it
doable with the Eclipse Flex plugin ?
Flash Builder is shipped with the Flex SDK. And Adobe Flex ships with the AIR SDK [Note: Apache Flex does not ship w/ the AIR SDK due to licensing differences; but there is a handy installer]. Flash Builder, also, is an Eclipse plugin and can be installed into any eclipse instance you wish.
You do not need Flash Builder to create a Flex Application. You can use command line tools and other IDEs, such as IntelliJ, if you prefer.
Using Flash Professional, you can package and export to a number of platforms using AIR. You can port to both Android or iOS (as a native app), in addition to creating a .swf file that can be embedded onto a webpage - all using the one application (go 'File' > 'Publish Settings' then change the player target).
I'm not sure whether the same options are available in Flash Builder, (appears to be possible -
adobe website) but not other IDE (such as Eclipse) or framework should be needed.
You may want to consider an alternative development and deployment strategy depending on your requirements, e.g. PhoneGap which should offer support for a greater number of devices.
I've got Flex Builder 3 running on a Mac. I'm using the Flex 3.2 SDK. I'd like to upgrade the SDK, so that I can target Flash Player 10. I've never upgraded the SDK; and I don't want to blow it and foul up my old projects.
I found this link to upgrade the SDK, but I'm not sure which version to upgrade to-- milestone, stable, or nightly. Also, which type-- Adobe Flex SDK, Open Source Flex SDK, or Adobe Add-ons. I would assume that I need the Adobe Flex SDK.
I also found this upgrade link. Should I use this version instead?
I want to keep using Flex Builder 3. I'm not ready to upgrade to Flash Builder 4, yet.
As I understand it, I download the SDK, uninstall Flash, got to Preferences->Flex->Installed SDKs and add the zip, and then re-install Flash. If I want to work on an old project, I just select the old SDK.
Thank you.
-Laxmidi
Yes Adobe Flex SDK is the one you want, a stable release. Your understanding of the installation is correct except you don't need to uninstall and reinstall Flash unless you're switching flash player versions, and unless I'm mistaken you can't select the zip without extracting it to a directory first.
I was wondering if Parsley framework is compatible for Flex Hero Mobile 4.5? I seem to get a warning saying it's not compatible.
Thanks guys
Flex 4.5 and Parsley 2.3 don't play nicely together. Grab 2.4M2 from the website and all should be fine.
See this forum post for more details.
Are you using the code? OR a SWC you downloaded from a web site? I assume the latter.
Download the code and recompile it against the Flex 4.5 SDK. There are often issues when using a SWC that is compiled against a different version of the SDK than your main application.
I want to develop an Adobe air application. Whats the difference between using the Air SDK or Flex SDK and what are the advantages / disadvantages? My application will use a SQLlite database and PHP may be involved later if I turn the whole thing into a web app.
thanks
"If you want to develop an Air application, you must use the Air SDK. If you want to develop a Flex application that runs on Air, you need to use both." - #joshtnjala
I believe #joshtnjala to be partially correct, but I wanted to add on it. If using the Flex 3.3 SDK, you no longer require the AIR SDK as those tools are available to the Flex 3.3 SDK. It is important to note, because I see a lot of confusion or misuse of the term, Flex is actually three things.
Flex SDK (currently 3.3)
allows developers without the Flash and/or Flex IDE's, to develop and compile/publish Actionscript3 and MXML code to flash content (SWF). For example, one could use FlashDevelop for an IDE, and compile the code using the Flex 3.3 SDK.
Flex Framework
(From adobe [http://www.adobe.com/products/flex/overview/][1]) Flex is a free, open source framework for building highly interactive, expressive web applications that deploy consistently on all major browsers, desktops, and operating systems. It provides a modern, standards-based language and programming model that supports common design patterns. MXML, a declarative XML-based language, is used to describe UI layout and behaviors, and ActionScript™ 3, a powerful object-oriented programming language, is used to create client logic. Flex also includes a rich component library with more than 100 proven, extensible UI components for creating rich Internet applications (RIAs), as well as an interactive Flex application debugger.
Flex Builder 3
Flex Builder is merely an IDE to assist in the development of flash (SWF), or AIR content. This builder utilizes the SDK above to compile. The framework may or may not be used depending on the developers needs. Many developers have taken themselves out of the FLASH IDE (THAT NASTY TIMELINE!) and began scripting their AS3 purely in the Flex Builder IDE as it provides many useful features for the "advanced" programmer; Not to mention its a very clean UI and is built on eclipse so it has many plugins and a solid community behind its architecture.
That being said, to expand on what joshtnala said, the difference between using the AIR SKD and the Flex 3.3 SDK, is that if you merely want to build an AIR app, composed of Actiosncript3 code, the AIR SDK is all you need (33mb unpacked). If you intend to use MXML and any part of the "Flex Framework" then you must use the Flex 3.3 SDK (190mb unpacked). This will allow you to use the many available components such as Datagrids, Accordions, etc, in your AIR application. So in the end, both will develop an AIR application as Flex 3.3 SDK incorporates the AIR 1.5 development tools. Abstract your project out, figure out what you will need, if a component works for that, or if a custom implementation is needed, etc, then choose your toolkit.
Hope this helps.
These frameworks are combinable. If you want your app to be both on the web and the desktop, make it using the Flex SDK, then wrap the desktop version of this using Air.
If you're considering deploying on the web, and communicating with a backend server and all that jazz, then flex is the way to go. If your target is desktop users, then AIR.
If you want to develop an Air application, you must use the Air SDK. If you want to develop a Flex application that runs on Air, you need to use both.