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

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

by Andrei Chis

Hi Stef, Which build/version are you using? These methods are removed in the latest version. You can download the latest version from the Moose CI. From the bloc project you need the bleeding edge build. The link to this version is here: https://ci.inria.fr/moose/job/bloc/PHARO=alpha,VERSION=bleedingEdge,VM=vmLa… Cheers, Andrei On Mon, Apr 4, 2016 at 5:17 PM, stepharo <stepharo(a)free.fr> wrote: > BlElement >>drawStrokeOnAthensCanvas: aCanvas > "Actually render stroke of a receiver on aCanvas in local bounds. > Override to customize. > aCanvas is an instance of AthensCanvas > aCanvas must not be nil" > | pathTransform strokePath strokeScaling strokeOffset | > > "fast exit if stroke has no width or it is transparent" > (self shape strokePaint width <= 0 or: [ self shape strokePaint > isTransparent ]) > ifTrue: [ ^ self ]. > > pathTransform := aCanvas pathTransform. > strokePath := self shape path strokePathOn: aCanvas. > strokeScaling := self shape path strokeScaling. > strokeOffset := self shape path strokeOffset. > > pathTransform restoreAfter:[ > pathTransform translateBy: strokeOffset * strokeScaling. > pathTransform scaleBy: strokeScaling. > aCanvas > setPaint: self shape strokePaint; > drawShape: strokePath ] > > > > > BlElement >>drawFillOnAthensCanvas: aCanvas > "Actually render fill of a receiver on aCanvas in local bounds. > Override to customize. > aCanvas is an instance of AthensCanvas > aCanvas must not be nil" > | pathTransform fillPath fillScaling fillOffset | > pathTransform := aCanvas pathTransform. > > "fast exit if fill is transparent" > (self shape fillPaint isTransparent) > ifTrue: [ ^ self ]. > > fillPath := self shape path fillPathOn: aCanvas. > fillScaling := self shape path fillScaling. > fillOffset := self shape path fillOffset. > > pathTransform restoreAfter: [ > pathTransform translateBy: fillOffset * fillScaling. > pathTransform scaleBy: fillScaling. > aCanvas > setPaint: self shape fillPaint; > drawShape: fillPath ] > >

April 4, 2016

Re: [Pharo-dev] TxText model

by Thierry Goubier

2016-04-04 17:10 GMT+02:00 Stephan Eggermont <stephan(a)stack.nl>: > On 04-04-16 16:49, Thierry Goubier wrote: > >> Framemaker-like or web-page like? Thierry >> > Framemaker. Really challenging. Did you had a look at the Doc code (of Design Pattern fame)? It has allways been freely available. Thierry

April 4, 2016

[ bloc ] I do not understand why some behavior is not in the right place

by stepharo

BlElement >>drawStrokeOnAthensCanvas: aCanvas "Actually render stroke of a receiver on aCanvas in local bounds. Override to customize. aCanvas is an instance of AthensCanvas aCanvas must not be nil" | pathTransform strokePath strokeScaling strokeOffset | "fast exit if stroke has no width or it is transparent" (self shape strokePaint width <= 0 or: [ self shape strokePaint isTransparent ]) ifTrue: [ ^ self ]. pathTransform := aCanvas pathTransform. strokePath := self shape path strokePathOn: aCanvas. strokeScaling := self shape path strokeScaling. strokeOffset := self shape path strokeOffset. pathTransform restoreAfter:[ pathTransform translateBy: strokeOffset * strokeScaling. pathTransform scaleBy: strokeScaling. aCanvas setPaint: self shape strokePaint; drawShape: strokePath ] BlElement >>drawFillOnAthensCanvas: aCanvas "Actually render fill of a receiver on aCanvas in local bounds. Override to customize. aCanvas is an instance of AthensCanvas aCanvas must not be nil" | pathTransform fillPath fillScaling fillOffset | pathTransform := aCanvas pathTransform. "fast exit if fill is transparent" (self shape fillPaint isTransparent) ifTrue: [ ^ self ]. fillPath := self shape path fillPathOn: aCanvas. fillScaling := self shape path fillScaling. fillOffset := self shape path fillOffset. pathTransform restoreAfter: [ pathTransform translateBy: fillOffset * fillScaling. pathTransform scaleBy: fillScaling. aCanvas setPaint: self shape fillPaint; drawShape: fillPath ]

April 4, 2016

Re: [Pharo-dev] TxText model

by Thierry Goubier

