|
List Info
Thread: Re: output panel filters problem.
|
|
| Re: output panel filters problem. |
|
2007-03-06 11:29:37 |
|
OH man, I was just going through my Xray email and I saw this!! So sorry I didn't reply sooner!
below...
On 2/26/07, analogdesign < newsl analogdesign.ch">
newslanalogdesign.ch> wrote:
>> You're
the first person to bring it up ;)
Ok so I've right to go
nuts ;)
1:
package filtering!! That's a must have feature ;) How do you
intend to add this regarding to the GUI a radio button+ a
textfield ?
(
) DEBUG ; ( ) INFO ( ) WARN ( ) ERROR ; ( )
FATAL ( ) PACKAGE [whichPackage to filter]
a
radio button + a combobox automatically filled ? Go od questions  the answer is: I don't know yet. I have 2 other guys bugging me for Package filtering (including myself) and I just have to sit down and think it out. Part of the problem with it is, you have to use MTASC to compile or with the as3 version, you have to use the debug player to get packages. But that's all doable. Just need to sit and "do" it.
2:
bug report:
when I put in the search text field a string with a . the string isn't
searched:
myPackage ---> search occurs
myPackage. --->
search doesn't work
sometimes search
doesn9;t work and select random string in the output panel. I've remarked the
same behaviour in Flashout logger, so that's surely not caused by
xray.
Yeah, I'm sure I can fix that up much cleaner. I really just took it from the old interface and ported the functionality to as3/flex2.
3:
feature
request:
A:
It could be very
useful to have a search field which "keep an history of 10 previews searches "
(a bit like firefox does)
So, would this just be a history of the last 10 search phrases?
B:
next to [ ] case
sensitive: what about adding toggle autoscroll? What about
adding clear panel on new connection established?
It does auto scroll, maybe I'm missing what you're asking?
what's a clear panel? OH do you mean "clear trace output when new connection occurs"? yeah, I've wanted that too, but I think adding an Xray call instead might make more sense. That way, the developer can control if Xray's output is cleared or not when the app starts, OR when an app hits a certain section
C:
I definitely prefer
the way you choosed to output each trace occurence over flashout logger. I mean
including the class path + function where it was called.
Also the "show
output" check box and the way it behave.
Flashout logger:
when you pause trace output, it caches all the traces, when you
reenable trace outputs you have a flood of cached traces that most of the
time kill eclipse...
Don't you think that
show output should be by default on when you restart xray?
It's a toss up - I could turn it back on. Right now, it just remembers your last choice. I'm open to changing that though ;)
Don't you think that
the check box is a bit confusing for this feature? What about for example a
"play, stop button" ?
D:
Do you plan to add a
background color for each trace occurence? Whether a light odd/even
visualisation or/and a background color by log category?
Yeah, i'd like to, but to do that (correct me if I'm wrong) I have to do html text for the formatting. That slows down the output even faster/sooner than regular text. ; IE: when you get alot of traces happening, it takes up more CPU to render all of that then regular text. ; THe original interface used to do that btw
E:
what about adding
differenciation between traces which are called on fly from the xray interface
and those which are in classes?
Yeah that sounds good
I haven't much
experience with other loggers, but I feel like I prefer to have all centered in
one tool like xray.
Which logger do you
use? And do you think that xray can support all the must have features of a
perfect logger? (I trust you on that point ;) )
I use Xray's logger of course ;) All the features? Not yet, but it will have 90% of what most developers look for. I think that other 10% would be items like accomodating another logger or trace utility, but as for functionality (barring, of course, breakpoints), it'll have the features. If anything, it'll have more "runtime" options that other loggers aren't able to do without a proper interface to control them at runtime. Make sense?
Waouw one more time a bit long
;)
Sorry for
that.
Have a nice week
end!
Best regards.
Cedric Madelaine (aka
maddec)
analogdesign.ch
De : xray-bouncesosflash.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">xray-bouncesosflash.org
[mailto: xray-bouncesosflash.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">xray-bouncesosflash.org] De la part de John
Grden
Envoyé : vendredi, 23. février 2007
14:26
À : xrayosflash.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">xrayosflash.org
Objet : Re: [xray]
output panel filters problem.
you9;re right, there's an issue with that unfortunately. I was
waiting to put in package filtering before fixing that bug ;(
You9;re the
first person to bring it up ;)
On 2/23/07, analogdesign < newslanalogdesign.ch" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">newslanalogdesign.ch
>; wrote:
Hello
John,
I'd like to use the Xray
output instead of the flashout logger panel.
Traces are correctly
catched by xray output panel. But the filter thing with DEBUG, INFO, WARN,
ERROR, FATAL, doesn't filter anything...
XRAY
interface version:
Windows SWHX Projector v 2.0
connector version:
1.6.2
Based
on you sample Code
import com.blitzagency.xray.logger.XrayLog
;
log= new XrayLog();
trace(log.debug("stringMessage"
[
, object]));
trace(log.info("stringMessage"[
,
object]));
trace(log.warn("stringMessage"[,
object
]));
trace(log.error("stringMessage"[, object
]));
trace(log.fatal("stringMessage";[, object
]
));
trace("What's obj got!?";); Traces are correctly outputed but the log differenciation doesn't seem to work...
If you have some time to help me, it will be very kind of you...
Thank you in advance.
Best regards. Cedric Madelaine (aka maddec)
analogdesign.ch
_______________________________________________
xray
mailing list
xrayosflash.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">xrayosflash.org
http://osflash.org/mailman/listinfo/xray_osflash.org
--
[ JPG ]
_______________________________________________
xray mailing list
osflash.org">xrayosflash.org
http://osflash.org/mailman/listinfo/xray_osflash.org
--
[ JPG ]
|
| Re: output panel filters problem. |
|
2007-03-06 12:28:09 |
|
Hi,
John, why do you need mtasc or as3 to get the packages? Using the ClassFinder you are already using and the FunctionFinder, this info is readily available in as2 (and cached). Maybe not in 100% of the cases, but anyway, it might help^^.
I know the note on xflas2 still says the f...g thing is in beta^^ but it is actually pretty stable.
How it basically works is like this:
a function calls Logger.log ("foo");
The ClassFinder adds info to each class about its classname and package name, the FunctionFinder adds info to each function concerning its defining class.
In your log call you look up the calling function, ie arguments.caller
then you need two lookups:
myClass = FunctionFinder.getFunctionClass (arguments.caller);
myClassPath = ClassFinder.getPath(myClass);
Note that if you have:
class a.b.c.d.MyClass {
; function myMethod() {
; Logger.log("foo");
}
}
you could actually get Logger.log("foo") to say, okay this call came from "a.b.c.d.MyClass.myMethod", and then you can filter away.
This is exactly how it happens in xflas2.
I know we've been down this road before but feel free to copy anything usable. If you do want to take a look at the barebones of it, you'd need to check out the Logger / SendInfo / ClassFinder &; FunctionFinder classes. Packagefiltering, methodname filtering etc is all included as well though. And like I said, you dont need mtasc or as3 to do it.
An other option would be ofcourse to not include anything like this, and simply let people download the loggers of their choice. Most of them support Xray and if they dont... WELL THEY SHOULD coz it roxxors
Up the irons!
JC
On 3/6/07, John Grden < neorileygmail.com">neorileygmail.com> wrote:
OH man, I was just going through my Xray email and I saw this!! So sorry I didn't reply sooner!
below...
On 2/26/07, analogdesign <analogdesign.ch" target="_blank"> newslanalogdesign.ch
>; wrote:
>> You're the first person to bring it up ;)
Ok so I've right to go nuts ;)
1:
package filtering!! That's a must have feature ;) How do you intend to add this regarding to the GUI a radio button+ a textfield ?
( ) DEBUG ; ( ) INFO ( ) WARN ( ) ERROR ; ( ) FATAL ; ( ) PACKAGE [whichPackage to filter]
a radio button + a combobox automatically filled ?
Good questions the answer is: I don't know yet. I have 2 other guys bugging me for Package filtering (including myself) and I just have to sit down and think it out. Part of the problem with it is, you have to use MTASC to compile or with the as3 version, you have to use the debug player to get packages. But that's all doable. Just need to sit and "do" it.
2:
bug report:
when I put in the search text field a string with a . the string isn't searched:
myPackage ---> search occurs
myPackage. ---> search doesn't work
sometimes search doesn't work and select random string in the output panel. I've remarked the same behaviour in Flashout logger, so that's surely not caused by xray.
Yeah, I'm sure I can fix that up much cleaner. I really just took it from the old interface and ported the functionality to as3/flex2.
3:
feature request:
A:
It could be very useful to have a search field which "keep an history of 10 previews searches " (a bit like firefox does)
So, would this just be a history of the last 10 search phrases?
B:
next to [ ] case sensitive: what about adding toggle autoscroll? What about adding clear panel on new connection established?
It does auto scroll, maybe I'm missing what you're asking?
what's a clear panel? OH do you mean "clear trace output when new connection occurs"? yeah, I've wanted that too, but I think adding an Xray call instead might make more sense. That way, the developer can control if Xray's output is cleared or not when the app starts, OR when an app hits a certain section
C:
I definitely prefer the way you choosed to output each trace occurence over flashout logger. I mean including the class path + function where it was called.
Also the "show output" check box and the way it behave.
Flashout logger: when you pause trace output, it caches all the traces, when you reenable trace outputs you have a flood of cached traces that most of the time kill eclipse...
Don't you think that show output should be by default on when you restart xray?
It's a toss up - I could turn it back on. Right now, it just remembers your last choice. I'm open to changing that though ;)
Don't you think that the check box is a bit confusing for this feature? What about for example a "play, stop button" ?
D:
Do you plan to add a background color for each trace occurence? Whether a light odd/even visualisation or/and a background color by log category?
Yeah, i'd like to, but to do that (correct me if I'm wrong) I have to do html text for the formatting. That slows down the output even faster/sooner than regular text. ; IE: when you get alot of traces happening, it takes up more CPU to render all of that then regular text. ; THe original interface used to do that btw
E:
what about adding differenciation between traces which are called on fly from the xray interface and those which are in classes?
Yeah that sounds good
I haven't much experience with other loggers, but I feel like I prefer to have all centered in one tool like xray.
Which logger do you use? And do you think that xray can support all the must have features of a perfect logger? (I trust you on that point ;) )
I use Xray's logger of course ;) All the features? Not yet, but it will have 90% of what most developers look for. I think that other 10% would be items like accomodating another logger or trace utility, but as for functionality (barring, of course, breakpoints), it'll have the features. If anything, it'll have more "runtime" options that other loggers aren't able to do without a proper interface to control them at runtime. Make sense?
Waouw one more time a bit long ;)
Sorry for that.
Have a nice week end!
Best regards.
Cedric Madelaine (aka maddec)
analogdesign.ch
you9;re right, there's an issue with that unfortunately. I was waiting to put in package filtering before fixing that bug ;(
You9;re the first person to bring it up ;)
On 2/23/07, analogdesign <analogdesign.ch" target="_blank">newslanalogdesign.ch
> wrote:
Hello John,
I'd like to use the Xray output instead of the flashout logger panel.
Traces are correctly catched by xray output panel. But the filter thing with DEBUG, INFO, WARN, ERROR, FATAL, doesn't filter anything...
XRAY
interface version: Windows SWHX Projector v 2.0
connector version: 1.6.2
Based on you sample Code
import com.blitzagency
.xray.logger.XrayLog
;
log= new XrayLog();
trace(log.debug("stringMessage"
[
, object]));
trace(log.info("stringMessage"[
,
object]));
trace(log.warn("stringMessage"[,
object
]));
trace(log.error("stringMessage"[, object
]));
trace(log.fatal("stringMessage";[, object
]
));
trace("What's obj got!?";); Traces are correctly outputed but the log differenciation doesn't seem to work...
If you have some time to help me, it will be very kind of you...
Thank you in advance.
Best regards. Cedric Madelaine (aka maddec)
analogdesign.ch
_______________________________________________
xray mailing list
osflash.org" target="_blank">xrayosflash.org
http://osflash.org/mailman/listinfo/xray_osflash.org
--
[ JPG ]
_______________________________________________
xray mailing list
osflash.org" target="_blank">
xrayosflash.org
http://osflash.org/mailman/listinfo/xray_osflash.org
--
[ JPG ]
_______________________________________________
xray mailing list
osflash.org">
xrayosflash.org
http://osflash.org/mailman/listinfo/xray_osflash.org
|
| Re: output panel filters problem. |
 
