- Pharo-users - lists.pharo.org

Re: [Pharo-users] A Logo Proposal for Smalltalk

by horrido

I expect it to be used in exactly the same way other languages like Clojure, Elixir, Kotlin, and Julia use theirs. Of course, whether these logos are widely used has more to do with the languages' promotional efforts. As for the commercial entities, they may choose to use it or not. This depends on their marketing approaches. Cincom doesn't have a product logo for VisualWorks, nor does Instantiations for VA Smalltalk, but GemTalk does for GemStone/S. It's entirely up to them. I think the logo can, and should, be used whenever the presentation is *not product-specific*. I wonder how other languages control their copyrights. Ben Coman wrote > I half like the idea of a Smalltalk logo, but logos are most effective > when > they are widely used. > Once we have this "official" logo, how do you expect it to be used? > Do you expect organisations to use it in their literature as part of their > branding identity? > Should it get equal weighting as their corporate identity? > Will all these commercial entities feel the logo strengthens their > position > in solidarity, > or dilutes their position. You know that some our community differentiate > Pharo from Smalltalk. > > Also an important question to determine early on, > how will copyright and trademark rights of the logo be controlled? > > cheers -ben -- View this message in context: http://forum.world.st/A-Logo-Proposal-for-Smalltalk-tp4945122p4945487.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 3, 2017

Re: [Pharo-users] A Logo Proposal for Smalltalk

by horrido

I prefer your first attempt (just centre the [|] against the square). Your first design instinct was correct. I prefer [|] having the same height. I like the blue colour but you may experiment with different colours. philippeback wrote > SVG file. Works in Inkscape. > > I wanted the [ | ] to be a golden rectangle. > > See https://en.wikipedia.org/wiki/Golden_ratio > > 1.618 something > (1 + 5 sqrt) / 2 > > Look at how the reciprocal of the golden ratio looks like [|] > > We should have GoldenRatio in Float class. > > initialize > "Float initialize" > "Constants from Computer Approximations, pp. 182-183: > Pi = 3.14159265358979323846264338327950288 > Pi/2 = 1.57079632679489661923132169163975144 > Pi*2 = 6.28318530717958647692528676655900576 > Pi/180 = 0.01745329251994329576923690768488612 > 2.0 ln = 0.69314718055994530941723212145817657 > 2.0 sqrt = 1.41421356237309504880168872420969808" > > Pi := 3.14159265358979323846264338327950288. > Halfpi := Pi / 2.0. > Twopi := Pi * 2.0. > ThreePi := Pi * 3.0. > RadiansPerDegree := Pi / 180.0. > > Ln2 := 0.69314718055994530941723212145817657. > Ln10 := 10.0 ln. > Sqrt2 := 1.41421356237309504880168872420969808. > E := 2.718281828459045235360287471353. > > Epsilon := 0.000000000001. "Defines precision of mathematical functions" > > MaxVal := 1.7976931348623157e308. > MaxValLn := 709.782712893384. > MinValLogBase2 := -1074. > > Infinity := MaxVal * MaxVal. > NegativeInfinity := 0.0 - Infinity. > NaN := Infinity - Infinity. > NegativeZero := 1.0 / Infinity negated. > > On Wed, May 3, 2017 at 2:52 PM, Esteban A. Maringolo > < > emaringolo@ > > wrote: >> Hi Phil, >> >> I don't like the diamond in the back, nor the colors (looks old). >> Also the square brackets and vertical bar are not horizontally centered. >> >> I still like the concept though. I couldn't see the golden ratio. Can >> you overlay it? >> >> Regards! >> Esteban A. Maringolo >> >> >> 2017-05-03 9:38 GMT-03:00 > phil@ > < > phil@ > >: >>> I got a shot at this and this gives the following. >>> >>> What we should do: >>> >>> - ensure the [|] shape has the gold ratio (so it is naturally >>> attractive). >>> - make sure the square is positioned so that the golden ratio is also >>> all over the place. >>> >>> Color wise, I went for blue because Smalltalk has a natural elegance >>> and goes for no crap. >>> >>> Phil >>> >>> On Wed, May 3, 2017 at 12:49 PM, horrido < > horrido.hobbies@ > > wrote: >>>> Esteban A. Maringolo wrote >>>>> A decade+ ago I created the one attached, and I've seen used in some >>>>> Smalltalk related sites. I still like it but it can be done better. >>>> >>>> *[|]* seems to be a popular choice. I got two votes for this at >>>> LinkedIn. >>>> >>>> It looks rather plain to me, though. It lacks sizzle. >>>> >>>> Maybe the best way to settle this is to have a Smalltalk logo >>>> competition. >>>> People can submit their logo designs and a panel of judges can decide >>>> on the >>>> best one. The winning entry would be the "official" Smalltalk logo. >>>> >>>> For the panel of judges, I would like representatives from each of the >>>> following: >>>> >>>> o ESUG >>>> o the Pharo project >>>> o the Squeak project (Alan Kay?) >>>> o Cincom >>>> o Instantiations >>>> o GemTalk >>>> >>>> Of course, my stylized hot air balloon would be Logo Candidate Entry >>>> #1. >>>> >>>> If you think this is a good idea, I'll start organizing it. The >>>> submission >>>> deadline for the competition would be July 18, 2017 (the first >>>> anniversary >>>> of my TechBeacon article, " How learning Smalltalk can make you a >>>> better >>>> developer >>>> <https://techbeacon.com/how-learning-smalltalk-can-make-you-better-developer> >>>> "). >>>> >>>> >>>> >>>> -- >>>> View this message in context: >>>> http://forum.world.st/A-Logo-Proposal-for-Smalltalk-tp4945122p4945390.html >>>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>>> >>>> >> >> > > > SmalltalkLogo.svg (3K) > <http://forum.world.st/attachment/4945437/0/SmalltalkLogo.svg> > SmalltalkLogo.png (8K) > <http://forum.world.st/attachment/4945437/1/SmalltalkLogo.png> > SmalltalkLogo2.svg (6K) > <http://forum.world.st/attachment/4945437/2/SmalltalkLogo2.svg> -- View this message in context: http://forum.world.st/A-Logo-Proposal-for-Smalltalk-tp4945122p4945484.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 3, 2017

