Heliopolis and Pylennium projects: progress, next wxPython 4 powered snapshot posted

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Heliopolis and Pylennium projects: progress, next wxPython 4 powered snapshot posted

Joseph Lee

Dear NVDA community,

 

For new people: the following may not concern you unless you are eager to try absolutely latest alpha-level code, interested in helping out with coding and testing, or curious about what goes on in some development labs. Also, note that I (Joseph Lee) do not work for NV Access.

 

I’m here to report on the progress of two projects I’m working on:

 

  • Heliopolis: let NVDA’s GUI be powered by wxPython 4 (Project Phoenix). I’m happy to announce the release of the next snapshot (20170725), powered by latest NVDA master snapshot code and wxPython 4 beta 1. For those of you who’ve used previous snapshots from this family, the major wx.Yield bug remains, and it appears it’s time to come up with our own solution (ask Jamie as to why). The new snapshot can be found at:

http://www.josephsl.net/files/bin/nvda_snapshot_wxPy4-20170725.exe

 

For new people: Project Heliopolis (Greek for “sun city”) is meant to test NVDA with wxPython 4.0.0. Use of wxPython 4 is a critical milestone before we can embark fully on Pylennium (see below).

 

  • Pylennium: Moving onto Python 3. As of latest commit, you’ll be able to see first moments of NVDA’s initialization (core.main up to an attempt to initialize app module handler) via command line (Python 3’s python.exe). In order to see this, you need the following dependencies installed or copied to misc-deps/python directory: Python 3.6.x (I use 3.4.3 internally for now), comtypes 1.1.3, configobj 5.0.6, wxPython 4.0.0, pywin32 221, six 1.10.0. Also, before copying misc-deps/python modules, you need to run scons source at least once under Python 2.7 to build the source code copy BEFORE “upgrading” to Python 3 dependencies. In case of wxPython, you need to use the wheel designed for the Python release you plan to test with. I’m using Python 3.4 so basic porting can happen, release a source code level snapshot that should run on Windows XP, and then switch to Python 3.6 and start gathering ideas in using Python 3 modules fully (such as collections.ChainMap, asyncio and what not). I expect this project to take about a year or so to complete, including porting add-ons. At the moment the biggest showstoppers are attribute error exception in nvwave when WavePlayer.__del__ is called (resulting in failure to initialize audio output subsystem), inability to gather log output due to file() versus (open() functions, and Python 3 and liblouis is disputing Unicode width.

 

For new people: NVDA is written in Python 2.7, but there were numerous feedback regarding switching the source code to Python 3. NV Access staff and some contributors believe that next year would be a good time to port bulk of NVDA to Python 3, but I figured it’d be a good idea to lay the foundation and send a report to the community regarding preparations and what to expect in the end. The name “pylennium” is a combination of “python” and “millennium”, with the latter term coming from Python 3000.

 

Cheers,

Joseph


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Heliopolis and Pylennium projects: progress, next wxPython 4 powered snapshot posted

austin pinto
will this snapshot be updated?

On 7/25/17, Joseph Lee <[hidden email]> wrote:

> Dear NVDA community,
>
>
>
> For new people: the following may not concern you unless you are eager to
> try absolutely latest alpha-level code, interested in helping out with
> coding and testing, or curious about what goes on in some development labs.
> Also, note that I (Joseph Lee) do not work for NV Access.
>
>
>
> I'm here to report on the progress of two projects I'm working on:
>
>
>
> * Heliopolis: let NVDA's GUI be powered by wxPython 4 (Project
> Phoenix). I'm happy to announce the release of the next snapshot
> (20170725),
> powered by latest NVDA master snapshot code and wxPython 4 beta 1. For
> those
> of you who've used previous snapshots from this family, the major wx.Yield
> bug remains, and it appears it's time to come up with our own solution (ask
> Jamie as to why). The new snapshot can be found at:
>
> http://www.josephsl.net/files/bin/nvda_snapshot_wxPy4-20170725.exe
>
>
>
> For new people: Project Heliopolis (Greek for "sun city") is meant to test
> NVDA with wxPython 4.0.0. Use of wxPython 4 is a critical milestone before
> we can embark fully on Pylennium (see below).
>
>
>
> * Pylennium: Moving onto Python 3. As of latest commit, you'll be able
> to see first moments of NVDA's initialization (core.main up to an attempt
> to
> initialize app module handler) via command line (Python 3's python.exe). In
> order to see this, you need the following dependencies installed or copied
> to misc-deps/python directory: Python 3.6.x (I use 3.4.3 internally for
> now), comtypes 1.1.3, configobj 5.0.6, wxPython 4.0.0, pywin32 221, six
> 1.10.0. Also, before copying misc-deps/python modules, you need to run
> scons
> source at least once under Python 2.7 to build the source code copy BEFORE
> "upgrading" to Python 3 dependencies. In case of wxPython, you need to use
> the wheel designed for the Python release you plan to test with. I'm using
> Python 3.4 so basic porting can happen, release a source code level
> snapshot
> that should run on Windows XP, and then switch to Python 3.6 and start
> gathering ideas in using Python 3 modules fully (such as
> collections.ChainMap, asyncio and what not). I expect this project to take
> about a year or so to complete, including porting add-ons. At the moment
> the
> biggest showstoppers are attribute error exception in nvwave when
> WavePlayer.__del__ is called (resulting in failure to initialize audio
> output subsystem), inability to gather log output due to file() versus
> (open() functions, and Python 3 and liblouis is disputing Unicode width.
>
>
>
> For new people: NVDA is written in Python 2.7, but there were numerous
> feedback regarding switching the source code to Python 3. NV Access staff
> and some contributors believe that next year would be a good time to port
> bulk of NVDA to Python 3, but I figured it'd be a good idea to lay the
> foundation and send a report to the community regarding preparations and
> what to expect in the end. The name "pylennium" is a combination of
> "python"
> and "millennium", with the latter term coming from Python 3000.
>
>
>
> Cheers,
>
> Joseph
>
>


--
search for me on facebook, google+, orkut..
[hidden email]
follow me on twitter.
austinmpinto
contact me on skype.
austin.pinto3

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Heliopolis and Pylennium projects: progress, next wxPython 4 powered snapshot posted

Joseph Lee
Hi,
Yes and no. Yes, I'll continue to release this snapshot series, and no, you
cannot update to newer versions directly as there's no "check for update"
option.
Cheers,
Joseph

-----Original Message-----
From: Austin Pinto [mailto:[hidden email]]
Sent: Tuesday, July 25, 2017 3:12 AM
To: NVDA screen reader development <[hidden email]>
Subject: Re: [Nvda-devel] Heliopolis and Pylennium projects: progress, next
wxPython 4 powered snapshot posted

will this snapshot be updated?

On 7/25/17, Joseph Lee <[hidden email]> wrote:
> Dear NVDA community,
>
>
>
> For new people: the following may not concern you unless you are eager
> to try absolutely latest alpha-level code, interested in helping out
> with coding and testing, or curious about what goes on in some development
labs.

> Also, note that I (Joseph Lee) do not work for NV Access.
>
>
>
> I'm here to report on the progress of two projects I'm working on:
>
>
>
> * Heliopolis: let NVDA's GUI be powered by wxPython 4 (Project
> Phoenix). I'm happy to announce the release of the next snapshot
> (20170725), powered by latest NVDA master snapshot code and wxPython 4
> beta 1. For those of you who've used previous snapshots from this
> family, the major wx.Yield bug remains, and it appears it's time to
> come up with our own solution (ask Jamie as to why). The new snapshot
> can be found at:
>
> http://www.josephsl.net/files/bin/nvda_snapshot_wxPy4-20170725.exe
>
>
>
> For new people: Project Heliopolis (Greek for "sun city") is meant to
> test NVDA with wxPython 4.0.0. Use of wxPython 4 is a critical
> milestone before we can embark fully on Pylennium (see below).
>
>
>
> * Pylennium: Moving onto Python 3. As of latest commit, you'll be able
> to see first moments of NVDA's initialization (core.main up to an
> attempt to initialize app module handler) via command line (Python 3's
> python.exe). In order to see this, you need the following dependencies
> installed or copied to misc-deps/python directory: Python 3.6.x (I use
> 3.4.3 internally for now), comtypes 1.1.3, configobj 5.0.6, wxPython
> 4.0.0, pywin32 221, six 1.10.0. Also, before copying misc-deps/python
> modules, you need to run scons source at least once under Python 2.7
> to build the source code copy BEFORE "upgrading" to Python 3
> dependencies. In case of wxPython, you need to use the wheel designed
> for the Python release you plan to test with. I'm using Python 3.4 so
> basic porting can happen, release a source code level snapshot that
> should run on Windows XP, and then switch to Python 3.6 and start
> gathering ideas in using Python 3 modules fully (such as
> collections.ChainMap, asyncio and what not). I expect this project to
> take about a year or so to complete, including porting add-ons. At the
> moment the biggest showstoppers are attribute error exception in
> nvwave when WavePlayer.__del__ is called (resulting in failure to
> initialize audio output subsystem), inability to gather log output due
> to file() versus
> (open() functions, and Python 3 and liblouis is disputing Unicode width.
>
>
>
> For new people: NVDA is written in Python 2.7, but there were numerous
> feedback regarding switching the source code to Python 3. NV Access
> staff and some contributors believe that next year would be a good
> time to port bulk of NVDA to Python 3, but I figured it'd be a good
> idea to lay the foundation and send a report to the community
> regarding preparations and what to expect in the end. The name
> "pylennium" is a combination of "python"
> and "millennium", with the latter term coming from Python 3000.
>
>
>
> Cheers,
>
> Joseph
>
>


--
search for me on facebook, google+, orkut..
[hidden email]
follow me on twitter.
austinmpinto
contact me on skype.
austin.pinto3

----------------------------------------------------------------------------
--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Heliopolis and Pylennium projects: progress, next wxPython 4 powered snapshot posted

Development mailing list
In reply to this post by Joseph Lee
Clear as mud of course for me, but if this is still going to be 32 bit code,
where is the benefit? If on the other hand it is envisaged to go 64 bit and
multi processor support then you have a whole new ball game here.
 Brian

[hidden email]
Sent via blueyonder.
Please address personal email to:-
[hidden email], putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <[hidden email]>
To: "'NVDA screen reader development'" <[hidden email]>
Sent: Tuesday, July 25, 2017 8:57 AM
Subject: [Nvda-devel] Heliopolis and Pylennium projects: progress, next
wxPython 4 powered snapshot posted


> Dear NVDA community,
>
>
>
> For new people: the following may not concern you unless you are eager to
> try absolutely latest alpha-level code, interested in helping out with
> coding and testing, or curious about what goes on in some development
> labs.
> Also, note that I (Joseph Lee) do not work for NV Access.
>
>
>
> I'm here to report on the progress of two projects I'm working on:
>
>
>
> * Heliopolis: let NVDA's GUI be powered by wxPython 4 (Project
> Phoenix). I'm happy to announce the release of the next snapshot
> (20170725),
> powered by latest NVDA master snapshot code and wxPython 4 beta 1. For
> those
> of you who've used previous snapshots from this family, the major wx.Yield
> bug remains, and it appears it's time to come up with our own solution
> (ask
> Jamie as to why). The new snapshot can be found at:
>
> http://www.josephsl.net/files/bin/nvda_snapshot_wxPy4-20170725.exe
>
>
>
> For new people: Project Heliopolis (Greek for "sun city") is meant to test
> NVDA with wxPython 4.0.0. Use of wxPython 4 is a critical milestone before
> we can embark fully on Pylennium (see below).
>
>
>
> * Pylennium: Moving onto Python 3. As of latest commit, you'll be able
> to see first moments of NVDA's initialization (core.main up to an attempt
> to
> initialize app module handler) via command line (Python 3's python.exe).
> In
> order to see this, you need the following dependencies installed or copied
> to misc-deps/python directory: Python 3.6.x (I use 3.4.3 internally for
> now), comtypes 1.1.3, configobj 5.0.6, wxPython 4.0.0, pywin32 221, six
> 1.10.0. Also, before copying misc-deps/python modules, you need to run
> scons
> source at least once under Python 2.7 to build the source code copy BEFORE
> "upgrading" to Python 3 dependencies. In case of wxPython, you need to use
> the wheel designed for the Python release you plan to test with. I'm using
> Python 3.4 so basic porting can happen, release a source code level
> snapshot
> that should run on Windows XP, and then switch to Python 3.6 and start
> gathering ideas in using Python 3 modules fully (such as
> collections.ChainMap, asyncio and what not). I expect this project to take
> about a year or so to complete, including porting add-ons. At the moment
> the
> biggest showstoppers are attribute error exception in nvwave when
> WavePlayer.__del__ is called (resulting in failure to initialize audio
> output subsystem), inability to gather log output due to file() versus
> (open() functions, and Python 3 and liblouis is disputing Unicode width.
>
>
>
> For new people: NVDA is written in Python 2.7, but there were numerous
> feedback regarding switching the source code to Python 3. NV Access staff
> and some contributors believe that next year would be a good time to port
> bulk of NVDA to Python 3, but I figured it'd be a good idea to lay the
> foundation and send a report to the community regarding preparations and
> what to expect in the end. The name "pylennium" is a combination of
> "python"
> and "millennium", with the latter term coming from Python 3000.
>
>
>
> Cheers,
>
> Joseph
>
>


--------------------------------------------------------------------------------


> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot


--------------------------------------------------------------------------------


> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|

Re: Heliopolis and Pylennium projects: progress, next wxPython 4 powered snapshot posted

Joseph Lee
Hi,
The biggest benefit is ease of internationalization and reaching more global
audience through use of Unicode throughout.
Cheers,
Joseph

-----Original Message-----
From: Brian's Mail list account BY via Nvda-devel
[mailto:[hidden email]]
Sent: Tuesday, July 25, 2017 8:09 AM
To: NVDA screen reader development <[hidden email]>
Cc: Brian's Mail list account BY <[hidden email]>
Subject: Re: [Nvda-devel] Heliopolis and Pylennium projects: progress, next
wxPython 4 powered snapshot posted

Clear as mud of course for me, but if this is still going to be 32 bit code,
where is the benefit? If on the other hand it is envisaged to go 64 bit and
multi processor support then you have a whole new ball game here.
 Brian

[hidden email]
Sent via blueyonder.
Please address personal email to:-
[hidden email], putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Joseph Lee" <[hidden email]>
To: "'NVDA screen reader development'" <[hidden email]>
Sent: Tuesday, July 25, 2017 8:57 AM
Subject: [Nvda-devel] Heliopolis and Pylennium projects: progress, next
wxPython 4 powered snapshot posted


> Dear NVDA community,
>
>
>
> For new people: the following may not concern you unless you are eager
> to try absolutely latest alpha-level code, interested in helping out
> with coding and testing, or curious about what goes on in some
> development labs.
> Also, note that I (Joseph Lee) do not work for NV Access.
>
>
>
> I'm here to report on the progress of two projects I'm working on:
>
>
>
> * Heliopolis: let NVDA's GUI be powered by wxPython 4 (Project
> Phoenix). I'm happy to announce the release of the next snapshot
> (20170725), powered by latest NVDA master snapshot code and wxPython 4
> beta 1. For those of you who've used previous snapshots from this
> family, the major wx.Yield bug remains, and it appears it's time to
> come up with our own solution (ask Jamie as to why). The new snapshot
> can be found at:
>
> http://www.josephsl.net/files/bin/nvda_snapshot_wxPy4-20170725.exe
>
>
>
> For new people: Project Heliopolis (Greek for "sun city") is meant to
> test NVDA with wxPython 4.0.0. Use of wxPython 4 is a critical
> milestone before we can embark fully on Pylennium (see below).
>
>
>
> * Pylennium: Moving onto Python 3. As of latest commit, you'll be able
> to see first moments of NVDA's initialization (core.main up to an
> attempt to initialize app module handler) via command line (Python 3's
> python.exe).
> In
> order to see this, you need the following dependencies installed or
> copied to misc-deps/python directory: Python 3.6.x (I use 3.4.3
> internally for now), comtypes 1.1.3, configobj 5.0.6, wxPython 4.0.0,
> pywin32 221, six 1.10.0. Also, before copying misc-deps/python
> modules, you need to run scons source at least once under Python 2.7
> to build the source code copy BEFORE "upgrading" to Python 3
> dependencies. In case of wxPython, you need to use the wheel designed
> for the Python release you plan to test with. I'm using Python 3.4 so
> basic porting can happen, release a source code level snapshot that
> should run on Windows XP, and then switch to Python 3.6 and start
> gathering ideas in using Python 3 modules fully (such as
> collections.ChainMap, asyncio and what not). I expect this project to
> take about a year or so to complete, including porting add-ons. At the
> moment the biggest showstoppers are attribute error exception in
> nvwave when WavePlayer.__del__ is called (resulting in failure to
> initialize audio output subsystem), inability to gather log output due
> to file() versus
> (open() functions, and Python 3 and liblouis is disputing Unicode width.
>
>
>
> For new people: NVDA is written in Python 2.7, but there were numerous
> feedback regarding switching the source code to Python 3. NV Access
> staff and some contributors believe that next year would be a good
> time to port bulk of NVDA to Python 3, but I figured it'd be a good
> idea to lay the foundation and send a report to the community
> regarding preparations and what to expect in the end. The name
> "pylennium" is a combination of "python"
> and "millennium", with the latter term coming from Python 3000.
>
>
>
> Cheers,
>
> Joseph
>
>


----------------------------------------------------------------------------
----


> ----------------------------------------------------------------------
> -------- Check out the vibrant tech community on one of the world's
> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot


----------------------------------------------------------------------------
----


> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>


----------------------------------------------------------------------------
--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel