Re: [Pharo-dev] [VM] Windows VM SurfacePlugin.dll LoadLibrary failure

Same here, in #60442. Smalltalk vm version ---> "'CoInterpreter * VMMaker.oscog-EstebanLorenzano.2136 uuid: 40534c32-ca6b-4e97-91ec-31d509e49b0c Feb 22 2017 StackToRegisterMappingCogit * VMMaker.oscog-EstebanLorenzano.2136 uuid: 40534c32-ca6b-4e97-91ec-31d509e49b0c Feb 22 2017 VM: 201702221539

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

On Thu, Mar 16, 2017 at 6:25 AM, Sven Van Caekenberghe wrote: > > > > On 15 Mar 2017, at 20:52, Rein, Patrick wrote: > > > > Unfortunately, as I am trying to fix a Travis build, I can not change the > > call to Zinc. > > > > To be clear about this: I also

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

> On 15 Mar 2017, at 20:52, Rein, Patrick wrote: > > Unfortunately, as I am trying to fix a Travis build, I can not change the > call to Zinc. > > To be clear about this: I also think that squeaksource should serve UTF-8. > However, at the same time a missing charset in

[Pharo-dev] Extra Contents has been modified

Hi I'm coding on 60438 and I have a super annoying glitch. When I click on a method in the method list of a test method I get systematically a Contents validate or cancel. I do not have the time to carefully check because I need to commit and stop and tomorrow is totally crazy (even

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

Unfortunately, as I am trying to fix a Travis build, I can not change the call to Zinc. To be clear about this: I also think that squeaksource should serve UTF-8. However, at the same time a missing charset in a HTTP response means that the content should be decoded as ISO-8859-1 [1]. So in

Re: [Pharo-dev] Capitalized

Hi torsten I do not get your point. In Pharo 60 we have. capitalized "Return a copy with the first letter capitalized" | cap | self isEmpty ifTrue: [ ^self copy ]. cap := self copy. cap at: 1 put: (cap at: 1) asUppercase. ^ cap "'snoopy'

Re: [Pharo-dev] Capitalized

Ok I got it you mean "'snOOpy' capitalized >>>'Snoopy'" and not "'snOOpy' capitalized >>>'SnOOpy'" Indeed. Now captialized comment is clear. We could do that in Pharo70 alpha. Now for OS that distinguish S from s we should pay attention. Stef On

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

> Sent: Wednesday, March 15, 2017 at 2:16 PM > From: "Ben Coman" > To: "Pharo Development List" > Subject: Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource > > On Thu, Mar 16, 2017 at 1:25 AM, Sven Van Caekenberghe

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

> On 15 Mar 2017, at 18:28, Rein, Patrick wrote: > > Thanks for looking into this :) > > @Dave: Can you explain what you would have expected to happen here? I see the > point > that squeaksource could also encode the response as UTF-8. However, currently > the > page is

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

> On 15 Mar 2017, at 19:16, Ben Coman wrote: > > On Thu, Mar 16, 2017 at 1:25 AM, Sven Van Caekenberghe wrote: >> >> Hi, >> >> This is a recurring issue. > > > It would be cool if some magic(TM) could raise a dialog with an > explanation and pull-down

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

Thanks for looking into this :) @Dave: Can you explain what you would have expected to happen here? I see the point that squeaksource could also encode the response as UTF-8. However, currently the page is correctly encoded and delivered in iso-8859-1. From the error message I read that Zinc

Re: [Pharo-dev] Type Inference tools

