- Pharo-users - lists.pharo.org

Re: [Pharo-users] Final 1.4 images...

by Bernat Romagosa

Thanks Benjamin! I've just submitted the bug and a pointer to where you can find the code that did the formatting in OB. Here's the issue: http://code.google.com/p/pharo/issues/detail?id=5664&thanks=5664 Cheers! 2012/4/20 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > I try hard to read mails :) > (and I have a magic rule which colorize mails with Nautilus in the body of > the mail ^^) > > For the format, I could add it ^^ > > Open a bug entry, it's better than just mails ^^ > > Thanks for your feedback, > > Ben > > On Apr 20, 2012, at 6:54 PM, Mariano Martinez Peck wrote: > > > > On Fri, Apr 20, 2012 at 6:50 PM, Bernat Romagosa < > tibabenfortlapalanca(a)gmail.com> wrote: > >> Thanks Mariano, >> >> I tried installing OmniBrowser but I couldn't manage to get autocomplete >> working. Now I just installed Nautilus and it works great, I'm only missing >> the "format" shortcut... anyone know if it's possible to get this feature >> in Nautilus? >> > > Whatever you need ask Benjamin Van Ryseghem ;) You have nothing to loose. > BUT, do not expect him to read all emails. So..start a clear email with a > clear subject like "format code in Nautilus" or directly open an issue and > cc' him. > Just in case, I wrote something about Nautilus: > http://marianopeck.wordpress.com/2012/02/26/nautilus-the-reborn-of-the-syst… > It is a little bit outdated but you will get an idea. > > Cheers > > >> >> Cheers! >> >> 2012/4/20 Mariano Martinez Peck <marianopeck(a)gmail.com> >> >>> >>> >>> On Fri, Apr 20, 2012 at 12:03 PM, Bernat Romagosa < >>> tibabenfortlapalanca(a)gmail.com> wrote: >>> >>>> One more thing, how does one rename a method? Was this option removed >>>> from the browser? >>>> >>>> >>> The problem is that the image you are using comes by default with a >>> limited system browser. It does not know anything about refactorings. >>> To have a really development image, install Nautilus on it. Imagine you >>> are using like the previous PharoCore + code completion + shout >>> >>> >>> >>>> >>>> 2012/4/20 Bernat Romagosa <tibabenfortlapalanca(a)gmail.com> >>>> >>>>> Congratulations, Pharo 1.4 looks really neat and so far very usable! >>>>> >>>>> Just one thing, what happened to the format shortcut (control+r)? I >>>>> use it all the time, like three times per method I write... is it possible >>>>> to get it back? :) >>>>> >>>>> Cheers, >>>>> >>>>> Bernat. >>>>> >>>>> >>>>> 2012/4/19 Marcus Denker <marcus.denker(a)inria.fr> >>>>> >>>>>> We added more infos in the worspace: >>>>>> >>>>>> https://gforge.inria.fr/frs/download.php/30620/Pharo-1.4-14438.zip >>>>>> >>>>>> https://gforge.inria.fr/frs/download.php/30621/Pharo-1.4-14438-OneClick.zip >>>>>> >>>>>> >>>>>> On Apr 18, 2012, at 2:39 PM, Marcus Denker wrote: >>>>>> >>>>>> > Hi, >>>>>> > >>>>>> > final images: >>>>>> > >>>>>> > One-Click: >>>>>> > >>>>>> > >>>>>> https://gforge.inria.fr/frs/download.php/30615/Pharo-1.4-14437-OneClick.zip >>>>>> > >>>>>> > Just image: >>>>>> > >>>>>> https://gforge.inria.fr/frs/download.php/30613/Pharo-1.4-14437.zip >>>>>> > >>>>>> > already linked on >>>>>> > >>>>>> > http://www.pharo-project.org/pharo-download/release-1-4 >>>>>> > >>>>>> > >>>>>> > -- >>>>>> > Marcus Denker -- http://marcusdenker.de >>>>>> > >>>>>> >>>>>> -- >>>>>> Marcus Denker -- http://marcusdenker.de >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Bernat Romagosa. >>>>> >>>> >>>> >>>> >>>> -- >>>> Bernat Romagosa. >>>> >>> >>> >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >>> >> >> >> -- >> Bernat Romagosa. >> > > > > -- > Mariano > http://marianopeck.wordpress.com > > > -- Bernat Romagosa.

