Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of aharui@adobe.com designates
 64.18.1.21 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Thu, 19 Jan 2012 22:42:59 -0800
Subject: Re: Trace & Log
Thread-Topic: Trace & Log
Thread-Index: AczXIQJTOAS+qREhTsqZ/IqES5JtKQAHb1RS
Message-ID: <CB3E4CF3.3A97E%aharui@adobe.com>
In-Reply-To: <4F18DAD4.9060904@leichtgewicht.at>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


On 1/19/12 7:09 PM, "Martin Heidegger" <mh@leichtgewicht.at> wrote:

> If I wanted to profile my application I would use a profiler. However,
> Logging can be used for profiling but is just one of various use-cases
> and its not a important one. If you wish I could list the others, but in
> short:
>=20
> Basically its three things I _want_ to change:
>   1) Doing what logging does, just more _granular_. Granulate to methods
> or files.
>   2) Doing what logging does, just with _less coding_  for the _user_.
> Granulate without currently needed boilerplate code.
>   3) Doing what logging does, just more _verbose_. Show where the
> particular log statements have been originating from.
>=20
I'm still lost.  That is a description of what you want to do, but not why.
If not profiling, what do you want to know about the framework code that
requires a release player?

A debug SWF has file and line number information in it.  Would it be
sufficient to simply remove some of that information so it only has
information at method entry points?


--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui