April 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] IDEA: I will record an Iceberg cast (an "Icecast" ; ) ) every tuesday

by Alexandre Bergel

Excellent!! Alexandre http://bergel.eu > Le 14 avr. 2018 Ã 09:17, Esteban Lorenzano <estebanlm(a)gmail.com> a Ã©crit : > > hi, > > The idea is to show a small example of something and to answer questions. > > First âIcecast" will be next Tuesday. > You can send your questions in the iceberg channel or in list. > > cheers, > Esteban > > ps: Is âevery tuesdayâ until I run out of things to show or time ;)

April 14, 2018

Re: [Pharo-users] Where do we go now ?

by Thierry Goubier

Le sam. 14 avr. 2018 10:46, Hilaire <hilaire(a)drgeo.eu> a Ã©crit : > Le 13/04/2018 Ã 19:49, Stephane Ducasse a Ã©crit : > > We know where we go (we have a roadmap) and this is always the same > > and we are getting there. Tell me one smalltalk that is bootstrapped. > I don't see we are there yet. At least from my humble point of view the > bootstrap still looks like WIP. > However, for pragmatic software deployments, working out of the minimal image is a nice improvement. The best of both world: full featured when needed, concise when needed. Thierry > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > > >

April 14, 2018

Re: [Pharo-users] Where do we go now ?

by Ben Coman

On 14 April 2018 at 01:52, Richard Sargent <richard.sargent@ gemtalksystems.com> wrote: > On Fri, Apr 13, 2018 at 1:11 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > >> Sometime Pharo frustrate me a lot, I felt it too in the message from >> Benoit, in the other hand its community is very kind and always helpful. So >> it is not about blaming people. >> >> In my opinion, there are too much things pushed at the same time in >> Pharo. You can't push too much things into the box, then when people >> complain about it to be overfull and bugged request them to fix it, I don't >> think it can work that way, at this scale of changes. In the other, this is >> not really what happen here, I very likely exaggerate this trait but you >> get the idea. >> >> For example, I developed DrGeo for several years on P3. Why sticking to >> P3? It gave me the opportunity to fine craft DrGeo to be stable and >> predictable in the way it behaves to its end users, and a lot of releases >> occurred. When I started to look at porting to newer image last June, I >> realized DrGeo will become unstable and oversized, so can of turning from >> A+ grade to a D- grade, just by the magic of porting it. My plan was to >> port it during the summer to get it ready end of August to deploy in local >> schools, it does not happen. And I can write it: it is s-u-p-e-r >> f-r-u-s-t-r-a-t-i-n-g. Is it normal when porting code? I don't know, I am a >> casual developer, but it makes developing well crafted and reliable Pharo >> application a bit expensive to my taste. To such a scale that I started to >> evaluate alternative to Pharo as the underneath system, idea I finally gave >> up after several weeks of evaluations. All in all I still have this felling >> Pharo is not developer friendly, I fell DrGeo is not secure there. See when >> porting to newer image, I end up using P7-32bits alpha on Linux because it >> was the most comfortable situation comparing to P5/P6/P6.1, is it not >> strange? >> >> In the other hand this struggle occurs at image change. Ok, may be it is >> a pattern specific to Smalltalk. Is it the case with commercial Smalltalk >> vendors? > > > Hi Hilaire, > > Thanks for articulating this. I've been mostly watching Pharo rather than > using it, so I haven't been affected by the changes between versions. With > respect to commercial products versus Pharo *at the present time*, I > think we have different driving forces shaping things. > > In my opinion, VA Smalltalk has been the one most strongly driven by the > importance of backward compatibility and ease of migration to a new > version. VisualWorks has been pretty good about providing a path forward > with minimal pain, although the more major version numbers difference, the > harder it is to transition. Likewise, GemStone/S has a strong emphasis on > keeping our customers' existing applications running with minimal changes. > > That being said, I have no doubt that the earliest versions of all these > products had substantial incompatibilities between versions. I am also > pretty sure there is a threshold beyond which the adoption of Pharo in > business applications will compel Pharo development to facilitate migration > to newer versions and to better maintain API compatibility. [And that may > be simply because, as more businesses rely on Pharo, they will be > financially supporting its development.] > You would expect this be a natural progression as more companies supporting such priorities join the consortium. The corollary is that its better the take greater leaps earlier when there is a greater percentage of Innovators and Early Adopters who are willing to ride some rough edges for the benefit they gain *now*. When the Majority arrive, such changes would be more disruptive to perception of Pharo i.e. more opinons, less care. cheers -ben > > A second consideration is the size of the product teams (measured in > full-time staffing). I think the commercial products had a much larger > staffing in their early days than Pharo has even now. And I think the > consequence of that is that the changes between v1 and v2 or between v2 and > v3 of the commercial products *may* have been comparable to the > differences between Pharo v(n) and v(n+3). > > > Richard > > >> >> Hilaire >> >> -- >> Dr. Geo >> http://drgeo.eu >> >> >> >> >

