From: Homme, J. <jam...@hi...> - 2012-10-31 07:27:36
|
Hi, I have some related questions. If I want to look at the source code for an app module that already comes with NVDA, but I really don't care about any other files, at least for now, is it an OK idea to browse it on the site? Then, if I decide to attempt to change it, is it OK to copy and paste it into my text editor, or is there a more propper way to do this? When I go out there, I also want to make sure I browse to the latest version of the source, if that's what I'm supposed to do. Do I look for the highest build number? I'm trying to ask questions like this without having someone teach me Python. I think that part of what's going on is that I don't understand how big projects like this are put together, and the various file types and what they do. If it's better to point me to other reading material, I would be happy to go and read about it. I don't want to clog up the list with things I can learn elsewhere. I know you all have limited time. Thanks. Jim -----Original Message----- From: nvd...@li... [mailto:nvd...@li...] On Behalf Of James Teh Sent: Tuesday, October 30, 2012 8:42 PM To: NVDA screen reader development Subject: Re: [NVDA-dev] App Module Development Baby Steps Question Hi. NVDA is aware of whether it is running as a portable or installed copy. It won't search your user profile unless you're running as an installed copy. Jamie On 31/10/2012 4:44 AM, Homme, James wrote: > Hi, > Are you using the portable version or are you installing the "normal" version. I use portable because I don't have administrative rights over my computer. I see, though, that my old copy of the "normal" version put folders into my user roaming folders. One of the things I did while I was attempting to try things was to put my app module in the place the documentation says to put it in my user folders besides where I put them in the portable version. Does NVDA know if its running as a portable or as a "normal" session? Right now I know enough Python to shoot myself in the foot, but hopefully that will change as time goes on. > > Thanks. > > Jim > > > > -----Original Message----- > From: nvd...@li... > [mailto:nvd...@li...] On Behalf Of Lubos Pintes > Sent: Tuesday, October 30, 2012 3:58 AM > To: NVDA screen reader development > Subject: Re: [NVDA-dev] App Module Development Baby Steps Question > > Really when I developed some app modules, I used the reload command and NVDA behaviour became weird. It is difficult for me to reproduce anything, or properly described what was weird, but after restart everything was good. > In the past I used NVDA from source, now when snapshots are signed I am using them. So maybe there is some problem... > > Dňa 29. 10. 2012 23:56 Mesar Hameed wrote / napísal(a): >> Sometimes the shortcut doesnt seem to take real effect, and to really reload we have to restart nvda. >> >> I am thinking maybe this is due to the reimport is happening from the >> pyc file, but python hasn't for some reason detected that it needs to be recompiled. >> >> Dont know if this still happens, it was several months back since I tried it last. >> -- Mesar >> On Mon 29/10/12,18:20, Lubos Pintes wrote: >>> Restart is not necessary, use nvda+control+f3 to reload global >>> plugins and modules. >>> Dňa 29. 10. 2012 18:12 Ondrej Rosik wrote / napísal(a): >>>> did you restart NVDA after adding the appmodule? I didn't test this >>>> thing but this should be the problem. >>>> >>>> >>>> Dňa 29.10.2012 12:31 Homme, James wrote / napísal(a): >>>>> Hi, >>>>> >>>>> My question is how do I diagnose that the sample app module for >>>>> Notepad is not beeping for me, or at least I'm not hearing it do >>>>> so? Here's what I have done so far. >>>>> >>>>> I'm reading the developer documentation about the example Notepad >>>>> app module. I pasted the example into a text editor. Next, I put >>>>> it in the app modules directory (I use portable NVDA). When I ran >>>>> Notepad, I didn't hear beeps as I switched focus through various >>>>> windows. Before I started Notepad, I changed the log settings to >>>>> debug, so that I could get the most messages. I'm pretty sure that >>>>> I can tell that my app module runs when I use NVDA + F1 >>>>> immediately after I run Notepad and it gains focus. >>>>> >>>>> Thanks. >>>>> >>>>> Jim >>>>> >>>>> >>>>> ------------------------------------------------------------------ >>>>> - >>>>> ----- >>>>> >>>>> This e-mail and any attachments to it are confidential and are >>>>> intended solely for use of the individual or entity to whom they are addressed. >>>>> If you have received this e-mail in error, please notify the >>>>> sender immediately and then delete it. If you are not the intended >>>>> recipient, you must not keep, use, disclose, copy or distribute >>>>> this e-mail without the author's prior permission. The views >>>>> expressed in this e-mail message do not necessarily represent the >>>>> views of Highmark Inc., its subsidiaries, or affiliates. >>>>> >>>>> >>>>> __________________________________________ >>>>> A discussion list about the development of NVDA, the free and open >>>>> source screen reader for Windows. >>>>> nvd...@li... >>>>> (http://lists.nvaccess.org/listinfo/nvda-dev) >>>>> Note this list is for discussion of NVDA's general development. >>>>> Discussion about translating NVDA to various languages happens on >>>>> a separate email list. For more information about NVDA >>>>> localization and translation, please visit: >>>>> http://www.nvda-project.org/wiki/TranslatingNVDA >>>>> For an overview of NVDA development, please visit: >>>>> http://www.nvda-project.org/wiki/Development >>>>> To be notified of source code changes and trac ticket updates, >>>>> please subscribe to the nvda-commits list: >>>>> http://lists.nvaccess.org/listinfo/nvda-commits >>>>> >>>> __________________________________________ >>>> A discussion list about the development of NVDA, the free and open >>>> source screen reader for Windows. >>>> nvd...@li... >>>> (http://lists.nvaccess.org/listinfo/nvda-dev) >>>> Note this list is for discussion of NVDA's general development. >>>> Discussion about translating NVDA to various languages happens on a >>>> separate email list. For more information about NVDA localization >>>> and translation, please visit: >>>> http://www.nvda-project.org/wiki/TranslatingNVDA >>>> For an overview of NVDA development, please visit: >>>> http://www.nvda-project.org/wiki/Development >>>> To be notified of source code changes and trac ticket updates, >>>> please subscribe to the nvda-commits list: >>>> http://lists.nvaccess.org/listinfo/nvda-commits >>> >>> __________________________________________ >>> A discussion list about the development of NVDA, the free and open source screen reader for Windows. >>> nvd...@li... >>> (http://lists.nvaccess.org/listinfo/nvda-dev) >>> Note this list is for discussion of NVDA's general development. Discussion about translating NVDA to various languages happens on a separate email list. For more information about NVDA localization and translation, please visit: >>> http://www.nvda-project.org/wiki/TranslatingNVDA >>> For an overview of NVDA development, please visit: >>> http://www.nvda-project.org/wiki/Development >>> To be notified of source code changes and trac ticket updates, please subscribe to the nvda-commits list: >>> http://lists.nvaccess.org/listinfo/nvda-commits >> __________________________________________ >> A discussion list about the development of NVDA, the free and open source screen reader for Windows. >> nvd...@li... >> (http://lists.nvaccess.org/listinfo/nvda-dev) >> Note this list is for discussion of NVDA's general development. Discussion about translating NVDA to various languages happens on a separate email list. For more information about NVDA localization and translation, please visit: >> http://www.nvda-project.org/wiki/TranslatingNVDA >> For an overview of NVDA development, please visit: >> http://www.nvda-project.org/wiki/Development >> To be notified of source code changes and trac ticket updates, please subscribe to the nvda-commits list: >> http://lists.nvaccess.org/listinfo/nvda-commits > > > __________________________________________ > A discussion list about the development of NVDA, the free and open source screen reader for Windows. > nvd...@li... > (http://lists.nvaccess.org/listinfo/nvda-dev) > Note this list is for discussion of NVDA's general development. Discussion about translating NVDA to various languages happens on a separate email list. For more information about NVDA localization and translation, please visit: > http://www.nvda-project.org/wiki/TranslatingNVDA > For an overview of NVDA development, please visit: > http://www.nvda-project.org/wiki/Development > To be notified of source code changes and trac ticket updates, please subscribe to the nvda-commits list: > http://lists.nvaccess.org/listinfo/nvda-commits > __________________________________________ > A discussion list about the development of NVDA, the free and open source screen reader for Windows. > nvd...@li... > (http://lists.nvaccess.org/listinfo/nvda-dev) > Note this list is for discussion of NVDA's general development. Discussion about translating NVDA to various languages happens on a separate email list. For more information about NVDA localization and translation, please visit: > http://www.nvda-project.org/wiki/TranslatingNVDA > For an overview of NVDA development, please visit: > http://www.nvda-project.org/wiki/Development > To be notified of source code changes and trac ticket updates, please subscribe to the nvda-commits list: > http://lists.nvaccess.org/listinfo/nvda-commits > -- James Teh Director, NV Access Limited Email: ja...@nv... Web site: http://www.nvaccess.org/ Phone: +61 7 5667 8372 __________________________________________ A discussion list about the development of NVDA, the free and open source screen reader for Windows. nvd...@li... (http://lists.nvaccess.org/listinfo/nvda-dev) Note this list is for discussion of NVDA's general development. Discussion about translating NVDA to various languages happens on a separate email list. For more information about NVDA localization and translation, please visit: http://www.nvda-project.org/wiki/TranslatingNVDA For an overview of NVDA development, please visit: http://www.nvda-project.org/wiki/Development To be notified of source code changes and trac ticket updates, please subscribe to the nvda-commits list: http://lists.nvaccess.org/listinfo/nvda-commits |