December 2015 - Pharo-users

Re: [Pharo-users] Dolphin Smalltalk open-sourced...

by SaÅ¡a JaniÅ¡ka

On Uto, 2015-12-29 at 12:30 +0000, Dimitris Chloupis wrote: > Standalone executables its not a big deal, you can rename the pharo > executable to anything you want and heavily customise your image > already with pharo. Standalone apps are a reality since before pharo > was created , from squeak days. What about GUI builders for the desktop apps? Someone on #pharo mentioned that Pharo is way behind Dolphin in this regard? Sincerely, Gour -- Those who are on this path are resolute in purpose, and their aim is one. O beloved child of the Kurus, the intelligence of those who are irresolute is many-branched.

Dec. 29, 2015

Re: [Pharo-users] Pharo 5: Bug in removing key combinations

by Johan Fabry

Thanks Nicolai for having a look! I added a bug report and notified you since you seem to be knowledgeable of the key shortcut system. In any case, URL to the bug report is https://pharo.fogbugz.com/f/cases/17304/Morph-removeKeyCombination-removes-… > On Dec 29, 2015, at 09:51, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2015-12-28 19:07 GMT+01:00 Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>>: > Hi all, > > Miguel and I found a bug in removing key combinations on a morph. Now they are global, while in Pharo 4 this was not the case. > > I was able to reproduce this on Pharo 4 as well, I think the main difference is that Pharo 5 uses Rubric for "Workspace/Playground" AND the Browser. > And in Pharo 4 these Tools use different Morphs. > > > Consider the following code: > > | morph | > morph := RubScrolledTextMorph new. > > (morph textArea) > removeKeyCombination: $s command; > removeKeyCombination: $s control; > on: $s command do: [morph flash ]; > on: $s control do: [morph flash ]. > > morph openInWorld. > > In the morph, cmd-s will cause a flash, as expected. However in other windows (or browsers and playgrounds least) the original shortcut is lost, only a s character is added to the text field. > > For me, the "morph flash" wasn't working on the RubRricTextMorph, unitil I opened a Transcript and enabled KeyLog setDebug. Only after this the morph was actually flashing (or the flashing wasn't visible?). > > > I did not see it on fogbugz so I would like to announce it here before I open a case, in case (heh) I missed it. So the question: is this a known bug? > > No, I think this bug is not yet reported. > > > > ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Dec. 29, 2015

Re: [Pharo-users] Pharo 5: Bug in removing key combinations

by Nicolai Hess

2015-12-28 19:07 GMT+01:00 Johan Fabry <jfabry(a)dcc.uchile.cl>: > Hi all, > > Miguel and I found a bug in removing key combinations on a morph. Now they > are global, while in Pharo 4 this was not the case. I was able to reproduce this on Pharo 4 as well, I think the main difference is that Pharo 5 uses Rubric for "Workspace/Playground" AND the Browser. And in Pharo 4 these Tools use different Morphs. > Consider the following code: > > | morph | > morph := RubScrolledTextMorph new. > > (morph textArea) > removeKeyCombination: $s command; > removeKeyCombination: $s control; > on: $s command do: [morph flash ]; > on: $s control do: [morph flash ]. > > morph openInWorld. > > In the morph, cmd-s will cause a flash, as expected. However in other > windows (or browsers and playgrounds least) the original shortcut is lost, > only a s character is added to the text field. > For me, the "morph flash" wasn't working on the RubRricTextMorph, unitil I opened a Transcript and enabled KeyLog setDebug. Only after this the morph was actually flashing (or the flashing wasn't visible?). > > I did not see it on fogbugz so I would like to announce it here before I > open a case, in case (heh) I missed it. So the question: is this a known > bug? > No, I think this bug is not yet reported. > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University > of Chile > > >

Dec. 29, 2015

Re: [Pharo-users] Dolphin Smalltalk open-sourced...

by Dimitris Chloupis

