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

Re: [Pharo-dev] [sbe] Pharo por Ejemplo vs Pharo en exemplos

by stephane ducasse

On May 21, 2013, at 8:47 AM, Oscar Nierstrasz <oscar(a)iam.unibe.ch> wrote: > > Be careful, there are many different forms of Spanish. The title should be consistent with the main text. We are not qualified to judge. Ask someone who knows the different dialects. Yes I know :) > > Oscar > > --- > Prof. Dr. O. Nierstrasz -- oscar(a)iam.unibe.ch > Software Composition Group -- http://scg.unibe.ch/oscar > University of Bern -- Tel/Fax +41 31 631.4618/3355 > > > On 2013-05-21, at 8:18, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi guys >> >> one guy mentions that Pharo en exemplos is a better translation than Pharo por Ejemplo so what is your point of view on that? >> >> Stef >> _______________________________________________ >> sbe mailing list >> sbe(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/sbe > > _______________________________________________ > sbe mailing list > sbe(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/sbe

May 21, 2013

Re: [Pharo-dev] TxText new version 0.8

by Denis Kudriashov

2013/5/20 stephane ducasse <stephane.ducasse(a)free.fr> > > Hello. > > New TxText version 0.8 is ready: > > - editor stuff extracted to separate packages TxText-Editor and > TxTextTests-Editor > > may be you should call the second package TxTextEditor-Tests > I just follow convention of other TxText packages: TxText-Model -> TxTextTests-Model, TxText-Layout -> TxTextTests-Layout and etc. Some times ago I suggest such repackaging and nobody was against it

May 21, 2013

Re: [Pharo-dev] TxText new version 0.8

by Denis Kudriashov

Hi. Sorry for late response. I have not internet yesterday. 2013/5/20 Igor Stasenko <siguctua(a)gmail.com> > On 19 May 2013 22:01, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > Hello. > > > > New TxText version 0.8 is ready: > > > > - editor stuff extracted to separate packages TxText-Editor and > > TxTextTests-Editor > > - edit decorators implemented: > > > > TxNoneEditDecorator- basic editing > then maybe it should be named as basiceditdecorator? > I named it "none" edit decorator because It actually not performs any decoration around basic editing operations. TxNoneEditDecorator just performs it. Concrete edit decorator can execute specific action on text to perform requested edit operation. There are three edit operations: #insertCharacters:at:, #removeNextCharacterAt:, #removePreviousCharacterAt:. They take aTextSelection as "at" argument. For example TxInsertModeEditDecorator extends text selection before characters insertion: TxInsertModeEditDecorato>>insertCharacters: aString at: aTextSelection aTextSelection isEmpty ifTrue: [aTextSelection end moveRight: aString size] aTextSelection replaceWith: aString > > > TxMaskedEditDecorator- input masked values like phone numbers > > TxInsertModeEditDecorator - input with "insert mode" where any new > character > > replace next one. > insert mode is actually opposite - inserts when you type. > replace mode is replaces when you type. > I choose this name because on Windows you have "insert key" to activate such mode in many text editors. > > > TxSmartCharsEditDecorator- input smart characters like ()[]{} > > TxSingleLineEditDecorator - general way to decorate editing with simple > > decoration format. TxSmartNumbersDecorationFormat is example. It > transform > > text with number format like: '10 000 000' or '10'000'000'. > > > btw, can you wrap decorators on top of each other i.e. > > Masked-SimgleLine > so i could have a single-line editor for entering only a phone number? > Now with mask decorator you have single line text field. Multilined mask is not supported (I dont try it actually). When you insert miltiline text to masked field only first line will be used. I make such restriction to simplify implementation. Actually I never see multilined masked field. Decorators can not be wrapped in general way. Maybe some of it. But there is no cases in current decorators. Main reason: most of decorators change cursor position with very specific way. And wrapping decorators will lead to unpredictable and useless results. Your example Masked-SingleLine (if mask can be multilined) is not about wrapping decorators. It is about input "filtering" . It is my next task. I want put at text morph specification of correct input. So you can forbid "cr" characters, can allow only numbers and etc. And at same time decorators can restrict input by its implementation requirements which happens with masked decorator. But edit decorators and "filters" are different concepts (I not choose name for "filters" yet). TxSingleLineEditDecorator implements general way to edit single line text with simple decoration format. Maybe it should be renamed. TxSingleLineEditDecorator transforms full text by decoration format after any edit operation. And it saves logical cursor position after transformation. Look at methods of TxSmartNumbersDecorationFormat as example. I will be happy if you introduce more clever names. Good names is difficult task for single brain. Especially if you are not native english speaker. But many of you already suggest different names. How we can agree on any one? Best regards, Denis > also, going ahead.. how easy/hard would be to implement a password input > field, > when model contains what user types, but display all *** chars? > > > According methods were added to TxTextMorph: > > > > #editDecorator: - set specific edit decorator (TxNoneEditDecorator by > > default) > > #inputContents - returns "native" value (undecorated). > > #displayedContents - returns raw text model asString > > > > See new examples on TxTextMorph class side. > > > > Best regards, > > Denis > > > > -- > Best regards, > Igor Stasenko. > >

