[Pharo-dev] R: [ANN] Material Design For Seaside V1.0.0

Great job! Thank you very much. Lorenzo Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di J.F. Rick Inviato: venerdì 23 settembre 2016 17.14 A: Pharo Development List Oggetto: Re: [Pharo-dev] [ANN] Material Design For Seaside V1.0.0 Lovely. Something's not quite

[Pharo-dev] R: The Smalltalk Revolution

Great job Richard! Lorenzo -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di horrido Inviato: giovedì 8 gennaio 2015 12:51 A: pharo-dev@lists.pharo.org Oggetto: [Pharo-dev] The Smalltalk Revolution https://medium.com/@richardeng/the-smalltalk-rev

[Pharo-dev] R: The Smalltalk Revolution

Hi people, I share 100% Phill's observations. Pharo is the best technical environment I have ever seen, but it is not "friendly" for those who are forced to use it for "stupid" application, where it is not so easy to find tools for everyday works. IMHO this is the reason for which Smalltalk loosed

[Pharo-dev] R: from 2009's The "death" of Smalltalk to 2014's But Really, You Should Learn Smalltalk

Hi, instead of using the trivial 2 + 2 as ST example, for many years I have found more impressive: 5 factorial printString size and then to show factorial method, that is very easy to understand. IMHO it is ST’s essence of innovation and power. Lorenzo Da: Pharo-dev [

[Pharo-dev] R: R: from 2009's The "death" of Smalltalk to 2014's But Really, You Should Learn Smalltalk

ev-boun...@lists.pharo.org] Per conto di Sven Van Caekenberghe Inviato: lunedì 12 gennaio 2015 09:48 A: Pharo Development List Oggetto: Re: [Pharo-dev] R: from 2009's The "death" of Smalltalk to 2014's But Really, You Should Learn Smalltalk > On 12 Jan 2015, at 09:15, Lorenz

[Pharo-dev] R: R: R: from 2009's The "death" of Smalltalk to 2014's But Really, You Should Learn Smalltalk

: R: from 2009's The "death" of Smalltalk to 2014's But Really, You Should Learn Smalltalk > On 12 Jan 2015, at 10:55, Lorenzo Schiavina wrote: > > Hi Sven, > > I find your observations absolutely reasonable; anyway, my point is to > show the difference b

[Pharo-dev] R: Finish one thing today

+1 Lorenzo -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Sven Van Caekenberghe Inviato: mercoledì 14 gennaio 2015 16:16 A: Pharo Development List Oggetto: Re: [Pharo-dev] Finish one thing today > On 14 Jan 2015, at 15:12, Pablo Estefo wrote

[Pharo-dev] R: InfoWorld on Redline Smalltalk

+1 Lorenzo Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Sebastian Sastre Inviato: giovedì 15 gennaio 2015 12:56 A: Pharo Development List Oggetto: Re: [Pharo-dev] InfoWorld on Redline Smalltalk On Jan 14, 2015, at 9:44 PM, Esteban A. Maringolo wrote: Sh

[Pharo-dev] R: About method comments

Great Stef! Lorenzo -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Stephane Ducasse Inviato: venerdì 9 febbraio 2018 12:04 A: Pharo Development List Oggetto: [Pharo-dev] About method comments Hi guys >From now on I will VETO the introduction

[Pharo-dev] R: ANSICompatibility package

Hi Ben, I am available if you want to include VisualSmalltalk into ANSICompatibility package. I have both full documentation and lot of applications. Lorenzo -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Ben Coman Inviato: venerdì 18 settemb

[Pharo-dev] R: dear contributor

Hi Steff, I have not understood what I have to do. Ciao Lorenzo -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di stepharo Inviato: giovedì 22 ottobre 2015 17:18 A: Pharo Development List Oggetto: [Pharo-dev] dear contributor please sign the li

[Pharo-dev] R: A plea for responsive coding

+1 Lorenzo Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Dimitris Chloupis Inviato: domenica 22 novembre 2015 14:56 A: Pharo Development List Oggetto: Re: [Pharo-dev] A plea for responsive coding because making something work for me comes way before making somet

[Pharo-dev] R: Java Future

Perfect Dimitris! Lorenzo Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Dimitris Chloupis Inviato: mercoledì 25 novembre 2015 11:29 A: Pharo Development List Oggetto: Re: [Pharo-dev] Java Future Clickbait ! ClickBAIT ! Let me remind you that bloggers have b

[Pharo-dev] R: Back to Europe

Hi Steff, Great work with TinyBlogTutorial; have my compliments! May I translate it into Italian for my students? Happy new year! Lorenzo Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di stepharo Inviato: domenica 27 dicembre 2015 11:23 A: Pharo Development Lis

[Pharo-dev] R: a Pharo talk from a ruby conference

+1 Lorenzo Schiavina -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di kmo Inviato: giovedì 15 maggio 2014 20:03 A: pharo-dev@lists.pharo.org Oggetto: Re: [Pharo-dev] a Pharo talk from a ruby conference Looking at the new pharo website (it’s

[Pharo-dev] R: full version of a Lint Chapter for Entreprise Pharo forthcoming book :)

