RE: {Disarmed} [flexcoders] Just getting started, hitting walls...
Hello Flex Community,
I am a very experienced CF developer, and I want to get into Flex.
Based on your first impressions, how does the support from the Flex
community compare with than in the ColdFusion community?
- Gordon
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Dave @ VitalPodcasts.com
Sent: Wednesday, May 30, 2007 1:04 PM
To: flexcoders@yahoogroups.com
Subject: Re: {Disarmed} [flexcoders] Just getting started, hitting
walls...
Thanks for all the help everyone!
RE: {Disarmed} [flexcoders] Just getting started, hitting walls...
Nope, what you need to do is breakdown every part of your app into small
components. This way it will be easier to manage from coding perseptive, thats
all you need to understand and do. Thats how I do things, my first Flex apps 2
years ago where not like that and they turned out to be hard to maintain, but
as time went by I learned to break things down as small as possible.
Dimitrios Gianninas
Optimal Payments Inc.
-Original Message-
From: flexcoders@yahoogroups.com on behalf of Dave @ VitalPodcasts.com
Sent: Wed 5/30/2007 2:39 PM
To: flexcoders@yahoogroups.com
Subject: Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
I feel like its back to the Old QBasic ways...
Make one super long file that does everything, thats kind of nuts.
You mean there isn't a Load NextScreen type of thing? Where a whole
new set of objects live? and I don't have to worry about hiding
everything?
So far it feels to me, so far, I need to create lots canvases for the
different screens the application uses, and then create a funciton
that hides all but the one in focus...
Can anyone describe how they setup their code?
As far as logic, Im not too worried abotu that as most the logic will
be in CF webservices, im more worried about having an insane amount of
visual code in the MXML.
--
WARNING
---
This electronic message and its attachments may contain confidential,
proprietary or legally privileged information, which is solely for the use of
the intended recipient. No privilege or other rights are waived by any
unintended transmission or unauthorized retransmission of this message. If you
are not the intended recipient of this message, or if you have received it in
error, you should immediately stop reading this message and delete it and all
attachments from your system. The reading, distribution, copying or other use
of this message or its attachments by unintended recipients is unauthorized and
may be unlawful. If you have received this e-mail in error, please notify the
sender.
AVIS IMPORTANT
--
Ce message électronique et ses pièces jointes peuvent contenir des
renseignements confidentiels, exclusifs ou légalement privilégiés destinés au
seul usage du destinataire visé. L'expéditeur original ne renonce à aucun
privilège ou à aucun autre droit si le présent message a été transmis
involontairement ou s'il est retransmis sans son autorisation. Si vous n'êtes
pas le destinataire visé du présent message ou si vous l'avez reçu par erreur,
veuillez cesser immédiatement de le lire et le supprimer, ainsi que toutes ses
pièces jointes, de votre système. La lecture, la distribution, la copie ou
tout autre usage du présent message ou de ses pièces jointes par des personnes
autres que le destinataire visé ne sont pas autorisés et pourraient être
illégaux. Si vous avez reçu ce courrier électronique par erreur, veuillez en
aviser l'expéditeur.
winmail.dat
Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
Welcome to the community, Dave, good to have you! Essentially, the key to what you are trying to do is split up your application into individual modules. It's a bit difficult to give you a link to a single source that will step you through the process, because there are a number of items you'll have to look into. Someone may have a few bits and pieces of write-ups, but essentially you will need to look for the following: - Working with modules in Flex - May need to look at Cairngorm for a unified approach for large applications Working with modules will allow you to essentially create smaller portions of your application that you can reuse (if needed), but will keep your code in your main application concise. Look at the documentation for information on modules in Flex. Jurgen Dave @ VitalPodcasts.com wrote: Hello Flex Community, I am a very experienced CF developer, and I want to get into Flex. Perhaps it makes more sense to coem from Flash, however Adobe is letting CF jobs disappear everywhere, so its time to upgrade my skill set. here is the issues I am running into. Client Side Application: Of course this is completely different than the Web where we have sessions, Im used to the web, need to rethink to my old way of thinking. But here is my issue, I want to make LARGE applications, with many screens, and lots of functionality. How do I make an app that has multiple screen, I really do not feel like having 100's of objects on my MXML file waiting for visible = true to be set. Where is a decent walk through on how to develop a major app, not a resturant finder, an actual full blown application. I want to create other screens, with their own functions, maybe some modules... How do I make code, or set up my project so its not some huge mess of code on one of few files?
Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
I feel like its back to the Old QBasic ways... Make one super long file that does everything, thats kind of nuts. You mean there isn't a Load NextScreen type of thing? Where a whole new set of objects live? and I don't have to worry about hiding everything? So far it feels to me, so far, I need to create lots canvases for the different screens the application uses, and then create a funciton that hides all but the one in focus... Can anyone describe how they setup their code? As far as logic, Im not too worried abotu that as most the logic will be in CF webservices, im more worried about having an insane amount of visual code in the MXML.
Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
You can make your 'views' components and use a viewstack or other container to show that 'screen' or your can make each screen its own app and use the module system to pull each app into the main app as needed. On 5/30/07, Dave @ VitalPodcasts.com [EMAIL PROTECTED] wrote: I feel like its back to the Old QBasic ways... Make one super long file that does everything, thats kind of nuts. You mean there isn't a Load NextScreen type of thing? Where a whole new set of objects live? and I don't have to worry about hiding everything? So far it feels to me, so far, I need to create lots canvases for the different screens the application uses, and then create a funciton that hides all but the one in focus... Can anyone describe how they setup their code? As far as logic, Im not too worried abotu that as most the logic will be in CF webservices, im more worried about having an insane amount of visual code in the MXML. -- I am not a diabetic, I have diabetes my blog - http://grumpee.instantspot.com/blog
Re: {Disarmed} Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
Code is code. Not wanting to sound rude, but as with any other application that requires visual elements, you'll have to eventually create them somehow. The huge difference Flex makes is how you go about it. Essentially you will need to work with display containers, such as canvases, panels and the likes. However, Flex lets you break all this up into smaller pieces. Look for information on creating your own custom components, which sounds way harder than it actually is. On a higher level you can package components you have created (what you may call 'screens') and put them into separate modules. The key is to divide and conquer. Flex helps you quite a bit with it by using MXML components and modules. Jurgen Dave @ VitalPodcasts.com wrote: I feel like its back to the Old QBasic ways... Make one super long file that does everything, thats kind of nuts. You mean there isn't a Load NextScreen type of thing? Where a whole new set of objects live? and I don't have to worry about hiding everything? So far it feels to me, so far, I need to create lots canvases for the different screens the application uses, and then create a funciton that hides all but the one in focus... Can anyone describe how they setup their code? As far as logic, Im not too worried abotu that as most the logic will be in CF webservices, im more worried about having an insane amount of visual code in the MXML.
Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
From every example I see, its small apps, realesate finder, resturant finders... Is it possible, and when I mena possible, is it realistc to make something like a CMS in Flex? if anyone has a good tutorial on how to make modular code, and make a nice seperated program design, I would love to see it... everything google is turning up doesnt even come close to addressing entreprise level application needs.
{Disarmed} Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
Well I'm new to Flex, and it does seem cool, I just can't see having a large system built based on Flex... And i want too. I would like to rebuild my vitalpodcasts.com site with Flex, which is a small site, and great starter app. But my current company wants to look at making our flagship prodcut in Flex, and there are so many screens, so many functions, and I need to know how to piece out the code... So im researching Modules right now, not much sucess... which once I figure it out, is screaming for me to make a blog about it.
RE: {Disarmed} [flexcoders] Just getting started, hitting walls...
Well if you are going to make a big application, pick up Actionscript 3
design patterns. That will give you some ideas how
to construct a big application.
_
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Dave @ VitalPodcasts.com
Sent: Wednesday, May 30, 2007 11:57 AM
To: flexcoders@yahoogroups.com
Subject: Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
From every example I see, its small apps, realesate finder, resturant
finders...
Is it possible, and when I mena possible, is it realistc to make
something like a CMS in Flex?
if anyone has a good tutorial on how to make modular code, and make a
nice seperated program design, I would love to see it... everything
google is turning up doesnt even come close to addressing entreprise
level application needs.
Re: {Disarmed} Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
I'll address your first question: I'm doing this all the time. I'm working on my fourth huge Flex application. I've been developing enterprise type distributed applications for over 15 years and I can tell you that Flex is one of my favorite tools in terms of creating large RIA type apps. With Flex you now have the ability to bring to the web what previously has been mostly the domain of applications developed for the desktop/workstation world. Jurgen Dave @ VitalPodcasts.com wrote: From every example I see, its small apps, realesate finder, resturant finders... Is it possible, and when I mena possible, is it realistc to make something like a CMS in Flex? if anyone has a good tutorial on how to make modular code, and make a nice seperated program design, I would love to see it... everything google is turning up doesnt even come close to addressing entreprise level application needs.
Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
May need to look at Cairngorm for a unified approach for large applications Yes. A couple of resources: http://cairngormdocs.org/ http://www.brightworks.com/technology/adobe_flex/cairngorm.html Also, I like Joe Berkovitz's ideas on architecture: http://www.adobe.com/devnet/flex/articles/blueprint.html HTH, Douglas Jurgen Beck wrote: Welcome to the community, Dave, good to have you! Essentially, the key to what you are trying to do is split up your application into individual modules. It's a bit difficult to give you a link to a single source that will step you through the process, because there are a number of items you'll have to look into. Someone may have a few bits and pieces of write-ups, but essentially you will need to look for the following: - Working with modules in Flex - May need to look at Cairngorm for a unified approach for large applications Working with modules will allow you to essentially create smaller portions of your application that you can reuse (if needed), but will keep your code in your main application concise. Look at the documentation for information on modules in Flex. Jurgen Dave @ VitalPodcasts.com wrote: Hello Flex Community, I am a very experienced CF developer, and I want to get into Flex. Perhaps it makes more sense to coem from Flash, however Adobe is letting CF jobs disappear everywhere, so its time to upgrade my skill set. here is the issues I am running into. Client Side Application: Of course this is completely different than the Web where we have sessions, Im used to the web, need to rethink to my old way of thinking. But here is my issue, I want to make LARGE applications, with many screens, and lots of functionality. How do I make an app that has multiple screen, I really do not feel like having 100's of objects on my MXML file waiting for visible = true to be set. Where is a decent walk through on how to develop a major app, not a resturant finder, an actual full blown application. I want to create other screens, with their own functions, maybe some modules... How do I make code, or set up my project so its not some huge mess of code on one of few files?
Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
You may also want to have a look at Cairngorm
http://labs.adobe.com/wiki/index.php/Cairngorm
On May 31, 2007, at 12:52 AM, {reduxDJ} wrote:
Well if you are going to make a big application, pick up
Actionscript 3 design patterns. That will give you some ideas how
to construct a big application.
From: flexcoders@yahoogroups.com
[mailto:[EMAIL PROTECTED] On Behalf Of Dave @
VitalPodcasts.com
Sent: Wednesday, May 30, 2007 11:57 AM
To: flexcoders@yahoogroups.com
Subject: Re: {Disarmed} [flexcoders] Just getting started, hitting
walls...
From every example I see, its small apps, realesate finder, resturant
finders...
Is it possible, and when I mena possible, is it realistc to make
something like a CMS in Flex?
if anyone has a good tutorial on how to make modular code, and make a
nice seperated program design, I would love to see it... everything
google is turning up doesnt even come close to addressing entreprise
level application needs.
{Disarmed} Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
You can definitely build a large application in flex. I am working on a rather large Video asset management platform right now in flex. It has over a hundred screens and I have had little trouble getting it broken down into manageable pieces. We started the app doing dhtml and ajax and got maybe 45% of it done before we moved to flex. Our flex code, which is probably 80% done now is far easier to manage than the html was, and is a smaller download. We didn't opt to use Modules, they weren't released when we got started. I'm not sure it would have been much better for us. Our swf output size is only like 590k and loads at an acceptable speed over DSL. We have not tested on modem speeds simple because that does not fit our target market. Paul --- In flexcoders@yahoogroups.com, Dave @ VitalPodcasts.com [EMAIL PROTECTED] wrote: Well I'm new to Flex, and it does seem cool, I just can't see having a large system built based on Flex... And i want too. I would like to rebuild my vitalpodcasts.com site with Flex, which is a small site, and great starter app. But my current company wants to look at making our flagship prodcut in Flex, and there are so many screens, so many functions, and I need to know how to piece out the code... So im researching Modules right now, not much sucess... which once I figure it out, is screaming for me to make a blog about it.
Re: {Disarmed} Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
Maybe scrapblog.com is a good example for a cms? It's definitely possible to develop massive applications. Get a grip of Flex' component based development model first. Modules add a new layer of complexity, which might not be necessary. Cheers, Ralf. On 5/30/07, Paul DeCoursey [EMAIL PROTECTED] wrote: You can definitely build a large application in flex. I am working on a rather large Video asset management platform right now in flex. It has over a hundred screens and I have had little trouble getting it broken down into manageable pieces. We started the app doing dhtml and ajax and got maybe 45% of it done before we moved to flex. Our flex code, which is probably 80% done now is far easier to manage than the html was, and is a smaller download. We didn't opt to use Modules, they weren't released when we got started. I'm not sure it would have been much better for us. Our swf output size is only like 590k and loads at an acceptable speed over DSL. We have not tested on modem speeds simple because that does not fit our target market. Paul --- In flexcoders@yahoogroups.com flexcoders%40yahoogroups.com, Dave @ VitalPodcasts.com [EMAIL PROTECTED] wrote: Well I'm new to Flex, and it does seem cool, I just can't see having a large system built based on Flex... And i want too. I would like to rebuild my vitalpodcasts.com site with Flex, which is a small site, and great starter app. But my current company wants to look at making our flagship prodcut in Flex, and there are so many screens, so many functions, and I need to know how to piece out the code... So im researching Modules right now, not much sucess... which once I figure it out, is screaming for me to make a blog about it. -- Ralf Bokelberg [EMAIL PROTECTED] Flex Flash Consultant based in Cologne/Germany Phone +49 (0) 221 530 15 35
Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
Dave,
I would suggest having a look at Cliff Hall's pureMVC framework.
http://puremvc.org
He has 2 sample applications with which you can see how the framework can
easily be extended to larger scale applications.
Cairngorm is good too, personally I understood pureMVC faster.
- Original Message
From: Flexing... [EMAIL PROTECTED]
To: flexcoders@yahoogroups.com
Sent: Wednesday, May 30, 2007 3:23:23 PM
Subject: Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
You may also want to have a look at Cairngorm
http://labs. adobe.com/ wiki/index. php/Cairngorm
On May 31, 2007, at 12:52 AM, {reduxDJ} wrote:
Well if you are going to make a big application, pick up Actionscript 3 design
patterns. That will give you some ideas how
to construct a big application.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Dave @
VitalPodcasts.com
Sent: Wednesday, May 30, 2007 11:57 AM
To: flexcoders@yahoogroups.com
Subject: Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
From every example I see, its small apps, realesate finder, resturant
finders...
Is it possible, and when I mena possible, is it realistc to make
something like a CMS in Flex?
if anyone has a good tutorial on how to make modular code, and make a
nice seperated program design, I would love to see it... everything
google is turning up doesnt even come close to addressing entreprise
level application needs.
!--
#ygrp-mlmsg {font-size:13px;font-family:arial, helvetica, clean, sans-serif;}
#ygrp-mlmsg table {font-size:inherit;font:100%;}
#ygrp-mlmsg select, input, textarea {font:99% arial, helvetica, clean,
sans-serif;}
#ygrp-mlmsg pre, code {font:115% monospace;}
#ygrp-mlmsg * {line-height:1.22em;}
#ygrp-text{
font-family:Georgia;
}
#ygrp-text p{
margin:0 0 1em 0;}
#ygrp-tpmsgs{
font-family:Arial;
clear:both;}
#ygrp-vitnav{
padding-top:10px;font-family:Verdana;font-size:77%;margin:0;}
#ygrp-vitnav a{
padding:0 1px;}
#ygrp-actbar{
clear:both;margin:25px 0;white-space:nowrap;color:#666;text-align:right;}
#ygrp-actbar .left{
float:left;white-space:nowrap;}
..bld{font-weight:bold;}
#ygrp-grft{
font-family:Verdana;font-size:77%;padding:15px 0;}
#ygrp-ft{
font-family:verdana;font-size:77%;border-top:1px solid #666;
padding:5px 0;
}
#ygrp-mlmsg #logo{
padding-bottom:10px;}
#ygrp-vital{
background-color:#e0ecee;margin-bottom:20px;padding:2px 0 8px 8px;}
#ygrp-vital #vithd{
font-size:77%;font-family:Verdana;font-weight:bold;color:#333;text-transform:uppercase;}
#ygrp-vital ul{
padding:0;margin:2px 0;}
#ygrp-vital ul li{
list-style-type:none;clear:both;border:1px solid #e0ecee;
}
#ygrp-vital ul li .ct{
font-weight:bold;color:#ff7900;float:right;width:2em;text-align:right;padding-right:.5em;}
#ygrp-vital ul li .cat{
font-weight:bold;}
#ygrp-vital a {
text-decoration:none;}
#ygrp-vital a:hover{
text-decoration:underline;}
#ygrp-sponsor #hd{
color:#999;font-size:77%;}
#ygrp-sponsor #ov{
padding:6px 13px;background-color:#e0ecee;margin-bottom:20px;}
#ygrp-sponsor #ov ul{
padding:0 0 0 8px;margin:0;}
#ygrp-sponsor #ov li{
list-style-type:square;padding:6px 0;font-size:77%;}
#ygrp-sponsor #ov li a{
text-decoration:none;font-size:130%;}
#ygrp-sponsor #nc {
background-color:#eee;margin-bottom:20px;padding:0 8px;}
#ygrp-sponsor .ad{
padding:8px 0;}
#ygrp-sponsor .ad #hd1{
font-family:Arial;font-weight:bold;color:#628c2a;font-size:100%;line-height:122%;}
#ygrp-sponsor .ad a{
text-decoration:none;}
#ygrp-sponsor .ad a:hover{
text-decoration:underline;}
#ygrp-sponsor .ad p{
margin:0;}
o {font-size:0;}
..MsoNormal {
margin:0 0 0 0;}
#ygrp-text tt{
font-size:120%;}
blockquote{margin:0 0 0 4px;}
..replbq {margin:4;}
--
Ready
for the edge of your seat?
Check out tonight's top picks on Yahoo! TV.
http://tv.yahoo.com/
Re: {Disarmed} [flexcoders] Just getting started, hitting walls...
Thanks for all the help everyone!
