There was 1 vote for including the legacy Mac plugins and 0 against. So Craig and I made one last All-in-One and its uploaded.
So, I think can we call 4.6 "done" then?
On Sat, Jul 18, 2015 at 1:59 PM, Chris Muller ma.chris.m@gmail.com wrote:
There was 1 vote for including the legacy Mac plugins and 0 against. So Craig and I made one last All-in-One and its uploaded.
So, I think can we call 4.6 "done" then?
Do we have any volunteers to do some shake down tests? dare we do some shake down tests? SHould we instead release and handle problems as users find them? Chris, have you run your test suite using the 4.6 yet?
+ 1 for releasing 4.6 and handling problems as users find them :)
But there's one problem that I just found: try and run the following and you should get a SqueakSSL error (-5):
(WebClient new httpGet: ' https://api.travis-ci.org/repos/squeak-smalltalk/squeak.org/builds') content
Looks like we forgot to update the SqueakSSL plugins with the ones from [1]? After doing that manually, the above works just fine...
Regards, Fabio
[1] https://github.com/itsmeront/squeakssl/releases
--
On Sat, Jul 18, 2015 at 11:06 PM Eliot Miranda eliot.miranda@gmail.com wrote:
On Sat, Jul 18, 2015 at 1:59 PM, Chris Muller ma.chris.m@gmail.com wrote:
There was 1 vote for including the legacy Mac plugins and 0 against. So Craig and I made one last All-in-One and its uploaded.
So, I think can we call 4.6 "done" then?
Do we have any volunteers to do some shake down tests? dare we do some shake down tests? SHould we instead release and handle problems as users find them? Chris, have you run your test suite using the 4.6 yet?
-- _,,,^..^,,,_ best, Eliot
Thanks Fabio, say, which platform did you test on? Hm, something interesting -- that new SqueakSSL (for Linux) is 7 MB where the one I have been using is only 27K, which easily makes it the largest plugin and would slightly inflate teh size of the All-In-One.
Why is it so much bigger, is it compiled with debug information or something?
On Sun, Jul 19, 2015 at 3:56 AM, Fabio Niephaus lists@fniephaus.com wrote:
- 1 for releasing 4.6 and handling problems as users find them :)
But there's one problem that I just found: try and run the following and you should get a SqueakSSL error (-5):
(WebClient new httpGet: 'https://api.travis-ci.org/repos/squeak-smalltalk/squeak.org/builds') content
Looks like we forgot to update the SqueakSSL plugins with the ones from [1]? After doing that manually, the above works just fine...
Regards, Fabio
[1] https://github.com/itsmeront/squeakssl/releases
--
On Sat, Jul 18, 2015 at 11:06 PM Eliot Miranda eliot.miranda@gmail.com wrote:
On Sat, Jul 18, 2015 at 1:59 PM, Chris Muller ma.chris.m@gmail.com wrote:
There was 1 vote for including the legacy Mac plugins and 0 against. So Craig and I made one last All-in-One and its uploaded.
So, I think can we call 4.6 "done" then?
Do we have any volunteers to do some shake down tests? dare we do some shake down tests? SHould we instead release and handle problems as users find them? Chris, have you run your test suite using the 4.6 yet?
-- _,,,^..^,,,_ best, Eliot
On 19.07.2015, at 18:34, Chris Muller asqueaker@gmail.com wrote:
Thanks Fabio, say, which platform did you test on? Hm, something interesting -- that new SqueakSSL (for Linux) is 7 MB where the one I have been using is only 27K, which easily makes it the largest plugin and would slightly inflate teh size of the All-In-One.
Why is it so much bigger, is it compiled with debug information or something?
No, I statically linked against LibreSSL.
Best regards -Tobias
On Sun, Jul 19, 2015 at 3:56 AM, Fabio Niephaus lists@fniephaus.com wrote:
- 1 for releasing 4.6 and handling problems as users find them :)
But there's one problem that I just found: try and run the following and you should get a SqueakSSL error (-5):
(WebClient new httpGet: 'https://api.travis-ci.org/repos/squeak-smalltalk/squeak.org/builds') content
Looks like we forgot to update the SqueakSSL plugins with the ones from [1]? After doing that manually, the above works just fine...
Regards, Fabio
[1] https://github.com/itsmeront/squeakssl/releases
--
On Sat, Jul 18, 2015 at 11:06 PM Eliot Miranda eliot.miranda@gmail.com wrote:
On Sat, Jul 18, 2015 at 1:59 PM, Chris Muller ma.chris.m@gmail.com wrote:
There was 1 vote for including the legacy Mac plugins and 0 against. So Craig and I made one last All-in-One and its uploaded.
So, I think can we call 4.6 "done" then?
Do we have any volunteers to do some shake down tests? dare we do some shake down tests? SHould we instead release and handle problems as users find them? Chris, have you run your test suite using the 4.6 yet?
-- _,,,^..^,,,_ best, Eliot
I'm using OS X Yosemite. Hope this helps.
Regards, Fabio
--
On Sun, Jul 19, 2015 at 6:48 PM Tobias Pape Das.Linux@gmx.de wrote:
On 19.07.2015, at 18:34, Chris Muller asqueaker@gmail.com wrote:
Thanks Fabio, say, which platform did you test on? Hm, something interesting -- that new SqueakSSL (for Linux) is 7 MB where the one I have been using is only 27K, which easily makes it the largest plugin and would slightly inflate teh size of the All-In-One.
Why is it so much bigger, is it compiled with debug information or
something?
No, I statically linked against LibreSSL.
Best regards -Tobias
On Sun, Jul 19, 2015 at 3:56 AM, Fabio Niephaus lists@fniephaus.com
wrote:
- 1 for releasing 4.6 and handling problems as users find them :)
But there's one problem that I just found: try and run the following
and you
should get a SqueakSSL error (-5):
(WebClient new httpGet: 'https://api.travis-ci.org/repos/squeak-smalltalk/squeak.org/builds') content
Looks like we forgot to update the SqueakSSL plugins with the ones from
[1]?
After doing that manually, the above works just fine...
Regards, Fabio
[1] https://github.com/itsmeront/squeakssl/releases
--
On Sat, Jul 18, 2015 at 11:06 PM Eliot Miranda <eliot.miranda@gmail.com
wrote:
On Sat, Jul 18, 2015 at 1:59 PM, Chris Muller ma.chris.m@gmail.com wrote:
There was 1 vote for including the legacy Mac plugins and 0 against. So Craig and I made one last All-in-One and its uploaded.
So, I think can we call 4.6 "done" then?
Do we have any volunteers to do some shake down tests? dare we do some shake down tests? SHould we instead release and handle problems as
users
find them? Chris, have you run your test suite using the 4.6 yet?
-- _,,,^..^,,,_ best, Eliot
Project saving is broken, though project related items are part of the docking bar menu. Vaidotas
I think that project saving has been broken for quite some time. There should be a note in 'known issues'.
On 7/19/15, Vaidotas Didžbalis vaidasd@gmail.com wrote:
Project saving is broken, though project related items are part of the docking bar menu. Vaidotas
On Mon, Jul 20, 2015 at 10:48 AM, H. Hirzel hannes.hirzel@gmail.com wrote:
I think that project saving has been broken for quite some time.
Yes, this is the reason why we use 4.4 version for development. The whole concept of Projects makes no sense if Project can not be persisted, this is essential. We use this, eToys use this. What is the meaning of the Projects if they can not be saved? It is an irony that introduction of Environments have had an opposite effect. Couldn't Environments coexist with Projects? Maybe someone could elaborate what is the problem, what can be done?
From UI perspective, currently stock image is one click away from debugger
popup. regards, Vaidotas
A note that
'Project saving does not work, use 4.4 should be used instead'
should be included in the release notes.
--Hannes
On 7/20/15, Vaidotas Didžbalis vaidasd@gmail.com wrote:
On Mon, Jul 20, 2015 at 10:48 AM, H. Hirzel hannes.hirzel@gmail.com wrote:
I think that project saving has been broken for quite some time.
Yes, this is the reason why we use 4.4 version for development. The whole concept of Projects makes no sense if Project can not be persisted, this is essential. We use this, eToys use this. What is the meaning of the Projects if they can not be saved? It is an irony that introduction of Environments have had an opposite effect. Couldn't Environments coexist with Projects? Maybe someone could elaborate what is the problem, what can be done?
From UI perspective, currently stock image is one click away from debugger
popup. regards, Vaidotas
It would be great if we can put some focus on this as soon as we have completed the Squeak 4.6 and 5.0 releases (RSN).
I think that Levente had summarized the open issues regarding Environments in a post to this list within the last year. We also had the thread "Thinking about environments" on the list last December. We should find Levente's summary and see if we can make progress against it in the coming months.
Dave
On Mon, Jul 20, 2015 at 10:48 AM, H. Hirzel hannes.hirzel@gmail.com wrote:
I think that project saving has been broken for quite some time.
Yes, this is the reason why we use 4.4 version for development. The whole concept of Projects makes no sense if Project can not be persisted, this is essential. We use this, eToys use this. What is the meaning of the Projects if they can not be saved? It is an irony that introduction of Environments have had an opposite effect. Couldn't Environments coexist with Projects? Maybe someone could elaborate what is the problem, what can be done?
From UI perspective, currently stock image is one click away from debugger
popup. regards, Vaidotas
I agree that I missed project long enough so something must be made.
May be Environment was a must but it seems that nobody know how to use it. And the doc is waiting.
Project in is side is used but don"t work. Is it a feature of Skeak or only a "try for yourself'.
My intention here is not bashing I know there is so lot to do and so few ressources, but...
Retain that I would like something is done for project
Raymond Asselin
Le 2015-07-21 à 16:00, David T. Lewis lewis@mail.msen.com a écrit :
It would be great if we can put some focus on this as soon as we have completed the Squeak 4.6 and 5.0 releases (RSN).
I think that Levente had summarized the open issues regarding Environments in a post to this list within the last year. We also had the thread "Thinking about environments" on the list last December. We should find Levente's summary and see if we can make progress against it in the coming months.
Dave
On Mon, Jul 20, 2015 at 10:48 AM, H. Hirzel hannes.hirzel@gmail.com wrote:
I think that project saving has been broken for quite some time.
Yes, this is the reason why we use 4.4 version for development. The whole concept of Projects makes no sense if Project can not be persisted, this is essential. We use this, eToys use this. What is the meaning of the Projects if they can not be saved? It is an irony that introduction of Environments have had an opposite effect. Couldn't Environments coexist with Projects? Maybe someone could elaborate what is the problem, what can be done?
From UI perspective, currently stock image is one click away from debugger
popup. regards, Vaidotas
squeak-dev@lists.squeakfoundation.org
-
Chris Muller -
Chris Muller -
David T. Lewis -
Eliot Miranda -
Fabio Niephaus -
H. Hirzel -
Raymond Asselin -
Tobias Pape -
Vaidotas Didžbalis