Thank you! Doru
On Sun, Oct 5, 2014 at 8:44 AM, stepharo <[email protected]> wrote: > Thanks this is a great initiative. > > > > On 4/10/14 22:21, Nicolai Hess wrote: > > > 2014-10-04 12:11 GMT+02:00 stepharo <[email protected]>: > >> >> What are the plans to integrate TxText? >>> >> >> - Igor is taking clients one by one and improving txText. We got a >> new syntax hilighter. >> - Then I want to replace the workspace by a TxWorkspace. >> - After for athens we should rewrite all the drawOn: methods. >> - We were waiting to get integration based on configurations to >> include it and now this is ready. >> so soon we will have >> - TxText inside Pharo >> - >> > > > I made a fogbugz issue about changes to be done for > athens based morphic drawing > > 13790 <https://pharo.fogbugz.com/default.asp?13790> > Port what is needed for Athens (drawing morphs) > > One is about TextMorphs, I wrote about what I had to change to make > the basic drawing working. Maybe some of it is useless with TxText > but maybe it helps. > > 13449 <https://pharo.fogbugz.com/default.asp?13449> > AthensWrapMorph can not draw TextMorphs > > If we don't port/rewrite all text based morphs, we will have an > issue with this: > > 13448 <https://pharo.fogbugz.com/default.asp?13448> > No Font emphasis (bold/oblique...) on text drawn with Athens > > > AFAIK for the font handling in text morphs, they use the "normal" font > and holds the emphasis property on their own. But Athens (FreeType > renderer) > relies on the font allone, that means if you want a bold font you don't > take > the normal font *name* + bold emphasis, but you'll have to take the > "bold font" FreeType font entry, or something like that. > > About changing all the drawOn: methods for athens, there is > an alternative I proposed in > 13866 <https://pharo.fogbugz.com/default.asp?13866> > AthensFormCanvasWrapper > > Font rendering bug: > The font-bug for FreeType fonts (wrong sized characters) in Athens is not > solved. > (see screenshot) > The current solution is: "Don't use the same font (+font size) for > Athens and > Morphic". ( > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-June/097128.html > ) > But of course, how can we enforce this? > > > > >> >>> >>> Now I know that GTools have been used in Moose for a long time, but its >>> integration to Pharo REPLACING Workspace has been a cultural shock to those >>> that haven't used it before (myself included, though I'm lookign forward to >>> adapting). I think there'll be similar culture shock when Pharo 4 is >>> released, from those that don't follow the bleeding edge. I'd strongly >>> suggest that GTools operate for ONE release alongside existing tools, as an >>> additional item in the first level World menu next to 'Workspace'. >>> >> I said the same to doru :). >> >> >> Indeed, even if Playground is quite stable through long use in Moose, it >>> is new to Pharo, and marking its menu entry as 'Experimental' for now might >>> provide some benefits. >>> >>> * This may provide a to stress test new evolving frameworks like TxText >>> & Rubric - without affecting existing tools. >>> >>> * Now Playground has a wider community exposure, feedback from new users >>> is likely to be less pressure and less negative if they still have access >>> to old tools. >>> >>> * Feedback may result in changes. >>> >>> * Reduced culture shock. Builds confidence in a stable system not going >>> "too fast" but just "fast enough" (very subjective I know). >>> >>> >> >> > > -- www.tudorgirba.com "Every thing has its own flow"
