[ANN] Squeak 5.1 Feature Freeze -- Trunk closed for new features; only bug fixes or text updates

marcel.taeumel wrote

Hi, there!

It's "feature freeze" time. :-) Please do not try out new features in the Trunk for now. If you forgot something, please ask first. We'll find a way.

@Chris: What is needed in the image for the MC History function? There was at least one fix for the ServiceEntry left in your inbox, right?

We will now work on correcting some in-image texts, release information, etc. We will also work on the release automation scripts using TravisCI, smalltalkCI, and GitHub.

The next dates are:
  * Code Freeze on August 14, 23:59 AOE
  * Release between August 15 and 19

Let's hope that this will work out as expected. :-)

Best,
Marcel

Chris Muller-3 wrote

Hi Marcel, why the 3997 vm, its quite old?

On Wed, Aug 10, 2016 at 10:21 AM, marcel.taeumel <[hidden email]> wrote:
> marcel.taeumel wrote
>> Hi, there!
>>
>> It's "feature freeze" time. :-) Please do not try out new features in the
>> Trunk for now. If you forgot something, please ask first. We'll find a
>> way.
>>
>> @Chris: What is needed in the image for the MC History function? There was
>> at least one fix for the ServiceEntry left in your inbox, right?
>>
>> We will now work on correcting some in-image texts, release information,
>> etc. We will also work on the release automation scripts using TravisCI,
>> smalltalkCI, and GitHub.
>>
>> The next dates are:
>>   * Code Freeze on August 14, 23:59 AOE
>>   * Release between August 15 and 19
>>
>> Let's hope that this will work out as expected. :-)
>>
>> Best,
>> Marcel
>
> Hi, there.
>
> A first All-In-One can be tried out from here:
> https://www.hpi.uni-potsdam.de/hirschfeld/artefacts/squeak/Squeak5.1beta-16336-r3397-32bit-All-in-One.zip
>
> Note that we are looking for start-up bugs in the Linux scripts.
> Note that we have not yet fixed the Windows .ini bug.
> Note that Windows 10 is quite anxious about starting an unsigned executable.
> Note that the release artifacts will be on files.squeak.org soon. Be
> patient.
> Note that we still want to use a more recent CogVM if some one would declare
> one as stable.
>
> Best,
> Marcel
>
>
>
> --
> View this message in context: http://forum.world.st/ANN-Squeak-5-1-Feature-Freeze-Trunk-closed-for-new-features-only-bug-fixes-or-text-updates-tp4909004p4910338.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>

Hi Marcel, why the 3997 vm, its quite old?

On Wed, Aug 10, 2016 at 10:21 AM, marcel.taeumel <[hidden email]> wrote:

> marcel.taeumel wrote
>> Hi, there!
>>
>> It's "feature freeze" time. :-) Please do not try out new features in the
>> Trunk for now. If you forgot something, please ask first. We'll find a
>> way.
>>
>> @Chris: What is needed in the image for the MC History function? There was
>> at least one fix for the ServiceEntry left in your inbox, right?
>>
>> We will now work on correcting some in-image texts, release information,
>> etc. We will also work on the release automation scripts using TravisCI,
>> smalltalkCI, and GitHub.
>>
>> The next dates are:
>>   * Code Freeze on August 14, 23:59 AOE
>>   * Release between August 15 and 19
>>
>> Let's hope that this will work out as expected. :-)
>>
>> Best,
>> Marcel
>
> Hi, there.
>
> A first All-In-One can be tried out from here:
> https://www.hpi.uni-potsdam.de/hirschfeld/artefacts/squeak/Squeak5.1beta-16336-r3397-32bit-All-in-One.zip
>
> Note that we are looking for start-up bugs in the Linux scripts.
> Note that we have not yet fixed the Windows .ini bug.
> Note that Windows 10 is quite anxious about starting an unsigned executable.
> Note that the release artifacts will be on files.squeak.org soon. Be
> patient.
> Note that we still want to use a more recent CogVM if some one would declare
> one as stable.
>
> Best,
> Marcel
>
>
>
> --
> View this message in context: http://forum.world.st/ANN-Squeak-5-1-Feature-Freeze-Trunk-closed-for-new-features-only-bug-fixes-or-text-updates-tp4909004p4910338.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/ANN-Squeak-5-1-Feature-Freeze-Trunk-closed-for-new-features-only-bug-fixes-or-text-updates-tp4909004p4910373.html

To start a new topic under Squeak - Dev, email [hidden email]
To unsubscribe from Squeak - Dev, click here.
NAML

Hi Marcel, why the 3997 vm, its quite old?

On Wed, Aug 10, 2016 at 10:21 AM, marcel.taeumel <[hidden email]> wrote:

> marcel.taeumel wrote
>> Hi, there!
>>
>> It's "feature freeze" time. :-) Please do not try out new features in the
>> Trunk for now. If you forgot something, please ask first. We'll find a
>> way.
>>
>> @Chris: What is needed in the image for the MC History function? There was
>> at least one fix for the ServiceEntry left in your inbox, right?
>>
>> We will now work on correcting some in-image texts, release information,
>> etc. We will also work on the release automation scripts using TravisCI,
>> smalltalkCI, and GitHub.
>>
>> The next dates are:
>>   * Code Freeze on August 14, 23:59 AOE
>>   * Release between August 15 and 19
>>
>> Let's hope that this will work out as expected. :-)
>>
>> Best,
>> Marcel
>
> Hi, there.
>
> A first All-In-One can be tried out from here:
> https://www.hpi.uni-potsdam.de/hirschfeld/artefacts/squeak/Squeak5.1beta-16336-r3397-32bit-All-in-One.zip
>
> Note that we are looking for start-up bugs in the Linux scripts.
> Note that we have not yet fixed the Windows .ini bug.
> Note that Windows 10 is quite anxious about starting an unsigned executable.
> Note that the release artifacts will be on files.squeak.org soon. Be
> patient.
> Note that we still want to use a more recent CogVM if some one would declare
> one as stable.
>
> Best,
> Marcel
>
>
>
> --
> View this message in context: http://forum.world.st/ANN-Squeak-5-1-Feature-Freeze-Trunk-closed-for-new-features-only-bug-fixes-or-text-updates-tp4909004p4910338.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>

If you reply to this email, your message will be added to the discussion below:

http://forum.world.st/ANN-Squeak-5-1-Feature-Freeze-Trunk-closed-for-new-features-only-bug-fixes-or-text-updates-tp4909004p4910373.html

To start a new topic under Squeak - Dev, email [hidden email]
To unsubscribe from Squeak - Dev, click here.
NAML

Herbert König wrote

Hi,

when in the preferences browser, flaps selecting 'classic navigator
enabled' gives a debugger as attached.

While creating the png I brought up the halo and wanted to click the
menu button to export. If there is another window under the menu button
(my preference browser) clicking brings the other menu to the front and
the halo disappears. Move the other window out of the way and it works.

Not to forget: I like it, thanks to all for the work.

Cheers,

Herbert

Am 10.08.2016 um 17:21 schrieb marcel.taeumel:
> marcel.taeumel wrote
>> Hi, there!
>>
>> It's "feature freeze" time. :-) Please do not try out new features in the
>> Trunk for now. If you forgot something, please ask first. We'll find a
>> way.
>>
>> @Chris: What is needed in the image for the MC History function? There was
>> at least one fix for the ServiceEntry left in your inbox, right?
>>
>> We will now work on correcting some in-image texts, release information,
>> etc. We will also work on the release automation scripts using TravisCI,
>> smalltalkCI, and GitHub.
>>
>> The next dates are:
>>    * Code Freeze on August 14, 23:59 AOE
>>    * Release between August 15 and 19
>>
>> Let's hope that this will work out as expected. :-)
>>
>> Best,
>> Marcel
> Hi, there.
>
> A first All-In-One can be tried out from here:
> https://www.hpi.uni-potsdam.de/hirschfeld/artefacts/squeak/Squeak5.1beta-16336-r3397-32bit-All-in-One.zip
>
> Note that we are looking for start-up bugs in the Linux scripts.
> Note that we have not yet fixed the Windows .ini bug.
> Note that Windows 10 is quite anxious about starting an unsigned executable.
> Note that the release artifacts will be on files.squeak.org soon. Be
> patient.
> Note that we still want to use a more recent CogVM if some one would declare
> one as stable.
>
> Best,
> Marcel
>
>
>
> --
> View this message in context: http://forum.world.st/ANN-Squeak-5-1-Feature-Freeze-Trunk-closed-for-new-features-only-bug-fixes-or-text-updates-tp4909004p4910338.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>





Test.png (74K) <http://forum.world.st/attachment/4910354/0/Test.png>

Tobias Pape wrote

On 11.08.2016, at 20:14, tim Rowledge <[hidden email]> wrote:

