For future proofing we need to move to Gtk3 and to Python3
See project 1 (https://github.com/jaap-karssenberg/zim-desktop-wiki/projects/1) with refactoring actions to clean up the code base
Intermediate steps
gi library instead of pygtk - go to Gtk3Once this is completed we could support a more Gnome3 consistent interface (optional, keep classic interface for Windows and other desktops)
For porting to gi, there is a script named pygi-convert.sh in the PyGObject repo.
Let's do this, I can help!
Converting to gi now, may take till after the x-mas holiday to publish it (watch the next branch)
Once the big step is done, definitely could use help testing and cleaning up remaining issues
@jaap-karssenberg wrote:
Once the big step is done, definitely could use help testing and cleaning up remaining issues
Just leave a note here once its ready to test and I'm happy to help.
Just wondering, if you are planning to use gtk.builder and glade?
Ongoing, see branch "next"
@muguu: no first want to port what we have, rewriting bits using Gtk.Builder can be done later, but is additional work not needed now
Closing this bug and opening separate bugs per porting issue
Does the Zim-Next branch use the 32-bit or the 64-bit version of python3?
On Tue, Feb 20, 2018 at 2:27 PM, Jaap Karssenberg notifications@github.com
wrote:
Closing this bug and opening separate bugs per porting issue
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/152#issuecomment-367090402,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFqscehNaePT1VdlbFsLbwoWh6A6wdYdks5tWxxmgaJpZM4OXVdj
.
@mystyc as far as I'm aware any version of python3 should work, I provided
sources only, no compiled libraries
On Fri, Feb 23, 2018 at 1:09 AM mystyc notifications@github.com wrote:
Does the Zim-Next branch use the 32-bit or the 64-bit version of python3?
On Tue, Feb 20, 2018 at 2:27 PM, Jaap Karssenberg <
[email protected]>
wrote:Closing this bug and opening separate bugs per porting issue
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<
https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/152#issuecomment-367090402
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AFqscehNaePT1VdlbFsLbwoWh6A6wdYdks5tWxxmgaJpZM4OXVdj.
—
You are receiving this because you modified the open/close state.Reply to this email directly, view it on GitHub
https://github.com/jaap-karssenberg/zim-desktop-wiki/issues/152#issuecomment-367866128,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMMHtpyJYo-aiCqb2GGI1HWiwRKQ0Ufks5tXgHGgaJpZM4OXVdj
.
The next branch works nicely for me. There is only one issue I've seen so far: The ToC widget (zim.plugins.tableofcontents.FloatingToC) is too small, rendering it hard to read. Should I open a separate bug report for that?
Answering my previous comment: This is already reported as #328.
Most helpful comment
Converting to
ginow, may take till after the x-mas holiday to publish it (watch thenextbranch)Once the big step is done, definitely could use help testing and cleaning up remaining issues