Gone without a "trace"

[Jerry Daniels]

Troy (electron herder),

For the time being, GLX2 is being maintained. Mark and I keep a close  
eye on it. Are we adding tons of new features? No.

Will tRev supplant GLX2? We don't know yet. I think there is a good  
chance it will, but I don't want to commit to that just yet. Let's see  
how development on its debugger goes.

Technically, tRev has no debugger, but many of us can't use the  
debugger in Rev 3.5 or GLX2 with many scripts, anyway. This is due to  
architectural changes in the the way debugging is handled in Rev 3.5  
and higher.

What is the sound of a debugger not working? answer: no debugger. At  
least that's the case with my scripts.

We have gotten Rev to resolve tracebreak messages to tRev with  
contextual info. That is stage one of debugging remotely. I am also  
looking at kinder, gentler forms of debugging. tRev is a breakthrough  
product and not a me-too product, so I am going to look for really  
sleek solutions.

In the case of tRev, not having any debugger certainly helps me  
prioritize what needs to be in a debugging solution.

Best,

Jerry Daniels
Watch tRev - The Movie
http://reveditor.com/trev-the-movie


On Jul 28, 2009, at 7:25 PM, Troy Rollins wrote:

>
> On Jul 28, 2009, at 6:53 PM, Mark Wieder wrote:
>
>> I suppose I *should* point out that glx2 has a working trace in its
>> debugger...
>
> Will GLX2 even be maintained now that tRev is the hot new thing?  
> Which, as I understand it, does not have a debugger, right?
>
> --
> Troy
> RPSystems, Ltd.
> http://www.rpsystems.net
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution