- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Ubuntu ppa - How is it made?

by Damien Cassou

Markus Fritsche <mfritsche(a)reauktion.de> writes: > Damien Cassou originally created the scripts I am using. There are a few > manual steps involved that can be IMO automated. > > Look at > https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm-core-i386 > https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-launcher > https://github.com/mfritsche/pharo-ubuntu/tree/master/pharo-vm please update the scripts at https://github.com/pharo-project/pharo-ubuntu instead of having your own repositories. This looks more professional and everybody can find/modify them more easily. The only thing that can't easily be automated I think is the GPG signing. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] PetitMarkdown

by Damien Cassou

Christophe Demarey <Christophe.Demarey(a)inria.fr> writes: > Le 14 avr. 2015 Ã 22:51, phil(a)highoctane.be a Ã©crit : > >> I hate the figures not going where I want due to the LaTeX generation in Pillar. > > There should be options to place it where you want. Maybe a pillar expert could answer? this is not possible and, in my opinion, not desired. The following explains my reasons but requires some LaTeX knowledge to be understood. LaTeX does a really good job a placing figures at nice locations. For example, if your paragraph ends with 2 lines at the top of a page and you place a figure after this paragraph, LaTeX will make sure the figure appears at the top of a page and not after the 2 lines: this is because it would be ugly to have 2 lines, then a figure, then the rest of the text. In LaTeX, you have to make sure to always write things like "as can be seen in Figure 3" instead of "as can be seen in the figure below" because you can never be sure of the exact location of your figures. Please note that if in Pillar you don't specify any label you could reference from your text, then the figure will be placed by LaTeX at the exact location where you put it in Pillar. This is because, in this case, there is no way to write "as can be seen in Figure 3" when there is no label. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Kasper Osterbye

Damien Cassou wrote >> The TextRenderer accepts at least the commands shown by the screenshot >> noted >> by Damien. In addition I would like to point to a special link type I >> added: >> *LinkText>pharo://Classname[/methodname]* which will render a link which >> when clicked will open a new Nautilus browser on said class and >> method. > > I'm a bit skeptical about this syntax has it is heavyweight and I'm not > sure developers will want to use it. What about either: > > 1- let the developer simply write "TheClass" or "TheClass>>method" of > "#method" and get links (when target entity exists)? That's the > simplest. > > 2- or let the developer write ${pharo:TheClass}$, > ${pharo:TheClass>>method}$ or ${pharo:#method}$? This is more complex > but also more explicit. I like it to be a link, and hence the * syntax. A short version could be *>pharo://Class/method* - with auto picking the class or method name as link text as no other links (atm) will be without link text, it might default to *>Class/method* It depends a bit on the parser if it will be able to read it, I cannot try it right now. -- View this message in context: http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Damien Cassou

KasperOsterbye <kasper(a)itu.dk> writes: > The TextRenderer accepts at least the commands shown by the screenshot noted > by Damien. In addition I would like to point to a special link type I added: > *LinkText>pharo://Classname[/methodname]* which will render a link which > when clicked will open a new Nautilus browser on said class and > method. I'm a bit skeptical about this syntax has it is heavyweight and I'm not sure developers will want to use it. What about either: 1- let the developer simply write "TheClass" or "TheClass>>method" of "#method" and get links (when target entity exists)? That's the simplest. 2- or let the developer write ${pharo:TheClass}$, ${pharo:TheClass>>method}$ or ${pharo:#method}$? This is more complex but also more explicit. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Damien Cassou

kilon alios <kilon.alios(a)gmail.com> writes: > ok, but where and which repo ? Smalltalkhub ? GitHub ? Is part of Pillar ? > How I install these packages ? load a Pillar image from https://ci.inria.fr/pharo-contribution/job/Pillar (using the launcher for example :-)) and load Pillar-TextRenderer and Pillar-NautilusProofOfConcept in this order from the pillar repository (already in monticello). -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

April 16, 2015

Re: [Pharo-dev] two things I would like to know how to do in Spotter

by Tudor Girba