Re: [Pharo-users] A Logo Proposal for Smalltalk

by horrido

I have to say, I really like it! Is this Logo Candidate Entry #2 ? philippeback wrote > I got a shot at this and this gives the following. > > What we should do: > > - ensure the [|] shape has the gold ratio (so it is naturally attractive). > - make sure the square is positioned so that the golden ratio is also > all over the place. > > Color wise, I went for blue because Smalltalk has a natural elegance > and goes for no crap. > > Phil > > On Wed, May 3, 2017 at 12:49 PM, horrido < > horrido.hobbies@ > > wrote: >> Esteban A. Maringolo wrote >>> A decade+ ago I created the one attached, and I've seen used in some >>> Smalltalk related sites. I still like it but it can be done better. >> >> *[|]* seems to be a popular choice. I got two votes for this at LinkedIn. >> >> It looks rather plain to me, though. It lacks sizzle. >> >> Maybe the best way to settle this is to have a Smalltalk logo >> competition. >> People can submit their logo designs and a panel of judges can decide on >> the >> best one. The winning entry would be the "official" Smalltalk logo. >> >> For the panel of judges, I would like representatives from each of the >> following: >> >> o ESUG >> o the Pharo project >> o the Squeak project (Alan Kay?) >> o Cincom >> o Instantiations >> o GemTalk >> >> Of course, my stylized hot air balloon would be Logo Candidate Entry #1. >> >> If you think this is a good idea, I'll start organizing it. The >> submission >> deadline for the competition would be July 18, 2017 (the first >> anniversary >> of my TechBeacon article, " How learning Smalltalk can make you a better >> developer >> <https://techbeacon.com/how-learning-smalltalk-can-make-you-better-developer> >> "). >> >> >> >> -- >> View this message in context: >> http://forum.world.st/A-Logo-Proposal-for-Smalltalk-tp4945122p4945390.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > > > SmalltalkLogo.png (7K) > <http://forum.world.st/attachment/4945411/0/SmalltalkLogo.png> -- View this message in context: http://forum.world.st/A-Logo-Proposal-for-Smalltalk-tp4945122p4945482.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 3, 2017