April 23, 2012

Re: [Pharo-users] truly basic terminal emulation

by Camillo Bruni

On 2012-04-22, at 22:00, Daniel Lyons wrote: > Cami, > > On Apr 22, 2012, at 1:32 PM, Camillo Bruni wrote: > >>> It doesn't seem to recognize Pragmata Pro or any other font name I put in, I always get the default font I set in my preferences (which is a system font and works fine). I see there's a FixedFaceFont class, but it looks like a completely different sort of thing. >> >> indeed maybe a workspace will do just fine then :), sadly I'm not that much into morphic hence my partial approach here (that's why I personally find it far easier to directly use the terminal)... > > Yes, it probably would be, but I think the Smalltalk environment contains great power, I just need to learn enough to harness it, and that means baby steps. well smalltalk spent too much time in the image, it kind of blinds you after some years :). plus by using the terminal you don't leave the environment at all, since you still control everything from within the image. >> - check that you have freetype enabled in your settings (otherwise system fonts won't be recognized) > > It is, and it works great, I'm using a system font everywhere else. I take it the invocation I used was not incorrect then? > >> - as a pragmatic solution I'd change the coding font globally to fixed-width (default in my images since I cannot program in a non mono-spaced font :P) > > I can live with that for a while. > >> "open a new workspace " >> ws := Workspace openContents: 'Initial Contents' >> " update the contents of the workspace" >> ws contents: 'new Contents' > > OK, I can do that for writing, but for reading, I will need the read message to block until I type a character. Is there a way to do that with the workspace? I guess there is a nicer way to plug things together, but I'd say keep an external text / String / readline and update the contents of the workspace each time they changed... I suggest you read the corresponding chapters in http://pharobyexample.org/ that should help you with most of the UI questions >>> I also don't see how to get started with your Readline implementation. I'm sure I'd like to use it eventually but I want to get something basic working that I can understand first. >> >> for the readline stuff check the test (that's generally the best place to see how code works ;) >> see class: RLReadlineTest >> >> a small example is given in RLReadline >> #readlineExample >> >> the basic principle is that you move around a cursor and put characters / strings there: >> >> RLReadline >> #write: >> RLReadline >> #writeAll: >> >> I know the readline implementation is quite complex for what it does, but you shouldn't bother too much and simply rely on the public interface and the example use-cases provided by the tests. > > > Thanks, I'll dig through that later tonight. > > â > Daniel Lyons > >

April 22, 2012

Re: [Pharo-users] truly basic terminal emulation

by Daniel Lyons

On Apr 22, 2012, at 9:53 AM, Daniel Lyons wrote: > font := TextFontReference toFont: (StrikeFont familyName: 'Pragmata Pro' size: 16). OK, this works if I use LogicalFont instead: textArea := TextMorph new contents: ('This is a test' asText addAttribute: (TextFontReference toFont: (LogicalFont familyName: 'Consolas' pointSize: 14))) I bet there is a more abstract way of locating a font than using one of these two classes. â Daniel Lyons

April 22, 2012

Re: [Pharo-users] truly basic terminal emulation

by Daniel Lyons

Cami, On Apr 22, 2012, at 1:32 PM, Camillo Bruni wrote: >> It doesn't seem to recognize Pragmata Pro or any other font name I put in, I always get the default font I set in my preferences (which is a system font and works fine). I see there's a FixedFaceFont class, but it looks like a completely different sort of thing. > > indeed maybe a workspace will do just fine then :), sadly I'm not that much into morphic hence my partial approach here (that's why I personally find it far easier to directly use the terminal)... Yes, it probably would be, but I think the Smalltalk environment contains great power, I just need to learn enough to harness it, and that means baby steps. > - check that you have freetype enabled in your settings (otherwise system fonts won't be recognized) It is, and it works great, I'm using a system font everywhere else. I take it the invocation I used was not incorrect then? > - as a pragmatic solution I'd change the coding font globally to fixed-width (default in my images since I cannot program in a non mono-spaced font :P) I can live with that for a while. > "open a new workspace " > ws := Workspace openContents: 'Initial Contents' > " update the contents of the workspace" > ws contents: 'new Contents' OK, I can do that for writing, but for reading, I will need the read message to block until I type a character. Is there a way to do that with the workspace? >> I also don't see how to get started with your Readline implementation. I'm sure I'd like to use it eventually but I want to get something basic working that I can understand first. > > for the readline stuff check the test (that's generally the best place to see how code works ;) > see class: RLReadlineTest > > a small example is given in RLReadline >> #readlineExample > > the basic principle is that you move around a cursor and put characters / strings there: > > RLReadline >> #write: > RLReadline >> #writeAll: > > I know the readline implementation is quite complex for what it does, but you shouldn't bother too much and simply rely on the public interface and the example use-cases provided by the tests. Thanks, I'll dig through that later tonight. â Daniel Lyons

April 22, 2012

Re: [Pharo-users] truly basic terminal emulation

by Camillo Bruni

On 2012-04-22, at 17:53, Daniel Lyons wrote: > > On Apr 21, 2012, at 1:19 PM, Camillo Bruni wrote: >> well you could also plug my readline implementation to any text morph and >> set the a monospace font as default for code :) (that's what I have anyway). >> >> Manually creating a text morph an changing it's font to some fixed-width >> version is not that hard. And then depending on your needs you would simply >> edit / change the underlying text (in this case with even my readline implementation)... > > I believe you but I seem to need a bit more explicit hand-holding. For example, when I create a new text morph, it winds up on the screen by itself with no enclosing window. Using the code derived from the TextMorph class comment: > > font := TextFontReference toFont: (StrikeFont familyName: 'Pragmata Pro' size: 16). > tMorph := TextMorph new. > t1 := 'This is fixed-width' asText addAttribute: font. > tMorph contents: t1. > tMorph openInHand. > > It doesn't seem to recognize Pragmata Pro or any other font name I put in, I always get the default font I set in my preferences (which is a system font and works fine). I see there's a FixedFaceFont class, but it looks like a completely different sort of thing. indeed maybe a workspace will do just fine then :), sadly I'm not that much into morphic hence my partial approach here (that's why I personally find it far easier to directly use the terminal)... - check that you have freetype enabled in your settings (otherwise system fonts won't be recognized) - as a pragmatic solution I'd change the coding font globally to fixed-width (default in my images since I cannot program in a non mono-spaced font :P) "open a new workspace " ws := Workspace openContents: 'Initial Contents' " update the contents of the workspace" ws contents: 'new Contents' > I also don't see how to get started with your Readline implementation. I'm sure I'd like to use it eventually but I want to get something basic working that I can understand first. for the readline stuff check the test (that's generally the best place to see how code works ;) see class: RLReadlineTest a small example is given in RLReadline >> #readlineExample the basic principle is that you move around a cursor and put characters / strings there: RLReadline >> #write: RLReadline >> #writeAll: I know the readline implementation is quite complex for what it does, but you shouldn't bother too much and simply rely on the public interface and the example use-cases provided by the tests. best cami

