June 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Gradualtalk

by Bob Williams

Johan Thank you for pointing me to the VM download on the Pharo site, that worked after I changed Pharo.exe to Gradualtalk.exe. Is there a more thorough reference than the quick reference (I have the paper Gradual Typing For Smalltalk)? I noticed that Magnitude, Number and Integer have uses:TTyped. The quick reference stated that the class and it subclasses would have the type system activated, so are the last two required or is the reference in error? Will this typing be incorporated into Pharo or is it dead? Thanks bw -- View this message in context: http://forum.world.st/Gradualtalk-tp4762633p4762831.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 12, 2014

Re: [Pharo-users] [Pharo-dev] [ANN] Base62/Base36

by Norbert Hartl

Hmm *cough* http://smalltalkhub.com/#!/~NorbertHartl/Base62 Norbert Am 12.06.2014 um 13:12 schrieb Norbert Hartl <norbert(a)hartl.name>: > Just for the record. Iâve uploaded a package to smalltalkhub that contains util classes to en-/decode values into/from Base62/Base36. > > Base62/Base36 encode numbers in short strings. These are used e.g. by url shortener services from google, bit.ly etc. > > Base36 uses lowercase letters and numbers to encode, Base62 uses all characters from Base36 plus all uppercase letters. Base62 produces smaller strings while Base36 produces case insensitive ones. > > Example: > > Base62 fromNumber: 100000 -> 'q0Uâ > > Base36 fromNumber: 100000 -> â255s' > > FYI, > > Norbert > >

June 12, 2014

[ANN] Base62/Base36

by Norbert Hartl

Just for the record. Iâve uploaded a package to smalltalkhub that contains util classes to en-/decode values into/from Base62/Base36. Base62/Base36 encode numbers in short strings. These are used e.g. by url shortener services from google, bit.ly etc. Base36 uses lowercase letters and numbers to encode, Base62 uses all characters from Base36 plus all uppercase letters. Base62 produces smaller strings while Base36 produces case insensitive ones. Example: Base62 fromNumber: 100000 -> 'q0Uâ Base36 fromNumber: 100000 -> â255s' FYI, Norbert

June 12, 2014

Re: [Pharo-users] Base64 encoding + UTF8 ?

by Henrik Johansen

On 11 Jun 2014, at 10:28 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Bonsoir FranÃ§ois, > > From the class comment of ZnBase64Encoder: > > [...] > Note that to encode a String as Base64, you first have to encode the characters as bytes using a character encoder. > [...] > > Sending #asByteArray to a String is the same as doing no encoding (or doing null encoding). > > Consider: > > ZnBase64Encoder new encode: (ZnUTF8Encoder new encodeString: 'tamÃ¨reenslipdeguerre'). > > => 'dGFtw6hyZWVuc2xpcGRlZ3VlcnJl' > > ZnBase64Encoder new encode: (ZnByteEncoder iso88591 encodeString: 'tamÃ¨reenslipdeguerre'). > > => 'dGFt6HJlZW5zbGlwZGVndWVycmU=' > > ZnBase64Encoder new encode: (ZnNullEncoder new encodeString: 'tamÃ¨reenslipdeguerre'). > > => 'dGFt6HJlZW5zbGlwZGVndWVycmU=' > > The last two are often the same, and thus equivalent to #asByteArray, but not always. > > HTH, > > Sven In other words, Base64 isnât really an encoding, itâs a transfer format, whose purpose is to only transmit bytes with "safe" values that have no chance of being interpreted as control sequences by a set of protocols. Encoding Strings -> Bytes is a separate concern. Cheers, Henry

June 12, 2014

Re: [Pharo-users] Base64 encoding + UTF8 ?

by FranÃ§ois Stephany

