February 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] PetitParser in 2.0

by H. Hirzel

Thank you for the status report and putting it into the 'untrusted' directory. Actually I am interested in the GUI. So I'll wait for Glamour to catch up. --Hannes On 2/14/13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > hi, > > something like: > > Gofer it > renggli: 'petit'; > package: 'ConfigurationOfPetitParser'; > load. > (ConfigurationOfPetitParser project version: '1.5') > load: #(Core PetitXml PetitJson PetitXPath PetitCSV) > > UI will not load in 2.0 right now because it uses glamour who is being > migrated. > It will throw a warning because BlockContext is not in the image anymore. > You can safely ignore it. > > I copied the configuration into the "untrusted" directory. Some benevolent > soul could prepare a reliable configuration for 2.0 and copy it into > MetaRepoForPharo20... :) > > Esteban > > > On Feb 14, 2013, at 6:46 PM, "H. Hirzel" <hannes.hirzel(a)gmail.com> wrote: > >> Hello >> >> How do I load >> >> PetitParser >> >> into Pharo-2.0? >> >> There is no entry in the configuration browser. >> >> Regards >> >> Hannes >> > > >

Feb. 15, 2013

Re: [Pharo-project] Another stupid question

by Henrik Johansen

On Feb 15, 2013, at 1:51 AM, Benjamin wrote: > On Feb 15, 2013, at 1:40 AM, "Torsten Bergmann" <astares(a)gmx.de> wrote: > >> This was just an example to play with since you asked >> for a #convertFromBase:to: method in your original mail >> and one cant provide such a method on Number. Your >> original request >> >> 11 convertFromBase: 2 to: 10 >> >> may work - but it wont work for hex values: >> >> FF convertFromBase: 16 to: 10 >> >> then FF would have to be a string. >> >> 'FF' convertFromBase: 16 to: 10 >> >> So having a #convertFromBase:to: on String is not to recommend >> (especially since the string has to be in a number format) >> and also not necessary. I should have added this to my mail >> as a warning. >> >> Just use >> >> (Number readFrom: self base: sourceBase) printStringBase: targetBase >> > > Thank you > >> If necessary put it in a private helper method for conversion. >> >> May I ask why you require conversions between the different base systems? > > I have to implement a FTP server for a lecture, and the port is provided in a strange format (twice 8 bits). > So I needed to change the port in base 10 to base 2, cut it into two pieces, then turn those pieces back in base 10 :) > >> Working on a hex editor for Nautilus? ;) > > Is a hex editor a need ? :) > > Ben > >> >> Bye >> T. >> >> >> > > Wait, wait, wait. You mean like #[16 45] ? What's wrong with Number1 := sourceNumber >> 8 Number2 := sourceNumber bitAnd: 255 ? Cheers, Henry

Feb. 15, 2013

[Pharo-project] TxTextMorph based on new text model

by Stephan Eggermont

Sean wrote: Denis Kudriashov wrote >> Do you think that presenting any letter with real object (not just >> character) is sufficient for modern computers? I think not. Of course such >> model significantly simplified all logic around text layout stuff. But I >> think it is too expensive. In a case study on designing a document editor in 'Design Patterns (1995)' , there is a reference to a thesis from 1993 showing that using Flyweight or sharing commonality makes it fast enough. I assume that was c++, but 20 years of hardware improvements should be enough. Paul R Calder. Building User Interfaces with Lightweight Objects. PhD Thesis, Stanford University, 1993 >I don't know how efficient it would be, but how much text do we really >layout at once? If it makes the code simpler and more beautiful, then it >would be my starting point. Doing otherwise is premature optimization. One book at a time. In multiple columns, with tables. But we don't need to show more than one screenful at a time. I noticed the current strategy seems to be to make a very simple model work, and add abstractions late. That means a lot of refactorings will be needed. Cocoa fundamental abstractions are TextStorage, LayoutManager, TextContainer and TextView. LayoutManager uses TypeSetter(s) to layout glyphs in lines according to the dimensions of one or more text container objects in one or more text views, directs the GlyphGenerator to translate characters in the textstorage into glyphs... Stephan

Feb. 15, 2013

[Pharo-project] [update 2.0] #20547

by Marcus Denker

20547 ----- Issue 7511: Nautilus highlight issue Issue 7511: Nautilus highlight issue Diff information: http://ss3.gemstone.com/ss/Pharo20/Nautilus-MarcusDenker.421.diff

Feb. 15, 2013

[Pharo-project] Opening a webbrowser (using NB on non-Windows)

by Torsten Bergmann

In Pharo 2.0 one can now use NBWin32Shell shellBrowse: 'http://www.pharo-project.org' which will open an external webbrowser on the given URL. This is currently limited to Windows. Anyone able to implement/call appropriate NB functions for Mac and Linux? I would like to see a unified interface coming with 2.0 NBWebbrowser shellBrowse: url dispatching to the appropriate class depending on OS. Since these days a lot of work is done using webbrowsers I think a unified way to open a browser on a given URL is required for Pharo. I also need this for the upcoming Pharo online help to work on all major platforms. Thanks T.

