That is true,we need to be able to activate/deactivate it. Personally I've used the old debug to trace my old and lazy writtentemplates, formost lazy written queries ( select * from ) on tables with 50 columns or so and finding plenty of Red millisecons displayed. Some of these outputs should have been dark red rather :)
On Tuesday, January 10, 2012, Alex Skinner <[email protected]> wrote: > I would say that there are instances when you do need the old way of debugging in addition to the debugger. Especially if we're looking to add the templating support which i am in the process of specing out. This is listed under coldfire support in the issue tracker. > My biggest thing would be to get the debugger rolled into the core and give a way of activating and dactivating it as with the current setup you can't remove the feature and restore standard debugging without restarting your app and removing the jar > A > > > > On 10 January 2012 17:04, Mats Stromberg <[email protected]> wrote: > > Well I would say they sure perform different functions since one can do so much morewith the plugin. So if it would be possible to deactivate the old debug for selected pages then the plugin debugger could switch it off for the frame set. On the other hand, when the plugin is there one really don't need the old way of debugging. It's more an issue of having something that behaves like the other engines. > > > On Tuesday, January 10, 2012, Alex Skinner <[email protected]> wrote: >> Yeah I think it makes total sense if the debugger goes into the standard build and there is an option to say >> Debugger (inpage / Plugin ) >> And switch between the two but as it is there is no way to easily switch. >> Though i'd say actually why not allow both ? >> They perform different functions ? >> A >> >> On 10 January 2012 16:06, Mats Stromberg <[email protected]> wrote: >>> >>> Well I could agree on that the debug output would be turned off if the plugin is used. Or a much cooler version would be that the standard debug would be deactivated and the controlling of the debug would be done as normal over the admin panel. >>> >>> /Mats/ >>> >>> On Tuesday, January 10, 2012, Alex Skinner <[email protected]> wrote: >>> > Guys also see the issue in the bug tracker regarding debugging added recently >>> > Thanks >>> > Alex >>> > >>> > On 10 January 2012 14:59, Mats Stromberg <[email protected]> wrote: >>> >> >>> >> Small Note for Alan.... Since you're planning on killing the WIKI.... don't forget to remove or change the link in the top frame for "debugger wiki" >>> >> /Mats/ >>> >> >>> >> -- >>> >> online documentation: http://openbd.org/manual/ >>> >> google+ hints/tips: https://plus.google.com/115990347459711259462 >>> >> http://groups.google.com/group/openbd?hl=en >>> >> >>> >> Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012 >>> > >>> > >>> > >>> > -- >>> > Alex Skinner >>> > Managing Director >>> > Pixl8 Interactive >>> > Tel: +448452600726 >>> > Email: [email protected] >>> > Web: pixl8.co.uk >>> > >>> > -- >>> > online documentation: http://openbd.org/manual/ >>> > google+ hints/tips: https://plus.google.com/115990347459711259462 >>> > http://groups.google.com/group/openbd?hl=en >>> > >>> > Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012 >>> > >>> >>> -- >>> online documentation: http://openbd.org/manual/ >>> google+ hints/tips: https://plus.google.com/115990347459711259462 >>> http://groups.google.com/group/openbd?hl=en >>> >>> Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012 >> >> >> >> -- >> Alex Skinner >> Managing Director >> Pixl8 Interactive >> Tel: > > -- > online documentation: http://openbd.org/manual/ > google+ hints/tips: https://plus.google.com/115990347459711259462 > http://groups.google.com/group/openbd?hl=en > > Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012 > -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012
