[nvda] Re: What should the next version number be?
- From: Nimer Jaber <nimerjaber1@xxxxxxxxx>
- To: nvda@xxxxxxxxxxxxx
- Date: Tue, 28 Jul 2009 08:08:56 -0600
Thanks Nimer J Brian Gaff Lineone downstairs wrote:
Is powerpoint support actually doable? I've tried it in a number of readers and cannot make head nor tail of it, but then, its probably me!Brian bgaff@xxxxxxxxxxx Brian Gaff's other account. ----- Original Message ----- From: "Nimer Jaber" <nimerjaber1@xxxxxxxxx> To: <nvda@xxxxxxxxxxxxx> Sent: Tuesday, July 28, 2009 3:01 PM Subject: [nvda] Re: What should the next version number be?How about powerpoint support? Thanks Nimer J Brian's mail list account wrote:Yes, indeed, but I do feel we need to make it as transparent to an end user as possible. With regard to features. Firstly, the fields in some microsoft products, like access databases are not spoken as you cursor, similar ofn some programs like Goldwave dialogues, some speak when cursoring, some do not. Tags on emails would be nice too. I don't know if the crash on checkbox on Windows update is fixable, but if it is it would be less annoying. Brian bglists@xxxxxxxxxxxxxxxx Sent via blueyonder. Please address personal email to:- briang1@xxxxxxxxxxxxxxxx, putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Kennydog" <hurrikenny@xxxxxxxxxxxxxxx> To: <nvda@xxxxxxxxxxxxx> Sent: Tuesday, July 28, 2009 11:21 AM Subject: [nvda] Re: What should the next version number be?I don't mind version numbers so at least you know where the software is up to so 0.6, 0.7, 0.8 etc is ok till' you get to version numbers like 1 and as we progress in version numbers, then maybe it could go to RC1,RC2 then version? or the updates to that version or the old type alpha or beta. But before we get to version 1 I would like to see video hooks, reading of edit areas like ticket 84 which will make a difference to users - likewhen you fill in forms. Actually anything that is easy to understand isfine with me. the above might be easier to understand than preview releases maybe.. I am just thankful for just have and I am sure there are heaps out there like me.ing a free screen reader to use and promote compaired to something thattimes out and can't afford. Gene NZ On 28/07/2009 9:12 p.m., Simon Jaeger (laptop) wrote:yeah, I agree with that. besides, 2009.1 sounds so.....long. Simon ----- Original Message ----- From: "Ravi Paul"<ravipaul.rp@xxxxxxxxx> To:<nvda@xxxxxxxxxxxxx> Sent: Tuesday, July 28, 2009 2:05 AM Subject: [nvda] Re: What should the next version number be?The problem with basing the version numbering on year though, is, thatpeople may get confused about the feature ritch nature of a software or the lack of it. I think, the whole point of a version number is to make people understand the level up to which a software has progressed. I am not saying that essentially any software that has a greater version number is necessarily superior to one that has a lesser version number, but with NVDA, or with its continuous development, I feel that 0.6, 0.7 and so on or that kind of version scheme is more suitable... Regards Ravi PaulOn 7/28/09, Brian's mail list account<bglists@xxxxxxxxxxxxxxxx> wrote:Yes, I thought of this as well. I mean, look at amd processors, not content with a stupid name like Duron, they had to code name it Morgan as well! I still favour the year. It is what it says on the tin, so to speak, no need to look yp which is the latest, you would know pretty well which year it was built. Brian bglists@xxxxxxxxxxxxxxxx Sent via blueyonder. Please address personal email to:- briang1@xxxxxxxxxxxxxxxx, putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Vince Thacker"<vince@xxxxxxxxxxxxxxxxxxxxx> To:<nvda@xxxxxxxxxxxxx> Sent: Tuesday, July 28, 2009 4:28 AM Subject: [nvda] Re: What should the next version number be?You could always establish a Department for Silly Names, like the people who brought you Longhorn and Vista. So you could have NVDA<Moonwalker, followed by NVDA SunTrkker, follwed by....um, freedom rider.... Oh, no, someone might sue you. I wouldn't like to say who that might be. Hmm, you've also got to worry about what the name means in 65 other languages. Remember the Rolls-Royce Silver Mist? Ok, back to the drawing board. Vince. ----- Original Message ----- From: "Brian's mail list account"<bglists@xxxxxxxxxxxxxxxx> To:<nvda@xxxxxxxxxxxxx> Sent: Monday, July 27, 2009 5:46 PM Subject: [nvda] Re: What should the next version number be?No, but its not snazzy enough to convince people to try it out is it? grin. people like easy, easy is the year, in my view. Notice on for example, File Hippo, you get given new versions of software served up to you, and any beta ones. A nice name makes it clear what it is, so people tell me. Not that I'm suggesting allowing file hippo to have it, but then again... Brian bglists@xxxxxxxxxxxxxxxx Sent via blueyonder. Please address personal email to:- briang1@xxxxxxxxxxxxxxxx, putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Mike Bledig"<mgbledig@xxxxxxxxxxxxxx> To:<nvda@xxxxxxxxxxxxx> Sent: Monday, July 27, 2009 4:19 PM Subject: [nvda] Re: What should the next version number be?Hi there, I think the current versioning system is ok, but just needs to be made a little more clear. so in other words, version nvda_0.6p3.2_installer could be stated as nvda_rel0.6pre3.2_installer.So reading it one would know: it's a release of 0.6 of a preview atstage 3 with a miner repair at that stage Its not that difficult to follow if you really think about it. Kind regards, Mike -----Original Message----- From: nvda-bounce@xxxxxxxxxxxxx [mailto:nvda-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Curran Sent: Monday, July 27, 2009 12:25 PM To: nvda@xxxxxxxxxxxxx; Development for NonVisual Desktop Access Subject: [nvda] What should the next version number be? Hi all, Please have a read of the blog post: http://www.nvda-project.org/blog/WhatShouldNextVersionNumberBe And provide any feedback you can. Thanks Mick To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvda Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvda Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda--------------------------------------------------------------------------------No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.32/2266 - Release Date: 07/27/09 05:58:00 To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvdaThank you for your continued support of Nonvisual Desktop Access, anopen source free screen reader for Microsoft Windows: http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvdaTo post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvda Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda--------------------------------------------------------------------------------No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.32/2266 - Release Date: 07/27/09 05:58:00 To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvda Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvdaTo post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvda Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvda Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda------------------------------------------------------------------------No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.33/2267 - Release Date: 07/27/09 17:59:00--------------------------------------------------------------------------------No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.392 / Virus Database: 270.13.34/2268 - Release Date: 07/28/09 06:00:00 To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvda Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvdaTo post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvdaThank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows:http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda--------------------------------------------------------------------------------No virus found in this incoming message. Checked by AVG - www.avg.comVersion: 8.5.392 / Virus Database: 270.13.34/2268 - Release Date: 07/28/09 06:00:00To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvdaThank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows:http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda
To post messages to the list send email to nvda@xxxxxxxxxxxxx To modify your NVDA Email settings go to: http://www.freelists.org/list/nvda Thank you for your continued support of Nonvisual Desktop Access, an open source free screen reader for Microsoft Windows: http://www.nvda-project.org/ To get the latest NVDA snapshot: http://www.nvda-project.org/snapshots/ Report bugs or make feature requests at: http://trac.nvda-project.org/ Message Archive: http://www.freelists.org/archives/nvda
- References:
- [nvda] What should the next version number be?
- From: Michael Curran
- [nvda] Re: What should the next version number be?
- From: Mike Bledig
- [nvda] Re: What should the next version number be?
- From: Brian's mail list account
- [nvda] Re: What should the next version number be?
- From: Vince Thacker
- [nvda] Re: What should the next version number be?
- From: Brian's mail list account
- [nvda] Re: What should the next version number be?
- From: Ravi Paul
- [nvda] Re: What should the next version number be?
- From: Simon Jaeger \(laptop\)
- [nvda] Re: What should the next version number be?
- From: Kennydog
- [nvda] Re: What should the next version number be?
- From: Brian's mail list account
- [nvda] Re: What should the next version number be?
- From: Nimer Jaber
- [nvda] Re: What should the next version number be?
- From: Brian Gaff Lineone downstairs
- [nvda] What should the next version number be?
Other related posts:
- » [nvda] What should the next version number be? - Michael Curran
- » [nvda] Re: What should the next version number be? - Michel Such
- » [nvda] Re: What should the next version number be? - Felix Grützmacher
- » [nvda] Re: What should the next version number be? - Mike Bledig
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Kevin Cussick
- » [nvda] Re: What should the next version number be? - kendell clark
- » [nvda] Re: What should the next version number be? - Simon Jaeger \(laptop\)
- » [nvda] Re: What should the next version number be? - Brian Gaff Lineone downstairs
- » [nvda] Re: What should the next version number be? - José Manuel Ramos
- » [nvda] Re: What should the next version number be? - Brian Gaff Lineone downstairs
- » [nvda] Re: What should the next version number be? - shaun everiss
- » [nvda] Re: What should the next version number be? - shaun everiss
- » [nvda] Re: What should the next version number be? - Vince Thacker
- » [nvda] Re: What should the next version number be? - Ravi Paul
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Ravi Paul
- » [nvda] Re: What should the next version number be? - Simon Jaeger \(laptop\)
- » [nvda] Re: What should the next version number be? - James Teh
- » [nvda] Re: What should the next version number be? - Ravi Paul
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Kennydog
- » [nvda] Re: What should the next version number be? - Brian's mail list account
- » [nvda] Re: What should the next version number be? - Nimer Jaber
- » [nvda] Re: What should the next version number be? - Brian Gaff Lineone downstairs
- » [nvda] Re: What should the next version number be? - Nimer Jaber
- » [nvda] Re: What should the next version number be? - Timothy
- » [nvda] Re: What should the next version number be? - Trenton Matthews
- » [nvda] Re: What should the next version number be? - Nimer Jaber
- » [nvda] Re: What should the next version number be? - Brian Gaff
- » [nvda] Re: What should the next version number be? - Trenton Matthews
- » [nvda] Re: What should the next version number be? - Timothy
- » [nvda] Re: What should the next version number be? - Trenton Matthews
- » [nvda] Re: What should the next version number be? - Nimer Jaber