- Pharo-dev - lists.pharo.org

[ANN] Pomodoro 1.6 for Pharo 5 + video

by Torsten Bergmann

I did a new pass on the Pomodoro timer for Pharo 5: - settings with custom start value and custom colors - better resizing behavior of the morph - pause/continue - start/restart possibility - default colors aligned with Pharo scheme - pause state in Pomodoro instead of Morph - separate core and tests in own packages all included in a new release 1.6. Just use Spotter/Catalog to load. Enjoy the new video: http://youtu.be/voSUzOu5feU Bye T.

April 6, 2016

Re: [Pharo-dev] TxText model

by Stephan Eggermont

On 06-04-16 19:31, Sean P. DeNigris wrote: > [rant]I find the whole text system very confusing. What the heck does > a paragraph know about insertion points?? A view has one paragraph > object, even if there are several paragraphs (as understood by the > rest of humanity as a block of text with breaks between the adjoining > ones. Editors and Paragraphs are thrown out and replaced on a whim. > I'm finding it very hard to understand and modify[/rant] [1] [rant] Of > course, the instant I touched Paragraph/XxxEditor, and friends I got > lost down the rabbit hole of incomprehensibility... like Paragraph, > which draws the cursor and keeps track of the selection, obviously... > not! wtf ?! There is both a lot of inherent, as well as accidental complexity there. Paragraph is obviously not such a good name for what it does, but at least it has a clear comment saying what it's for. It seems the right place to deal with the display parts of selection, though delegating that to a separate class might clean up things a bit. The number of things that are just broken is rather annoying as is the lack of tests and examples. Stephan

April 6, 2016

Re: [Pharo-dev] TxText model

by Denis Kudriashov

2016-04-06 19:31 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > (As it is based on TxText (or a fork) maybe it isn't that difficult to add > rendering on athens ?) It should be not difficult. In Twisty end rendering on canvas is just 1% of code (or less). I plan to adopt it for Bloc. And for this I will need Athens. And I think Bloc will simplify it a bit. TwyTextMorph implements similar concept of Bloc design which can be used directly.

April 6, 2016

Re: [Pharo-dev] TxText model

by Henrik Nergaard

The only thing required for styling is to specify the attributes for the runs associated with the text. A simple example: | text attributes oldRuns clr| text := (String loremIpsum: 1234) asText. attributes := Array new: text size. clr := TextColor color: Color random. 1 to: text size do: [ :index | attributes at: index put: { clr. TextFontChange font2 }. (text at: index) isSeparator ifTrue: [ clr := TextColor color: Color random ] ]. text runs: (RunArray newFrom: attributes). text Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Nicolai Hess Sent: Wednesday, April 6, 2016 8:23 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: Re: [Pharo-dev] TxText model 2016-04-06 18:11 GMT+02:00 phil(a)highoctane.be<mailto:phil@highoctane.be> <phil(a)highoctane.be<mailto:phil@highoctane.be>>: Ok. Call me stupid but in Pharo I don't see how to do that easily. Phil At least for Rubric, it can not be that difficult. I saw a GT-Inspector with a XML-styer On Wed, Apr 6, 2016 at 5:41 PM, Stephan Eggermont <stephan(a)stack.nl<mailto:stephan@stack.nl>> wrote: On 06-04-16 11:13, phil(a)highoctane.be<mailto:phil@highoctane.be> wrote: Another pain is the styling of text where the only styler we have is the SHSt80Styler (class name out of my mind, need to check) and that's a huge pain to support other stylings. Styling with different stylers worked in TextMorph. In Squeak it is easy to add styling for a different language in the class browser. Levente did that for PostgreSQLv3. Stephan

April 6, 2016

Re: [Pharo-dev] TxText model

by Nicolai Hess

2016-04-06 18:11 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > Ok. Call me stupid but in Pharo I don't see how to do that easily. > > Phil > At least for Rubric, it can not be that difficult. I saw a GT-Inspector with a XML-styer > > On Wed, Apr 6, 2016 at 5:41 PM, Stephan Eggermont <stephan(a)stack.nl> > wrote: > >> On 06-04-16 11:13, phil(a)highoctane.be wrote: >> >>> Another pain is the styling of text where the only styler we have is the >>> SHSt80Styler (class name out of my mind, need to check) and that's a huge >>> pain to support other stylings. >>> >> >> Styling with different stylers worked in TextMorph. In Squeak it is easy >> to add styling for a different language in the class browser. Levente did >> that for PostgreSQLv3. >> >> Stephan >> >> >> >

April 6, 2016

Re: [Pharo-dev] TxText model

by phil＠highoctane.be

I have two or three Moleskine books full of notes about all of this text stuff. Still a maddening thing to deal with. Especially when you send wrong things and the whole UI freezes all over. Phil On Wed, Apr 6, 2016 at 7:31 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > > What are the main problems with Text, Paragraph, ... and other old > > TextComponents? > > And how are these solved with TxText? > > Stephan Eggermont wrote > >> |t1 t2 ball page| > >> page := Morph new. > >> ... > > Yes, this example brackets the situation quite nicely. The current text > system "makes hard things easy, and the easy things impossible". Text > winding around little Morphic tubes, while the coolest thing ever, is > rarely > useful, but try changing the caret and you will end up in hell: > > [rant]I find the whole text system very confusing. What the heck > does a > paragraph know about insertion points?? A view has one paragraph object, > even if there are several paragraphs (as understood by the rest of humanity > as a block of text with breaks between the adjoining ones. Editors and > Paragraphs are thrown out and replaced on a whim. I'm finding it very hard > to understand and modify[/rant] [1] > > [rant] > Of course, the instant I touched Paragraph/XxxEditor, and friends > I got > lost down the rabbit hole of incomprehensibility... like Paragraph, which > draws the cursor and keeps track of the selection, obviously... not! wtf ?! > > Quick definition... > paragraph |ËparÉËgraf| > noun > a distinct section of a piece of writing, usually dealing with a > single > theme and indicated by a new line, indentation, or numbering. > > Where, tell me, does it say anything about cursors and selections?? > [/rant] [2] > > 1. > > http://forum.world.st/Customizing-the-Caret-of-a-PluggableTextMorph-tt46402… > 2. http://forum.world.st/Re-Vim-Keys-tt4657381.html#a4657594 > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/TxText-model-tp4888199p4888748.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 6, 2016

Re: [Pharo-dev] TxText model

by Igor Stasenko

On 6 April 2016 at 20:31, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2016-04-06 18:00 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > >> >> >> On 6 April 2016 at 18:34, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >> >>> >>> Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko" <siguctua(a)gmail.com>: >>> > >>> > btw, >>> > >>> > if you wanna feel a difference, why we wanted vector based rendering, >>> by yourself, open: >>> > >>> > Morph comment asText asMorph openInSceneView >>> > >>> > and then >>> > >>> > | sceneView view | >>> > sceneView := AthensSceneView new. >>> > view := TxAthensLayoutView on: Morph comment asTxModel extent: 400@400. >>> > >>> > sceneView scene: view. >>> > sceneView openInWindow >>> > >>> > >>> > and try zooming it in and out with mouse wheel. >>> > >>> > >>> >>> I know it's limitation. My point was, that it is not impossible, or >>> depends an the model Text vs. TxModel, alone. >>> >> Of course it doesn't depends on either of those. But it wasn't an answer >> concerning model, but you question why i had to abandon idea to keep using >> DisplayScanner & friends. >> > > Sure, but as you talked about limitiations solved by TxText, I thought > about limitation for building editor/tools around Text or TxText. > I see that you had rendering vector based graphics with TxText and Athens. > What I want to see, is a Text-Tool framework for building custom editors > or easily add features (code tools or tools for other kinds of text). > Rubric comes close, it has some good features for text decorations. > Twisty looks promisinig too, I like that it is build on similar classes > like TxText but looks more finished. > (As it is based on TxText (or a fork) maybe it isn't that difficult to add > rendering on athens ?) > > I payed attention to make things modular. Things like model, layout and view, and then text editor, forming layers and replaceable or close to it. As in snippet of code above, it demonstrates, that you can easily use just layout view, just for text rendering, without paying any attention to higher level things, like text editor, events and UI. Now try doing this with morphic TextMorph. It is far from ideal, and missing a number of features. So, if you see how you can improved - feel free to do it. > >> >> -- >> Best regards, >> Igor Stasenko. >> > > -- Best regards, Igor Stasenko.

April 6, 2016

Re: [Pharo-dev] TxText model

by Nicolai Hess

2016-04-06 18:00 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > > > On 6 April 2016 at 18:34, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > >> >> Am 06.04.2016 5:21 nachm. schrieb "Igor Stasenko" <siguctua(a)gmail.com>: >> > >> > btw, >> > >> > if you wanna feel a difference, why we wanted vector based rendering, >> by yourself, open: >> > >> > Morph comment asText asMorph openInSceneView >> > >> > and then >> > >> > | sceneView view | >> > sceneView := AthensSceneView new. >> > view := TxAthensLayoutView on: Morph comment asTxModel extent: 400@400. >> > >> > sceneView scene: view. >> > sceneView openInWindow >> > >> > >> > and try zooming it in and out with mouse wheel. >> > >> > >> >> I know it's limitation. My point was, that it is not impossible, or >> depends an the model Text vs. TxModel, alone. >> > Of course it doesn't depends on either of those. But it wasn't an answer > concerning model, but you question why i had to abandon idea to keep using > DisplayScanner & friends. > Sure, but as you talked about limitiations solved by TxText, I thought about limitation for building editor/tools around Text or TxText. I see that you had rendering vector based graphics with TxText and Athens. What I want to see, is a Text-Tool framework for building custom editors or easily add features (code tools or tools for other kinds of text). Rubric comes close, it has some good features for text decorations. Twisty looks promisinig too, I like that it is build on similar classes like TxText but looks more finished. (As it is based on TxText (or a fork) maybe it isn't that difficult to add rendering on athens ?) > > > -- > Best regards, > Igor Stasenko. >

April 6, 2016

Re: [Pharo-dev] TxText model

by Sean P. DeNigris

> What are the main problems with Text, Paragraph, ... and other old > TextComponents? > And how are these solved with TxText? > Stephan Eggermont wrote >> |t1 t2 ball page| >> page := Morph new. >> ... Yes, this example brackets the situation quite nicely. The current text system "makes hard things easy, and the easy things impossible". Text winding around little Morphic tubes, while the coolest thing ever, is rarely useful, but try changing the caret and you will end up in hell: [rant]I find the whole text system very confusing. What the heck does a paragraph know about insertion points?? A view has one paragraph object, even if there are several paragraphs (as understood by the rest of humanity as a block of text with breaks between the adjoining ones. Editors and Paragraphs are thrown out and replaced on a whim. I'm finding it very hard to understand and modify[/rant] [1] [rant] Of course, the instant I touched Paragraph/XxxEditor, and friends I got lost down the rabbit hole of incomprehensibility... like Paragraph, which draws the cursor and keeps track of the selection, obviously... not! wtf ?! Quick definition... paragraph |ËparÉËgraf| noun a distinct section of a piece of writing, usually dealing with a single theme and indicated by a new line, indentation, or numbering. Where, tell me, does it say anything about cursors and selections?? [/rant] [2] 1. http://forum.world.st/Customizing-the-Caret-of-a-PluggableTextMorph-tt46402… 2. http://forum.world.st/Re-Vim-Keys-tt4657381.html#a4657594 ----- Cheers, Sean -- View this message in context: http://forum.world.st/TxText-model-tp4888199p4888748.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 6, 2016

Re: [Pharo-dev] [ bloc ] I do not understand why some behavior is not in the right place

by Ben Coman

On Wed, Apr 6, 2016 at 4:36 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > That explains, why, there initially certain features of Cairo, that not > exposed by Athens. > It is not because we can't or just don't care.. we do.. But only after we > can see that it consistent with rest of API and can be easily implemented on > most of other potential backends. > Yes, i am talking about that damn 'minimal common denominator' problem. :) > > Oh, and also i forgot to mention, that there could be also 2 more potential > backends: > - OpenVG > and > - Quartz, that is a vector graphics library for Mac OS and Vulkan? and thanks for writing up that explanation on Athens. cheers -ben

April 6, 2016