I'm still waiting for reply.
--- In flexcoders@yahoogroups.com, "maxym.hryniv" <[EMAIL PROTECTED]> wrote:
>
> Hi, Peter
> It's good that we have at last normal exception handling in 8.5
beta.
> But it's only beta for now and we are creating apps using Flex 1.5.
So
> the question is "How we can fight silent exceptions death in Flex 1.
5
> ???".
> I have some ideas but to realise them i have to rewrite all flex 1.5
> framework and i think it's not acceptable.
>
> Waiting for reply ,
> Max
> --- In flexcoders@yahoogroups.com, "Peter Farland" <pfarland@>
> wrote:
> >
> > Hi Mykola,
> > 
> >     Have you used the debug versions of the Flash Player during
> > development? The debug version of the Flash Player reports
uncaught
> > exceptions and it also traces information to a flashlog.txt file
as
> long
> > as you have a mm.cfg file setup in your user directory. We include
> debug
> > versions of the Flash Player (i.e. the Standalone Player, the
> > Firefox/Netscape/Opera plugin and MSIE Active-X player) in the
Flex
> > installer. We include them for the same reasons that you state -
> > "without having proper error reporting it is impossible to build
> > anything larget than hello-world presentations". Flex Builder has
a
> > visual debugger with breakpoints and watch statements. Also AS3
> Error
> > objects remember their stacktraces and you can print them out if
> you're
> > using the debug player. We built the Flex 2 framework of over 1000
> > classes using the same tools as you would to build your own
> > applications... I feel that they are adequate.
> > 
> >     Regarding the confusion, it wasn't that important - it was
just
> that
> > from my reading the various posts on this thread I got the
> impression
> > that there were two complaints here that were at odds with each
> other.
> > One complaining they couldn't manage errors coming from lots of
> > different places and the other that they weren't getting enough
> errors
> > and related information at runtime.
> > 
> > Regards,
> >     Pete
> >
> > ________________________________
> >
> > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED]
com]
> On
> > Behalf Of Mykola Paliyenko
> > Sent: Tuesday, April 25, 2006 5:24 PM
> > To: flexcoders@yahoogroups.com
> > Subject: Re: [flexcoders] Uncaught exceptions in Flex 1.5
> >
> >
> > Ok Peter,
> > no idea why you've been confused but...
> > ActionScript specification has a notion of throwable objects, so
> saying
> > that Exception is a bug of the AS2Lib is slightly incorrect. I'm
> > relaizing that due to the size constraints of the player it might
be
> > good idea not to include exception handling in it, but once more
> again
> > you can add this in the development version of the player and this
> > should be extremely easy to do if the overal palyer's architecture
> is
> > good enough, isn't it?
> >
> > My opinion is that without having proper error reporting it is
> > impossible to build anything larger than hello-world presentations
> with
> > a very good quality, so I'd warn people to treat Flex/Flash as a
> really
> > serious platform unless this feature will be implemented.
> > Flex Developers in my company mostly are very unhappy with the
> quality
> > of the framework and the level of the support Adobe provide for
the
> > users, I'm not saying about paid support I'm saying about
community
> > support, feature requests, bugfixes, open source frameworks around
> Flex
> > etc. I see no other way for developing the really good product
other
> > than involve the community into the development. It is the way
lots
> of
> > really cool stuff were developed for the last year and it is
mostly
> > ignored by Adobe.
> >
> > You have a great idea of RIA and a great high performant player,
if
> you
> > make a great product it will be an "all win" situation. The only
way
> to
> > make a great product is to make it more open to the contributing
> than it
> > is now. IMHO but it is proven many times in Java world
> > So do not just throw away comment from such crazy guys like me,
> Maxym,
> > Sergey and lots more, all we want is to make the platform we are
> using
> > better, and do trust me without responding to the real feedback
from
> > developers any technology will shortly become outdated.
> >
> >
> > On 4/24/06, Peter Farland <pfarland@> wrote:
> >
> >       Mykola, I'm slightly confused by your post in contrast to what
> > Sergey and Stanislav originally said.
> >      
> >       I read Sergey's post as that he was having trouble with uncaught
> > exceptions and had to add a lot of code to catch and possibly
ignore
> > such errors. I read your post to mean the opposite of this in that
> the
> > uncaught exceptions were important at development time because if
> they
> > were silently caught and ignored it would be hard to diagnose what
> the
> > problem was.
> >      
> >       As Matt said, in general for our data services framework code we
> > tend to not throw exceptions but instead funnel everything through
a
> > fault event mechanism. If you run into exceptions in our Flex
> framework
> > code then it may be a bug and should be reported with a
reproducible
> > case or at the very least a stacktrace. If these exceptions are
due
> to
> > non-Flex framework code then either its a bug in that 3rd party
code
> or,
> > as Matt suggested, the number of entry points that need to be
> checked
> > can be reduced by centralizing the calling code.
> >      
> >       Finally, the behavior of uncaught exceptions isn't determined by
> > Flex - it's a feature of the Flash Player virtual machine and how
it
> > handles ActionScript.
> >      
> >
> > ________________________________
> >
> >       From: flexcoders@yahoogroups.com
> > [mailto:[EMAIL PROTECTED] On Behalf Of Mykola Paliyenko
> >       Sent: Monday, April 24, 2006 3:34 AM
> >      
> >       To: flexcoders@yahoogroups.com
> >       Subject: Re: [flexcoders] Uncaught exceptions in Flex 1.5
> >      
> >
> >      
> >       Hm...
> >       Matt, I thought the problem will be fixed in 2.0, because
> > developing in the runtime that silently ignors the exceptions is
> > absolutely unaceptable for a lot of developers. It is extremely
hard
> to
> > locate problems in this case. I can understand why it is not
> implemented
> > in Flex 1.5 since the flash player did not changed, but I see no
> reasons
> > why whould not introduce this with a new version of player or at
> least
> > allow player to run in a debug mode where such stuff will be
> handled.
> >      
> >       Mykola
> >      
> >      
> >       On 4/23/06, Matt Chotin <mchotin@> wrote:
> >
> >             I see, the same problem exists in 2.0 I guess too
> > (though I've asked
> >             internally about it to make sure).  Only thing I can
> > recommend is you
> >             try to centralize your entry points.  If you use a
> > framework like
> >             Cairngorm you can do that in the framework by catching
> > errors in the
> >             broadcaster or some main method that triggers your
> > service handlers.
> >            
> >            
> >             Matt
> >            
> >            
> >             -----Original Message-----
> >             From: flexcoders@yahoogroups.com [mailto:
> > flexcoders@yahoogroups.com <mailto:flexcoders@yahoogroups.com> ]
On
> >             Behalf Of Stanislav Zayarsky
> >            
> >             Sent: Sunday, April 23, 2006 3:45 AM
> >             To: flexcoders@yahoogroups.com
> >             Subject: Re: [flexcoders] Uncaught exceptions in Flex
> > 1.5
> >            
> >             Matt, we are using 3rd party libraries like AS2lib, and
> > it throws
> >             exceptions.
> >             And also we starting to throw exceptions from our custom
> > classes too.
> >            
> >             Best regards
> >             Stanislav
> >            
> >             On 4/23/06, Matt Chotin <mchotin@> wrote:
> >             > In 1.5 we don't throw exceptions as a practice, I'm
> > not sure what
> >             you're
> >             > actually running into here?
> >             >
> >             > -----Original Message-----
> >             > From: flexcoders@yahoogroups.com [mailto:
> > flexcoders@yahoogroups.com <mailto:flexcoders@yahoogroups.com> ]
> >             On
> >             > Behalf Of Stanislav Zayarsky
> >             > Sent: Saturday, April 22, 2006 7:52 AM
> >             > To: flexcoders@yahoogroups.com
> >             > Subject: Re: [flexcoders] Uncaught exceptions in Flex
> > 1.5
> >             >
> >             > Hello FlexCoders,
> >             >
> >             > I have the same problem!
> >             >
> >             > Adobe guys, can you help us?
> >             >
> >             > Best regards
> >             > Stanislav
> >             >
> >             > On 4/21/06, Sergey Kovalyov
> > <skovalyov.flexcoders@> wrote:
> >             > > Hi All!
> >             > >
> >             > > How to deal with uncaught exceptions in Flex 1.5?
> > Actually they kill
> >             > > application running via terminating the current
> > script.
> >             > >
> >             > > Due to the fact Flex application has a lot of "entry
> > points" (each
> >             and
> >             > every
> >             > > event handling delegate), I  need either put
> > try..catch..finally
> >             > statements
> >             > > in each and every function assigned as an event
> > handler that is
> >             wrong
> >             > copy
> >             > > and paste method or create own Delegate class that
> > is much more
> >             better
> >             > by
> >             > > design.
> >             > >
> >             > > But on the other hand using the second approach
> > force me not to
> >             assign
> >             > event
> >             > > handlers in MXML (like <mx:Button
> > click="onClick()">). Instead we
> >             need
> >             > to
> >             > > assign those handlers in linked ActionScript class.
> > It's very
> >             > difficult when
> >             > > you deal with complex nested structures, repeaters,
> > ViewStack,
> >             > Accordion and
> >             > > their successors.
> >             > >
> >             > > Any suggestions?
> >             > >
> >             > > Thank you in advance.
> >             > >
> >             > > Regards, Sergey.
> >            
> >
> >
> >
> >       --
> >       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
> >
> >
> >            
> >       *      Visit your group "flexcoders
> > <http://groups.yahoo.com/group/flexcoders> " on the web.
> >              
> >       *      To unsubscribe from this group, send an email to:
> >               [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]
subject=Unsubscribe>
> >              
> >       *      Your use of Yahoo! Groups is subject to the Yahoo!
> > Terms of Service <http://docs.yahoo.com/info/terms/> .
> >
> >
> > ________________________________
> >
> >
> >
> >
> > --
> > WBR, Mykola
> >
> > --
> > 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
> >
> >
> >      
> > *      Visit your group "flexcoders
> > <http://groups.yahoo.com/group/flexcoders> " on the web.
> >        
> > *      To unsubscribe from this group, send an email to:
> >       [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]
subject=Unsubscribe>
> >        
> > *      Your use of Yahoo! Groups is subject to the Yahoo! Terms of
> > Service <http://docs.yahoo.com/info/terms/> .
> >
> >
> > ________________________________
> >
>






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




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to