wow nice, thats more than welcomed. I probably should have seen that coming when they posted about making dolphin available to macos through wineskin, they are definetly interested into porting to other platforms. Obviously it will have some impact, maybe we can borrow some code from them like interfacing with DLLs which is Estabans area of interest , and generally to bring better support for windows. Its not a threat to Pharo itself because we are mostly MacOS and Linux developers and we support these platforms quite well. Standalone executables its not a big deal, you can rename the pharo executable to anything you want and heavily customise your image already with pharo. Standalone apps are a reality since before pharo was created , from squeak days. Personally I think taking some code for native support for the windows platforms, like DLLs, some window specific libraries etc would be nice. Generally I think both projects will continue to co exist happily and helping each other as Pharo hapily coexists with Squeak and Cuis. We are one big happy that is about to get a bit bigger. So Thank you Object Arts!!!! On Tue, Dec 29, 2015 at 1:58 PM SaÅ¡a JaniÅ¡ka <gour(a)atmarama.com> wrote: > ...with MIT license, so I wonder if that will have some impact on > further development of Pharo? > > Iirc, Dolphin can produce stand-alone Windows executable, but maybe > something else can be utilized as well? > > Here is the link with: http://object-arts.com/gettingstarted.html > > Sincerely, > Gour > > -- > The humble sages, by virtue of true knowledge, see with equal > vision a learned and gentle brÄhmana, a cow, an elephant, a dog > and a dog-eater. > > > > > >

Dec. 29, 2015

Re: [Pharo-users] why Pillar

by Ferlicot D. Cyril

Le 29/12/2015 13:18, Offray Vladimir Luna CÃ¡rdenas a Ã©crit : > Hi, > > > If you're on Mac/Linux. Windows is another story. > Hi, since Pillar 1.0.0 the only difference is that Pillar doesn't generate a Windows script to compile the .tex into pdf. Else Pillar should works on Windows. > Cheers, > > Offray > > > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Dec. 29, 2015

Re: [Pharo-users] Dolphin Smalltalk open-sourced...

by Serge Stinckwich

I dunno if they will be any impact on Pharo, because having a software open-source is great, but you also need a benevolent dictator and a community to give a direction ;-) If the licence is MIT, this is great, because Pharo could reuse some parts of Dolphin Smalltalk without any problems. Regards, On Tue, Dec 29, 2015 at 12:57 PM, SaÅ¡a JaniÅ¡ka <gour(a)atmarama.com> wrote: > ...with MIT license, so I wonder if that will have some impact on > further development of Pharo? > > Iirc, Dolphin can produce stand-alone Windows executable, but maybe > something else can be utilized as well? > > Here is the link with: http://object-arts.com/gettingstarted.html > > Sincerely, > Gour > > -- > The humble sages, by virtue of true knowledge, see with equal > vision a learned and gentle brÄhmana, a cow, an elephant, a dog > and a dog-eater. > > > > > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Dec. 29, 2015

Re: [Pharo-users] why Pillar

by Offray Vladimir Luna CÃ¡rdenas

Hi, On 29/12/15 06:01, Dimitris Chloupis wrote: > > I think in case of Pillar makes sense to create something in Pharo > because the existing solutions are not that powerful anyway with the > notable exception of Latex which is something that Pillar can use and > inline anyway. Personally I love Pillar, the syntax, installation and > the general usage is super simple. > If you're on Mac/Linux. Windows is another story. > I also think that having a documentation frameworks instead of using > one from another language is a must have because documentation is > super important and you should not be limited by what people do in > other languages and its not that complex to implement like for example > version control. > Agreed. > Of course Pillar is somewhere in between because on one hand yes its a > Pharo implementation but on the other it depends on Latex for the > creation of pdfs, so I think overall its a very well designed > frameworks with very good syntax, small learning curve and enormous > abilities because of the latex integration. > Same as Pandoc. > So to answer your question > > Why Pillar ? > > Because its awesome :) > Same as pandoc. Cheers, Offray

Dec. 29, 2015

Dolphin Smalltalk open-sourced...

by SaÅ¡a JaniÅ¡ka

...with MIT license, so I wonder if that will have some impact on further development of Pharo? Iirc, Dolphin can produce stand-alone Windows executable, but maybe something else can be utilized as well? Here is the link with:Â http://object-arts.com/gettingstarted.html Sincerely, Gour -- The humble sages, by virtue of true knowledge, see with equal vision a learned and gentle brÄhmana, a cow, an elephant, a dog and a dog-eater.

Dec. 29, 2015

Re: [Pharo-users] what is Pharo's mission statement? (was Re: Transcendental #new (was Re: why Pillar))

by Robert Withers