Oh stupid me! Thanks a lot Sven, crystal clear explanations (and class comments!), as always :) On Wed, Jun 11, 2014 at 10:28 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Bonsoir FranÃ§ois, > > From the class comment of ZnBase64Encoder: > > [...] > Note that to encode a String as Base64, you first have to encode the > characters as bytes using a character encoder. > [...] > > Sending #asByteArray to a String is the same as doing no encoding (or > doing null encoding). > > Consider: > > ZnBase64Encoder new encode: (ZnUTF8Encoder new encodeString: > 'tamÃ¨reenslipdeguerre'). > > => 'dGFtw6hyZWVuc2xpcGRlZ3VlcnJl' > > ZnBase64Encoder new encode: (ZnByteEncoder iso88591 encodeString: > 'tamÃ¨reenslipdeguerre'). > > => 'dGFt6HJlZW5zbGlwZGVndWVycmU=' > > ZnBase64Encoder new encode: (ZnNullEncoder new encodeString: > 'tamÃ¨reenslipdeguerre'). > > => 'dGFt6HJlZW5zbGlwZGVndWVycmU=' > > The last two are often the same, and thus equivalent to #asByteArray, but > not always. > > HTH, > > Sven > > On 11 Jun 2014, at 21:56, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> > wrote: > > > I might hit some problem with Base64 encoding in there. > > It seems that Pharo does not use UTF8 for its Base64 encoding. > > > > I'm probably missing something related to Base64 encoding... > > > > In Pharo 3.0: > > > > ZnBase64Encoder new encode: 'tamÃ¨reenslipdeguerre' asByteArray. > > -> 'dGFt6HJlZW5zbGlwZGVndWVycmU=' > > > > 'tamÃ¨reenslipdeguerre' base64Encoded. > > -> 'dGFt6HJlZW5zbGlwZGVndWVycmU=' > > > > In Ruby 2.0: > > > > Base64.strict_encode64("tamÃ¨reenslipdeguerre") > > -> dGFtw6hyZWVuc2xpcGRlZ3VlcnJl > > > > http://www.motobit.com/util/base64-decoder-encoder.asp > > (iso-8859-1) > > tamÃ¨reenslipdeguerre -> dGFt6HJlZW5zbGlwZGVndWVycmU= > > > > http://www.motobit.com/util/base64-decoder-encoder.asp > > (utf8) > > -tamÃ¨reenslipdeguerre > dGFtw6hyZWVuc2xpcGRlZ3VlcnJl > > >

June 11, 2014

Re: [Pharo-users] Base64 encoding + UTF8 ?

by Sven Van Caekenberghe

Bonsoir FranÃ§ois, >From the class comment of ZnBase64Encoder: [...] Note that to encode a String as Base64, you first have to encode the characters as bytes using a character encoder. [...] Sending #asByteArray to a String is the same as doing no encoding (or doing null encoding). Consider: ZnBase64Encoder new encode: (ZnUTF8Encoder new encodeString: 'tamÃ¨reenslipdeguerre'). => 'dGFtw6hyZWVuc2xpcGRlZ3VlcnJl' ZnBase64Encoder new encode: (ZnByteEncoder iso88591 encodeString: 'tamÃ¨reenslipdeguerre'). => 'dGFt6HJlZW5zbGlwZGVndWVycmU=' ZnBase64Encoder new encode: (ZnNullEncoder new encodeString: 'tamÃ¨reenslipdeguerre'). => 'dGFt6HJlZW5zbGlwZGVndWVycmU=' The last two are often the same, and thus equivalent to #asByteArray, but not always. HTH, Sven On 11 Jun 2014, at 21:56, FranÃ§ois Stephany <tulipe.moutarde(a)gmail.com> wrote: > I might hit some problem with Base64 encoding in there. > It seems that Pharo does not use UTF8 for its Base64 encoding. > > I'm probably missing something related to Base64 encoding... > > In Pharo 3.0: > > ZnBase64Encoder new encode: 'tamÃ¨reenslipdeguerre' asByteArray. > -> 'dGFt6HJlZW5zbGlwZGVndWVycmU=' > > 'tamÃ¨reenslipdeguerre' base64Encoded. > -> 'dGFt6HJlZW5zbGlwZGVndWVycmU=' > > In Ruby 2.0: > > Base64.strict_encode64("tamÃ¨reenslipdeguerre") > -> dGFtw6hyZWVuc2xpcGRlZ3VlcnJl > > http://www.motobit.com/util/base64-decoder-encoder.asp > (iso-8859-1) > tamÃ¨reenslipdeguerre -> dGFt6HJlZW5zbGlwZGVndWVycmU= > > http://www.motobit.com/util/base64-decoder-encoder.asp > (utf8) > -tamÃ¨reenslipdeguerre > dGFtw6hyZWVuc2xpcGRlZ3VlcnJl

June 11, 2014

Base64 encoding + UTF8 ?

by FranÃ§ois Stephany

