Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#106 F1 auto keyword help; Interact with edit lines

open
nobody
None
5
2010-08-19
2010-08-19
kxroberto
No

F1 keyword help
F1: Python Help
Ctrl+F1: PythonWin
Alt+F1: MSDN
Numpy & wx

quick debugging and trying things out
(Ctrl-Enter Debugger can be used also after that:)
Ctrl-K : interact with marked editor lines in Interactive (in __main__)
Ctrl-E : exectued marked editor lines in Interactive (in __main__)
(works also while in debugger;)

Discussion

  • Mark Hammond
    Mark Hammond
    2010-08-25

    Thanks! But I think I'd prefer to see most of the help functionality in pywin/framework/help.py which already has support for the help menus. If we have support for the keyboard for these new help files, the menu should probably get them too (which the short-cut keys included) - but that might make things ugly given many people may not have wx or numpy installed. I wonder how hard it would be to refactor some of that and only show menu items if the help file is installed?

     
  • kxroberto
    kxroberto
    2010-08-26

    well, keyword help code perhaps could go permanently to help.py or the editor code.
    because probably there remain mainly only 2 kind of actions: keyword -> helpfile, keyword -> URL-templatestring "http:/....xy=%s". the only special handling, keyword modification "wx%s" could be also enabled by a predefined scheme. For the rest a (short) .cfg handler could still use the functions from pywin.framework.help.

    for (optional) help files a keyword help key could be set together with the help file (.chm or ULR) in registry, valueName/value like

    default="http://social.msdn.microsoft.com/Search/en-US/?Query=%s"
    keyword_help_key=Alt+F1

    WX-C-Help..
    keyword_help_key=F12
    keyword_help_keyword="wx%s"