I don't code bytecode, I code AS & MXML.  I don't really care what it 
becomes at runtime, I just want to code it faster, better, and cooler than I 
have in the past.  So far, so good.

LayoutManager?  Dude, it was referenced in the v2 component framework for 
Flash, but it didn't exist.  Who was I to know I was a furry rodent/Flash 
Developer guinea pig for you guys?  Seriously, yeah, it woulda been nice. 
FLOW for Flash and REX for MXML now exist, but I want it at design time as 
well, not just runtime.

If they think <mx:VBox> is just another implementation of XUL, I say we keep 
quiet.

Naw, it's cool, this thread doesn't have my name on it, and I welcome 
dialogue about code since Flashcoders n' Friends email lists are down since 
Sunday night, and I haven't gotten my email list dosage since last Friday; 
nic'n pretty bad.

Bottom line, Flash developers who "get it" dig MXML because they no longer 
have to write GUI code.

I think incoming dev's dig AS2 and definately AS3, at least to prove we meet 
"standards", and see how easy it is to plug their stuff into the client in a 
multitude of ways.

I think the weirdo web developers Macromedia keeps insisting on being nice & 
inviting too will see the plethora of API's with the familiar 
HTML/CSS/JavaScript development paradigm, and go "Wow, that goes great with 
my AJAX!" after that Web 2.0 stint.

Something for everyone.  I do admit, however, good practices are extremely 
hard to see... at least for me.  I loathe HTML/JavaScript anything, so I 
don't really have any experience in that realm to really say what is a good 
mixture of MXML/CSS/AS.. but I do know what's decent AS.  Complicate that 
even further in that I'm more pragmatic than most developers because my 
deadlines are made by those who invest heavely in their crack smoking 
habits.

Either way, something for everyone, and stock up on your caffeine as the 
Flash developers flood here after they play with the Zorn alpha the 17th.  I 
tried to setup a n00b list, as did someone else on here, but it's too late 
now... brace for impact!

----- Original Message ----- 
From: "Dave Wolf" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, October 11, 2005 10:57 PM
Subject: [flexcoders] Re: WebServices via ActionScript


I agree with what youre saying.  Although one might argue a nice OO
layout manager in AS might have solved those issues too.  I mean
net-net Flex components just become AS code at compile time....

I am just cautioning given an amazingly good model for how things can
go wrong in j2EE to not miss the forest for the trees.  I bet you
might be shocked how many folks who read this forum didnt actually
realize that an <mx:VBox> actually gets precompiled into AS when your
request the MXML.

Clearly a good application is going to require a mixture of tags and
AS.  The risk is that you will find when pressed, folks like to "run
home to momma".  If they are AS folks, and the going gets tough, they
will write lots of AS.  If they are newbies, they will flounder
wondering why MX tags dont do everything.

Next you add in enterprise class services, and its pure confusion time.

I think the whole goal of a public forum is as much about education as
answers.

I think it becomes pretty clear who gets it and who doesnt.  Our goal
is to help those that dont, do.

I have now hijacked a hijacked thread!  Back to your originally
scheduled presentation.....

-- 
Dave Wolf
Cynergy Systems, Inc.
Macromedia Flex Alliance Partner
http://www.cynergysystems.com

Email:  [EMAIL PROTECTED]
Office: 866-CYNERGY x

--- In [email protected], "JesterXL" <[EMAIL PROTECTED]> wrote:
>
> Because, doing GUI code in Flash sux.  Dare you to use Flash for 6
years
> doing GUI development, and THEN ask the same questions.
>
> You can do layout in Flash via dragging form elements, but:
> 1. you run into initialization challenges which complicate your
coding &
> elongate debugging
> 2. layout changes break existing code
> 3. preventing #1, and allowing for more fluid positioning of
components, you
> create things dynamically.  Suddenly you're doing layout with
code...???
> "Nope... needs to come over 4 pixels, let me recompile."  Huh?
Photoshop
> users would blow their brains out... I just use beer to compensate.
 3 weeks
