Begin forwarded message:
From: Randall Caton rcaton@cnu.edu Date: 7. Oktober 2009 01:04:18 MESZ To: Bert Freudenberg bert@freudenbergs.de Subject: etoys4
Dear Bert,
I know I am supposed to use tracker, but as is often the case I get a "500 servlet error" when trying to access the tracker. When I view a script from a project made in etoys3, using the beta etoys4, many of the tiles are compressed so there is no access to parts of their function. I have noticed this in other upgrades. This means you have to spend a lot of time reconstructing your scripts. Is there a way to fix this for the final version?
Randy
I might have seen this, but with older projects. I thought we did not really change the layout that much between Etoys 3 and 4?
- Bert -
At Wed, 7 Oct 2009 01:10:13 +0200, Bert Freudenberg wrote:
Begin forwarded message:
From: Randall Caton rcaton@cnu.edu Date: 7. Oktober 2009 01:04:18 MESZ To: Bert Freudenberg bert@freudenbergs.de Subject: etoys4
Dear Bert,
I know I am supposed to use tracker, but as is often the case I get a "500 servlet error" when trying to access the tracker. When I view a script from a project made in etoys3, using the beta etoys4, many of the tiles are compressed so there is no access to parts of their function. I have noticed this in other upgrades. This means you have to spend a lot of time reconstructing your scripts. Is there a way to fix this for the final version?
Randy
I might have seen this, but with older projects. I thought we did not really change the layout that much between Etoys 3 and 4?
And Kedama tiles have often this trouble.
One way to fix it is to get the halo on the scriptor, go to the white-handle menu and choose "fix layout". It usually solve the problem.
-- Yoshiki
On 07.10.2009, at 22:59, Yoshiki Ohshima wrote:
At Wed, 7 Oct 2009 01:10:13 +0200, Bert Freudenberg wrote:
Begin forwarded message:
From: Randall Caton rcaton@cnu.edu Date: 7. Oktober 2009 01:04:18 MESZ To: Bert Freudenberg bert@freudenbergs.de Subject: etoys4
Dear Bert,
I know I am supposed to use tracker, but as is often the case I get a "500 servlet error" when trying to access the tracker. When I view a script from a project made in etoys3, using the beta etoys4, many of the tiles are compressed so there is no access to parts of their function. I have noticed this in other upgrades. This means you have to spend a lot of time reconstructing your scripts. Is there a way to fix this for the final version?
Randy
I might have seen this, but with older projects. I thought we did not really change the layout that much between Etoys 3 and 4?
And Kedama tiles have often this trouble.
One way to fix it is to get the halo on the scriptor, go to the white-handle menu and choose "fix layout". It usually solve the problem.
I filed with steps to reproduce
http://tracker.squeakland.org/browse/SQ-500
- Bert -
On Thursday 08 October 2009 02:35:25 am Bert Freudenberg wrote:
I filed with steps to reproduce
Can you toggle usePangoRenderer and see if it makes any difference? I see text overshooting alignment when this option is turned off.
Subbu
On 08.10.2009, at 20:40, K. K. Subramaniam wrote:
On Thursday 08 October 2009 02:35:25 am Bert Freudenberg wrote:
I filed with steps to reproduce
Can you toggle usePangoRenderer and see if it makes any difference? I see text overshooting alignment when this option is turned off.
Makes no difference (unsurprisingly, since the option does nothing on Mac and Windows).
- Bert -
... When I view a script from a project made in etoys3, using the beta etoys4, many of the tiles are compressed so there is no access to parts of their function. I have noticed this in other upgrades. This means you have to spend a lot of time reconstructing your scripts. Is there a way to fix this for the final version?
And Kedama tiles have often this trouble.
One way to fix it is to get the halo on the scriptor, go to the white-handle menu and choose "fix layout". It usually solve the problem.
-- Yoshiki
... and the workaround that Yoshiki suggests should provide a useful clue for anyone undertaking to fix this bug.
-- Scott
On 07.10.2009, at 23:32, Scott Wallace wrote:
... When I view a script from a project made in etoys3, using the beta etoys4, many of the tiles are compressed so there is no access to parts of their function. I have noticed this in other upgrades. This means you have to spend a lot of time reconstructing your scripts. Is there a way to fix this for the final version?
And Kedama tiles have often this trouble.
One way to fix it is to get the halo on the scriptor, go to the white-handle menu and choose "fix layout". It usually solve the problem.
-- Yoshiki
... and the workaround that Yoshiki suggests should provide a useful clue for anyone undertaking to fix this bug.
... as might be examining the difference between dragging out of the viewer (which works) vs. opening from All Scripts (fails) - see
http://tracker.squeakland.org/browse/SQ-500
- Bert -
On Oct 7, 2009, at 2:53 PM, Bert Freudenberg wrote:
On 07.10.2009, at 23:32, Scott Wallace wrote:
... When I view a script from a project made in etoys3, using the beta etoys4, many of the tiles are compressed so there is no access to parts of their function. I have noticed this in other upgrades. This means you have to spend a lot of time reconstructing your scripts. Is there a way to fix this for the final version?
And Kedama tiles have often this trouble.
One way to fix it is to get the halo on the scriptor, go to the white-handle menu and choose "fix layout". It usually solve the problem.
-- Yoshiki
... and the workaround that Yoshiki suggests should provide a useful clue for anyone undertaking to fix this bug.
... as might be examining the difference between dragging out of the viewer (which works) vs. opening from All Scripts (fails) - see
http://tracker.squeakland.org/browse/SQ-500
- Bert -
Right. Also, until the bug gets fixed, a way to assure that an old project is immune from the problem is to open the project, and then, one by one, fix up each script by dragging it out from its corresponding viewer, which will get its layout fixed, then dismissing the script again; then re-save the project.
-- Scott
etoys-dev@lists.squeakfoundation.org