October 2014 - Pharo-dev - lists.pharo.org

.source file

by Hilaire

For information, a iStoa user reported to me this problem, related to a Pharo regression I already discussed about here https://bugs.launchpad.net/istoa/+bug/1384649 I see this related bug report: https://pharo.fogbugz.com/f/cases/10464/Always-warn-when-sources-or-changes… So what is the plan regarding source code, will we be forced to ship it. It is untrue disk space is cheap, especially for desktop or tablet application. Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Oct. 23, 2014

Re: [Pharo-dev] Microframeworks was: Re: Thank you so much for Pharo 3.0

by Eliot Miranda

Hi Thierry, On Oct 23, 2014, at 12:36 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 23/10/2014 09:18, phil(a)highoctane.be a Ã©crit : >> >> On Thu, Oct 23, 2014 at 8:42 AM, Thierry Goubier >> <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> >> How long is long? > > 900 nodes in the AST seems to be the limit for the type of method SmaCC generates (cascading ifTrue:ifFalse:). > > Other limits exist (number of literals, for example). Unless you generate automatically some code, it's hard to hit them. Once you generate automatically, it's easy to hit them :P Spur and Sista together lift these limits. Spur provides 64k literals per method and Sista uses a bytecode set with effectively unlimited jumps. We could possibly deploy the Sista bytecode set before the Sista optimizer. Would you be interested in being a guinea pig? Eliot (phone) > >> Now, the point is to see all that as a stream, cut methods at >> appropriate places and compile code under a WAComponent subclass. > > Yes. But then you need some kind of syntax to mark the start of a method. Change sets and dolphin packages use !! markers. > >> I don't know about SmaCC but I think I can do something with PetitParser >> and Smalltalk compile: > > It's all done with RBParser. Since you're parsing Smalltalk, it's easier to do it that way (and probably a bit faster). And you're also playing with the AST, so you want to fall back to a well defined API for that AST (and visitors, and the like). > > Extending RBParser with a scheme to parse multi-methods files could be convenient. > > Unless you fall back on a variant of a changeset. > > Thierry >

Oct. 23, 2014

[pharo-project/pharo-core] 8a6b13: 40321

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 8a6b139b4a1e6655d56b9aee1d2eb0651bda943a https://github.com/pharo-project/pharo-core/commit/8a6b139b4a1e6655d56b9aee… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-23 (Thu, 23 Oct 2014) Changed paths: M NautilusCommon.package/AbstractKeyPressedPlugin.class/instance/registration/registerTo_.st M NautilusCommon.package/AbstractPackageSelectedPlugin.class/instance/registration/registerTo_.st M NautilusCommon.package/AbstractTextChangedPlugin.class/instance/registration/registerTo_.st M NautilusCommon.package/AlexPlugin.class/instance/registration/registerTo_.st M NautilusCommon.package/MondrianPlugin.class/instance/registration/registerTo_.st M NautilusCommon.package/NautilusBreadcrumbsPlugin.class/instance/registration/registerTo_.st M NautilusCommon.package/URLPlugin.class/instance/registration/registerTo_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script321.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40321.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Tool-Profilers.package/TimeProfiler.class/class/opening/spyFor_.st Log Message: ----------- 40321 14068 Should add spyFor: to systemProfiler https://pharo.fogbugz.com/f/cases/14068 14296 Replace Announcer>>#on:send:to:s senders in NautilusCommon https://pharo.fogbugz.com/f/cases/14296 http://files.pharo.org/image/40/40321.zip

Oct. 23, 2014

[pharo-project/pharo-core]

by GitHub

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

Oct. 23, 2014

Time Series in Smalltalk

by Blondeau Vincent

Hi ! I am looking for a time series library available for Pharo. Serge Stinckwich asked the same thing a year ago (http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-February/07…) and I would know whether any improvement has been made since? Thanks Cheers, Vincent BLONDEAU ________________________________ Ce message et les pi?ces jointes sont confidentiels et r?serv?s ? l'usage exclusif de ses destinataires. Il peut ?galement ?tre prot?g? par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir imm?diatement l'exp?diteur et de le d?truire. L'int?grit? du message ne pouvant ?tre assur?e sur Internet, la responsabilit? de Worldline ne pourra ?tre recherch?e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'exp?diteur ne donne aucune garantie ? cet ?gard et sa responsabilit? ne saurait ?tre recherch?e pour tout dommage r?sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Oct. 23, 2014

Re: [Pharo-dev] Voyage - weird messages in the build (PR*)

by phil＠highoctane.be

On Thu, Oct 23, 2014 at 9:55 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Oct 22, 2014 at 8:40 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > > There are strange things showing up during the load, like PRWikiWriter ?! > > > PRWikiWriter is the old name of PRPillarWriter IIRC. So, I guess that > you are loading a recent version of Pillar (or Pier) but still has > code that references the old one. > I do not load any of these, so, I'll check what's going on behind the scenes. Phil > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

Oct. 23, 2014

Re: [Pharo-dev] Microframeworks was: Re: Thank you so much for Pharo 3.0

by phil＠highoctane.be