Feb. 15, 2013

Re: [Pharo-project] Another stupid question

by Benjamin

On Feb 15, 2013, at 1:40 AM, "Torsten Bergmann" <astares(a)gmx.de> wrote: > This was just an example to play with since you asked > for a #convertFromBase:to: method in your original mail > and one cant provide such a method on Number. Your > original request > > 11 convertFromBase: 2 to: 10 > > may work - but it wont work for hex values: > > FF convertFromBase: 16 to: 10 > > then FF would have to be a string. > > 'FF' convertFromBase: 16 to: 10 > > So having a #convertFromBase:to: on String is not to recommend > (especially since the string has to be in a number format) > and also not necessary. I should have added this to my mail > as a warning. > > Just use > > (Number readFrom: self base: sourceBase) printStringBase: targetBase > Thank you > If necessary put it in a private helper method for conversion. > > May I ask why you require conversions between the different base systems? I have to implement a FTP server for a lecture, and the port is provided in a strange format (twice 8 bits). So I needed to change the port in base 10 to base 2, cut it into two pieces, then turn those pieces back in base 10 :) > Working on a hex editor for Nautilus? ;) Is a hex editor a need ? :) Ben > > Bye > T. > > >

Feb. 15, 2013

[Pharo-project] Another stupid question

by Torsten Bergmann

This was just an example to play with since you asked for a #convertFromBase:to: method in your original mail and one cant provide such a method on Number. Your original request 11 convertFromBase: 2 to: 10 may work - but it wont work for hex values: FF convertFromBase: 16 to: 10 then FF would have to be a string. 'FF' convertFromBase: 16 to: 10 So having a #convertFromBase:to: on String is not to recommend (especially since the string has to be in a number format) and also not necessary. I should have added this to my mail as a warning. Just use (Number readFrom: self base: sourceBase) printStringBase: targetBase If necessary put it in a private helper method for conversion. May I ask why you require conversions between the different base systems? Working on a hex editor for Nautilus? ;) Bye T.

Feb. 15, 2013

Re: [Pharo-project] Another stupid question

by Benjamin

Thank you guys :) I feel a little less dumb :) (even if it's not really natural for me to have this behaviour on string but ^^) Ben On Feb 15, 2013, at 12:33 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Euh, sure this works: > > (Number readFrom: 'FF' base: 16) printStringBase: 2 > > Number class>>#readFrom:base: > Integer class>>#readFrom:base: > > On 15 Feb 2013, at 00:26, "Torsten Bergmann" <astares(a)gmx.de> wrote: > >> Sven wrote: >>> So something like this should work: >>> >>> (Integer readFrom: 'FF' base: 16) printStringBase: 2 >> >> Integer readFrom: 'FF' will not work since #readFrom: expects a string in decimal representation >> and 'FF' is hexadecimal. It also wont work for large numbers due to sending it to "Integer". >> >> Just use >> >> (Number readFrom: '16rFF') printStringBase: 2 >> >> which works for large numbers >> >> (Number readFrom: '16rFFFFFFFFF') printStringBase: 2 >> >> >> Bye >> Torsten >> >> > >

Feb. 14, 2013

[Pharo-project] Another stupid question

by Torsten Bergmann

>Euh, sure this works: > (Number readFrom: 'FF' base: 16) printStringBase: 2 Yes, one has to use "Number" instead of Integer and #readFrom:base: #readFrom: works too if you already have the string in source base representation, e.g. '16rFF'. The timing is good - currently work on the literal section for the new Pharo help system and will integrate this as an example in the tutorial. Bye T.

Feb. 14, 2013

Re: [Pharo-project] TxTextMorph based on new text model

by Fernando Olivero

Hi, this is really interesting! To have a simpler text model and UI. I recall Safara, in squeaksource. Lukas and a student worked on a nice text model. Worth checking it out. Fernando On Fri, Feb 15, 2013 at 12:29 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Thanks again for tackling this! I'm definitely available to collaborate :) > > > Denis Kudriashov wrote > > Do you think that presenting any letter with real object (not just > > character) is sufficient for modern computers? I think not. Of course > such > > model significantly simplified all logic around text layout stuff. But I > > think it is too expensive. > > I don't know how efficient it would be, but how much text do we really > layout at once? If it makes the code simpler and more beautiful, then it > would be my starting point. Doing otherwise is premature optimization. > > > Denis Kudriashov wrote > > Another thing which I always not agree is introduction scripting > languages > > inside smalltalk... [but] I like what they do inside rules. It is > > really simple and understandable code. > > Yes, I think a special scripting language would be way outside the bounds > of > Pharo, but the rules idea simplicity of that style could be great for us :) > > Cheers, > Sean > > > > -- > View this message in context: > http://forum.world.st/TxTextMorph-based-on-new-text-model-tp4663219p4669991… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Feb. 14, 2013