Hi, Thanks for the feedback. On Thu, Apr 16, 2015 at 8:32 AM, stepharo <stepharo(a)free.fr> wrote: > How can I find a directly package and not a class? > > How can I scope search? > If you type the name of a package, you will see it in the Packages category. For example, searching for "Collec" will show the packages category below the classes one: [image: Inline image 1] You can use Cmd+Shift+ArrowDown to jump to the next category faster. If you want to scope, you can use #. For example, if you want to look for packages category, you can add #pa to your query: [image: Inline image 2] > When I try to read the help via spotter I get an inspector? > Ah :(. That's because that is the default action for an object. I now added a spotter action to spawn the help browser for a help item. After I found the help browser and the global shortcut. > may be it would be good that help found via spotter open it > and that there is a menu inside the wheel to get it. > I do not quite get this one. Could you rephrase? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

April 16, 2015

Re: [Pharo-dev] [squeak-dev] vm crash from BalloonEngine (maybe B2DPlugin or BitBltPlugin)

by Nicolai Hess

2015-04-15 23:31 GMT+02:00 karl ramberg <karlramberg(a)gmail.com>: > You also get weird artifacts when the gradient orientation and normal is > very small. > looks funny:) > > In attached image, orientation is 0@-1 and normal is 1@1 > > Karl > > On Wed, Apr 15, 2015 at 10:34 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> >> >> 2015-04-08 20:02 GMT+02:00 karl ramberg <karlramberg(a)gmail.com>: >> >>> Confirmed. >>> >>> Karl >>> >>> On Wed, Apr 8, 2015 at 5:33 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> >>>> In order to reproduce it, draw a rectangle with radial gradient fill, >>>> with direction >>>> and normal, both of length 1. >>>> >>> >> This is not the reason why it crashes. It happens for other values as >> well: >> >> |form canvas fill direction normal| >> direction := 4@0. >> normal := 0@2. >> form := Form extent:300@300 depth:32. >> canvas := form getCanvas. >> fill := GradientFillStyle new colorRamp:{0 -> Color white . 0.5 -> Color >> green . 1 -> Color blue};origin:400@400 >> ;direction:direction;normal:normal;radial:true;yourself. >> canvas fillRectangle: (0@0 extent:800@800) fillStyle: fill. >> Display getCanvas drawImage: form at: 300@300 >> >> This uses a different value for direction and normal and the fill is >> defined for a larger area (800x800) -> CRASH >> >> Maybe, this is a rare bug, because, normally you don't create a small >> gradient t o >> fill a large area. But a vm crash is not nice, I would like to get this >> fixed. >> >> I am not sure what is the exact cause, but it may come from a signed >> integer overflwo, >> It looks like Balloon uses fixed point arithmetik (binary scaling). >> This fixed point representation (16.16 bit fixed point represented in a >> 32 integer) tend >> to overflow, especially for operations like computing the squared length >> of a vector >> x*x+y*y -> overflow -> result is a negative number. >> >> Possible solutions: >> downscale prior to the multiplication -> lost of precision >> use a larger datatype for intermediate results. >> >> It looks like B2D uses the first option (look at senders of >> accurateLengthOfwith >> and >> squaredLenghtOfwith >> Maybe there is something wrong with the other code that >> multiplies the values, or the 16.16 bit fixed point is just not >> large enough for some fills? >> >> >> Any ideas? >> >> Nicolai >> >> >> >> >>> >>>> This one works (no vm crash): >>>> |form canvas fill direction normal| >>>> direction := 1@0. >>>> normal := 0@0. >>>> form := Form extent:300@300 depth:32. >>>> canvas := form getCanvas. >>>> fill := GradientFillStyle new colorRamp:{0 -> Color white . 0.5 -> >>>> Color green . 1 -> Color blue};origin:150@150 >>>> ;direction:direction;normal:normal;radial:true;yourself. >>>> canvas fillRectangle: (50@50 extent:200@200) fillStyle: fill. >>>> Display getCanvas drawImage: form at: 300@300. >>>> >>>> >>>> direction := 1@0. >>>> normal := 0@0. >>>> -> OK >>>> >>>> direction := 0@0. >>>> normal := 0@1. >>>> -> OK >>>> >>>> direction := 1@0. >>>> normal := 0@1. >>>> -> VM-Crash (Pharo and Squeak) >>>> >>>> Pharo: >>>> VM Version: Cog VM 4.0.0 (release) from Feb 16 2015 >>>> Compiler: gcc 4.6.2 >>>> Interpreter Build: NBCoInterpreter >>>> NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: >>>> 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Feb 16 2015 >>>> Cogit Build: NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: >>>> 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Feb 16 2015 >>>> Source Version: https://github.com/pharo-project/pharo-vm.git Commit: >>>> 55fbd0b0279998a4a33852f5afb3d213986cc3ae Date: 2015-02-16 17:54:00 +0100 >>>> By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14895 >>>> >>>> Current byte code: -1 >>>> Primitive index: 117 >>>> Smalltalk stack dump: >>>> 0x24c830 M BalloonEngine>copyLoopFaster 0x6b09b80: a(n) BalloonEngine >>>> 0x24c848 M BalloonEngine>copyBits 0x6b09b80: a(n) BalloonEngine >>>> 0x24c860 M BalloonEngine>postFlushIfNeeded 0x6b09b80: a(n) >>>> BalloonEngine >>>> 0x24c884 I >>>> BalloonEngine>drawRectangle:fill:borderWidth:borderColor:transform: >>>> 0x6b09b80: a(n) BalloonEngine >>>> 0x24c8b8 I BalloonCanvas>drawRectangle:color:borderWidth:borderColor: >>>> 0x6b099c0: a(n) BalloonCanvas >>>> 0x24c8e8 I BalloonCanvas>fillRectangle:basicFillStyle: 0x6b099c0: >>>> a(n) BalloonCanvas >>>> >>>> >>>> Squeak: >>>> VM Version: Cog VM 4.0.0 (release) from Aug 22 2013 >>>> Compiler: gcc 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) >>>> Interpreter Build: CoInterpreter VMMaker.oscog-eem.331 uuid: >>>> 37d2e4b0-2f37-4e2d-8313-c63637785e59 Aug 22 2013 >>>> Cogit Build: StackToRegisterMappingCogit VMMaker.oscog-eem.333 uuid: >>>> 84da9cb8-7f30-4cb7-b4fb-239a11f63b54 Aug 22 2013 >>>> Source Version: VM: r2776 >>>> http://www.squeakvm.org/svn/squeak/branches/Cog >>>> Plugins: r2545 >>>> http://squeakvm.org/svn/squeak/trunk/platforms/Cross/plugins >>>> >>>> Current byte code: -1 >>>> Primitive index: 117 >>>> >>>> >>>> nicolai >>>> >>>> >>>> >>>> >>> >> >> >> >> >

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by Kasper Osterbye

