Home Tutorials Forums Articles Blogs Movies Library Employment Press
Old 06-14-2011, 01:05 PM   #1
jjcb
Registered User
 
Join Date: Jun 2011
Posts: 2
Default concepts for large application

Hi, I am very new to flash or flex...

We are thinking about use it in a very large application (now more than 3300 jsp).
An we want to port some part of it for use in tablets (primary focus on Android)

I have some querys:

- what are the diferences between flash and flesh?

- there are any "good practices manual" for large application in flash/flesh?
- can a swf be broken in several swf? How they comunicate with others parts? Is this the same for web application than for air application?
(I guess that if in a future will need an "air application" (applet IOs, or blckberry), I think its better not to use html code... Am I right?)

- does this tecnology permit the use of continuous integration?
Basicaly, get source code from central repository, compile it, package it, etc...
Does this process need flash builder, or only the free sdk?

- What is about memory leaks, performace isues, etc?

- Any other tips you consider important?

Thankyou very much

javi
jjcb is offline   Reply With Quote
Old 06-14-2011, 08:14 PM   #2
Barna Biro
Senior Member
 
Barna Biro's Avatar
 
Join Date: Nov 2009
Location: LU, Switzerland
Posts: 1,410
Default

1) Flash is the technology... Flex ( not "flesh" ) is just a framework.
2) There might be a few, but what are you in fact expecting from such a manual?
3) Yes they can... I won't get deep into how they communicate, but you should Google a bit and you'll see that all the answers are out there ( or in the official documentation ). The SDK is free and there are a few free IDEs out there as well that have some nice support for this technology ( like Flash Develop ), but obviously, you can just use Notepad if you feel more comfortable with that...
4) It permits continuous integration ( no special tools are required than the ones you'd normally use ).
5) You have a profiler in Flash Builder Premium that can help you find memory leaks more easily and observe other performance related aspects. If you write good code, you shouldn't worry that much about memory leaks and such...

Suggestion & Tip: Google more and read the official and free documentation... you could have answered all your questions in maximum 1 hour if you would have been really interested in finding answers. Be less lazy, more proficient...
__________________
Titus M. Plautus - Not by age but by capacity is wisdom acquired.

Last edited by Barna Biro; 06-14-2011 at 08:20 PM.
Barna Biro is offline   Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 02:08 AM.

///
Follow actionscriptorg on Twitter

 


Powered by vBulletin® Version 3.8.5
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Ad Management plugin by RedTyger
Copyright 2000-2013 ActionScript.org. All Rights Reserved.
Your use of this site is subject to our Privacy Policy and Terms of Use.