April 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3965 in pharo: Turn off Smart Characters in Full Image by default

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3965 by marcus.d...(a)gmail.com: Turn off Smart Characters in Full Image by default http://code.google.com/p/pharo/issues/detail?id=3965 maybe not... lets see how many people will complain

April 8, 2011

Re: [Pharo-project] Issue 3842 in pharo: 1.2 Config needs to load latest code from OB Repository

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #5 on issue 3842 by marcus.d...(a)gmail.com: 1.2 Config needs to load latest code from OB Repository http://code.google.com/p/pharo/issues/detail?id=3842 TODO: update Configuration based on the latest packages <https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st> (It should be noted that this is only possible after 1.2 was released. Before, the latest packages where compatible to 1.1...)

April 8, 2011

Re: [Pharo-project] Making layouts using anchors

by Fernando Olivero

The idea is simple yet powerful, i'm favor. Can they be somehow integrated into the current layout mechanism? LayoutPolicy subclass: #AnchorPolicy Then they are just another option, and the merge could be transparent. I could add them in the context of SMx. Fernando On Thu, Apr 7, 2011 at 8:45 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hi, > > i hacked morphs a bit to use anchors for laying out the morphs. > > The idea that you can force morph to make one of its edges (left, top, > bottom, right) > be dependent from other morph's edge. > > Here an example: > > | window morph morph2 | > > window := StandardWindow labelled: 'foo'. > window color: Color red. > morph := Morph new. > > morph anchorLeft: window leftAnchor + (window widthAnchor * 0.5) - 20. > morph anchorRight: window leftAnchor + (window widthAnchor * 0.5) + 20. > morph anchorTop: window topAnchor + 20. > morph anchorBottom: window bottomAnchor - 20. > > morph2 := Morph new. > morph2 color: Color green. > > morph2 anchorLeft: morph rightAnchor + 10. > morph2 anchorRight: morph rightAnchor + 50. > morph2 anchorTop: window topAnchor + 20. > morph2 anchorBottom: window bottomAnchor - 20. > > window addMorph: morph2. > window addMorph: morph. > > window openInWorld. > > window extent: 200@200. > > > You can of course implement same layout using proportional layouts > i.e. you can do > > window addMorph: fullFrame: ... > > but note that while its okay for first morph you add , a morph2 left > edge is actually depending on first morph right edge. > So, if it will be resized by other means (like stretched by inner > morph), you won't be able to align sibling accordingly, > and then you are forced to use table layout or something else. > > What i like about anchors that it reflects the natural way of thinking > of UI designer i.e. : "I want this morph to align to window right > edge" > or "I want this morph to align to previous morph right edge with 10 > pixels offset" > > For example, if i have two morphs, left and right, and i want to put > my morph in the middle of them to fill the space between them, > i can simply do: > > middle := Morph new. > > middle anchorLeft: leftMorph rightAnchor + 10. > middle anchorRight: rightMorph leftAnchor - 10. > > so, you will get a following layout: > > [leftMorph] [ 10 pixels ] [ ... middle morph ..... ] [ 10 pixels ] > [right morph ] > > with just two lines of code! > > P.S. Of course , anchors are in conflict with layouts, because you > cannot have both. But some combination of them could still be used. > > -- > Best regards, > Igor Stasenko AKA sig. >

April 8, 2011

Re: [Pharo-project] Issue 3754 in pharo: Omnibrowser's an extra horizontal scrollbar

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3842 Comment #16 on issue 3754 by marcus.d...(a)gmail.com: Omnibrowser's an extra horizontal scrollbar http://code.google.com/p/pharo/issues/detail?id=3754 (No comment was entered for this change.)

April 8, 2011

Re: [Pharo-project] [COTDC] 43 - TextStyleFontSelectorDialogWindow

by Marcus Denker

On Apr 7, 2011, at 10:23 PM, laurent laffont wrote: > TextStyleFontSelectorDialogWindow new => error. > > Is it used ?? If it is broken, it is not used. > Should we remove it ? > things that nobody cares about should be removed. Who will maintain them? Nobody. > > For FreeTypeFontSelectorDialogWindow: > > I'm a dialog to select a font. Usage example: > > |fontSelector| > fontSelector := FreeTypeFontSelectorDialogWindow new. > UITheme builder openModal: fontSelector. > fontSelector selectedFont inspect. > > > Laurent. > > > > On Wed, Apr 6, 2011 at 9:52 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > Today: TextStyleFontSelectorDialogWindow > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 8, 2011

Re: [Pharo-project] Issue 3842 in pharo: 1.2 Config needs to load latest code from OB Repository

by pharo＠googlecode.com

Updates: Cc: renggli Comment #4 on issue 3842 by marcus.d...(a)gmail.com: 1.2 Config needs to load latest code from OB Repository http://code.google.com/p/pharo/issues/detail?id=3842 Issue 3754 has been merged into this issue.

April 8, 2011

Re: [Pharo-project] Initial PetitC parser

by Tudor Girba

Hi Javier, On 8 Apr 2011, at 05:37, Javier PimÃ¡s wrote: > Hi, > I took some time to start developing a C parser with PetitParser. I used the slides of the smalltalk school, they were pretty useful, and after some hours I have a very basic tokens scanner. The idea of this work is to be able to feed the parser with C headers and automagically get the C bindings done in smalltalk. Nice. I took a quick look. If you want to scale, please write tests (one small example per test). Grammars become complex and if you do not have close to 100% coverage, you will get stuck. Cheers, Doru > Now I have to actually start doing something with the scanned code. How should I do that, all in the same class? What if I want to generate bindings for different kinds of FFIs? Other question, how should I handle preprocessing? (now there isn't any kind of preprocessing) > > You can see the code, download it and commit improvements to the repo at www.squeaksource.com/Bindings > > Anybody who is interested is welcomed to help in the development! > > Regards, > Javier. > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

April 8, 2011

Re: [Pharo-project] Issue 3754 in pharo: Omnibrowser's an extra horizontal scrollbar

by pharo＠googlecode.com

Comment #15 on issue 3754 by renggli: Omnibrowser's an extra horizontal scrollbar http://code.google.com/p/pharo/issues/detail?id=3754 I looked at ConfigurationOfOmniBrowser this morning and it is definitely very outdated and mixes incompatible versions. Look at the images I linked to see what versions to load. Alternatively you can use the script <https://github.com/renggli/builder/blob/master/scripts/omnibrowser.st> to load a working configuration into a PharoCore image.

April 8, 2011

Re: [Pharo-project] Issue 3969 in pharo: MorphTreeMorph performance

by pharo＠googlecode.com

Comment #4 on issue 3969 by marcus.d...(a)gmail.com: MorphTreeMorph performance http://code.google.com/p/pharo/issues/detail?id=3969 Issue 3970 has been merged into this issue.

April 8, 2011

Re: [Pharo-project] Issue 3970 in pharo: Finder broken with last updates related to MorphTreeMorph

by pharo＠googlecode.com

Updates: Status: Duplicate Mergedinto: 3969 Comment #1 on issue 3970 by marcus.d...(a)gmail.com: Finder broken with last updates related to MorphTreeMorph http://code.google.com/p/pharo/issues/detail?id=3970 fixed by Issue 3969

April 8, 2011