stepharo wrote > I was just thinking about an experiment to map our world into a kind of > file system and use it to navigate > because in your link you want to refer to the class/method > and in fact it could be package/class/method package/resource or > package/class/resources (that we may have one day) He he - yes, I have had all kinds of thoughts in that direction. But at the moment it is most likely not where I will look. If anything - I would rather take a look on how one can use pillar-markup inside method comments, and try to see if one can find a way to make the interaction work. It should somehow be possible to hack into the syntax highlighter to do this, but I am not sure. Right now, I will try to consolidate what I did. But Damien suggested I just hold back until the Tx work is further progressed. -- View this message in context: http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 16, 2015

Re: [Pharo-dev] Class comments rendered in Nautilus (through Pillar)

by stepharo

I was just thinking about an experiment to map our world into a kind of file system and use it to navigate because in your link you want to refer to the class/method and in fact it could be package/class/method package/resource or package/class/resources (that we may have one day) but this was just an idea Le 15/4/15 21:42, Kasper Osterbye a Ã©crit : > stepharo wrote >> an idea: what about a version of FileSystem that can be used to navigate >> classes? > I assume there is some tooling you would like to re-use? > > If that is the case, I would think it would be more useful to look into what > might be the right common abstraction between filesystem and class/method > hierarchy - but it is hard to say without knowing the problem you were > thinking of (and was it related to the text-renderer in some way I did not > see?) > > -- Kasper > > > > -- > View this message in context: http://forum.world.st/Class-comments-rendered-in-Nautilus-through-Pillar-tp… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > >

April 16, 2015

two things I would like to know how to do in Spotter

by stepharo

How can I find a directly package and not a class? How can I scope search? When I try to read the help via spotter I get an inspector? After I found the help browser and the global shortcut. may be it would be good that help found via spotter open it and that there is a menu inside the wheel to get it. Stef

April 16, 2015