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

Re: [Pharo-dev] .source file

by stepharo

>> -- >> Dr. Geo - http://drgeo.eu >> iStoa - http://istoa.drgeo.eu > > Few NB-FFI methods will work without sources, as many rely on the > automatic argument name -> signature mapping. > This happens the first time a method is called after startup, and > platform-specific recompilation occurs. When the argument names are > decompiled as arg1, arg2, the mapping will fail. > (Other NB methods that generate machine code without using NB-FFI, > will still work though) > > Theoretically, one could solve this by internalizing the source of all > NB-FFI calling method in the method trailer* at the end of deployment > preparation process. (so no NB methods have a chance to trigger before > image save) > NB puts native code into the same trailer space, and combing different > method trailer types is currently unsupported (AFAIK), but the transition > TrailerWithEmbeddedSource** -> TrailerWithNBCode should happen only once. Yes it would be good to have a method for doing that. https://pharo.fogbugz.com/default.asp?14311 > > Cheers, > Henry > > * something along the lines of: > | nativeMethods | > nativeMethods := (Pragma allInstances select: [ :each | each arguments > = #(#primitiveNativeCall #NativeBoostPlugin) ]) collect: #method. > > nativeMethods do: [ :nativeMethod | > nativeMethod methodClass methodDict at: nativeMethod selector put: > (nativeMethod copyWithTrailerBytes: > (CompiledMethodTrailer new sourceCode: nativeMethod sourceCode))] > > ** TrailerWithEmbeddedTemps would probably be sufficient, but other > than a reserved type, I can't see there's working code for it > >

Oct. 24, 2014

Re: [Pharo-dev] Run Spur run!!

by stepharo

On 24/10/14 10:31, Hilaire wrote: > Le 23/10/2014 21:49, Tudor Girba a Ã©crit : >> This is amazing. If we add to it that we will be able to have >> significantly larger images ... dreaming ... :) >> > Hey, but some time you also need smaller one ;-) Guille got a 11k image :) so we are getting there too :) >

Oct. 24, 2014

Re: [Pharo-dev] Playground/Rubric bracket highlighting in the System Browser

by stepharo

> Hi! > > Playground has a very nice feature that it highlights matching > bracket. I guess Rubric does it. The default editor does it too. if you go at the end of the [ ] ^ you get the first one in bold check also the settings Stef > Is this something that is planned to be implemented into the System > Browser editor? That would probably mean replacing the > PluggableTextMorph, but I don't know if there are any problems with > doing so. > > Also is there a keyboard shortcut for jumping to the matching > brace/bracket? > > Peter

Oct. 24, 2014

Re: [Pharo-dev] Take care with Package renaming in Pharo 3/4

by Esteban Lorenzano

most probably the class is still there. Just not packaged. you can execute RPackageOrganizer default initializeFromMC. to rebuild the packaging and see what happens. (anyway is a bug, but wellâ¦ at least you have a workaround to not lose your changes) Esteban > On 24 Oct 2014, at 13:18, stepharo <stepharo(a)free.fr> wrote: > > Are you sure that the class is not there because it happens to me and it was that the class was packaged elsewere. > > On 24/10/14 12:48, Torsten Bergmann wrote: >> Take care when renaming a package in Pharo: when you rename >> by just changing upper/lower case the package and code vanishes away. >> >> https://pharo.fogbugz.com/f/cases/14310/Renaming-a-package-just-by-changing… >> >> This is in Pharo 4.0 (up to 40324) and 3.0 (up to 30858). >> >> Nice way to get rid of fresh written code, even change sorter, changes file or >> recover lost changes will not help anymore :( >> >> >> >> >> >> > >

Oct. 24, 2014

Re: [Pharo-dev] .source file

by Henrik Johansen

> On 24 Oct 2014, at 10:48 , Hilaire <hilaire(a)drgeo.eu> wrote: > > Le 24/10/2014 10:35, Sven Van Caekenberghe a Ã©crit : >> I have to add that NativeBoost based code (like accessing environment variables for certain FileLocator places) breaks down when you have no sources ... > > Even with a fake .sources file? > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu <http://istoa.drgeo.eu/> Few NB-FFI methods will work without sources, as many rely on the automatic argument name -> signature mapping. This happens the first time a method is called after startup, and platform-specific recompilation occurs. When the argument names are decompiled as arg1, arg2, the mapping will fail. (Other NB methods that generate machine code without using NB-FFI, will still work though) Theoretically, one could solve this by internalizing the source of all NB-FFI calling method in the method trailer* at the end of deployment preparation process. (so no NB methods have a chance to trigger before image save) NB puts native code into the same trailer space, and combing different method trailer types is currently unsupported (AFAIK), but the transition TrailerWithEmbeddedSource** -> TrailerWithNBCode should happen only once. Cheers, Henry * something along the lines of: | nativeMethods | nativeMethods := (Pragma allInstances select: [ :each | each arguments = #(#primitiveNativeCall #NativeBoostPlugin) ]) collect: #method. nativeMethods do: [ :nativeMethod | nativeMethod methodClass methodDict at: nativeMethod selector put: (nativeMethod copyWithTrailerBytes: (CompiledMethodTrailer new sourceCode: nativeMethod sourceCode))] ** TrailerWithEmbeddedTemps would probably be sufficient, but other than a reserved type, I can't see there's working code for it

Oct. 24, 2014

Re: [Pharo-dev] Take care with Package renaming in Pharo 3/4

by stepharo

