January 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] What Logging framework for Pharo

by stepharo

If you need the pdf just ask we should put back the ci crushing pillar and producing pdf Le 12/1/15 19:25, Alain Rastoul a Ã©crit : > Le 12/01/2015 19:11, stepharo a Ã©crit : >> >> Le 12/1/15 18:56, Sven Van Caekenberghe a Ã©crit : >>>> On 12 Jan 2015, at 18:27, Alain Rastoul >>>> <alf.mmm.cat(a)gmail.com> wrote: >>>> >>>> hi all, >>>> >>>> Googling a bit for a logging framework in Pharo, I found sl4j, which >>>> sounds familiar to me. >>>> http://ss3.gemstone.com/ss/Log4s.html/Wiki >>>> >>>> I suppose the API is the same as the java package, as claimed by the >>>> project page. >>>> I wonder if anybody is using it , or has tried it and have an advice >>>> on that package ? >>>> (I saw there was no test and no comments ... :( ) >>>> >>>> I think it could be great for Pharo to have a standard package like >>>> that, a logging facility is mandatory for most -if not all- >>>> applications >>>> >>>> Any advice or pointers ? >>> Object logging instead of String logging is the way to go. >>> SystemLogger, Beacon, Zinc's ZnLogEvent are examples. Search the >>> mailing list for past discussions. >> >> we will merge SystemLogger and Beacon. Now there is a full documentation >> about SystemLogger at >> https://github.com/SquareBracketAssociates/PharoReadyForReviews > Cool chapters. > And I found the projects on smalltalk hub. > thank you Stef > >> >>> >>>> TIA >>>> -- >>>> Regards, >>>> >>>> Alain >>>> >>>> >>> >>> >> >> >> > >

Jan. 12, 2015

Re: [Pharo-dev] [Pharo4] Slots can now be saved with MC

by stepharo

+ 1 Great post marcus. I want slots!!! and I want to have slot for caches because the analysis of guille showed that we have aroun 40 different caches in the system.... Stef Le 12/1/15 15:59, Marcus Denker a Ã©crit : >> On 11 Jan 2015, at 18:50, Chris Muller <asqueaker(a)gmail.com> wrote: >> >> It has been a while since I read the paper, but my memory is that >> Slots lets you define features and/or constraints on inst-var's. For >> example, assigning default values or restricting the set of valid >> values. >> >> This would probably be appealing for folks coming from languages like >> Java or C++, because they're used to all of their "slots" being >> statically typed. It does seem ironic that where those static >> languages have been trying to move toward being more dynamic, Pharo >> newbies would find themselves arrived at a language which is trying to >> make something that was purely dynamic into something more static. >> > It is *possible* to implement a kind of TypedSlot, but I do not think that > this is what people will use Slots for. And for sure there will be no TypeSlot > by default in Pharo. > > For Slots there are two levels > > 1) having objects that describe variables instead of strings. This is very powerful > already and will allow us to e.g. do watchpoints/breakpoitns in variables very easily > > This is already in Pharo3, but Pharo4 enhances the API and provides with the LinkWrapper > slot a way to transparently hook into variable access. This will be very powerful. > > 2) provide a way to declare that a slot is described by a special subclass of Slot. This is what this > change is about > > This is what we use Slots for are three directions: > > 1) active slots that announce when the are set. Replacing the whole ValueHolder stuf to some extend. > (This is where Slots + their Meta Object Protocol allow one to implement the special variables in Tweak > very easily. It is interesting that there, one had to copy the whole compiler and do many, many hacks. > > 2) Allow optimizing memory representation. E.g. look at Morph. Many flags are needed, but each takes a > whole pinter to true of false. So we have MorphExtension. And then on top of that a property dictionary. > With Slots, flags (sots that can only store true or false) can be realised very efficiently (31 boolean slots > of the hierarchy map to one ivar). With a PropertySlot, one can have values that are used seldomely > encoded in a way that they take no space. > > 3) Slots + Magritte. Magritte now relies of conventions and methods added to the class side. But what it > is: meta descriptions for ivars. I think there will be something very powerful in combining Magritte and Slots. > > 4) Experiments. One way to see Pharo is that it is suppose to be flexible enough to allow experiments > to be done fast and easy so we can explore many ideas easily. > These experiments will often be just that: experiments. But some of them will be so good that they will > turn out to be useful. > >> My understanding is that specifying a certain Slot-type can save the >> need to write, i.e., initializing or validating methods. In exchange, >> the number of concepts inherent in the language that must be learned >> and remembered is increased. Standard Smalltalk is only about 2 or 3 >> concepts -- sending messages and assigning pointers. Period. There's >> something exciting about that because even Grandma can grok 2 or 3 >> concepts. No other language is so simple. >> > Slots do not really increase the concepts: they just are meta objects that have the > definition of the behaviour of assignment, turning assignment into message sends. > >> By introducing the implicit behaviors of slots, the number of >> different conceptual interactions between code and the slots it >> references increases exponentially with the number of slot-types. I >> fear trying to explain them to Grandma will have her eyes starting to >> glazeâ¦ >> > I do not see now an active slot is harder to understand than e.g. a ValueHolder. > or a BooleanSlot should be easier to understand than doing all that explicitely? > > > Marcus > > >

Jan. 12, 2015

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

by stepharo

Le 12/1/15 19:08, J.F. Rick a Ã©crit : > Hi Sebastian, > > Noel is actually my academic older brother (i.e., we had the same > doctoral advisor). Noel's introduction is nice but it is to people who > know how to program (specifically, Ruby programmers). That's useful. > The Pharo books and YouTube videos do this very well. But, you also > need to provide a way in for people who are learning to program. One > thing you could do is provide a book that could be used at a > university to teach object-oriented programming. Indeed. People are really interested I have a lot of material that did not go in my botsinc book on OOP (a breakout, and a lot more). Stef > > Cheers, > > Jeff > > *Da:*Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] *Per > conto di *Sebastian Sastre > *Inviato:* venerdÃ¬ 9 gennaio 2015 19:07 > *A:* Pharo Development List > *Oggetto:* Re: [Pharo-dev] from 2009's The "death" of Smalltalk to > 2014's But Really, You Should Learn Smalltalk > > Hi Jochen, > > have in mind that the talk you referred is from 2009 and many > controversial things happened in the Ruby community at that time. > > Coming closer to today, we just had this presentation which > presents Smalltalk better than many Smalltalkers Iâve heard! > > https://www.youtube.com/watch?v=eGaKZBr0ga4 > > Want to show off smalltalk to non-smalltalker audiences *in an > effective way*? watch and learn! > > -- > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick

Jan. 12, 2015

Re: [Pharo-dev] What Logging framework for Pharo

by Alain Rastoul

Le 12/01/2015 19:11, stepharo a Ã©crit : > > Le 12/1/15 18:56, Sven Van Caekenberghe a Ã©crit : >>> On 12 Jan 2015, at 18:27, Alain Rastoul >>> <alf.mmm.cat(a)gmail.com> wrote: >>> >>> hi all, >>> >>> Googling a bit for a logging framework in Pharo, I found sl4j, which >>> sounds familiar to me. >>> http://ss3.gemstone.com/ss/Log4s.html/Wiki >>> >>> I suppose the API is the same as the java package, as claimed by the >>> project page. >>> I wonder if anybody is using it , or has tried it and have an advice >>> on that package ? >>> (I saw there was no test and no comments ... :( ) >>> >>> I think it could be great for Pharo to have a standard package like >>> that, a logging facility is mandatory for most -if not all- applications >>> >>> Any advice or pointers ? >> Object logging instead of String logging is the way to go. >> SystemLogger, Beacon, Zinc's ZnLogEvent are examples. Search the >> mailing list for past discussions. > > we will merge SystemLogger and Beacon. Now there is a full documentation > about SystemLogger at > https://github.com/SquareBracketAssociates/PharoReadyForReviews Cool chapters. And I found the projects on smalltalk hub. thank you Stef > >> >>> TIA >>> -- >>> Regards, >>> >>> Alain >>> >>> >> >> > > > -- Regards, Alain

Jan. 12, 2015

Re: [Pharo-dev] Woden on Windows?

by Torsten Bergmann