April 22, 2012

Re: [Pharo-users] truly basic terminal emulation

by Daniel Lyons

On Apr 21, 2012, at 1:19 PM, Camillo Bruni wrote: > well you could also plug my readline implementation to any text morph and > set the a monospace font as default for code :) (that's what I have anyway). > > Manually creating a text morph an changing it's font to some fixed-width > version is not that hard. And then depending on your needs you would simply > edit / change the underlying text (in this case with even my readline implementation)... I believe you but I seem to need a bit more explicit hand-holding. For example, when I create a new text morph, it winds up on the screen by itself with no enclosing window. Using the code derived from the TextMorph class comment: font := TextFontReference toFont: (StrikeFont familyName: 'Pragmata Pro' size: 16). tMorph := TextMorph new. t1 := 'This is fixed-width' asText addAttribute: font. tMorph contents: t1. tMorph openInHand. It doesn't seem to recognize Pragmata Pro or any other font name I put in, I always get the default font I set in my preferences (which is a system font and works fine). I see there's a FixedFaceFont class, but it looks like a completely different sort of thing. I also don't see how to get started with your Readline implementation. I'm sure I'd like to use it eventually but I want to get something basic working that I can understand first. Thanks again, â Daniel Lyons

April 22, 2012

Re: [Pharo-users] truly basic terminal emulation

by Camillo Bruni

On 2012-04-21, at 18:51, Daniel Lyons wrote: > > On Apr 21, 2012, at 5:34 AM, Camillo Bruni wrote: > >> runnnig it from real stdin / stdout won't help you? >> Cause that's what I did with my readline implementation: >> >> - open an image from the command-line >> - run a readline instance in the image using FileStream stdout as output >> - test my implementation with the image and the real terminal side-by-side > > I suppose I could, but I was hoping to have it working inside Smalltalk. Also for didactic purposes. I intend to write something to visualize the registers in the CPU next. Is it the fixed-width font that's making it difficult to do from a UI inside Pharo? I could certainly compromise on that. well you could also plug my readline implementation to any text morph and set the a monospace font as default for code :) (that's what I have anyway). Manually creating a text morph an changing it's font to some fixed-width version is not that hard. And then depending on your needs you would simply edit / change the underlying text (in this case with even my readline implementation)... Check my implementation at: http://ss3.gemstone.com/ss/readline.html