Are you sure that the class is not there because it happens to me and it was that the class was packaged elsewere. On 24/10/14 12:48, Torsten Bergmann wrote: > Take care when renaming a package in Pharo: when you rename > by just changing upper/lower case the package and code vanishes away. > > https://pharo.fogbugz.com/f/cases/14310/Renaming-a-package-just-by-changing… > > This is in Pharo 4.0 (up to 40324) and 3.0 (up to 30858). > > Nice way to get rid of fresh written code, even change sorter, changes file or > recover lost changes will not help anymore :( > > > > > >

Oct. 24, 2014

Re: [Pharo-dev] .source file

by Sven Van Caekenberghe

> On 24 Oct 2014, at 10:48, Hilaire <hilaire(a)drgeo.eu> wrote: > > Le 24/10/2014 10:35, Sven Van Caekenberghe a Ã©crit : >> I have to add that NativeBoost based code (like accessing environment variables for certain FileLocator places) breaks down when you have no sources ... > > Even with a fake .sources file? Yes, I believe NativeBoost needs to know the argument names of primitives to match method arguments to C primitives, and this cannot be done with decompilation or something like that

Oct. 24, 2014

Take care with Package renaming in Pharo 3/4

by Torsten Bergmann

Take care when renaming a package in Pharo: when you rename by just changing upper/lower case the package and code vanishes away. https://pharo.fogbugz.com/f/cases/14310/Renaming-a-package-just-by-changing… This is in Pharo 4.0 (up to 40324) and 3.0 (up to 30858). Nice way to get rid of fresh written code, even change sorter, changes file or recover lost changes will not help anymore :(

Oct. 24, 2014

Re: [Pharo-dev] PackageChooser logic

by Thierry Goubier

I replaced it in my AltBrowser by the finder toolbar without package selection: if the browser instance is scoped to a package (or a class), then all finder searches are limited to that package (or class, or set of methods, or ...). Crtl+F makes the finder toolbar appear, Esc or Ctrl+F makes it disappear. Very convenient when used like that. Could do Spotliight in the same way, thinking of it. Oh, and the finder results are a new browser showing only the results. Like that, you can find over a finder previous search in a single keystroke (Ctrl+F). Thierry 2014-10-24 12:02 GMT+02:00 Marcus Denker <marcus.denker(a)gmail.com>: > Yes, the whole Finder is quite old... lots of things could be improved. > (the best would be to replace it by a global spotlight like search...) > > > > > On Fri, Oct 24, 2014 at 11:54 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > >> I found the logic of the PackageChooser from the finder to be pretty >> weird. >> >> You can't directly select the packages you want to search in: you need >> to select all, reject, then reselect the ones you want to search in. >> >> >> How do you think about it? >> >> >> -- >> Dr. Geo - http://drgeo.eu >> iStoa - http://istoa.drgeo.eu >> >> >> >

Oct. 24, 2014

LivingCode was: Clickable class side example and initialize methods in Pharo 4.0

by kilon alios

Dont know what you feed this monster but it took forever to load on Pharo 4 and now it gives me the error MNU receiver of "do:" is nil Pharo 3 seems to work ok, so from what I gather this is a flow chart representation of Smalltalk language, very interesting , I like it very much. Are you serious about this project or its just a little experiment for you ? Blender users have been wanting a flow based programming language for some time, I have been looking into Phratch but apparently most people prefer flow charts like yours because its what they are used to to as users inside Blender and other 3d apps. So its also an area that interests me too for example procedural creation of 3d objects which is an area that Blender lacks right now while other apps like Houdini and Softimage have again been based on flow chart languages like yours. The nice thing about your approach is that is inside Pharo so it does not lock down into a flow chart-only approach as most implementations do. So the user can use LiveCode to quickly create code and then use normal text code to customise and further refine. Does that make sense to you ? I was thinking creating something similar myself but I was afraid it would be too much work. So I am definitely interested to learn how far you want to go with this . On Thu, Oct 23, 2014 at 9:46 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > I guess so, although I am not really sure what I am looking at - but it > > seems very cool. > > > kilon.alios wrote > > What the hell is that, looks very interesting !!!! > > Ha ha, yeah I guess a bit of context would help ;) > > It's a prototype I've been working on that combines some of (IMHO) the best > IDE ideas of various systems. That particular one shows Self Outliners (the > Morphs on the left of the connector). By pressing $M when an outliner has > the focus, you get a "Message Menu" of Scratch-like interactive tiles for > all the messages it understands. You can click on the unary messages or > type > expressions for the ones taking arguments (actually just realized that the > binary ones don't work so just keyword messages right now). When the > message > is sent, a new Self Outliner open(s)InHand on the result. > > It's a WIP, but if you want to play, start with: > > 1. > Gofer it > smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; > configurationOf: 'LivingCode'; > load. "Strangely I can not #loadDevelopment here because the > ScrollableWorldMorph package doesn't get loaded, even though it does with > the next line" > #ConfigurationOfLivingCode asClass project development load. > #SelfWorld asClass open. > > 2. Then in the search bar, type an evaluatable expression, e.g. "1" and > accept > 3. Drop the Outliner from the hand into the Self World > 4. For fun, click the world background and drag. OMG, you have an infinite > world > 5. Click on the M button in the outliner and the message menu will appear > (erroneously in the World instead of the Self World). > 6. Expand e.g. the "bit manipulation" protocol (assuming you started with > "1" as above) > 7. Click into the text field to the right of bitAnd: and accept the text > A new Outliner of the result will appear in the hand > > Other buttons on the Outliner: > B - open a nautilus on the class of the object > I - traditional inspector > S - open the test class if it exists (I call them Specification(s) in my > personal work) > E - Evaluator (very close to Self) > > Also, if you click on the icons to the right of "class" and "package" > Outliner(s) will appear on those objects. > > That's pretty much it for now. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Clickable-class-side-example-and-initialize-methods-i… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Oct. 24, 2014