Re: [Pharo-users] How to detect encoding of a file

by Norbert Hartl

> Am 03.05.2017 um 18:10 schrieb Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com>: > >> Le 03/05/2017 Ã 16:41, Sven Van Caekenberghe a Ã©crit : >> >>> On 3 May 2017, at 12:18, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> >>> Hi Cyril, >>> >>> I want to try to write such a detector. I'll get back to you. >> >> I added the following (Zn #bleedingEdge): >> >> === >> Name: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.49 >> Author: SvenVanCaekenberghe >> Time: 3 May 2017, 4:30:44.081888 pm >> UUID: fe8b083d-010b-0d00-9df5-fde304bccfdc >> Ancestors: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.48 >> >> Add ZnCharacterEncoder class>>#detectEncoding: to try to heuristically and unreliably guess the encoding used by a collection of bytes >> >> Add ZnCharacterEncoderTests>>#testDetectEncoding >> >> Add #= and #hash to ZnSimplifiedByteEncoder and ZnEndianSensitiveUTFEncoder >> >> Always use canonical name in ZnSimplifiedByteEncoder class>>#newForEncoding: >> === >> Name: Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.31 >> Author: SvenVanCaekenberghe >> Time: 3 May 2017, 4:31:09.469852 pm >> UUID: 30ef8b3e-010b-0d00-9df6-4a9304bccfdc >> Ancestors: Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.30 >> >> Add ZnCharacterEncoder class>>#detectEncoding: to try to heuristically and unreliably guess the encoding used by a collection of bytes >> >> Add ZnCharacterEncoderTests>>#testDetectEncoding >> >> Add #= and #hash to ZnSimplifiedByteEncoder and ZnEndianSensitiveUTFEncoder >> >> Always use canonical name in ZnSimplifiedByteEncoder class>>#newForEncoding: >> === >> >> >> Now you can do the following: >> >> ZnCharacterEncoder detectEncoding: ((FileLocator desktop / 'some.data') binaryReadStreamDo: [ :in | in upToEnd ]). >> >> (FileLocator desktop / 'some.data') binaryReadStreamDo: [ :in | >> | bytes encoder | >> bytes := in upToEnd. >> encoder := ZnCharacterEncoder detectEncoding: bytes. >> encoder decodeBytes: bytes ]. >> >> It works on the test file you gave me, but this process is just a guess, a heuristic that is unreliable and often wrong (especially for very similar byte encodings), see https://en.wikipedia.org/wiki/Charset_detection. >> >> You can give the whole contents to the detector, or just a header. >> >> I was a bit too optimistic though, this is basically an unsolvable problem. It is MUCH better to somehow know up front what the encoding used is, or to know something useable about the contents (like the header of HTML or XML). >> >> Sven >> > > Thank you! I'll try this tomorrow. If it works well I wonder if we can > still includes it in Pharo6. Since it's only a little feature unused in > Pharo it should not break anything but it would be cool addition for Moose. > > But since it is feature freeze if people do not want I'll not push it > for Pharo 6 :) > It shouldn't be included. There no such thing as side-effect-free change. Moose can load a newer version of zinc. That is how it is supposed to be. Norbert > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

May 3, 2017

Re: [Pharo-users] How to detect encoding of a file

by Cyril Ferlicot D.