>> On 10-08-2016, at 8:21 AM, marcel.taeumel <[hidden email]> wrote:
>> A first All-In-One can be tried out from here:
>> https://www.hpi.uni-potsdam.de/hirschfeld/artefacts/squeak/Squeak5.1beta-16336-r3397-32bit-All-in-One.zip
>>
>
>
> I like the idea of the welcome dialogue stuff. But I see some problems that we hopefully still have time to handle.
>
> -The initial ‘welcome’ text is in the middle of the screen and then jumps to the top. Seems a bit jarring.
> - second ‘page’ - “You can try… “ might be better more like  “You can see the effects of these settings in the live and editable windows to the right”
> - there’s no hint what many of the settings will do or how they might affect things. Help balloons might be enough to solve this, explaining for example how to see the effect of choosing ‘fast drag and resize’.
> - at the end of the welcome we are dropped into a dark empty world. I half expect Orcs to come charging at me. Maybe an open browser and workspace ought to be left in place? For experts skipping the whole thing I suspect the first thing we’d do is open a browser/workspace anyway!
> - it leaves out the thing I’d suggest is most important of all - urging the user to first save the image in a new place to discourage the ‘abuse’ of changing the default image. I claim we should conventionally start a new system from the all-in-one, save the image in a local place and thereafter run that image until and unless a fresh image needs to be started. Think of this like many applications that allow opening a new file or a template, with the default image being a very well set up template.
> - another useful start-up option here would be entering developer initials
> - another would be to point out the help system. Of course, we need to improve the content therein as well. And the swiki as always is in need of love.
>
>
>> Note that we are looking for start-up bugs in the Linux scripts.
>
> At least for the ARM linux tree the ‘squeak’ shell script is not so good.
> - it ought to be finding the latest vm; this is a little complex because of the naming change from blah-XXXX to blah-2106MMDDHHMM. And of course, affected by which VM is to be delivered anyway.
> - the newer versions of the script add an option for a gdb flag.
> - it may be appropriate to have the x86 & ARM versions differ in their approach to finding the clib
> - at least for the ARM version there is a serious issue with remote displays (that is, ARM linux has the problem, which squeak triggers) and we need to wrap the whole thing in ‘sudo -E’. We have a program that can be used to test this at runtime (I can send it to anyone interested) but all my attempts to wrap the final line of the script in the required sudo have met with no success. It is likely some problem with how forking and execing and sudo didn’t get on well as children. A better solution would be to fix linux so it doesn't cause the problem in the first case but it seems to have been around for many years.
>
>
>> Note that we have not yet fixed the Windows .ini bug.
>> Note that Windows 10 is quite anxious about starting an unsigned executable.
> And you should see how annoyed OS X gets about it.
>
> The image is frikkin’ huge. How on earth do we have 22Mb of ByteArray/BitMap/ByteString around? And it looks like we are keeping a very large amount of MC stuff; 13018 instances of MCVersionInfo/MCVersionName/DateAndTime/Date/Time/UUID. Is that smart? Simply flushing the cached ancestry from the MC browser gets rid of 60% of them and appears to save 3Mb. Except the damn saved image afterwards is exactly the same size! Sigh.

We can convert all base64 strings to ascii85 and save some 10-20% ;D

>
>
> tim

tim Rowledge wrote

> On 12-08-2016, at 1:49 PM, Chris Muller <[hidden email]> wrote:
>
>>> And if I manually try `PreferenceWizardMorph new openInWorld` I see the entire thing, and on choosing ‘configure it looks as if the default window size is too small to fit the config options in. I needed to make it quite a bit bigger to lay out correctly.
>>
>> And why the multiple 1 second delays? It makes it appear as if Squeak is really slow, which probably wasn’t the intention.
>
> I was just thinking how innovative the little pauses were.  A UI tool
> to delineate and direct the users eyes to the sequence of elements to
> look at.
>
> The delays feel intentional, as if it was designed for a refined human
> consumption experience.  It feels relaxed, not a strained feel as if Squeak were
> struggling to keep up because it were slow.

If we were fading in/out smoothly - which usually requires some exponential rate of change with acceleration and decceleration -  I’d likely agree. And of course, I’m testing this out on a box that is maybe 10% of your machine’s performance.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: IO: Illogical Or

marcel.taeumel wrote

tim Rowledge wrote

> On 12-08-2016, at 1:49 PM, Chris Muller <[hidden email]> wrote:
>
>>> And if I manually try `PreferenceWizardMorph new openInWorld` I see the entire thing, and on choosing ‘configure it looks as if the default window size is too small to fit the config options in. I needed to make it quite a bit bigger to lay out correctly.
>>
>> And why the multiple 1 second delays? It makes it appear as if Squeak is really slow, which probably wasn’t the intention.
>
> I was just thinking how innovative the little pauses were.  A UI tool
> to delineate and direct the users eyes to the sequence of elements to
> look at.
>
> The delays feel intentional, as if it was designed for a refined human
> consumption experience.  It feels relaxed, not a strained feel as if Squeak were
> struggling to keep up because it were slow.

If we were fading in/out smoothly - which usually requires some exponential rate of change with acceleration and decceleration -  I’d likely agree. And of course, I’m testing this out on a box that is maybe 10% of your machine’s performance.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: IO: Illogical Or

We had a little hick-up with that one build, here is what it looks like with
http://files.squeak.org/5.1beta/Squeak5.1beta-16395-32bit-r3397-All-in-One.zip



Best,
Marcel