April 21, 2012

Re: [Pharo-users] truly basic terminal emulation

by Daniel Lyons

On Apr 21, 2012, at 5:34 AM, Camillo Bruni wrote: > runnnig it from real stdin / stdout won't help you? > Cause that's what I did with my readline implementation: > > - open an image from the command-line > - run a readline instance in the image using FileStream stdout as output > - test my implementation with the image and the real terminal side-by-side I suppose I could, but I was hoping to have it working inside Smalltalk. Also for didactic purposes. I intend to write something to visualize the registers in the CPU next. Is it the fixed-width font that's making it difficult to do from a UI inside Pharo? I could certainly compromise on that. â Daniel Lyons

April 21, 2012

Re: [Pharo-users] truly basic terminal emulation

by Camillo Bruni

runnnig it from real stdin / stdout won't help you? Cause that's what I did with my readline implementation: - open an image from the command-line - run a readline instance in the image using FileStream stdout as output - test my implementation with the image and the real terminal side-by-side On 2012-04-21, at 10:34, Daniel Lyons wrote: > > On Apr 21, 2012, at 2:17 AM, StÃ©phane Ducasse wrote: >> Ahhhh >> have a look at transcripter :) >> because you will get an simple repl >> Why a workspace is not enough for you :) > > They might be! Sorry if I'm being dense. :) > > I hate to ask for this much hand-holding, but I'm just not seeing how it's done. Supposing I have an object with a #writeCharacter:aChar and #readCharacter selectors that read and write a character to/from the device respectively, what do I need to do to hook that object up to a Transcripter or a Workspace? And how can I force the font to be fixed-width? > > Thanks again, > > â > Daniel Lyons > >

April 21, 2012

Re: [Pharo-users] truly basic terminal emulation

by Daniel Lyons

On Apr 21, 2012, at 2:17 AM, StÃ©phane Ducasse wrote: > Ahhhh > have a look at transcripter :) > because you will get an simple repl > Why a workspace is not enough for you :) They might be! Sorry if I'm being dense. :) I hate to ask for this much hand-holding, but I'm just not seeing how it's done. Supposing I have an object with a #writeCharacter:aChar and #readCharacter selectors that read and write a character to/from the device respectively, what do I need to do to hook that object up to a Transcripter or a Workspace? And how can I force the font to be fixed-width? Thanks again, â Daniel Lyons

April 21, 2012