On 11 October 2011 01:23, karl ramberg <karlramberg at gmail.com> wrote:
> A bunch of work was done on Sophie and using the Rome plugin
>
What is license of its code?

> Karl
>
> On Mon, Oct 10, 2011 at 10:55 PM, Igor Stasenko <siguctua at gmail.com> wrote:
>> On 10 October 2011 21:52, Nicolas Cellier
>> <nicolas.cellier.aka.nice at gmail.com> wrote:
>>> 2011/10/10 Igor Stasenko <siguctua at gmail.com>:
>>>> On 8 October 2011 20:01, Bernhard Pieber <bernhard at pieber.com> wrote:
>>>>> Hi Igor,
>>>>>
>>>>> Thank you for your interest. I am afraid I did not have time to release the code yet. Sorry about that. :-(
>>>>>
>>>>> I will try my best to increase the priority for that.
>>>>>
>>>>
>>>> Well, currently i am trying to approach text rendering from fresh
>>>> perspective, and it would be nice to look how you did it.
>>>>
>>>> In Cuis, i see a lot of clean up, but it is still more or less same,
>>>> years old model.
>>>> My main interest is text layout , not rendering, since rendering will
>>>> be done differently.
>>>
>>> You mean composition, like in CompositionScanner ?
>>> Do you wish to handle font selection, line splitting, graphics
>>> embedding, alignment, margins, indentations, tab stops, inter line
>>> spacing etc... in Smalltalk?
>>>
>> Yikes.. :)  yes this is what i looking for.
>>
>>> If you use external rendering, you'll have to use external layout
>>> measurement, no?
>>> Then basic rendering API might have to cope with inter letter spacing
>>> adjustment (with kerning) and inter word spacing adjustment...
>>> Is that what you're looking for, splitting responsibilities in current
>>> implementation?
>>>
>>
>> Yes. I just want to make it work similar to current implementation.
>> The rendering engine should care only about blitting/displaying glyphs,
>> and the rest are separate, computed by language.
>> This is basicly what current implementation does, minus i'm not happy
>> how it does :)
>>
>>
>>> Nicolas
>>>
>>>>
>>>> The problem with current text rendering, that it tries to optimize
>>>> very hard towards using primitive(s) which can blit
>>>> raster font glyphs in a loop.
>>>> But once you start using freetype, all those optimization are useless
>>>> and serve only for increase in complexity.
>>>>
>>>>> Cheers,
>>>>> Bernhard
>>>>>
>>>>> Am 05.10.2011 um 18:11 schrieb Igor Stasenko:
>>>>>
>>>>>> Hello,
>>>>>> at ESUG there was a presentation of new text editor made for Cuis, and
>>>>>> unfortunately i missed that presentation
>>>>>> so, i found it only now.
>>>>>> The state of text rendering/editing in squeak/pharo is very bad, and
>>>>>> it is good that you took an effort to improve it.
>>>>>> So, my question, is there a downloadable stuff somewhere i can look
>>>>>> at, play with it?
>>>>>>
>>>>>> I heard it is planned to be ported to Pharo, i would like to help with it.
>>>>>>
>>>>>> --
>>>>>> Best regards,
>>>>>> Igor Stasenko.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Igor Stasenko.
>>>>
>>>>
>>>
>>>
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>>
>
>



-- 
Best regards,
Igor Stasenko.