On 27 August 2014 22:17, Tudor Girba <tudor@tudorgirba.com> wrote:
That is cool. What I suggest is to get it out there and then we work with you to tell you the use cases and we evolve the API from there.
Okay.
Cheers, Doru
On Wed, Aug 27, 2014 at 5:43 PM, Igor Stasenko <siguctua@gmail.com> wrote:
On 27 August 2014 09:42, stepharo <stepharo@free.fr> wrote:
Igor
we should integrate TxText as soon as the new integration handle configurations (normally next week). So can you get prepared?
I can make configuration with latest versions.. but that won't make things more 'prepared' in aspect that i am still did not took time to think about high-level API , so there's almost none at the moment.. and it is still a big question to me, how it should look like.
i need a list of requirements from perspective of text editor widget, to at least know what API should be there.. because if people start using it without API, then it will be hard to do any changes later, once people integrate it into own projects.. i just don't want the complexity overflow us, we should keep things simple enough, hiding implementation details behind.
We should discuss that.. because yeah.. you can create morph, place it on screen.. but that don't makes it easy or convenient to use.
Stef
On 26/8/14 17:43, Igor Stasenko wrote:
On 26 August 2014 00:24, Nicolai Hess <nicolaihess@web.de> wrote:
I tried an alternative approach for rendering Morphs on athens without implementing drawOnAthensCanvas for every morph:
13866 <https://pharo.fogbugz.com/default.asp?13866> AthensFormCanvasWrapper
still struggling with the text rendering. Yet I am not sure what is the better approach.
A new text model, which i am working on :)
Nicolai
-- Best regards, Igor Stasenko.
-- Best regards, Igor Stasenko.
-- www.tudorgirba.com
"Every thing has its own flow"
-- Best regards, Igor Stasenko.