Le 03/05/2017 Ã 16:41, Sven Van Caekenberghe a Ã©crit : > >> On 3 May 2017, at 12:18, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi Cyril, >> >> I want to try to write such a detector. I'll get back to you. > > I added the following (Zn #bleedingEdge): > > === > Name: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.49 > Author: SvenVanCaekenberghe > Time: 3 May 2017, 4:30:44.081888 pm > UUID: fe8b083d-010b-0d00-9df5-fde304bccfdc > Ancestors: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.48 > > Add ZnCharacterEncoder class>>#detectEncoding: to try to heuristically and unreliably guess the encoding used by a collection of bytes > > Add ZnCharacterEncoderTests>>#testDetectEncoding > > Add #= and #hash to ZnSimplifiedByteEncoder and ZnEndianSensitiveUTFEncoder > > Always use canonical name in ZnSimplifiedByteEncoder class>>#newForEncoding: > === > Name: Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.31 > Author: SvenVanCaekenberghe > Time: 3 May 2017, 4:31:09.469852 pm > UUID: 30ef8b3e-010b-0d00-9df6-4a9304bccfdc > Ancestors: Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.30 > > Add ZnCharacterEncoder class>>#detectEncoding: to try to heuristically and unreliably guess the encoding used by a collection of bytes > > Add ZnCharacterEncoderTests>>#testDetectEncoding > > Add #= and #hash to ZnSimplifiedByteEncoder and ZnEndianSensitiveUTFEncoder > > Always use canonical name in ZnSimplifiedByteEncoder class>>#newForEncoding: > === > > > Now you can do the following: > > ZnCharacterEncoder detectEncoding: ((FileLocator desktop / 'some.data') binaryReadStreamDo: [ :in | in upToEnd ]). > > (FileLocator desktop / 'some.data') binaryReadStreamDo: [ :in | > | bytes encoder | > bytes := in upToEnd. > encoder := ZnCharacterEncoder detectEncoding: bytes. > encoder decodeBytes: bytes ]. > > It works on the test file you gave me, but this process is just a guess, a heuristic that is unreliable and often wrong (especially for very similar byte encodings), see https://en.wikipedia.org/wiki/Charset_detection. > > You can give the whole contents to the detector, or just a header. > > I was a bit too optimistic though, this is basically an unsolvable problem. It is MUCH better to somehow know up front what the encoding used is, or to know something useable about the contents (like the header of HTML or XML). > > Sven > Thank you! I'll try this tomorrow. If it works well I wonder if we can still includes it in Pharo6. Since it's only a little feature unused in Pharo it should not break anything but it would be cool addition for Moose. But since it is feature freeze if people do not want I'll not push it for Pharo 6 :) -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

May 3, 2017

Re: [Pharo-users] Smalltalk syntactic coloration in Spec's TextModel

by Nicolai Hess