Hi Richard, this is an error from NativeBoost. Have a look at the previous methods back in the debugger stack. There must be one with a native Boost call including something like options: { WinUnicode }. Change this to optWinUnicode and try again. Â I guess we now use "opt" prefix for Native Boost options.Â Bye T. Â Â Gesendet:Â Montag, 12. Januar 2015 um 16:18 Uhr Von:Â "Richard Wettel" <wettel(a)gmail.com> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] Woden on Windows? Hi Â I am also interested in the current status of Woden.I tried to follow the instructions from Alex (under Windows 7) and I get a: Â NBFFICallout>>error:Â 'Invalid option name WinUnicode, must begin with ''opt''' Â Any help is appreciated. Â Cheers Ricky Â On Mon, Jan 12, 2015 at 2:46 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote:You should do: Gofer new smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; package: 'ConfigurationOfNBOpenGL'; load. ((Smalltalk at: #ConfigurationOfNBOpenGL) project version: '3.0') load. Gofer new smalltalkhubUser: 'Pharo' project: 'OSWindow'; package: 'ConfigurationOfOSWindow'; load. (Smalltalk at: #ConfigurationOfOSWindow) loadBleedingEdge. Gofer new smalltalkhubUser: 'ronsaldo' project: 'Woden'; package: 'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden) loadBleedingEdge. Some of the things are not up to date in pharo. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre BergelÂ http://www.bergel.eu[http://www.bergel.eu] ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jan 11, 2015, at 2:06 PM, Torsten Bergmann <astares@gmx.de[astares@gmx.de]> wrote: > > Hi, > > is woden 3D engine for Pharo working out of the box with Pharo 4 and > latest VM on Windows? As OSWindow is already integrated I do not know > if the load script still fits. Wanted to ask first. > What is required to load? > > If so can we have a config in the config browser for easy access? > > Thx > T. > Â

Jan. 12, 2015

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

by stepharo

you mean 1000 factorial / 9999 factorial. Le 12/1/15 09:15, Lorenzo Schiavina a Ã©crit : > > Hi, > > instead of using the trivial 2 + 2 as ST example, for many years I > have found more impressive: 50000 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 [mailto:pharo-dev-bounces@lists.pharo.org] *Per conto > di *Sebastian Sastre > *Inviato:* venerdÃ¬ 9 gennaio 2015 19:07 > *A:* Pharo Development List > *Oggetto:* Re: [Pharo-dev] from 2009's The "death" of Smalltalk to > 2014's But Really, You Should Learn Smalltalk > > Hi Jochen, > > have in mind that the talk you referred is from 2009 and many > controversial things happened in the Ruby community at that time. > > Coming closer to today, we just had this presentation which presents > Smalltalk better than many Smalltalkers Iâve heard! > > https://www.youtube.com/watch?v=eGaKZBr0ga4 > > Want to show off smalltalk to non-smalltalker audiences *in an > effective way*? watch and learn! > > On Jan 9, 2015, at 3:37 PM, J.F. Rick <self(a)je77.com > <mailto:self@je77.com>> wrote: > > Hi everyone, > > I just watched https://www.youtube.com/watch?v=YX3iRjKj7C0and had > a few comments that I thought I would share. > > First, there is a real opportunity for Smalltalk to come back in > the guise of Pharo. Steph and Marcus are doing a great job > providing leadership towards that end and the community is great. > Second, we need to be careful in spreading the word. Slowly but > surely (the current Pharo approach) is a great approach as it > allows really building something worth spreading before trying to > get everyone into it. If it spreads too quickly, bad API or > immature toolkits will become ingrained and flaws will be > apparent. The books, websites, etc. are really good things to get > right before trying to get others into it; they are already very > good. Third, if you want to really spread Smalltalk, then the > fundamentals that newcomers experience need to be without obvious > flaws. From personal experience, I can tell you that BitBlt > rendering makes newbies think that Pharo is a toy language. > Switching to Athens rendering is therefore tremendously important > for adoption. Package management really needs to be cleaned up. > There needs to be a simple way to merge resources (bitmaps, audio, > external files) into the codebase. Simple audio needs to work on > all platforms. This may seem trivial but audio is one of the > simplest things that newcomers want to do. From a Linux > perspective, this will probably necessitate switching to a 64-bit > VM as the 32-bit sound plug-ins are a giant pain. Given that even > phone OSs are switching to 64-bit, there may not be a need for a > 32-bit Pharo. Of course, much of this is already on the horizon. > > As the new year begins, I'll once again be coding in Pharo and > look forward to it. I'm really hopeful about the future. > > Cheers, > > Jeff > > -- > > Jochen "Jeff" Rick, Ph.D. > http://www.je77.com/ > Skype ID: jochenrick >

Jan. 12, 2015

Re: [Pharo-dev] athens font rendering and subpixel antialiasing

by stepharo

Igor once explained to me that FreeType has the possibility to degrade fonts when the family does not provide it. Cairo does not have this possibility. Esteban I'm sure that the same code is used. FreeType is much more advanced than Cairo when it is about fonts. Stef Le 11/1/15 22:43, Nicolai Hess a Ã©crit : > Anyone knows, why the text rendering with athens (cairo) looks slightly > different than the freetypeplugin one? > > attached is a screenshot, left side athen right side (morphic) > freetypeplugin. > > It "looks" like the cairo freetype fontrendering uses > CAIRO_ANTIALIAS_GRAY, no colored subpixel antialiasing. > But the font options do define antialiase subpixel and a subpixel > ordering RGB. > > This is on windows 7 with the latest vm, does it look different on other > Systems? > > > nicolai > >

Jan. 12, 2015

Re: [Pharo-dev] GTInspector does not refresh printString

by stepharo

Hi andrei > The inspector does not automatically update the string representation > for now (as it does not automatically refresh-- the same discussion as > the state view). > It should however update the representation if you change printOn: and > manually refresh/ inspect the object again. Just checked it and it > works for me. If it doesn't work for you then there is a bug. > What did you do? I was doing a lecture and this is really sad to get all features gone. So I had to reinspect again. In addition GTInspector bubble is a pain because sometimes you really want to keep the result and not inpect it. Did you see my request to get that enter put the bubble contents into the text pane? I'm sorry but I cannot use GT as it is now. And I'm working on the new version of Pharo by example and it would be good to have something full working. Stef > > > Cheers, > Andrei > > On Mon, Jan 12, 2015 at 12:14 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > GTInspector does not change the printString representation when we > change the printOn:. > Am I the only one to see this behavior? > > Stef > >

Jan. 12, 2015

Re: [Pharo-dev] What Logging framework for Pharo

by stepharo

Le 12/1/15 18:56, Sven Van Caekenberghe a Ã©crit : >> On 12 Jan 2015, at 18:27, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: >> >> hi all, >> >> Googling a bit for a logging framework in Pharo, I found sl4j, which sounds familiar to me. >> http://ss3.gemstone.com/ss/Log4s.html/Wiki >> >> I suppose the API is the same as the java package, as claimed by the project page. >> I wonder if anybody is using it , or has tried it and have an advice on that package ? >> (I saw there was no test and no comments ... :( ) >> >> I think it could be great for Pharo to have a standard package like that, a logging facility is mandatory for most -if not all- applications >> >> Any advice or pointers ? > Object logging instead of String logging is the way to go. SystemLogger, Beacon, Zinc's ZnLogEvent are examples. Search the mailing list for past discussions. we will merge SystemLogger and Beacon. Now there is a full documentation about SystemLogger at https://github.com/SquareBracketAssociates/PharoReadyForReviews > >> TIA >> -- >> Regards, >> >> Alain >> >> > >

Jan. 12, 2015

Re: [Pharo-dev] What Logging framework for Pharo

by Alain Rastoul

Le 12/01/2015 18:56, Sven Van Caekenberghe a Ã©crit : > >> On 12 Jan 2015, at 18:27, Alain Rastoul <alf.mmm.cat(a)gmail.com> wrote: >> >> hi all, >> >> Googling a bit for a logging framework in Pharo, I found sl4j, which sounds familiar to me. >> http://ss3.gemstone.com/ss/Log4s.html/Wiki >> >> I suppose the API is the same as the java package, as claimed by the project page. >> I wonder if anybody is using it , or has tried it and have an advice on that package ? >> (I saw there was no test and no comments ... :( ) >> >> I think it could be great for Pharo to have a standard package like that, a logging facility is mandatory for most -if not all- applications >> >> Any advice or pointers ? > > Object logging instead of String logging is the way to go. SystemLogger, Beacon, Zinc's ZnLogEvent are examples. Search the mailing list for past discussions. Thank you Sven, Googling for those names gave me more interesting results :) I'll dig into that > >> TIA >> -- >> Regards, >> >> Alain >> >> > > > -- Regards, Alain

Jan. 12, 2015