Hi Stef, I cannot download the paper; can you check if there is any problem? Grazie -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Stéphane Ducasse Inviato: domenica 6 ottobre 2013 09:41 A: Pharo Development List; Any question about pharo is w

[Pharo-dev] R: R: full version of a Lint Chapter for Entreprise Pharo forthcoming book :)

version of a Lint Chapter for Entreprise Pharo forthcoming book :) Mind the newline in the middle of the link posted by stef: https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ws/Lint/Lin t.pier.pdf On 2013-10-07, at 16:30, "Lorenzo Schiavina" wrote: > Hi Stef,

[Pharo-dev] R: Invoice management

Hi Dario, maybe you remember I have developed in VSE ST a full package (MIDA) for company management (bookkeeping, stock management, invoicing...). I am sure you can find what you are looking for and I believe it will not be very hard to port what you need to Pharo. Lorenzo -Messaggio origin

[Pharo-dev] Error in loading libreries

Hi, every time I try to load a package from Monticello, I receive the message: ERROR: MCHttpRepository expected. Can anybody tell me why and suggest me a workeround? Many thanks and season's greetings Lorenzo

[Pharo-dev] Lost changes recovery

Hi, I tried to recover lost changes but I failed. I used the item in tools menu and I followed the expected actions, but I was not able to find the lost changes in my image; where do they go? Is there any place where I can find details about the expected results and understand what I missed? Than

[Pharo-dev] R: poolDictionaries removal breaks my projects

Just the same in all the world! Lorenzo Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Sebastian Sastre Inviato: sabato 1 febbraio 2014 13:33 A: Pharo Development List Oggetto: Re: [Pharo-dev] poolDictionaries removal breaks my projects How many lectures did y

[Pharo-dev] R: Hello

Benissimo! Lorenzo -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Lorenzo Baracchi Inviato: mercoledì 5 febbraio 2014 16:43 A: pharo-dev@lists.pharo.org Oggetto: [Pharo-dev] Hello Hello, I write this message only to introduce myself. I am Lore

[Pharo-dev] R: Why Smalltalk is not popular?

+1 -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di askoh Inviato: mercoledì 12 febbraio 2014 14:55 A: pharo-dev@lists.pharo.org Oggetto: [Pharo-dev] Why Smalltalk is not popular? The recent arguments in Smalltalk made me have an Eureka moment on

[Pharo-dev] R: Morphic UI designer

Yes, I think could be very important to have it in Pharo. Some time ago I had a glance to it: it could be better, but it is not bad. Lorenzo Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di jannik laval Inviato: venerdì 21 febbraio 2014 12:02 A: Pharo Development L

[Pharo-dev] R: Morphic UI designer

Hi Steff, may I ask why Phobos is not considered as a good candidate as a basis for an interface designer? I have experience with PARTS (which is the best application in the field I have ever seen in ST environment) and I believe that it could be used as a basis for tools of this kind. If any

[Pharo-dev] R: James Robertson

+1 Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Sebastian Sastre Inviato: sabato 19 aprile 2014 17:07 A: Pharo Development List Oggetto: Re: [Pharo-dev] James Robertson So young, we are so few, very sad. He pioneered making smalltalk known to the world using scr

[Pharo-dev] R: [Screencast] request for review

Hi Laurent, if you need a help in Italian, I am available. Lorenzo -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Laurent Laffont Inviato: giovedì 1 maggio 2014 23:21 A: pharo-dev@lists.pharo.org Oggetto: [Pharo-dev] [Screencast] request for r

[Pharo-dev] R: Pharo VM Release - v9.0.21

Grazie Paolo! Da: teso...@gmail.com [mailto:teso...@gmail.com] Inviato: lunedì 12 dicembre 2022 14:30 A: Any question about pharo is welcome ; Pharo-dev Oggetto: [Pharo-dev] Pharo VM Release - v9.0.21 Hello, I have released a new version of the Pharo VM for Pharo 9, Pharo 10 and Phar

[Pharo-dev] R: crm in pharo?

Hi Tudor, I have developed a CRM application not in Pharo but using VSE; if you are interested, I will be happy to help porting it in Pharo. Let me know. Lorenzo Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Tudor Girba Inviato: domenica 21 giugno 2015 15:02 A

[Pharo-dev] R: R: crm in pharo?

t List Oggetto: Re: [Pharo-dev] R: crm in pharo? Indeed, I would be interested in the domain model. Cheers, Doru On Mon, Jun 22, 2015 at 7:41 AM, Lorenzo Schiavina wrote: Hi Tudor, I have developed a CRM application not in Pharo but using VSE; if you are interested, I will be hap

[Pharo-dev] R: Abbreviations

+1 -Messaggio originale- Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di Max Leske Inviato: giovedì 4 luglio 2013 12:58 A: Pharo Development List Oggetto: Re: [Pharo-dev] Abbreviations I agree wholeheartedly! I still believe in (mostly) self documenting code and that