[Pharo-users] Seaside 3.1 and 3.2 in Pharo 5

2016-03-20 Thread Torsten Bergmann
Issues I've found directly: 1. Seaside still uses #subStrings: instead of substrings: on several places. #subStrings: is deprecated since April 2015. 2. The Seaside control panel icon in menu is not displayed => the icon expression in WAPharoServerAdapterSpecBrowser(class)>>menuCommandOn:

Re: [Pharo-users] [Pharo-dev] 3 new Pharo videos

2016-03-20 Thread Alexandre Bergel
Hubcap is great!! It should definitely be part of Pharo. Can it show the project description? Cheers, Alexandre > On Mar 18, 2016, at 4:56 PM, Torsten Bergmann wrote: > > I provided 3 new videos about my tools/goodies on YouTube: > > Pharo OS-Linux-Ubuntu > https://www.youtube.com/watch?v=1

Re: [Pharo-users] Seaside 3.1 and 3.2 in Pharo 5

2016-03-20 Thread Johan Brichau
Hi Cyril, > I use Seaside 3.1 in Pharo 5 and I have an application running with this > setup currently. Great! There were indeed very few failing tests that were fixed quickly. I think most of Seaside was just working and you confirm that. > This is the main issues I got the past few weeks: > -

Re: [Pharo-users] Seaside 3.1 and 3.2 in Pharo 5

2016-03-20 Thread Cyril Ferlicot D.
Le 20/03/2016 19:49, Johan Brichau a écrit : > Hi Pharoers, > > If you are looking to use Seaside in Pharo 5, please go ahead and let us > know if you run into any issues. > Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are > green [1]. > Hi, I use Seaside 3.1 in Pharo 5

Re: [Pharo-users] Seaside 3.1 and 3.2 in Pharo 5

2016-03-20 Thread Sven Van Caekenberghe
SUPER !! Thanks > On 20 Mar 2016, at 19:49, Johan Brichau wrote: > > Hi Pharoers, > > If you are looking to use Seaside in Pharo 5, please go ahead and let us know > if you run into any issues. > Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are > green [1]. > > Also:

[Pharo-users] Seaside 3.1 and 3.2 in Pharo 5

2016-03-20 Thread Johan Brichau
Hi Pharoers, If you are looking to use Seaside in Pharo 5, please go ahead and let us know if you run into any issues. Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are green [1]. Also: I know the finalization of 3.2.0 is long overdue, so news about that is coming soon.

Re: [Pharo-users] Image Cleaner no longer useful?

2016-03-20 Thread Stephan Eggermont
Hello Maximiliano On 20-03-16 13:29, Maximiliano Tabacman via Pharo-users wrote: With the latest Image (50651) and VM, the issue remains the same. As Marcus wrote, that is a well-known problem. At the moment, there is one higher priority issue on the image side, and it might well be related.

Re: [Pharo-users] [Pillar] Logo for Pillar

2016-03-20 Thread Cyril Ferlicot
Hi, Personally I do not like it. (Maybe I'm difficult :) ). I think that it would be better to have the "illar" at the bottom and not compressed in the middle. The second column look like an "y" and we read "Pillary". And why is there a wave under pillar? I think that things in a logo have to b

Re: [Pharo-users] Image Cleaner no longer useful?

2016-03-20 Thread Maximiliano Tabacman via Pharo-users
--- Begin Message --- With the latest Image (50651) and VM, the issue remains the same. The most critical part for me is the fact that cleaning the image (at least using ImageCleaner) does not reduce its size.I have a commercial product with users already using it, who obtain the product by downl

Re: [Pharo-users] Use Shell Command from Pharo

2016-03-20 Thread g_ongenae
Thanks for the answer, I've already seen this page. And the problem is when I do : OSProcess command: 'touch files.txt', I can't find the created files. But I don't have any error message. For the new lib, I'm working on Pharo 4, and it only works and version 5. -- Guillaume -- View this mess

Re: [Pharo-users] extracting segments in an array

2016-03-20 Thread Damien Pollet
SequenceableCollection mostly, but possibly streams as well On 19 March 2016 at 21:21, Hernán Morales Durand wrote: > Hi Damien, > > I didn't understood, which kind of sequences? > > > 2016-03-19 7:40 GMT-03:00 Damien Pollet : > >> Yeah if we redesign the String API it should account for Arrays