I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr tcl/tk], but now I'm at a loss on how you debug the running application. I'm having trouble following the state variables of the megawidgets, and I'd really like to be able to set break points in the tcl/tk code and examine objects. Any help would be appreciated. My goal is to provide fixes to the source, and add an optional new editor keybindings configuration file (wordstar to start with). Thanks _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com
I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr tcl/tk], but now I'm at a loss on how you debug the running application. I'm having trouble following the state variables of the megawidgets, and I'd really like to be able to set break points in the tcl/tk code and examine objects. Any help would be appreciated. My goal is to provide fixes to the source, and add an optional new editor keybindings configuration file (wordstar to start with). Thanks _________________________________________________________________ Join the worldÂs largest e-mail service with MSN Hotmail. http://www.hotmail.com
At 01:19 AM 12/13/01 +0000, you wrote:
Here is my wish list:
- HTML help files included with binary
- list of array variables in menu Symbols-View-Variables
- goto line doesn't seem to work (if patch isn't currently included with d/l)
- iconise all windows command in Window menu
- Goto sel in top level Search menu instead of its own Search-Goto-Goto
menu. This to make the goto command easier to get to.
- multiple bookmarks (at least 10), with its own bookmarks menu, instead of
just the one bookamark in the Search-Goto menu.
- a version of SN with compiled executable tcl/tk files instead of the
interpreted format for improved execution speed (if not already done).
- and last but not least, reduced memory usage if possible
>I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr
>tcl/tk], but now I'm at a loss on how you debug the running application.
>I'm having trouble following the state variables of the megawidgets, and
>I'd really like to be able to set break points in the tcl/tk code and
>examine objects.
>
>Any help would be appreciated. My goal is to provide fixes to the source,
>and add an optional new editor keybindings configuration file (wordstar to
>start with).
Yeah, those would be nice. So far, I've only been able to change simple things like changing the default symbol browser combo box to check only Functions, and change some key bindings. >From: Mike Fahlbusch <mcf@cobweb.com.au> >To: sourcenav@sources.redhat.com >CC: "Left Spin" <leftspin@hotmail.com> >Subject: Re: Debugging SourceNavigator >Date: Thu, 13 Dec 2001 12:21:10 +1030 > >At 01:19 AM 12/13/01 +0000, you wrote: > >Here is my wish list: > >- HTML help files included with binary >- list of array variables in menu Symbols-View-Variables >- goto line doesn't seem to work (if patch isn't currently included with >d/l) >- iconise all windows command in Window menu >- Goto sel in top level Search menu instead of its own Search-Goto-Goto >menu. This to make the goto command easier to get to. >- multiple bookmarks (at least 10), with its own bookmarks menu, instead of >just the one bookamark in the Search-Goto menu. >- a version of SN with compiled executable tcl/tk files instead of the >interpreted format for improved execution speed (if not already done). >- and last but not least, reduced memory usage if possible > > >>I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr >>tcl/tk], but now I'm at a loss on how you debug the running application. >>I'm having trouble following the state variables of the megawidgets, and >>I'd really like to be able to set break points in the tcl/tk code and >>examine objects. >> >>Any help would be appreciated. My goal is to provide fixes to the source, >>and add an optional new editor keybindings configuration file (wordstar to >>start with). > _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com
Mike Fahlbusch wrote: > > At 01:19 AM 12/13/01 +0000, you wrote: > > Here is my wish list: > > - HTML help files included with binary They should be there, actually. They should end up in share/doc/html or some such place. > - list of array variables in menu Symbols-View-Variables > - goto line doesn't seem to work (if patch isn't currently included with d/l) > - iconise all windows command in Window menu > - Goto sel in top level Search menu instead of its own Search-Goto-Goto > menu. This to make the goto command easier to get to. > - multiple bookmarks (at least 10), with its own bookmarks menu, instead of > just the one bookamark in the Search-Goto menu. > - a version of SN with compiled executable tcl/tk files instead of the > interpreted format for improved execution speed (if not already done). Unlikely. Tcl/Tk is much faster now than it used to be. Most of the slowdowns are in questionable coding practices in the tcl code or the extensions that were written for SN. We did not have time to fix them all. > - and last but not least, reduced memory usage if possible Difficult at best. SN has a lot of info sitting around. > >I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr > >tcl/tk], but now I'm at a loss on how you debug the running application. There is no good way to step SN through a debugger. I would investigate setting the SN_DEBUG variable and using the logging. I have also spent time actually in gdb with the C code for the Tcl interpreter figuring out problems. > >I'm having trouble following the state variables of the megawidgets, and > >I'd really like to be able to set break points in the tcl/tk code and > >examine objects. One thing you can do is launch the console, load the SN part, and then selectively replace the pieces you need. tk is a dynamic coding environment, and you should be able to take advantage of that. > >Any help would be appreciated. My goal is to provide fixes to the source, > >and add an optional new editor keybindings configuration file (wordstar to > >start with). Good luck to you.
At 01:18 AM 12/13/01 +0000, you wrote: >I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr >tcl/tk], but now I'm at a loss on how you debug the running application. I'm >having trouble following the state variables of the megawidgets, and I'd >really like to be able to set break points in the tcl/tk code and examine >objects. There's a very good debugger/inspector for Tcl/Tk/Tix called TixInspect, which has a basic but fairly useful debugger built into it. The inspector lets you see everything, and modify things on the fly - it's very powerful. Look at http://tix.sourceforge.net/Tixapps To use SN with TixInspect under Unix, you'll have to comply with Tk's semi-rigorous demands for Xauth authentication and no xhosts, or recompile the tk dynamic library with this turned off. In the Makefile for tk, look for # To turn off the security checks that disallow incoming sends when # the X server appears to be insecure, reverse the comments on the # following lines: SECURITY_FLAGS = #SECURITY_FLAGS = -DTK_NO_SECURITY Then in the SN code, if it's not already there, add the following line; tk appname "SN#[winfo id .]" To use SN with TixInspect under Windows, you'll have make sure the Tcl tcldde83.dll is available either in the directory with with the tcl83.dll or in lib/tcl8.3/dde1.0 (replace 83 with whatever verion of Tcl you're using). Then in the SN code, if it's not already there, add the following lines; package require dde dde servername "SN#[winfo id .]" >Any help would be appreciated. My goal is to provide fixes to the source, >and add an optional new editor keybindings configuration file (wordstar to >start with). TixInspect is the revised updated version of the time-honoured Tkinspect, and is built for Tix applications such as SN. OTOH, if I had of known you were going to use it for adding Wordstar bindings, I would never have released it:-) Mike.
At 10:50 PM 12/12/01 -0800, Syd Polk wrote: > > >Mike Fahlbusch wrote: > >> >I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr >> >tcl/tk], but now I'm at a loss on how you debug the running application. > >There is no good way to step SN through a debugger. I would investigate >setting the SN_DEBUG variable and using the logging. I have also spent >time actually in gdb with the C code for the Tcl interpreter figuring >out problems. With Tixinspect you are debugging the run-time program by connecting to it with Tk's send mechanism. After making the SN interpreter "visible" to send by doing the steps I outlined previously, use File/Select Interpreter/ and look for the interpreter named SN#xxxx where xxxx is the window id. >> >I'm having trouble following the state variables of the megawidgets, and >> >I'd really like to be able to set break points in the tcl/tk code and >> >examine objects. > >One thing you can do is launch the console, load the SN part, and then >selectively replace the pieces you need. tk is a dynamic coding >environment, and you should be able to take advantage of that. With Tixinspect use Tcl/TixDebug to bring up the debugger, then click on Refresh. It takes advantage of the fact that tk is a dynamic coding environment, and selectively replace the pieces you choose with instrumented procedures that activate the debugger. You can set breakpoints, or step through procedures. Mike.
I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr tcl/tk], but now I'm at a loss on how you debug the running application. I'm having trouble following the state variables of the megawidgets, and I'd really like to be able to set break points in the tcl/tk code and examine objects. Any help would be appreciated. My goal is to provide fixes to the source, and add an optional new editor keybindings configuration file (wordstar to start with). Thanks _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com
[-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 638 bytes --] I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr tcl/tk], but now I'm at a loss on how you debug the running application. I'm having trouble following the state variables of the megawidgets, and I'd really like to be able to set break points in the tcl/tk code and examine objects. Any help would be appreciated. My goal is to provide fixes to the source, and add an optional new editor keybindings configuration file (wordstar to start with). Thanks _________________________________________________________________ Join the worldÂs largest e-mail service with MSN Hotmail. http://www.hotmail.com
At 01:19 AM 12/13/01 +0000, you wrote:
Here is my wish list:
- HTML help files included with binary
- list of array variables in menu Symbols-View-Variables
- goto line doesn't seem to work (if patch isn't currently included with d/l)
- iconise all windows command in Window menu
- Goto sel in top level Search menu instead of its own Search-Goto-Goto
menu. This to make the goto command easier to get to.
- multiple bookmarks (at least 10), with its own bookmarks menu, instead of
just the one bookamark in the Search-Goto menu.
- a version of SN with compiled executable tcl/tk files instead of the
interpreted format for improved execution speed (if not already done).
- and last but not least, reduced memory usage if possible
>I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr
>tcl/tk], but now I'm at a loss on how you debug the running application.
>I'm having trouble following the state variables of the megawidgets, and
>I'd really like to be able to set break points in the tcl/tk code and
>examine objects.
>
>Any help would be appreciated. My goal is to provide fixes to the source,
>and add an optional new editor keybindings configuration file (wordstar to
>start with).
Yeah, those would be nice. So far, I've only been able to change simple things like changing the default symbol browser combo box to check only Functions, and change some key bindings. >From: Mike Fahlbusch <mcf@cobweb.com.au> >To: sourcenav@sources.redhat.com >CC: "Left Spin" <leftspin@hotmail.com> >Subject: Re: Debugging SourceNavigator >Date: Thu, 13 Dec 2001 12:21:10 +1030 > >At 01:19 AM 12/13/01 +0000, you wrote: > >Here is my wish list: > >- HTML help files included with binary >- list of array variables in menu Symbols-View-Variables >- goto line doesn't seem to work (if patch isn't currently included with >d/l) >- iconise all windows command in Window menu >- Goto sel in top level Search menu instead of its own Search-Goto-Goto >menu. This to make the goto command easier to get to. >- multiple bookmarks (at least 10), with its own bookmarks menu, instead of >just the one bookamark in the Search-Goto menu. >- a version of SN with compiled executable tcl/tk files instead of the >interpreted format for improved execution speed (if not already done). >- and last but not least, reduced memory usage if possible > > >>I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr >>tcl/tk], but now I'm at a loss on how you debug the running application. >>I'm having trouble following the state variables of the megawidgets, and >>I'd really like to be able to set break points in the tcl/tk code and >>examine objects. >> >>Any help would be appreciated. My goal is to provide fixes to the source, >>and add an optional new editor keybindings configuration file (wordstar to >>start with). > _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com
Mike Fahlbusch wrote: > > At 01:19 AM 12/13/01 +0000, you wrote: > > Here is my wish list: > > - HTML help files included with binary They should be there, actually. They should end up in share/doc/html or some such place. > - list of array variables in menu Symbols-View-Variables > - goto line doesn't seem to work (if patch isn't currently included with d/l) > - iconise all windows command in Window menu > - Goto sel in top level Search menu instead of its own Search-Goto-Goto > menu. This to make the goto command easier to get to. > - multiple bookmarks (at least 10), with its own bookmarks menu, instead of > just the one bookamark in the Search-Goto menu. > - a version of SN with compiled executable tcl/tk files instead of the > interpreted format for improved execution speed (if not already done). Unlikely. Tcl/Tk is much faster now than it used to be. Most of the slowdowns are in questionable coding practices in the tcl code or the extensions that were written for SN. We did not have time to fix them all. > - and last but not least, reduced memory usage if possible Difficult at best. SN has a lot of info sitting around. > >I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr > >tcl/tk], but now I'm at a loss on how you debug the running application. There is no good way to step SN through a debugger. I would investigate setting the SN_DEBUG variable and using the logging. I have also spent time actually in gdb with the C code for the Tcl interpreter figuring out problems. > >I'm having trouble following the state variables of the megawidgets, and > >I'd really like to be able to set break points in the tcl/tk code and > >examine objects. One thing you can do is launch the console, load the SN part, and then selectively replace the pieces you need. tk is a dynamic coding environment, and you should be able to take advantage of that. > >Any help would be appreciated. My goal is to provide fixes to the source, > >and add an optional new editor keybindings configuration file (wordstar to > >start with). Good luck to you.
At 01:18 AM 12/13/01 +0000, you wrote: >I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr >tcl/tk], but now I'm at a loss on how you debug the running application. I'm >having trouble following the state variables of the megawidgets, and I'd >really like to be able to set break points in the tcl/tk code and examine >objects. There's a very good debugger/inspector for Tcl/Tk/Tix called TixInspect, which has a basic but fairly useful debugger built into it. The inspector lets you see everything, and modify things on the fly - it's very powerful. Look at http://tix.sourceforge.net/Tixapps To use SN with TixInspect under Unix, you'll have to comply with Tk's semi-rigorous demands for Xauth authentication and no xhosts, or recompile the tk dynamic library with this turned off. In the Makefile for tk, look for # To turn off the security checks that disallow incoming sends when # the X server appears to be insecure, reverse the comments on the # following lines: SECURITY_FLAGS = #SECURITY_FLAGS = -DTK_NO_SECURITY Then in the SN code, if it's not already there, add the following line; tk appname "SN#[winfo id .]" To use SN with TixInspect under Windows, you'll have make sure the Tcl tcldde83.dll is available either in the directory with with the tcl83.dll or in lib/tcl8.3/dde1.0 (replace 83 with whatever verion of Tcl you're using). Then in the SN code, if it's not already there, add the following lines; package require dde dde servername "SN#[winfo id .]" >Any help would be appreciated. My goal is to provide fixes to the source, >and add an optional new editor keybindings configuration file (wordstar to >start with). TixInspect is the revised updated version of the time-honoured Tkinspect, and is built for Tix applications such as SN. OTOH, if I had of known you were going to use it for adding Wordstar bindings, I would never have released it:-) Mike.
At 10:50 PM 12/12/01 -0800, Syd Polk wrote: > > >Mike Fahlbusch wrote: > >> >I'd like to improve on Source Navigator. I've read up on tcl/tk and [incr >> >tcl/tk], but now I'm at a loss on how you debug the running application. > >There is no good way to step SN through a debugger. I would investigate >setting the SN_DEBUG variable and using the logging. I have also spent >time actually in gdb with the C code for the Tcl interpreter figuring >out problems. With Tixinspect you are debugging the run-time program by connecting to it with Tk's send mechanism. After making the SN interpreter "visible" to send by doing the steps I outlined previously, use File/Select Interpreter/ and look for the interpreter named SN#xxxx where xxxx is the window id. >> >I'm having trouble following the state variables of the megawidgets, and >> >I'd really like to be able to set break points in the tcl/tk code and >> >examine objects. > >One thing you can do is launch the console, load the SN part, and then >selectively replace the pieces you need. tk is a dynamic coding >environment, and you should be able to take advantage of that. With Tixinspect use Tcl/TixDebug to bring up the debugger, then click on Refresh. It takes advantage of the fact that tk is a dynamic coding environment, and selectively replace the pieces you choose with instrumented procedures that activate the debugger. You can set breakpoints, or step through procedures. Mike.