Afaik the xml is only to make the breakpoints persistent.
The ide writes this file on exit and loads it on start.

Cheers,
Ralf.

john grden wrote:

that does make sense, but I thought the debugger used the XML file, not the IDE? So, if you were debugging remotely, you'd have this scenario?

swf --> Debugger <-- IDE (after reading in the breakpoints)

Forgive me, but this seems wacked if this is the case. Why waste the effort of having SEPY create external XML files that the IDE has to load for no other purpose other than to hand them off to the debugger? Doesn't that seem off?


On 8/9/05, *Johannes Nel* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    the way i understand it:
    that xml file tells the ide where to break in the swd. the swd dfoes
    not contain breakpoints all that is ide specific.

    On 8/9/05, john grden <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:
     > Plus, setting breakpoints at runtime is *nice*, but it's a perk,
    not a
     > feature of debugging.  Wouldn't that be a huge pain in the ass to
    do EVERY
     > time I restart my app?  Seems very counter productive.  I'd have
    a solution
     > that allowed me to set breakpoints at development time, with the
    option of
     > setting them at runtime.
     >
     >
     > On 8/9/05, john grden <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:
     > > well, I don't know about the SWD, I thought breakpoints were in
    there?
     > Anyway, why would you say that external editors shouldn't be able
    to set
     > breakpoints?  I would think that's COMPLETELY  useful?  If I
    write a class
     > in SEPY, only to have to open it in the IDE to set breakpoints,
    that's a
     > really crapy work flow.  But if Eclipse/SEPY/Primal script can
    set them,
     > that's 100% better.
     > >
     > > Couple that with developing an open source version of the
    debugger and
     > being able to pause the player, your mcuh closer to a true debugger.
     > Granted, *you* may not use the XML, but since those
    products(SEPY/Primal and
     > every other flash AS editor out there) will support the creation
    of them, it
     > would be silly not to.
     > >
     > >
     > >
     > > On 8/9/05, Nicolas Cannasse < [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]> > wrote:
     > > > Such XML is not needed since the debugger is able to set
    breakpoints at
     > > > runtime.
     > > > There is no breakpoints stored into the SWD... please have a
    look at the
     > > > protocol first.
     > > >
     > > > Nicolas
     > > >
     > > > ----- Original Message -----
     > > > From: "Scott Hyndman" < [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>>
     > > > To: "Open Source Flash Mailing List" < osflash@osflash.org
    <mailto:osflash@osflash.org>>
     > > > Sent: Monday, August 08, 2005 7:36 PM
     > > > Subject: RE: [osflash] OFD Project continued :: new Flash 8
    breakpoints
     > > > feature
     > > >
     > > >
     > > > Interesting. Perhaps this is what MTASC should read to
    produce the swd.
     > > >
     > > > /Scott
     > > >
     > > > -----Original Message-----
     > > > From: [EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]> on behalf of john grden
     > > > Sent: Mon 8/8/2005 1:24 PM
     > > > To: Open Source Flash Mailing List
     > > > Cc:
     > > > Subject: [osflash] OFD Project continued :: new Flash 8
    breakpoints
     > feature
     > > > I'm in a fog today (Lots' to do), but I can't beleive I
    forgot about
     > this!!!
     > > > Now that we can talk about the 8Ball features:
     > > >
     > > > A new feature in 8Ball is that you can have an external XML
    file created
     > > > that represents all the breakpoints in your Flash app. Where
    this is
     > useful
     > > > is in the External Editor's section like SEPY - now you'll be
    able to
     > enter
     > > > breakpoints in sepy for use with the Flash debugger. This is
    a sample of
     > the
     > > > XML:
     > > >
     > > > <?xml version="1.0"?>
     > > >
     > > > <flash_breakpoints version="1.0">
     > > >
     > > > <file name="c:\san\test files\stopwatch\stopwatch.as">
     > > >
     > > > <breakpoint line="10"></breakpoint>
     > > >
     > > > <breakpoint line="8"></breakpoint>
     > > >
     > > > <breakpoint line="6"></breakpoint>
     > > >
     > > > </file>
     > > >
     > > > </flash_breakpoints>
     > > >
     > > > also, when I had heard of this the first time, i started
    asking about
     > > > getting the debugger options open to the public and this is
    one response
     > I
     > > > did get from MM:
     > > >
     > > > "there have not been plans to do this, though it can certainly be
     > > > considered (and currently the debugger does not run over
     > > > LocalConnection). please feel free to file it as an
    Enhancement Request
     > > > (ECR). thanks!"
     > > >
     > > > So, for what it's worth, there you to ;)
     > > >
     > > > --
     > > > John Grden - Blitz
     > > >
     > > >
     > > >
     > > >
     > > >
     > > >
     > > >
     >
    ----------------------------------------------------------------------------

     > > > ----
     > > >
     > > >
     > > > > _______________________________________________
     > > > > osflash mailing list
     > > > > osflash@osflash.org <mailto:osflash@osflash.org>
     > > > >
     > http://osflash.org/mailman/listinfo/osflash_osflash.org
     > > > >
     > > >
     > > >
     > > > _______________________________________________
     > > > osflash mailing list
     > > > osflash@osflash.org <mailto:osflash@osflash.org>
     > > > http://osflash.org/mailman/listinfo/osflash_osflash.org
     > > >
     > >
     > >
     > >
     > > --
     > > John Grden - Blitz
     >
     >
     >
     > --
     > John Grden - Blitz
     > _______________________________________________
     > osflash mailing list
     > osflash@osflash.org <mailto:osflash@osflash.org>
     > http://osflash.org/mailman/listinfo/osflash_osflash.org
     >
     >
     >


    --
    j:pn

    _______________________________________________
    osflash mailing list
    osflash@osflash.org <mailto:osflash@osflash.org>
    http://osflash.org/mailman/listinfo/osflash_osflash.org




--
John Grden - Blitz


------------------------------------------------------------------------

_______________________________________________
osflash mailing list
osflash@osflash.org
http://osflash.org/mailman/listinfo/osflash_osflash.org

_______________________________________________
osflash mailing list
osflash@osflash.org
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to