Please do also read the pharo-dev archives: type inference is something that crops up every 6 months or so. There are a whole bunch of techniques and tools lying around that people have developed. frank On 15 March 2017 at 01:35, Peter Uhnak wrote: > Moose (

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

On Thu, Mar 16, 2017 at 1:25 AM, Sven Van Caekenberghe wrote: > > Hi, > > This is a recurring issue. It would be cool if some magic(TM) could raise a dialog with an explanation and pull-down list to select an encoding - but maybe that is too much hand holding. > > The problem is

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

Hi, This is a recurring issue. The problem is that the server serves a resource, in this case text/html, without specifying its encoding. Today, when no encoding is specified, we default to UTF-8. In this case the server silently serves a resource which is ISO-8895-1 encoded. The error is

Re: [Pharo-dev] PharoSpur32Vm

2017-03-15 15:03 GMT+01:00 Esteban Lorenzano : > sorry for coming late to this thread… hard week :) > why we are trying to compile with cygwin? > is there a problem with the mingw distro? > > I didn’t have the time to update the README, sadly. But well… following > appveyor

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

squeaksource.com is still running on a quite old image, and I know that it has problems with multibyte characters. If you are seeing problems related to this, it's not the fault of Zinc. If you can confirm that this is what is happening, then I guess it is time to update that trusty old

Re: [Pharo-dev] How to listen for microsoft os windows messages (WM_MESSAGE's)?

True but if you want to work with GUI and Graphics APIs its C++ all the way. Mainly because Graphics are extremely complex data that benefits from the workflow of OOP and the performance of C. Combine the two and you have C++. The language we all love to hate. I have not tried myself , but I

Re: [Pharo-dev] ZnInvalidUTF8 on response from squeaksource

On Wed, Mar 15, 2017 at 8:19 PM, Patrick R. wrote: > > Hi everyone, > > I have been working on bringing http://squeaksource.com/ical/ up to speed > for Squeak and wanted to make sure that it also works for Pharo. Therefore, > I have created a travis build job for Squeak and

Re: [Pharo-dev] PharoSpur32Vm

sorry for coming late to this thread… hard week :) why we are trying to compile with cygwin? is there a problem with the mingw distro? I didn’t have the time to update the README, sadly. But well… following appveyor configuration should give you all you need to reproduce the build (that’s what

Re: [Pharo-dev] Capitalized

Hi, thanks for the feedback. So it depends on which definition we will follow... After investigating a little bit more I guess the current implementation is more valuable and should stay. For instance we can easily convert an ivar name into a class name with it: 'ellipseMorph' capitalized ->

Re: [Pharo-dev] Capitalized

On Wed, Mar 15, 2017 at 6:33 PM, Torsten Bergmann wrote: > According to https://en.wikipedia.org/wiki/Capitalization > > to "capitalize" is writing a word with its first letter as a capital > letter (upper-case letter) > AND THE REMAINING LETTERS IN LOWER CASE writing systems. >

Re: [Pharo-dev] Capitalized

On 03/15/2017 05:33 AM, Torsten Bergmann wrote: According to https://en.wikipedia.org/wiki/Capitalization to "capitalize" is writing a word with its first letter as a capital letter (upper-case letter) AND THE REMAINING LETTERS IN LOWER CASE writing systems. So 'SOMETHING' capitalized

Re: [Pharo-dev] Capitalized

Maybe for next Pharo version? As this is a breaking change, which you cannot just deprecate. Also then there would need to be another method that provides the current behavior. Peter On Wed, Mar 15, 2017 at 12:16:44PM +, Henrik Nergaard wrote: > >to "capitalize" is writing a word with its

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60442 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] f35d0c: 60442

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f35d0c707461ac1263574710cb05737da37ca5dd https://github.com/pharo-project/pharo-core/commit/f35d0c707461ac1263574710cb05737da37ca5dd Author: Jenkins Build Server Date:

[Pharo-dev] ZnInvalidUTF8 on response from squeaksource

Hi everyone, I have been working on bringing http://squeaksource.com/ical/ up to speed for Squeak and wanted to make sure that it also works for Pharo. Therefore, I have created a travis build job for Squeak and Pharo (https://travis-ci.org/codeZeilen/ical-smalltalk/jobs/211298950) which pulls

Re: [Pharo-dev] Missing Zip64 support