> out of a 2 month project is spent writing & tweaking draw and size
> functions...wtf?  And you still cannot justify Flex's cost to
benefit ratio?
>
> I've heard the same analogy talking to a Java developer I used to
work with,
> about how JSP tags weren't ever really used a lot, and people ended
up just
> coding the things anyway.
>
> However, Flex has something JSP does not: the capability to do a
good GUI,
> one that is rich, interactive, stateful, integrates easily with the
backend,
> and makes AJAX look like the hack it is.
>
> I don't really share your concerns, though.  When I first started
coding
> Flex, I thought the concept of using tags was disgusting.  I came
from a
> Flash background, not an Enterprise, JSP one.  However, I've come to
learn
> how powerful they are, mainly for laying out a GUI's that "seperation
> presentation from business logic."  It's so frikin' cheese but man it's
> true.
>
> However, I've always loved and felt comfortable doing logic in code,
just
> like in Flash.  However, MXML is only v1.  I'm sure as it matures,
so too
> will my willingness to start doing some of the more data orienated
aspects
> of it in tags vs. code, which helps signifinately if your GUI helps
support
> those practices, some of which FlexBuilder does.
>
>
>
> ----- Original Message ----- 
> From: "Dave Wolf" <[EMAIL PROTECTED]>
> To: <[email protected]>
> Sent: Tuesday, October 11, 2005 5:54 PM
> Subject: [flexcoders] Re: WebServices via ActionScript
>
>
> I may be out of the loop because I couldnt see which thread you broke
> from but....
>
> You can turn on the keep-generated to keep the generated AS from a
> <mx:WebService> call to prove its possible as well.  Since at runtime
> the J2EE Servlet Filter is generating AS from the <mx:*> tags pretty
> much anything you can do in a tag you can do in AS right?
>
> The real question is why?  You used to see this in JSP development a
> lot (Since JSP is a nearly direct analog to Flex) in that JSP
> developers would just make huge scriplet sections and do everything in
> Java. Eventually it reached the point that why not just write a darn
> servlet.  Since at runtime the JSP is just codegenerated to java and a
> servlet runs.
>
> Flex is the same right.  The MXML is code generated in AS.  I worry
> about Flex ending up like JSPs with huge script sections and wondering
> why you didnt just use Flash itself.
>
>
>
> Dave Wolf
> Cynergy Systems, Inc.
> Macromedia Flex Alliance Partner
> http://www.cynergysystems.com
>
> Email:  [EMAIL PROTECTED]
> Office: 866-CYNERGY x85
>
>
> --- In [email protected], "JesterXL" <[EMAIL PROTECTED]> wrote:
> >
> > Starting a new thread since we hijacked the other one.
> >
> > I tested this and it works in Flex 1.5 and Flash 8.
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <mx:Application xmlns:mx="http://www.macromedia.com/2003/mxml";
> >  initialize="getFunky()">
> >  <mx:Script>
> >  <![CDATA[
> >
> >  import mx.services.WebService;
> >  import mx.services.PendingCall;
> >
> >  var myWebServiceObject:WebService;
> >  var MyPendingCallObject:PendingCall;
> >
> >
> >  public var debug_str:String = "";
> >
> >  function getFunky()
> >  {
> >   d("WebService: " + WebService);
> >   var theURL = "http://radio.tapper.net/artist.cfc?wsdl";;
> >   myWebServiceObject = new WebService(theURL);
> >   MyPendingCallObject = myWebServiceObject.getCurrentSong();
> >   d("Made call...");
> >   MyPendingCallObject.onResult = function(result)
> >   {
> >    mx.core.Application.application.d("result: " + result);
> >    for(var p in result)
> >    {
> >     mx.core.Application.application.d(p + ": " + result[p]);
> >    }
> >   }
> >   MyPendingCallObject.onFault = function(fault)
> >   {
> >    mx.core.Application.application.d("fault: " + fault);
> >    for(var p in fault)
> >    {
> >     mx.core.Application.application.d(p + ": " + fault[p]);
> >    }
> >   }
> >  }
> >
> >  function d(o)
> >  {
> >   debug_str += o + "\n";
> >  }
> >
> >
> >  ]]>
> >  </mx:Script>
> >
> >  <mx:TextArea text="{debug_str}" width="400" height="300" />
> > </mx:Application>
> >
>
>
>
>
>
>
>
> --
> Flexcoders Mailing List
> FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> Search Archives:
http://www.mail-archive.com/flexcoders%40yahoogroups.com
> Yahoo! Groups Links
>







--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com
Yahoo! Groups Links









------------------------ Yahoo! Groups Sponsor --------------------~--> 
Fair play? Video games influencing politics. Click and talk back!
http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/nhFolB/TM
--------------------------------------------------------------------~-> 

--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/flexcoders/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to