On 7 April 2016 at 10:32, Nicolai Hess <nicolaih...@gmail.com> wrote:
> > > 2016-04-06 16:58 GMT+02:00 Igor Stasenko <siguc...@gmail.com>: > >> >> >> On 6 April 2016 at 17:07, Nicolai Hess <nicolaih...@gmail.com> wrote: >> >>> >>> >>> 2016-04-06 10:56 GMT+02:00 Igor Stasenko <siguc...@gmail.com>: >>> >>>> >>>> >>>> On 6 April 2016 at 11:36, Nicolai Hess <nicolaih...@gmail.com> wrote: >>>> >>>>> >>>>> >>>>> Thanks Igor. >>>>> Maybe some more Info? (I don't have much experience with this and >>>>> don't fully understand what is missing). >>>>> >>>>> >>>>>> 1. No support for vector graphics >>>>>> >>>>> >>>>> I know some parts of Athens (with Cairo font renderer and how it is >>>>> used in TxText) but at the moment >>>>> rendering a TextMorph in Athens works: >>>>> Morph comment asText asMorph openInSceneView >>>>> >>>> >>>> Sorry, missed to reply to that important point. >>>> It works because one good soul spent effort and helped me to finish >>>> implementation of a wrapper for Morph, to be able to render any morph into >>>> Form, and then render Form >>>> on Athens surface. >>>> >>> >>> Nah, actually it works a bit different. Many (Form)Canvas methods are >>> reimplemented on Athens API. But yes, I used some hacks as well. >>> >>> >> >> Didn't knew. >> Aha.. i see AthensCanvasWrapper. >> Ohh.. that's so much pain :) >> >> > As you are here and in a good mood for feedback, can you please answer some > Athens questions or review some code changes / issue entries? > > I added some instance variables for AthensCairoPatternPaint > (origin, extent) This was needed for converting Morphics GradientFillStyle > to Athens pattern > paint. But I am unsure if this was the intended way to use them. > > There are protocols for creating gradient paints in Athens: createLinearGradient: aColorRamp start: aStartPoint stop: aStopPoint createRadialGradient: colorRamp center: aCenter radius: aRadius focalPoint: fp how you storing things inside or transform this information is orthogonal. >From that perspective, anything what happens in AthensCairoPatternPaint is implementation detail. If you think that this protocol is not sufficient to define gradients, then fix it.. What happens on concrete implementation is last thing that should worry about. >From my POV , two points and color ramp is enough to define linear gradient. Things like extent is a derived data, that can be obtained via simple calculations from original data. That why it wasn't there in a first place. I am interested on issue > 14800 AthensCanvas clipRect oddity (Aliaskei thinks the current behavior is > on purpose ,but I am not sure). > > The intent was to make clipping work with Morphic.. This is true that morphic needs cliprect to be smart and not try to draw anything if it is fully outside clipped areas.. So, this is purely for optimization purpose. But i would prefer to have a consistent clipping model first, i.e.: - clipping using local coordinates - you can use any shape for clipping and then think how to adapt users with their concrete cases. That may, indeed make accessing such properties like clipRect impossible to get, since clipped area cannot be represented by a simple rectangle anymore. But then you could, perhaps instead provide a protocol to tell if given point/bounds/shape is fully outside currently clipped region(s) or not. And thus, you don't have to worry about cliprect anymore. AthensPathSegment: > I understand how they use the visit: messages but I don't understand the > #accept: or the #sendCommandTo: methods, are they used? > > The intent is to use it for path conversion/transformation etc. It is because we cannot guarantee that all backends will support various kinds of path segments, that Athens providing to user. And so, we need a small private toolset for converting some segments into simpler form, in case of need. So , it is there when you need to iterate over path for things like converting it to polygon etc. But that part needs review and cleanup, because it smells... Aliaksei fixed a bug in > CairoFreetypeFontRenderer>>#glyphsOf:from:to: > (the bug was: sometimes, some characters uses glyphs with wrong size). > > I think some AthensText classes are obsolete: > AthensTextScanner/AthensParagraph/AthensTextMorph/AthensPluggableTextMorph > Can we remove them? > > Well, if i remember, there are some leftovers from attempt to make text rendering it at least partially work with Balloon backend. While some other is result of failed attempt to make anything with TextMorph. So, nobody will cry if you clean this mess. -- Best regards, Igor Stasenko.