|
2007-03-09 04:24:19 |
|
| ;) I thought it was so long that it blocked your e-mail
;)
Thank you for your answers.
My answers are below:
OH man, I was just going through my Xray email and I saw this!!
So sorry I didn't reply sooner!
below...
On 2/26/07, analogdesign <analogdesign.ch"> newslanalogdesign.ch> wrote:
>> You're the first person to bring
it up ;)
Ok so I've right to go nuts ;)
1:
package filtering!!
That's a must have feature ;) How do you intend to add this
regarding to the GUI a radio button+ a textfield ?
( ) DEBUG ; ( )
INFO ( ) WARN ( ) ERROR ; ( ) FATAL ; (
) PACKAGE [whichPackage to filter]
a radio button + a
combobox automatically filled ?
Good questions the answer is: I don't know yet. I have 2
other guys bugging me for Package filtering (including myself) and I just have
to sit down and think it out. Part of the problem with it is, you have to
use MTASC to compile or with the as3 version, you have to use the debug player
to get packages. But that's all doable. Just need to sit and "do"
it. ;
*
Ok ;) So I'll stop bugging you about it
;)
2:
bug
report:
when I put in the search
text field a string with a . the string isn't searched:
myPackage ---> search
occurs
myPackage. ---> search doesn't
work
sometimes search doesn't work and select
random string in the output panel. I've remarked the same behaviour in
Flashout logger, so that's surely not caused by
xray.
Yeah, I'm sure I can fix that up much cleaner. I really just took
it from the old interface and ported the functionality to
as3/flex2.
3:
feature request:
A:
It could be very useful to have a search
field which "keep an history of 10 previews searches " (a bit like firefox
does)
So, would this just be a history of the last 10 search phrases?
* yes or
more..
wether through an auto
complete string or a
combobox which is filled automatically. Like SEPY does for the search
feature.
B:
next to [ ] case sensitive: what about
adding toggle autoscroll? What about adding clear panel on new
connection established?
It does auto scroll, maybe I'm missing what you're asking?
* it was about
allowing to stop/activate the autoscroll feature. when you stop
autoscroll traces continue to be written below but let you freely scoll the
panel, without that it jumps to the bottom. (this is a different behaviour from
toggle output).
what's a clear panel? OH do
you mean "clear trace output when new connection occurs"? yeah, I've wanted that
too, but I think adding an Xray call instead might make more sense. That
way, the developer can control if Xray's output is cleared or not when the app
starts, OR when an app hits a certain section
*Yes ,
it's exactly what I meant.
C:
I definitely prefer the way you choosed to
output each trace occurence over flashout logger. I mean including the class
path + function where it was called.
Also the "show output" check box and the
way it behave.
Flashout logger: when you pause trace
output, it caches all the traces, when you reenable trace outputs you
have a flood of cached traces that most of the time kill
eclipse...
Don't you think that show output should be
by default on when you restart xray?
It's a toss up - I could turn it back on. Right now, it just
remembers your last choice. I'm open to changing that though ;)
Don't you think that the check box is a bit
confusing for this feature? What about for example a "play, stop button"
?
D:
Do you plan to add a background color for
each trace occurence? Whether a light odd/even visualisation or/and a
background color by log category?
Yeah, i'd like to, but to do that (correct me if I'm wrong) I have to
do html text for the formatting. That slows down the output even
faster/sooner than regular text. ; IE: when you get alot of traces
happening, it takes up more CPU to render all of that then regular text. ;
THe original interface used to do that btw
* Mmm, yes you're right.
Maybe a toggle output
coloring check box could be a solution?
E:
what about adding differenciation between
traces which are called on fly from the xray interface and those which are in
classes?
Yeah that sounds good
I haven't much experience with other
loggers, but I feel like I prefer to have all centered in one tool like
xray.
Which logger do you use? And do you think
that xray can support all the must have features of a perfect logger? (I trust
you on that point ;) )
I use Xray's logger of course ;) All the features? Not yet,
but it will have 90% of what most developers look for. I think that other 10%
would be items like accomodating another logger or trace utility, but as for
functionality (barring, of course, breakpoints), it'll have the features.
If anything, it'll have more "runtime" options that other loggers aren't able to
do without a proper interface to control them at runtime. Make
sense?
* Yes
of course, that's good news ;) breakpoints are definetely a
feature I'm looking forward to!
Have a nice week end!
Best
regards.
Cedric Madelaine (aka
maddec)
http://analogdesign.ch |
[1-3]
|
|
osflash.or
osflash.or
ray-bounce