2016-04-04 17:07 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > > >> For now, external objects can't extend below the baseline. >> > > Slightly not like that. An external object are bound to concrete position > in text. And layout of a single line are computed based on dimensions of > that object, as well as dimensions of other parts of a line. The text flow > are not affected by the object in terms that there is no capability to > compute wrapping text around it or align it left/right whatever separately > from text. It means that basically external object is like a special kind > of glyph/icon that uses same layout rules as character glyphs, but just > rendered separately. > I understood as much. I've just seen code that such a "special" glyph can only contribute to text ascent (since, per comment, it is aligned to the baseline). Not very important, just a detail. > >> >> Position inside spans can be ambiguous: last position of a span and first >> position of the next span are the same position. >> >> Well, for some operation the are treated as same, for some - don't. > Since there's nothing can be between two positions at the ends of adjacent > spans, from standpoint of user they represent same position in text. But > from standpoint of model they are different since position are belong to > different spans. > Sure thing, there certain pieces added to avoid problems with such > ambiguity, so that it don't causing problems on user-level. > Ok. Thierry

April 4, 2016

Re: [Pharo-dev] TxText model

by Igor Stasenko

On 4 April 2016 at 17:47, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2016-04-04 16:11 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> It is. Five packages, 1609 + 2647 lines of code (excluding tests and >> styler). >> >> I think Denis has worked on it (and extended it). >> > > History was that: > At some point I realised that I can't use old TextMorph anymore. For my > project I needed flexible editors which allows me implement validation, > mask fields, secrete fields and others. It was almost impossible to hack > old text morph to support these features. > I read about Igor project TxText. It included only model at that time > which was very similar to my ideas. So I decided to implement editors on > top of it. I was try to not touch model itself and only fix bugs. But > during development I saw all weakness of model and I start refactoring with > idea of active text which announces any changes. > And in same time Igor returned to this project. He saw all problems with > model and started refactoring too. But his idea was opposite to my. > I would not say it opposite. You see, you started implementing advanced features, right from the beginning, while we didn't even finished the basic set of features, like simple text input/editing. The only 'opposite' to your direction was decision to stop thinking upfront how much steroids we can put into model & editor and concentrate on completing a bare bone feature set, so that we can replace morphic text editor with it. Adding steroids can wait :) > At the end I forked my refactored version of TxText into separate project > Twisty. So I think current TxText not includes any my code. > > > Glad to hear that you did not thrown away your project. -- Best regards, Igor Stasenko.

April 4, 2016

Re: [Pharo-dev] TxText model

by Stephan Eggermont

On 04-04-16 16:49, Thierry Goubier wrote: > Framemaker-like or web-page like? Thierry Framemaker. Stephan

April 4, 2016

Re: [Pharo-dev] TxText model

by philippe.back＠highoctane.be

On Apr 4, 2016 4:24 PM, "Sven Van Caekenberghe" <sven(a)stfx.eu> wrote: > > > > On 04 Apr 2016, at 16:02, philippe.back(a)highoctane.be < philippe.back(a)gmail.com> wrote: > > > > Is TxText part of the image? > > Try (in 5.0): > > TxViewContainer exampleOneLineEditor. > > TxViewContainer editText: 'Philippe Back'. Thx Sven. I'll try that out. Phil > > Sven

April 4, 2016

Re: [Pharo-dev] TxText model

by Igor Stasenko

