PRELIMINARY ! // but it still works fine on my windows PC
^^^^^^^^^^^^^
With the PAGE's author Don Rozenberg I am in contact, he is doing a general "Windows" rework. Thx!
Coming soon.
TOC:
1/5 MY (and your PAGE patch)
2/5 a single file TCL/TK interpreter
3/5 managing a working directory
...
5/5 PAGE for "windows OS" - a PAGE portable package
( 4/5 is still in work: "PAGE for "windows OS" - cleaning up the PAGE distribution":
PAGE 4.22 (page-4.22.tgz): Two "dirty" spots are in work: docs\PAGE-tutorial.zip // this s redundant (and outdated!): the "doc\tutorial\" is already here!
.... this costs 2MB (!) in the actual distribution the two directories: "examples\" and "examples-3\"
.. + should be unified to one "examples\" folder (thus removing unnecessary redundancy)
.. + and all the examples should be (re)checked again, if the actual PAGE versions does,
.... from the given example project files .tcl - if actual PAGE does really generate
.... correct and "errorfree" .py files?
)
The here targeted problem for Windows users is:
The PAGE created python files in europe: using the €, Ü, ö ... ( non ASCI characters) - crashes.
Solution: Use the (preliminary) portable PAGE. Attached here.
Extensive testing of the submitted faulty example revealed two real problems:
(a) faulty specification of a non-ACSII character and
(b) when that was repaired the example would run with Python 3 but not with Python 2
For this example, Python 2 execution failed on 32 bit and 64 bit Windows as well as Linux. Using Python 3 the example executed OK on those same platforms.
SO, if you require non-ASCII characters use Python 3. Reserve Python 2 for legacy programs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I read the first half of your reply about ten times. I still don't get it though.
First of all, what faulty example are you referring to?
What did you mean when you said "faulty specification"? Is it a character out of the default ANSI encoding on a certain Windows machine?
What did you repair, and how?
I would really like to understand it because I'm quite interested in character encoding and problems related to it.
Best regards
Steffen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2019-04-13
One bug in 4.22 (I can not post a new topic, So describe this bug here):
Win10 BIt64:
1. Open Page;
2. draw a Label, select "image", browse A.png, check the check box to confirm it;
3. Save all,
4. Then File-Quit;
5. Reopen Page, File-Recent Files-this file.
6. Gen-Python-GenerateGUI.
7. get error: no same volume.
8. But if at step 5: Reopen Page, File-Open-this file. Everything OK.
It seems the "File-Recent Files" use diffrent action compare to "File-Open".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
PRELIMINARY ! // but it still works fine on my windows PC
^^^^^^^^^^^^^
With the PAGE's author Don Rozenberg I am in contact, he is doing a general "Windows" rework. Thx!
Coming soon.
TOC:
1/5 MY (and your PAGE patch)
2/5 a single file TCL/TK interpreter
3/5 managing a working directory
...
5/5 PAGE for "windows OS" - a PAGE portable package
( 4/5 is still in work: "PAGE for "windows OS" - cleaning up the PAGE distribution":
PAGE 4.22 (page-4.22.tgz): Two "dirty" spots are in work:
docs\PAGE-tutorial.zip // this s redundant (and outdated!): the "doc\tutorial\" is already here!
.... this costs 2MB (!) in the actual distribution the two directories: "examples\" and "examples-3\"
.. + should be unified to one "examples\" folder (thus removing unnecessary redundancy)
.. + and all the examples should be (re)checked again, if the actual PAGE versions does,
.... from the given example project files .tcl - if actual PAGE does really generate
.... correct and "errorfree" .py files?
)
The here targeted problem for Windows users is:
The PAGE created python files in europe: using the €, Ü, ö ... ( non ASCI characters) - crashes.
Solution: Use the (preliminary) portable PAGE. Attached here.
best regards
Johannes
hhuter a t gmail.com
nice!
thx
Extensive testing of the submitted faulty example revealed two real problems:
(a) faulty specification of a non-ACSII character and
(b) when that was repaired the example would run with Python 3 but not with Python 2
For this example, Python 2 execution failed on 32 bit and 64 bit Windows as well as Linux. Using Python 3 the example executed OK on those same platforms.
SO, if you require non-ASCII characters use Python 3. Reserve Python 2 for legacy programs.
Don
I read the first half of your reply about ten times. I still don't get it though.
First of all, what faulty example are you referring to?
What did you mean when you said "faulty specification"? Is it a character out of the default ANSI encoding on a certain Windows machine?
What did you repair, and how?
I would really like to understand it because I'm quite interested in character encoding and problems related to it.
Best regards
Steffen
One bug in 4.22 (I can not post a new topic, So describe this bug here):
Win10 BIt64:
1. Open Page;
2. draw a Label, select "image", browse A.png, check the check box to confirm it;
3. Save all,
4. Then File-Quit;
5. Reopen Page, File-Recent Files-this file.
6. Gen-Python-GenerateGUI.
7. get error: no same volume.
8. But if at step 5: Reopen Page, File-Open-this file. Everything OK.
It seems the "File-Recent Files" use diffrent action compare to "File-Open".