I might hit some problem with Base64 encoding in there. It seems that Pharo does not use UTF8 for its Base64 encoding. I'm probably missing something related to Base64 encoding... In Pharo 3.0: ZnBase64Encoder new encode: 'tamÃ¨reenslipdeguerre' asByteArray. -> 'dGFt6HJlZW5zbGlwZGVndWVycmU=' 'tamÃ¨reenslipdeguerre' base64Encoded. -> 'dGFt6HJlZW5zbGlwZGVndWVycmU=' In Ruby 2.0: Base64.strict_encode64("tamÃ¨reenslipdeguerre") -> dGFtw6hyZWVuc2xpcGRlZ3VlcnJl http://www.motobit.com/util/base64-decoder-encoder.asp (iso-8859-1) tamÃ¨reenslipdeguerre -> dGFt6HJlZW5zbGlwZGVndWVycmU= http://www.motobit.com/util/base64-decoder-encoder.asp (utf8) -tamÃ¨reenslipdeguerre > dGFtw6hyZWVuc2xpcGRlZ3VlcnJl

June 11, 2014

Re: [Pharo-users] Another Pharo based solution released

by Tudor Girba

Congratulations! Doru On Mon, Jun 9, 2014 at 8:22 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Last Friday my company released a new software solution that involves > Pharo in the server side. > > It consists of a Android based app running on tablets, used for the > showcase and sales of products during expos (of retail companies), > backed by a Pharo server through a REST API, and with a Seaside based > admin/users web. > > The first expo was during the last weekend (fri-sun), and it involved > the sales of a large number of orders and products (I can't disclose > the numbers). > The scale of the solution/user base is small, far from being "cloud > scale", but it is for one of the largest consumer goods manufacturer > (and the one who sold the most during the expo). > Anyhow, the server handled all the request perfectly, without a single > glitch. > > We already have some future expos scheduled. So it will continue to > run along the already running Pharo based solution in the same > company. > > Best regards! > > Esteban A. Maringolo > > -- www.tudorgirba.com "Every thing has its own flow"

June 11, 2014

Re: [Pharo-users] Gradualtalk

by Johan Fabry

Hi Bob, I think youâve got the wrong vm. We have not tried Gradualtalk on Windows, but itâs odd to me that your vm is Croquet.exe. Could you download the latest vm from the Pharo website and try with that? On Jun 11, 2014, at 10:16 AM, Bob Williams <rwilliams19(a)cox.net> wrote: > I am trying to look at the annotation typing used in Gradualtalk, but I am having no success. I download the gradualtalk. zip and what I think is the correct Cog VM, but when I run Croquet I do not see any window; I do see the application running in the Task Manager. I am trying to install it on a computer running Windows Vista. The files in the Gradualtalk directory are: > > Croquet.exe created 4 Oct 2010 > Croquet.ini > Croquet.map > Gradualtalk.changes created 3 12 2013 > Gradualtalk.image > PharoDebug.log > SqueadFFIPrims.dll > stderr > Win32OSProcessPlugin.dll > > Both stderr and PharoDebug.log were created when I attempted the run. The PharoDebug.log has the following: > > THERE_BE_DRAGONS_HERE > ==== Startup Error: MessageNotUnderstood: receiver of "do:" is nil > 11 June 2014 9:36:03.002 am > > VM: Win32 - IX86 - 6.0 - > > Any help would be appreciated. Would I have more success on a Mac? > > bw > > PS: Will the annotation typing be included in a future Pharo releases? ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

June 11, 2014

Gradualtalk

by Bob Williams

I am trying to look at the annotation typing used in Gradualtalk, but I am having no success. I download the gradualtalk. zip and what I think is the correct Cog VM, but when I run Croquet I do not see any window; I do see the application running in the Task Manager. I am trying to install it on a computer running Windows Vista. The files in the Gradualtalk directory are: Croquet.exe created 4 Oct 2010 Croquet.ini Croquet.map Gradualtalk.changes created 3 12 2013 Gradualtalk.image PharoDebug.log SqueadFFIPrims.dll stderr Win32OSProcessPlugin.dll Both stderr and PharoDebug.log were created when I attempted the run. The PharoDebug.log has the following: THERE_BE_DRAGONS_HERE ==== Startup Error: MessageNotUnderstood: receiver of "do:" is nil 11 June 2014 9:36:03.002 am VM: Win32 - IX86 - 6.0 - Any help would be appreciated. Would I have more success on a Mac? bw PS: Will the annotation typing be included in a future Pharo releases?

June 11, 2014