On 4 April 2016 at 17:47, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2016-04-04 16:14 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > >> >> >> On 4 April 2016 at 17:03, Thierry Goubier <thierry.goubier(a)gmail.com> >> wrote: >> >>> >>> >>> 2016-04-04 15:49 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: >>> >>>> >>>> >>>> On 4 April 2016 at 16:32, Thierry Goubier <thierry.goubier(a)gmail.com> >>>> wrote: >>>> >>>>> >>>>> >>>>> 2016-04-04 15:23 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: >>>>> >>>>>> >>>>>> >>>>>>> Analogies don't work. Right :) I never used Pillar and have remote >>>>>> ideas about what it does or requires. From that perspective you appeal to >>>>>> wrong person. On your place i would be asking a guy who knows Pillar >>>>>> innards about it. >>>>>> Forgive my ignorance.. but i am not omniscient. >>>>>> >>>>> >>>>> False humility doesn't work there, Igor :) >>>>> >>>> >>>> But i don't know what Pillar is. Never used it. I'm not lying here. I >>>> seen people doing something with it time to time.. but never got my eyes on >>>> it. >>>> Or would you prefer that i would pretend that i know something and can >>>> continue discussion about things related to it? Waving hands, pointing to >>>> milestones, drawing diagrams? :) >>>> >>> >>> Yes, diagrams :) Ok, I don't know that much Pillar in details myself; >>> except as one of those things where some of your characters in the text are >>> used to build a layout on a target. >>> >>> >>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>>> Second is: Pharo (and all smalltalks) is the place where supposedly >>>>>>> impossible stuff can be developed, simply because it takes far less lines >>>>>>> than anywhere else. No guarantees, but, at the rate we're dropping projects >>>>>>> by the side of the road (and reinventing stuff multiple times over), we >>>>>>> have manpower to spare :) >>>>>>> >>>>>>> But that is orthogonal. It is possible to do anything on >>>>>> turing-complete environment. Taking shortcuts etc etc yadda yadda. Now do >>>>>> such statements alone can bring us anywhere closer to grand goals and grand >>>>>> projects? >>>>>> Nope. Only hard day to day work could bring us there.. Not talks >>>>>> about how cool we are. >>>>>> >>>>> >>>>> Hard day to day work, yes. But if you make it that uninteresting, yes, >>>>> I'm sure we will never get there :) >>>>> >>>>> Okay, let me elaborate what was the whole point behind TxText project. >>>> It was part of work we were doing to migrate from old Canvas & BitBlt >>>> Morphic rendering towards vector-based rendering using Athens. Basically in >>>> a nutshell TxText is a model and rendering engine for text rendering. >>>> >>> >>> I'd say it is more: it is an interactive model for text editing and >>> rendering. How much of it is "interactive" by opposition to pure rendering? >>> Can they be easily separated? >>> >> >> Well, there is a model, TxModel, which is domain-based. Means it is >> abstract and agnostic from any kind of rendering engine or UI. >> It represents an object that contains text and allows certain operation >> on it, like selection, deletion, insertion etc. >> And rendering engine bridges that model with morphic and athens. >> It cannot be separated, since it implies using such model for computing >> layout, and implies to use Athens for rendering.. And implies to exist in >> Morphic (or some other kind of UI environment) for UI interaction, to be >> represented as a widget on screen and receive events and mouse/keyboard >> input etc. >> So, what kind of separation you trying to see there? >> > > I was trying to evaluate how much of it was tied to an underlying text > model, and a specific interaction approach / global high level view of the > UI. > > A short look through the layout part of it and I saw it has support for > arbitrary object spans. It also supposes a certain API from it's model > (interacting back to indicate where lines should be ended). A text is a > list of spans, isn't it? And spans are flat (no span inside span). One > could imagine extending attributes for spans / type of spans and get > customized rendering / handling for those. > Correct. > > For now, external objects can't extend below the baseline. > Slightly not like that. An external object are bound to concrete position in text. And layout of a single line are computed based on dimensions of that object, as well as dimensions of other parts of a line. The text flow are not affected by the object in terms that there is no capability to compute wrapping text around it or align it left/right whatever separately from text. It means that basically external object is like a special kind of glyph/icon that uses same layout rules as character glyphs, but just rendered separately. > > Position inside spans can be ambiguous: last position of a span and first > position of the next span are the same position. > > Well, for some operation the are treated as same, for some - don't. Since there's nothing can be between two positions at the ends of adjacent spans, from standpoint of user they represent same position in text. But from standpoint of model they are different since position are belong to different spans. Sure thing, there certain pieces added to avoid problems with such ambiguity, so that it don't causing problems on user-level. Thierry > -- Best regards, Igor Stasenko.

April 4, 2016

Re: [Pharo-dev] TxText model

by Denis Kudriashov

2016-04-04 16:51 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > Twisty renders only on Athens too? Only Morphic now. It should not be hard to support Athens, TxText can be used as example. Twisty is on Smalltalkhub, right? Yes

April 4, 2016

Re: [Pharo-dev] TxText model

by Thierry Goubier

2016-04-04 16:47 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2016-04-04 16:11 GMT+02:00 Thierry Goubier <thierry.goubier(a)gmail.com>: > >> It is. Five packages, 1609 + 2647 lines of code (excluding tests and >> styler). >> >> I think Denis has worked on it (and extended it). >> > > History was that: > At some point I realised that I can't use old TextMorph anymore. For my > project I needed flexible editors which allows me implement validation, > mask fields, secrete fields and others. It was almost impossible to hack > old text morph to support these features. > I read about Igor project TxText. It included only model at that time > which was very similar to my ideas. So I decided to implement editors on > top of it. I was try to not touch model itself and only fix bugs. But > during development I saw all weakness of model and I start refactoring with > idea of active text which announces any changes. > And in same time Igor returned to this project. He saw all problems with > model and started refactoring too. But his idea was opposite to my. > At the end I forked my refactored version of TxText into separate project > Twisty. So I think current TxText not includes any my code. > Twisty renders only on Athens too? Twisty is on Smalltalkhub, right? Thierry

April 4, 2016