April 14, 2018

Re: [Pharo-users] Where do we go now ?

by Hilaire

Le 13/04/2018 Ã 19:49, Stephane Ducasse a Ã©critÂ : > We know where we go (we have a roadmap) and this is always the same > and we are getting there. Tell me one smalltalk that is bootstrapped. I don't see we are there yet. At least from my humble point of view the bootstrap still looks like WIP. Hilaire -- Dr. Geo http://drgeo.eu

April 14, 2018

Recover question at startup

by Hilaire

Hi, When I build DrGeo app against P7, then test it on a *different* computer used to build it, I have this dialog message at start up: "Its seems your last Pharo session existed without saving some code. Do you want to recover it?" As far as I understand it is related to Epicea, as I don't I need it in appication built, what is the way to properly unactivate it? Can it be uninstalled may be? Hilaire -- Dr. Geo http://drgeo.eu

April 14, 2018

Re: [Pharo-users] IDEA: I will record an Iceberg cast (an "Icecast" ; ) ) every tuesday

by Richard O'Keefe

You hero, sir. On 14 April 2018 at 19:17, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > hi, > > The idea is to show a small example of something and to answer questions. > > First âIcecast" will be next Tuesday. > You can send your questions in the iceberg channel or in list. > > cheers, > Esteban > > ps: Is âevery tuesdayâ until I run out of things to show or time ;) >

April 14, 2018

IDEA: I will record an Iceberg cast (an "Icecast" ; ) ) every tuesday

by Esteban Lorenzano

hi, The idea is to show a small example of something and to answer questions. First âIcecast" will be next Tuesday. You can send your questions in the iceberg channel or in list. cheers, Esteban ps: Is âevery tuesdayâ until I run out of things to show or time ;)

April 14, 2018

Re: [Pharo-users] QRCode - A thank you note

by Stephane Ducasse