Thanks for this information, Ben. I have my protocol stack using sockets and am using Fuel, so a few more adjustments at my session layer and then my presentation layer and I can start passing packages around between minimal images, loading and unloading them, serialized as PassByConstruction, rather than PassByProxy so that code can be locally constituted. I would then work on building a distributed registry and package manager and take a close look at distributed logging. best, robert On 12/29/2015 05:55 AM, Ben Coman wrote: > On Tue, Dec 29, 2015 at 6:05 AM, Robert Withers > <robert.w.withers(a)gmail.com> wrote: >> >> On 12/28/2015 01:42 PM, Marcus Denker wrote: >>>> On 28 Dec 2015, at 19:33, Robert Withers <robert.w.withers(a)gmail.com> >>>> wrote: >>>> >>>> >>>> >>>> On 12/28/2015 01:18 PM, Sven Van Caekenberghe wrote: >>>>>> On 28 Dec 2015, at 19:11, Robert Withers <robert.w.withers(a)gmail.com> >>>>>> wrote: >>>>>> >>>>>> I got you, stephano. I do not wish to be banned. >>>>>> >>>>>> Leaving aside established spiritual traditions, but picking out the >>>>>> pattern for exploration, what would you say the meta-meme of Pharo is? In >>>>>> other words, what is the mission statement? This would help me grasp the >>>>>> motivations of the community and is not a meaningless exercise for the >>>>>> community, from a leadership development perspective.. >>>>> http://pharo.org/about. >>>>> https://gforge.inria.fr/frs/download.php/30434/PharoVision.pdf >>>> This is awesome, thank you for posting it. It mentions a roadmap. Is >>>> there such a page? >>> We are working on an updated roadmap. >> >> Thanks for setting the right expectations, please enjoy the holidays. I will >> enjoy it when it is properly aged. >> >>> We will update it to form a roadmap soonâ¦ (I wanted to have it done >>> already, but was busy >>> with other things end of the yearâ¦) >> >> I understand and the results of your efforts are plain to see. Pharo-5 runs >> my work well. I have been reading your section 4 in the Vision document with >> great interest. Particularly, I find I like 4.2, 4.3, 4.5, 4.6, 4.7, 4.8, >> 4.11 and 4.12. I would like to try my work on top of ocean. > 4.2 FileSystem was integrated integrated into Pharo 2 > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=f… > > 4.3 Announcement were introduced in Pharo 1.3 > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=a… > > Ephemeron VM support available soon in Spur VM (?). Probably work > more needed image side (?) > > 4.5 Bootstrap Core - Work In Progress > https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-3-Minimal/Full > > 4.6 Fully parametrized compiler tool chain > I'm not clear on what "fully parameterized" encompasses, but the old > Compiler was replaced by new OpalCompiler in Pharo 3 - I guess to > satisfy this. > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=o… > > 4.7 Packages as real objects > Begun in Pharo 2 with introduction of RPackage. Completed in Pharo 4 > with removal of PackageInfo. > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=p… > > 4.8 Package Meta-Data > Not sure what this entails or status. Package Manifest introduced in Pharo 2 > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=m… > > 4.11 New Network Layer - I don't know. > > 4.12 Serializers - Fuel is the default serializer since Pharo 2. I > don't know the rest of the scope for this point. > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=f… > > cheers -ben > -- Robert . .. ... ^,^

Dec. 29, 2015

Re: [Pharo-users] what is Pharo's mission statement? (was Re: Transcendental #new (was Re: why Pillar))

by stepharo

ocean. > 4.2 FileSystem was integrated integrated into Pharo 2 > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=f… > > 4.3 Announcement were introduced in Pharo 1.3 > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=a… > > Ephemeron VM support available soon in Spur VM (?). Probably work > more needed image side (?) > > 4.5 Bootstrap Core - Work In Progress > https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-3-Minimal/Full > > 4.6 Fully parametrized compiler tool chain > I'm not clear on what "fully parameterized" encompasses, but the old > Compiler was replaced by new OpalCompiler in Pharo 3 - I guess to > satisfy this. > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=o… we should be able to use the compiler to compiler itself in another environment. > > 4.7 Packages as real objects > Begun in Pharo 2 with introduction of RPackage. Completed in Pharo 4 > with removal of PackageInfo. > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=p… > > 4.8 Package Meta-Data > Not sure what this entails or status. Package Manifest introduced in Pharo 2 > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=m… going well > > 4.11 New Network Layer - I don't know. nothing on this side. > > 4.12 Serializers - Fuel is the default serializer since Pharo 2. I > don't know the rest of the scope for this point. > https://github.com/pharo-project/pharo-changelogs/search?utf8=%E2%9C%93&q=f… > > cheers -ben > >

Dec. 29, 2015