On Thu, Oct 23, 2014 at 9:36 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > Le 23/10/2014 09:18, phil(a)highoctane.be a Ã©crit : > >> >> On Thu, Oct 23, 2014 at 8:42 AM, Thierry Goubier >> <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: >> >> >> How long is long? >> > > 900 nodes in the AST seems to be the limit for the type of method SmaCC > generates (cascading ifTrue:ifFalse:). > > Other limits exist (number of literals, for example). Unless you generate > automatically some code, it's hard to hit them. Once you generate > automatically, it's easy to hit them :P > > Now, the point is to see all that as a stream, cut methods at >> appropriate places and compile code under a WAComponent subclass. >> > > Yes. But then you need some kind of syntax to mark the start of a method. > Change sets and dolphin packages use !! markers. > > I don't know about SmaCC but I think I can do something with PetitParser >> and Smalltalk compile: >> > > It's all done with RBParser. Since you're parsing Smalltalk, it's easier > to do it that way (and probably a bit faster). And you're also playing with > the AST, so you want to fall back to a well defined API for that AST (and > visitors, and the like). > > Extending RBParser with a scheme to parse multi-methods files could be > convenient. > > Unless you fall back on a variant of a changeset. Thanks for the pointers, I'll look into that. In the meantime, I put together a starting point (using your merge driver as an inspiration ;-) ). https://github.com/philippeback/Bubble clone it, make ./bubble --app blah.bubble (if one is on centos6.5, make centos) Check the makefile, I made everything load from filetree and rename the image with another name than a bland "Pharo.image" Phil > > Thierry > >

Oct. 23, 2014

Re: [Pharo-dev] Voyage - weird messages in the build (PR*)

by Damien Cassou

On Wed, Oct 22, 2014 at 8:40 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > There are strange things showing up during the load, like PRWikiWriter ?! PRWikiWriter is the old name of PRPillarWriter IIRC. So, I guess that you are loading a recent version of Pillar (or Pier) but still has code that references the old one. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 23, 2014

Re: [Pharo-dev] Microframeworks was: Re: Thank you so much for Pharo 3.0

by Thierry Goubier

Le 23/10/2014 09:18, phil(a)highoctane.be a Ã©crit : > > On Thu, Oct 23, 2014 at 8:42 AM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > > How long is long? 900 nodes in the AST seems to be the limit for the type of method SmaCC generates (cascading ifTrue:ifFalse:). Other limits exist (number of literals, for example). Unless you generate automatically some code, it's hard to hit them. Once you generate automatically, it's easy to hit them :P > Now, the point is to see all that as a stream, cut methods at > appropriate places and compile code under a WAComponent subclass. Yes. But then you need some kind of syntax to mark the start of a method. Change sets and dolphin packages use !! markers. > I don't know about SmaCC but I think I can do something with PetitParser > and Smalltalk compile: It's all done with RBParser. Since you're parsing Smalltalk, it's easier to do it that way (and probably a bit faster). And you're also playing with the AST, so you want to fall back to a well defined API for that AST (and visitors, and the like). Extending RBParser with a scheme to parse multi-methods files could be convenient. Unless you fall back on a variant of a changeset. Thierry

Oct. 23, 2014

Re: [Pharo-dev] Thank you so much for Pharo 3.0

by kilon alios

Fortunately my experience with people I introduced in pharo has been a lot more positive than your, they were facinated by what Pharo offers and find it very useful, productive and fun environment. Actually one person hated it but he was a big troll so I dont count him in. But none of the people I introduced to Pharo ended keep using it, mainly because they were too tied into other platforms and languages and cant blame them. It took me 1 year to switch from python and I had to redefine the way I was coding and thinking about code. Even though Stef keeps stressing that Pharo does not have the resources of big companies and of course he is correct on other hand we see a clear and steady improvement, I think Pharo is on the right path and will correct many of the mistakes of Smalltalk and eventually bring much more people in. The future is certainly exciting and I am glad I have joined this ride :) Phareos certainly makes my dreams about coding a reality. Thanks to all pharoers for giving us such amazing functionality and working hard and thinking outside the box. On Thu, Oct 23, 2014 at 8:40 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Mariano, > > It is good to hear from you, and it is even better to hear such nice > words. Thanks you ! > > I think that in general, in our day to day struggles, people underestimate > just how good Pharo is and how useful it is to do real work in the real > world, in other words, to be successful. > > Do we already have your story as a 'success story' for the website ? > > Sven > > > On 23 Oct 2014, at 03:15, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > Hi guys, > > > > I just wanted to share my happiness with you. I joined a team 2 years > ago almost to develop a Seaside 3.0 app, using and old Magritte version, > and Pharo 1.4. As soon as I started, I created a ConfigurationOfMyApp, and > migrated to Pharo 2.0. > > > > That worked fine for almost 2 years. Since several weeks/months, I > wanted to update to new Seaside versions and Pharo. Of course, you never > have time, there are always other problems to fix first, etc...But 10 days > ago, I stopped everything, and I migrated to Seaside 3.1.3, latest > Magritte, latest Bootstrap (very very cool project too...we are using it > everywhere), latest everything...and... of course...Pharo 3.0!!! > Also..the "port" was almost nothing...everything almost worked out of the > box. Thanks to contributors maintaining great softwares like Metacello and > all existing configurations. > > > > Btw...I am also deploying my app in GemStone since almost an year, and > this also is being good. Gemstone people also have a great support via > mailing list which I very much appreciate. > > > > I played with Pharo 3.0 when it was released and some time also before > that. But not that much. Now..I am using the very same image since at least > 10 days. Working full time. All my projects are working great. I cannot > believe so good it feels developing in Pharo 3.0. I am using the great Dark > Theme from Esteban. Everything is super fast, super nice, super stable. And > with my 2.0 images..they always grew too much (up to 500MB), that > everything started to be very very slow. I needed to start again with a > fresh image, etc. This 3.0 image has almost the same size as I started and > continues to be super fast. > > > > So...I cannot repeat myself how good Pharo 3.0 feels. I should have > migrated long ago. Thanks all the contributors and developers for such a > great and professional product. > > > > Best, > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > >

Oct. 23, 2014