May 21, 2013

Re: [Pharo-dev] [sbe] Pharo por Ejemplo vs Pharo en exemplos

by Oscar Nierstrasz

Be careful, there are many different forms of Spanish. The title should be consistent with the main text. We are not qualified to judge. Ask someone who knows the different dialects. Oscar --- Prof. Dr. O. Nierstrasz -- oscar(a)iam.unibe.ch Software Composition Group -- http://scg.unibe.ch/oscar University of Bern -- Tel/Fax +41 31 631.4618/3355 On 2013-05-21, at 8:18, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > one guy mentions that Pharo en exemplos is a better translation than Pharo por Ejemplo so what is your point of view on that? > > Stef > _______________________________________________ > sbe mailing list > sbe(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/sbe

May 21, 2013

Re: [Pharo-dev] collaborActive book refers to SS

by stephane ducasse

> About the current pull requests: > > - I merge 1 of them that correct some typo: > https://github.com/SquareBracketAssociates/PharoByExample-english/pull/18 > > I close (that was apparently an experiment from Ben): > https://github.com/SquareBracketAssociates/PharoByExample-english/pull/16 > > There is 2 pull requests left: > - https://github.com/SquareBracketAssociates/PharoByExample-english/pull/8 > Some work about DBXTalk done by Guile. Not sure if this work has been > integrated in PBE2 ? I will see him today. > - https://github.com/SquareBracketAssociates/PharoByExample-english/pull/19 > Some modifications proposed by Frank but this is for a new version of > PBE1 (for Pharo 2.0). > > Stef, apparently you remove everything related to PBE2 in this > repository. This is great ! > We should focused in this repository on PBE1 versions. > > Some months ago, I made a Pharo1.4 branch for updating the PBE1 book > to 1.4 but unfortunately no work has been done. > I think we can remove this branch now. > > Can we discuss about a workflow for managing the PBE1 versions. I > suggest using something like that: > http://nvie.com/posts/a-successful-git-branching-model/ > > The master branch used for last stable version of the book and a devel > branch for new version. > Comments ? something simple that I can manage please ;) For the fixes I would introduce them directly, BTW there are also the feedback of the japanese translators that we should have a look. > Regards, > > On Mon, May 20, 2013 at 11:13 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >> Thanks, Serge. >> >> frank >> >> On 20 May 2013 09:20, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: >>> Frank, nobody take care about pull issues on this repository. >>> There is 4 of them here : >>> https://github.com/SquareBracketAssociates/PharoByExample-english/pulls >>> I can try to merge some of them. >>> >>> Regards, >>> >>> On Sat, May 18, 2013 at 7:50 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>> Hi Stef, >>>> >>>> I mean this guy: >>>> https://github.com/SquareBracketAssociates/PharoByExample-english/pull/19 >>>> >>>> frank >>>> >>>> On 18 May 2013 15:52, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>>> frank you are about Pharo by example (which is hosted on github)? >>>>> >>>>> I'm checking because PBE2 is on github but this is an old version since I moved the chapter to svn. >>>>> >>>>> Stef >>>>> >>>>> >>>>> On May 16, 2013, at 12:44 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>>> >>>>>> >>>>>> On May 16, 2013, at 12:13 PM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>>>> >>>>>>> On 16 May 2013 10:38, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>>>>>> >>>>>>>> On May 16, 2013, at 11:23 AM, Frank Shearar <frank.shearar(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> http://book.pharo-project.org/book/Tidbits/FAQ/Packages/ >>>>>>>>> >>>>>>>>> talks about how you can create a SqueakSource project. Presumably we >>>>>>>>> want this to explain either how to create an SS3 project or a StHub >>>>>>>>> project? >>>>>>>>> >>>>>>>>> If all I need to do is issue a pull request to >>>>>>>>> https://github.com/SquareBracketAssociates/PharoByExample-english/ I'm >>>>>>>>> happy to update it to whichever you prefer. >>>>>>>> >>>>>>>> please do :) >>>>>>> >>>>>>> I'm guessing you'd want to point to StHub? >>>>>> >>>>>> yes >>>>>> >>>>>>> (I use ss3 for everything, >>>>>>> but it seems most of the Pharo devs are pushing for StHub.) >>>>>> >>>>>> Yes >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >>> >>> -- >>> Serge Stinckwich >>> UCBN & UMI UMMISCO 209 (IRD/UPMC) >>> Every DSL ends up being Smalltalk >>> http://www.doesnotunderstand.org/ >>> >> > > > > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ >

May 21, 2013

Pharo por Ejemplo vs Pharo en exemplos

by StÃ©phane Ducasse

Hi guys one guy mentions that Pharo en exemplos is a better translation than Pharo por Ejemplo so what is your point of view on that? Stef

May 21, 2013

[update 3.0] #30149

by Marcus Denker

30149 ----- 10687 VistaryThemeIcons class cannot be initialized https://pharo.fogbugz.com/f/cases/10687 10689 Finder>>#computeWithMethodFinder: directly references ReturnNode https://pharo.fogbugz.com/f/cases/10689 10690 Remove two unused classes from old compiler https://pharo.fogbugz.com/f/cases/10690 10693 SmalltalkEditorTest testCompilationOfUndefinedVar references UndeclaredVariable Exception https://pharo.fogbugz.com/f/cases/10693 10694 Force old compiler CompilerEvaluationTest https://pharo.fogbugz.com/f/cases/10694/ Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tools-MarcusDenker.1128.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Tests-MarcusDenker.539.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/Polymorph-Widgets-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/CompilerTests-MarcusDenker.16… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Compiler-MarcusDenker.465.diff

May 21, 2013

Re: [Pharo-dev] Spec Dialogs auto-accepting text

by Benjamin

Indeed, maybe it should. I have hit this a couple of time too Ben On May 21, 2013, at 12:01 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I started out writing this surprised that spec dialogs don't autoaccept their > text fields by default. Now, I'm not sure whether they should, but in case > anyone else runs into this... > > aDialogWindowModel okAction: [ > aDialogWindowModel window applyChanges. > ... ]. > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Spec-Dialogs-auto-accepting-text-tp4688649.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

May 20, 2013

Spec Dialogs auto-accepting text

by Sean P. DeNigris

I started out writing this surprised that spec dialogs don't autoaccept their text fields by default. Now, I'm not sure whether they should, but in case anyone else runs into this... aDialogWindowModel okAction: [ aDialogWindowModel window applyChanges. ... ]. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spec-Dialogs-auto-accepting-text-tp4688649.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 20, 2013

Re: [Pharo-dev] Bug in SimpleSwitchMorph

by Benjamin

I will try to have a look tomorrow afternoon :) Ben On May 20, 2013, at 10:50 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi > > It seems that the bug is link with the fact that the cursor get outside the bounds or not. > If you click and do not move or move but stay inside the morph it is ok > Now if you click and the mouse gets outside the bounds we get the funny and bad behavior. > > I'm definitely exhausted now to thinkâ¦. but here is the code for the night hackers :) > > > > > mouseDown: evt > > oldColor := self fillStyle. > > mouseMove: evt > > (self containsPoint: evt cursorPoint) > ifTrue: [self setSwitchState: (oldColor = offColor)] > ifFalse: [self setSwitchState: (oldColor = onColor)]. > > mouseUp: evt > > (self containsPoint: evt cursorPoint) > ifTrue: [ "toggle and do action" > self setSwitchState: (oldColor = offColor). > self doButtonAction] > ifFalse: [ "restore old appearance" > self setSwitchState: (oldColor = onColor)]. > >

May 20, 2013