Thanks Sven Yes QRCode is nice. Once I wanted to see if I could produce a pdf version for artefact and when I read the spec I stopped. And yes sometimes the atmosphere of this mailing-list is telling me to stay away from it. So thanks for your nice mail and energy. And thanks for your super cool libraries. Today we had a good laugh with Santiago because we will build a smart contracts corpus and use STON to save them (too easy ;P) Stef On Fri, Apr 13, 2018 at 8:47 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi, > > Given that the mailing lists are often used to ask questions when we get > in trouble, report bugs and other issues, conduct public discussion between > strong headed individuals, we quickly forget what a fantastic platform > Pharo is. > > Last month I implemented a rough MVP-style ticket sales platform that was > successfully used to sell and validate at the entrance, about 1000 digital, > online tickets for a relatively large 3000+ attendance event (a party). It > took only a couple of days to build and deploy, and it was a lot of fun - > it was even done in 'unstable' Pharo 7. > > Early on I decided to identify each individual ticket by a unique URL. For > easier presentation and scanning purposes, I encoded that URL in a QR code. > > Although I am grateful for the whole Pharo ecosystem (including Seaside), > we all build on top of other people's work, I was especially happy with > Jochen Rick's QRCode package (http://smalltalkhub.com/#!/~ > JochenRick/QRCode/). This is such a great piece of work ! > > It worked right out of the box in Pharo 7 (even though it is from > 2013/2014), was well designed, easy to figure out, was well documented, had > unit tests. I can't say anything bad about it, it is as close to perfect as > I have ever seen. So: thanks Jochen, you made my day ! > > Here is how a ticket generates its own QR code: > > T123Ticket>>#asQRCode > ^ self url asString asQRCode formWithQuietZone magnifyBy: 5 > > Just beautiful. > > It is also easy (for a non-graphics, non-UI person like me) to combine the > QR code with some text: > > T123Ticket >>#asQRCodeWithText > | form font | > form := Form extent: 535 @ 185 depth: 1. > font := LogicalFont familyName: 'Bitmap DejaVu Sans' pointSize: 14. > self asQRCode displayOn: form at: 0 @ 0. > form getCanvas > drawString: self url asString at: 180 @ 20 font: font color: Color > black; > drawString: self id36, ' - ', ticketId asString at: 180 @ 45 font: > font color: Color black; > drawString: (name ifNil: [ 'N.N' ]) at: 180 @ 90 font: font color: > Color black; > drawString: (email ifNil: [ '@' ]) at: 180 @ 115 font: font color: > Color black; > drawString: (phone ifNil: [ '+' ]) at: 180 @ 140 font: font color: > Color black. > ^ form > > Next we combine this with a nice template designed by a graphics artist: > > T123Ticket >>#asQRCodeWithTextInTemplate > | templateFile form | > templateFile := 'tickets123-template-{1}.jpg' format: { self event id }. > form := PluginBasedJPEGReadWriter formFromFileNamed: templateFile. > self asQRCodeWithText displayOn: form at: 20@540. > ^ form > > And finally, the ticket form is encoded as a JPEG (to be mailed and so on): > > T123Ticket >>#asJPEGBytes > ^ ByteArray streamContents: [ :out | > PluginBasedJPEGReadWriter putForm: self asQRCodeWithTextInTemplate > onStream: out ] > > > I also found GT Inspector very handy (again) in doing back end work > (managing payments and other administration), especially the ability to use > Spotter on a collection open in an inspector. > > Anyway, I know many of you have similar happy experiences, I just wanted > to share (one of) mine. > > Thanks Jochen, thanks everyone. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > >

April 13, 2018

QRCode - A thank you note

by Sven Van Caekenberghe

Hi, Given that the mailing lists are often used to ask questions when we get in trouble, report bugs and other issues, conduct public discussion between strong headed individuals, we quickly forget what a fantastic platform Pharo is. Last month I implemented a rough MVP-style ticket sales platform that was successfully used to sell and validate at the entrance, about 1000 digital, online tickets for a relatively large 3000+ attendance event (a party). It took only a couple of days to build and deploy, and it was a lot of fun - it was even done in 'unstable' Pharo 7. Early on I decided to identify each individual ticket by a unique URL. For easier presentation and scanning purposes, I encoded that URL in a QR code. Although I am grateful for the whole Pharo ecosystem (including Seaside), we all build on top of other people's work, I was especially happy with Jochen Rick's QRCode package (http://smalltalkhub.com/#!/~JochenRick/QRCode/) This is such a great piece of work ! It worked right out of the box in Pharo 7 (even though it is from 2013/2014), was well designed, easy to figure out, was well documented, had unit tests. I can't say anything bad about it, it is as close to perfect as I have ever seen. So: thanks Jochen, you made my day ! Here is how a ticket generates its own QR code: T123Ticket>>#asQRCode ^ self url asString asQRCode formWithQuietZone magnifyBy: 5 Just beautiful. It is also easy (for a non-graphics, non-UI person like me) to combine the QR code with some text: T123Ticket >>#asQRCodeWithText | form font | form := Form extent: 535 @ 185 depth: 1. font := LogicalFont familyName: 'Bitmap DejaVu Sans' pointSize: 14. self asQRCode displayOn: form at: 0 @ 0. form getCanvas drawString: self url asString at: 180 @ 20 font: font color: Color black; drawString: self id36, ' - ', ticketId asString at: 180 @ 45 font: font color: Color black; drawString: (name ifNil: [ 'N.N' ]) at: 180 @ 90 font: font color: Color black; drawString: (email ifNil: [ '@' ]) at: 180 @ 115 font: font color: Color black; drawString: (phone ifNil: [ '+' ]) at: 180 @ 140 font: font color: Color black. ^ form Next we combine this with a nice template designed by a graphics artist: T123Ticket >>#asQRCodeWithTextInTemplate | templateFile form | templateFile := 'tickets123-template-{1}.jpg' format: { self event id }. form := PluginBasedJPEGReadWriter formFromFileNamed: templateFile. self asQRCodeWithText displayOn: form at: 20@540. ^ form And finally, the ticket form is encoded as a JPEG (to be mailed and so on): T123Ticket >>#asJPEGBytes ^ ByteArray streamContents: [ :out | PluginBasedJPEGReadWriter putForm: self asQRCodeWithTextInTemplate onStream: out ] I also found GT Inspector very handy (again) in doing back end work (managing payments and other administration), especially the ability to use Spotter on a collection open in an inspector. Anyway, I know many of you have similar happy experiences, I just wanted to share (one of) mine. Thanks Jochen, thanks everyone. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

April 13, 2018

[OT] Reminder about quoting/top-posting

by Esteban A. Maringolo

Hi, Please apologize the digression, but these days there were a lot of interesting threads with LOTS of replies from different members. Can I ask for more trimming of the quoted text and/or emails replied to? The follow up of some replies was hard because they were nested deep into a chain of previous quotes, or in the case of top-posters, they keep the replied emails accumulating in the bottom, causing a scroll down to find nothing else was there. Thanks! -- Esteban A. Maringolo

April 13, 2018