2017-05-03 16:57 GMT+02:00 Julien Delplanque <julien(a)tamere.eu>: > Hello, > > I looked in the mailing list archive but did not found an answer. > > Is there any way to have Smalltalk syntactic coloration in a TextModel > without having to put efforts in it? > > I mean, if I do: > > TextModel new > isForSmalltalkCode: true; > text: (Collection>>#any) sourceCode; > openWithSpec > > The text displayed is black. > > Thanks in advance, > > Julien > > > Hi, you need to add aboutToStyle:true TextModel new isForSmalltalkCode: true; text: (Collection>>#anyOne) sourceCode; aboutToStyle: true; openWithSpec

May 3, 2017

Smalltalk syntactic coloration in Spec's TextModel

by Julien Delplanque

Hello, I looked in the mailing list archive but did not found an answer. Is there any way to have Smalltalk syntactic coloration in a TextModel without having to put efforts in it? I mean, if I do: TextModel new isForSmalltalkCode: true; text: (Collection>>#any) sourceCode; openWithSpec The text displayed is black. Thanks in advance, Julien

May 3, 2017

Re: [Pharo-users] How to detect encoding of a file

by Sven Van Caekenberghe

> On 3 May 2017, at 12:18, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Cyril, > > I want to try to write such a detector. I'll get back to you. I added the following (Zn #bleedingEdge): === Name: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.49 Author: SvenVanCaekenberghe Time: 3 May 2017, 4:30:44.081888 pm UUID: fe8b083d-010b-0d00-9df5-fde304bccfdc Ancestors: Zinc-Character-Encoding-Core-SvenVanCaekenberghe.48 Add ZnCharacterEncoder class>>#detectEncoding: to try to heuristically and unreliably guess the encoding used by a collection of bytes Add ZnCharacterEncoderTests>>#testDetectEncoding Add #= and #hash to ZnSimplifiedByteEncoder and ZnEndianSensitiveUTFEncoder Always use canonical name in ZnSimplifiedByteEncoder class>>#newForEncoding: === Name: Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.31 Author: SvenVanCaekenberghe Time: 3 May 2017, 4:31:09.469852 pm UUID: 30ef8b3e-010b-0d00-9df6-4a9304bccfdc Ancestors: Zinc-Character-Encoding-Tests-SvenVanCaekenberghe.30 Add ZnCharacterEncoder class>>#detectEncoding: to try to heuristically and unreliably guess the encoding used by a collection of bytes Add ZnCharacterEncoderTests>>#testDetectEncoding Add #= and #hash to ZnSimplifiedByteEncoder and ZnEndianSensitiveUTFEncoder Always use canonical name in ZnSimplifiedByteEncoder class>>#newForEncoding: === Now you can do the following: ZnCharacterEncoder detectEncoding: ((FileLocator desktop / 'some.data') binaryReadStreamDo: [ :in | in upToEnd ]). (FileLocator desktop / 'some.data') binaryReadStreamDo: [ :in | | bytes encoder | bytes := in upToEnd. encoder := ZnCharacterEncoder detectEncoding: bytes. encoder decodeBytes: bytes ]. It works on the test file you gave me, but this process is just a guess, a heuristic that is unreliable and often wrong (especially for very similar byte encodings), see https://en.wikipedia.org/wiki/Charset_detection. You can give the whole contents to the detector, or just a header. I was a bit too optimistic though, this is basically an unsolvable problem. It is MUCH better to somehow know up front what the encoding used is, or to know something useable about the contents (like the header of HTML or XML). Sven > Any chance you could give me (part of) a file that causes you trouble (one that is legal latin1, yet does not fail utf-8 while doing it wrong in utf-8) ? > > Sven > >> On 3 May 2017, at 11:40, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >> >> Hello, >> >> We have a problem using Moose because we have files which we don't know >> the encoding. Currently we have this implementation to get the content >> of a file: >> >> completeText >> self fileReference exists ifFalse: [ ^ '' ]. >> ^ self fileReference readStreamDo: [ :s | >> [ s contents ] >> on: Error >> do: [ [ s converter: Latin1TextConverter new; contents ] >> on: Error >> do: [ '' ] ] ] >> >> But, we have a problem because we have currently some files at >> Synectique in ISO-8859-1. The problem is that #contents is able to read >> some of the files without throwing an error, but the content is not >> right because it is not the good encoding. >> >> Thus I wonder if it is possible to get the Encoding of a FileReference >> in Pharo to be able to read the file with the right encoding? Something >> like the bash command `file -I myFile.txt`. >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr >> >> http://www.synectique.eu >> 2 rue Jacques PrÃ©vert 01, >> 59650 Villeneuve d'ascq France >> >

May 3, 2017

Re: [Pharo-users] A Logo Proposal for Smalltalk

by phil＠highoctane.be

SVG file. Works in Inkscape. I wanted the [ | ] to be a golden rectangle. See https://en.wikipedia.org/wiki/Golden_ratio 1.618 something (1 + 5 sqrt) / 2 Look at how the reciprocal of the golden ratio looks like [|] We should have GoldenRatio in Float class. initialize "Float initialize" "Constants from Computer Approximations, pp. 182-183: Pi = 3.14159265358979323846264338327950288 Pi/2 = 1.57079632679489661923132169163975144 Pi*2 = 6.28318530717958647692528676655900576 Pi/180 = 0.01745329251994329576923690768488612 2.0 ln = 0.69314718055994530941723212145817657 2.0 sqrt = 1.41421356237309504880168872420969808" Pi := 3.14159265358979323846264338327950288. Halfpi := Pi / 2.0. Twopi := Pi * 2.0. ThreePi := Pi * 3.0. RadiansPerDegree := Pi / 180.0. Ln2 := 0.69314718055994530941723212145817657. Ln10 := 10.0 ln. Sqrt2 := 1.41421356237309504880168872420969808. E := 2.718281828459045235360287471353. Epsilon := 0.000000000001. "Defines precision of mathematical functions" MaxVal := 1.7976931348623157e308. MaxValLn := 709.782712893384. MinValLogBase2 := -1074. Infinity := MaxVal * MaxVal. NegativeInfinity := 0.0 - Infinity. NaN := Infinity - Infinity. NegativeZero := 1.0 / Infinity negated. On Wed, May 3, 2017 at 2:52 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Hi Phil, > > I don't like the diamond in the back, nor the colors (looks old). > Also the square brackets and vertical bar are not horizontally centered. > > I still like the concept though. I couldn't see the golden ratio. Can > you overlay it? > > Regards! > Esteban A. Maringolo > > > 2017-05-03 9:38 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: >> I got a shot at this and this gives the following. >> >> What we should do: >> >> - ensure the [|] shape has the gold ratio (so it is naturally attractive). >> - make sure the square is positioned so that the golden ratio is also >> all over the place. >> >> Color wise, I went for blue because Smalltalk has a natural elegance >> and goes for no crap. >> >> Phil >> >> On Wed, May 3, 2017 at 12:49 PM, horrido <horrido.hobbies(a)gmail.com> wrote: >>> Esteban A. Maringolo wrote >>>> A decade+ ago I created the one attached, and I've seen used in some >>>> Smalltalk related sites. I still like it but it can be done better. >>> >>> *[|]* seems to be a popular choice. I got two votes for this at LinkedIn. >>> >>> It looks rather plain to me, though. It lacks sizzle. >>> >>> Maybe the best way to settle this is to have a Smalltalk logo competition. >>> People can submit their logo designs and a panel of judges can decide on the >>> best one. The winning entry would be the "official" Smalltalk logo. >>> >>> For the panel of judges, I would like representatives from each of the >>> following: >>> >>> o ESUG >>> o the Pharo project >>> o the Squeak project (Alan Kay?) >>> o Cincom >>> o Instantiations >>> o GemTalk >>> >>> Of course, my stylized hot air balloon would be Logo Candidate Entry #1. >>> >>> If you think this is a good idea, I'll start organizing it. The submission >>> deadline for the competition would be July 18, 2017 (the first anniversary >>> of my TechBeacon article, " How learning Smalltalk can make you a better >>> developer >>> <https://techbeacon.com/how-learning-smalltalk-can-make-you-better-developer> >>> "). >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/A-Logo-Proposal-for-Smalltalk-tp4945122p4945390.html >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >>> > >

May 3, 2017

Re: [Pharo-users] A Logo Proposal for Smalltalk

by Ben Coman

On Wed, May 3, 2017 at 6:49 PM, horrido <horrido.hobbies(a)gmail.com> wrote: > Esteban A. Maringolo wrote > > A decade+ ago I created the one attached, and I've seen used in some > > Smalltalk related sites. I still like it but it can be done better. > > *[|]* seems to be a popular choice. I got two votes for this at LinkedIn. > > It looks rather plain to me, though. It lacks sizzle. > > Maybe the best way to settle this is to have a Smalltalk logo competition. > People can submit their logo designs and a panel of judges can decide on > the > best one. The winning entry would be the "official" Smalltalk logo. > For the panel of judges, I would like representatives from each of the > following: > > o ESUG > o the Pharo project > o the Squeak project (Alan Kay?) > o Cincom > o Instantiations > o GemTalk > > I half like the idea of a Smalltalk logo, but logos are most effective when they are widely used. Once we have this "official" logo, how do you expect it to be used? Do you expect organisations to use it in their literature as part of their branding identity? Should it get equal weighting as their corporate identity? Will all these commercial entities feel the logo strengthens their position in solidarity, or dilutes their position. You know that some our community differentiate Pharo from Smalltalk. Also an important question to determine early on, how will copyright and trademark rights of the logo be controlled? cheers -ben Of course, my stylized hot air balloon would be Logo Candidate Entry #1. > > If you think this is a good idea, I'll start organizing it. The submission > deadline for the competition would be July 18, 2017 (the first anniversary > of my TechBeacon article, " How learning Smalltalk can make you a better > developer > <https://techbeacon.com/how-learning-smalltalk-can-make- > you-better-developer> > "). >

May 3, 2017