Some FlashBuilder issues and some solutions
What issues?
There are many...
Actually I will present just some things you could do, when you
think that robotlegs is causing the errors and headaches you're
getting for several hours...
Even though your robotlegs classes look fine, the context looks
fine, everything is as it should be, you get compiler or run-time
errors, or even no errors, but nothing happens, right?
Maybe it’s the Flash Builder, not the robotlegs-framework that messed up your project!
Things to consider:
1) Before opening a project (for example a robotlegs demo
written by someone) that contains
a) bin-debug (folder)
b) .settings (folder)
c) .actionScriptProperties (file)
d) .flexProperties (file)
e) .project (file)
you should delete those files and folders from
your project
2) Check if there is a libs folder in this project on your
hard-disk and whether it contains the libraries you need (for
example robotlegs-framework-v1.4.0.swc)
If not, create the folder libs and add the swc
file
3) Create the project - usual steps:
a) Project Location: Choose a name and location for your
project.
b) Configure Server Settings
c) Build Paths: Set the build paths for the new Flex
Project or ActionScript project.
Normally FlashBuilder finds the libs folder and you don’t
need to do anything if you are creating a FLEX
Project
Strangely enough that’s not the case for an
ActionScript Project. Even if the folder exists on
you hard-disk and it contains the library you need, Flash Builder
expects you to add it manually!!!
Click finish
4) Even if you added your libs folder make it a habit:
Check if the libraries you need are in your Build
Path: Project->Properties->Build Path->Library
Path->libs
If not, then add them:
Project->Properties->Build Path->Library Path->Add SWC
Folder
Browse to the location of your libs folder in your project and
select it
5) Check if the libraries you need are listed in the
FlashBuilder Package Explorer in the Referenced
Libraries
(NB: the “Referenced Libraries” appears only if the
libs folder isn’t empty)
6) Make it a habit:
Use the feature: Project->Clean
Clean is refreshing/re-writting the bin-debug and the project
settings, that somehow contain mixed values, old and new, which
confuses the poor FlashBuilder
7) FlashBuilder Package Explorer right click on the project -> Refresh
8) What to do when something goes really wrong with a
project’s settings in FB is:
a) right click on the project in the Package Explorer, choose
Delete
b) radiobutton: DO NOT DELETE CONTENTS !!
c) go to the folder of the project on your hard-disk
d) delete :bin-debug, .settings, .actionScriptProperties,
.flexProperties, .project
e) and eventually the libs content
f) don’t delete src !!
g) go back to FB, create a new Flex/Actioncript Project with the
same name and location as the deleted one, following the steps
described above
The structure of your project will be intact, you’ll just
have new settings.
I wrote this down pretty fast, so if it’s too confusing,
I’ll review and rephrase and /or complete it, when I’ll
get more time :)
Ondina
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Ondina D.F. closed this discussion on 01 Nov, 2011 04:03 PM.