Hi, yes, Iceberg will solve this problem by not having it, but it would be nice to be able to unzip bigger files from Pharo too (ok, maybe not a priority, but it would be cool anyway :P) Esteban > On 15 Mar 2017, at 13:07, Pavel Krivanek wrote: > > To clone the

Re: [Pharo-dev] Capitalized

>to "capitalize" is writing a word with its first letter. The Smalltalk String is not neccessarily just a word, it could be something else so the current implementation makes no assumptions of what the string is.

Re: [Pharo-dev] Missing Zip64 support

To clone the repository from Pharo we can use Iceberg: IceRepositoryCreator new remote: (IceRemote url: 'https://github.com/guillep/pharo-core.git'); location: ('pharo-core' asFileReference ensureCreateDirectory); createRepository. 2017-03-15 11:31 GMT+01:00 Thierry Goubier

[Pharo-dev] Capitalized

According to https://en.wikipedia.org/wiki/Capitalization to "capitalize" is writing a word with its first letter as a capital letter (upper-case letter) AND THE REMAINING LETTERS IN LOWER CASE writing systems. So 'SOMETHING' capitalized currently returns "SOMETHING" in Pharo but should

Re: [Pharo-dev] Missing Zip64 support

Hi Pavel, Which means command like these: cd pharo; mkdir filetree; cd filetree; wget -O - https://api.github.com/repos/dalehenrich/filetree/tarball/pharo6.0_dev | tar xz --strip-components=1 ./pharo-cli pharo/Pharo.image --no-default-preferences eval --save Metacello new baseline:

[Pharo-dev] Missing Zip64 support

Hi, our current Compression package does not support Zip64 which is limiting us in usage of Metacello together with Git. When we use the Metacello for installing of a baseline like: Metacello new baseline: 'IDE'; repository: 'github://guillep/pharo-core'; load. then the Metacello

[Pharo-dev] [ANN] Collecting all Pharo related publications

Hi, We want to create a list of all Pharo related papers. I have added this page: http://pharo.org/web/PharoPublications it is linked from http://pharo.org/documentation Marcus

Re: [Pharo-dev] PharoSpur32Vm

2017-03-15 9:22 GMT+01:00 philippe.b...@highoctane.be < philippe.b...@gmail.com>: > I made my own build here. > Not up to date with latest stuff but should work for the build process. > > https://ci.appveyor.com/project/philippeback/pharo-vm > > It uses my forked repo and provided you set your

Re: [Pharo-dev] Type Inference tools

Moose ( http://www.moosetechnology.org/ ) optionally uses RoelTyper when importing Smalltalk code for analysis. Lukas will need a good type inferencer as he is currently working on a better autocompetion. Peter On Tue, Mar 14, 2017 at 03:38:51PM -0700, Gus wrote: > Hi, > I am working on a

Re: [Pharo-dev] PharoSpur32Vm

I made my own build here. Not up to date with latest stuff but should work for the build process. https://ci.appveyor.com/project/philippeback/pharo-vm It uses my forked repo and provided you set your own bintray env vars for API keys will publish there. Check all of the output of env vars and

Re: [Pharo-dev] PharoSpur32Vm

2017-03-14 22:22 GMT+01:00 Nicolas Cellier < nicolas.cellier.aka.n...@gmail.com>: > > > 2017-03-14 9:30 GMT+01:00 Nicolas Cellier gmail.com>: > >> >> >> 2017-03-14 8:58 GMT+01:00 Nicolai Hess : >> >>> >>> >>> 2017-03-11 10:01 GMT+01:00 Nicolas

Re: [Pharo-dev] [Vm-dev] BUG? A problem with callbacks that shows up in 64bits (but is on 32bits too)

Le 14 mars 2017 17:34, "Eliot Miranda" a écrit : On Tue, Mar 14, 2017 at 8:56 AM, Nicolai Hess wrote: > > > > 2017-03-14 16:46 GMT+01:00 Eliot Miranda : > >> >> Hi Esteban, Hi Igor, Hi All, >> >> On Fri, Mar 10, 2017 at