We have a flex app and its correspoding SWC project which works great in flash builder 4.0, and we have imported it a bunch of times to a fresh installation no problem.
However, there doesnt seem to be any way to get it to import or run in FB 4.5.
First, the projects were checked out into:
c:\dev\flash_ws\apitester (this is the flex project)
c:\dev\flash_ws\flashAPI (this is just a bunch of actionscript and the swc project).
Now in FB4.5, I simply hit file->import flash builder project, chose c:\dev\flash_ws\apitester and it picks up the .actionScriptProperties or similar and loads the project. But it only imports half the project - it has lost the flashapi part. If I do the same thing in FB4.0, it picks up the flashapi library project too.
The second problem, is FB4.5 has NO option to import an existing library project, or link to it. If I go into project->properties->library path, neither "add project" "add swc folder" nor "add swc" will take the directory c:\dev\flash_ws\flashAPI which contains the source I want to be able to edit and use.
I notice that in source path is this:
${DOCUMENTS}\flashAPI\src
So it did remember the dependency on flashAPI
BUT: when I lookat project->properties->Resource->linked resoures, I see a load of rubbish:
DOCUMENTS->C:\Users\Simon\Adobe Flash Builder 4.5
PARENT_LOC->C:\Users\Simon\Adobe Flash Builder 4.5
PROJECT_LOC->C:\Users\Simon\Adobe Flash Builder 4.5
WORKSPACE_LOC->C:\Users\Simon\Adobe Flash Builder 4.5
I never chose these locations - flash did it by iteslf.
My workspace is in c:\dev\flash_ws.
I cant change the above! the Edit field is greyed out for all except DOCUMENTS.
So I changed DOCUMENTS to be c:\dev\flash_ws, but it still doesnt pick up my flashAPI library.
Also, none of my mxml files are lised in the run configuratinos - its lost those, and I cant find a way to make flash builder realise that its own mxml files should be runnable.
Any ideas?
NB The project imports and runs fine in flashdevelop - which is free. Thats what Im using until we can find away to get a flash builder project to work in flash builder.
Related
I am trying to find the elusive JavaFX scene builder so I can use it in Intellij. I am on Windows OS.
Oracle have stated that the JavaFX scene builder is included in a new download, but no matter how I search I cannot find it (see http://www.oracle.com/technetwork/java/javafx/downloads/index.html). I think they have linked to the incorrect page and Googling for it is getting me nowhere.
I already have Java 8 SDK installed and working fine. Apparently JavaFX is now included in that, but nowhere in the Java folder can I find the scene builder and it seems to be completely missing online.
Please can anyone help? I am just wanting to write a small GUI program and it seems like JavaFX is the way to go (if it isn't then feel free to disabuse me of this notion!)
With JDK8u40, according to this:
Starting with Oracle Java SE 8u40, Oracle does not provide a separate set of accompanying JavaFX Scene Builder binaries. If you would like to contribute changes, ideas or just let us know what you have done with the code, please consult the OpenJDK Community contribution guidelines and join the openjfx-dev mailing list.
You can still download the last binary at Oracle in this link. But check this warning:
WARNING: These versions of JavaFX Scene Builder may include components that do not contain the latest security patches and are not recommended for use in production.
This means it doesn't include the last changes of 8u40, like the new Spinner control.
Alternatives
The project is open source, and you can find the updated code at the OpenJFX repo. So you are free to download it and build it.
Since its released under BSD license, Gluon is offering support for an updated version of Scene Builder, and you can download an installer for your platform or an executable jar from here.
Besides, they have an open repository where anybody can contribute.
Install JavaFx Scene Builder (Gluon) with Intellij 14 on Windows with JDK7
This will probably work with Java 8 as well but I am using 7 so I didn't test 8.
I know this has been answered but this might be helpful for future Intellij users. To get scene builder to work with Intellij 14 use the following steps.
Install Scene Builder for Windows. Download/Install From Here (Windows Installer (x64))
Set Scene Builder path to executable in Intellij. File -> Settings
-> Languages And Frameworks -> JavaFx By default mine installed under C:\Users\kris\AppData\Local\SceneBuilder\
Open your .fxml file. Click on the scene builder tab.
UPDATE 2019:
The default install path appears to know be "Program Files" C:\Program Files\SceneBuilder\SceneBuilder.exe
JavaFX plugin might need to be enabled in Intellij 2019
On a mac, in Intellij, you need to go to preferences, then type JavaFX and then do this. Please look at the attached Image.
Below is the screenshot of CPU utilization.
Just curious what are those Interface Builder Cocoa Touch Tool & ibtoold process.
Because of this, to run app, it takes me around 1 min least.
Note: I am using xcode 5
I see that this happens when there are more view controllers. I have around 25 view controllers.
Yes, I had created project in Xcode 4.6 and after updating, opened in Xcode 5.
Attached is the screenshot for the file inspector.
There is a stack overflow question along similar lines but the question involved only a single nib. The project in that case was created for iOS2 and used a new version of Xcode. This led me to examine the latest Interface Builder Release Notes (3.2) which states:
"Interface Builder documents can no longer be saved in the NIB 2.x
file format. NIB 2.x files will automatically be upgraded to NIB 3.x
files upon opening."
So, I would suggest you check the file inspector of your nib files and verify their current version. I suspect that Interface Builder is simply attempting to update 25 nib files to version 3.x. If you have an older Carbon nib files then please see the Xcode Release Notes (v.4.0 - current) as they require using version 3.2 in Xcode 4 and higher.
Xcode 4.6.3 displays versioning of nibs on the file inspector using these menu items:
While Xcode 5.0.1 displays versioning somewhat differently.
The project document should also be in the latest format:
.
The basic premise is that Xcode is converting the project file/nibs on load. If this recurs on every load I would report that as a bug to Apple at http://bugreport.apple.com. I think the information found is pointing to the correct issue. Checking that the files are using the latest version should fix the issue unless there is a bug.
Other things to try:
Load the project on a separate machine/directory (There might be some
corruption on your current one)
Run Console and capture logs as the problem is occurring (you will
need to also capture system logs for Apple anyhow but the Console
might show a useful error message)
References
What is Interface Builder Cocoa Touch Tool, link.
Xcode Release Notes (v. 4.0 - current), link.
I have created gui related components in flash professional and exported the swc and added this swc into my referenced libraries (by adding link to the swc) and I can create/reference to the symbols in my flash builder project.
Every thing is fine untill I modify something(MC) and export the swc the changes won't reflect immediately. This is somewhat understood, so I just use to restart FB so that the changes are reflected. This was working find until yesterday.
After making changes to symbols, nothing will reflect the changes
I restart the FB (which use to work till yesterday)
Refresh project, referenced libraries
Clear browser cache
Clean the project
I left home with frustration and today morning when I restarted the system it got reflected the changes. And now I did changes to the gui again and its the same problem.
I know there is one easy way which is to remove and add the swc reference from the project
I am pretty sure there could be much easy simple way to do it.
The compiler cache can sometimes not pick changes in SWC libraries (old known issue).
Solution, when you think this problem happens, is to "clean" the project. Both FlashBuilder and FlashDevelop let you clean the project from the Project main menu.
Can I produce a native exe using flash builder and air.
I don't want the user to have to get any other dependencies such as air etc. I want everything bundled into a native application, a single exe perhaps that I could produce my own installer using nullsoft or similar.
I've searched around and spoken to people and come to the conclusion that no one is sure, seen some yes and no's.
With flash builder 4.6 they have included the captive build process in the gui. This enables you to produce an exe that is bundled with the AIR Dll's and requirements without the end user ever needing to install Adobe AIR.
Correct: Flash Builder 4.6 has the option right there in the Project menu option, when selecting "Export Release build" :-)
I have had some issues with the AWS IOS SDK framekit, since it was not built to work with OSX apps. I found a modified version of the SDK that Brad Larson created.
The directory structure looks something like:
AWSiOSSDK.framework/
src/
--Amazon.Runtime/
--Amazon.S3/
..
--AWSCocoa/
----AWSCocoa_Prefix.pch
----AWSCocoa.xcodeproj
----etc
--include/
So if I go into the xcode project, and build AWSCocoa it compiles. But when I look at the timestamp on the AWSiOSSDK.framework, it hasn't changed. So I don't know what compiling this AWSCocoa gets me, or where I can find the files it creates. So assuming that building AWSCocoa.xcodeproj is supposed to build a new version of the framework compatible with OSX development, where do I find and link what I've built?
The AWSiOSSDK.framework bundle is a precompiled framework, probably left over from my earlier experiments in making a Mac version of this (since you can't use frameworks like this with iOS, only static libraries). Ignore that.
If you are using Xcode 4, your built framework will be created somewhere in your ~/Library/Developer/Xcode/DerivedData/ directory. To find where it lies, go to your project navigator in Xcode 4, expand the Products group, right click on AWSCocoa.framework, and select Show in Finder. This is no different from any other third-party framework you would compile.
Nominally, you'll want to add this framework as a target dependency in your application so that it is built alongside that. You'll also have to make sure that the framework is copied into the appropriate location within your application bundle so that it can be used by your application at runtime.