- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About fonts (again)

by stepharo

Hi nicolas I agree with you :). My goal is not to drop strike fonts because I think that the code is working and it can be useful for some people. I just want to make sure that StandardFonts (TextStyle and others...) does not mess up FreeType and StrikeFonts. We got a lot of problems with this for our clients. Stef On 22/4/14 09:09, Nicolas Cellier wrote: > > 2014-04-22 6:30 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com > <mailto:tudor@tudorgirba.com>>: > > One question is why do still have the disable free type fonts option? > This was useful when free type was still in development, but I > think now it is no longer useful. > Or are there still use cases for it? > > Doru > > > > At the risk of repeating myself (that's maybe 10 times I say it here, > but it's like shouting in the desert...) , > freetype is pretty inefficient because it displays characters one by > one (call a primitive foreach and every character). > So if you are on a not so fast device, strike fonts are still a good > option because the primitive displays groups of characters in a batch. > So please, please, please, for once before breaking things that works > and replacing them by a thing that works only partially, > do it the other way around: > - first make it fully work (that means add a new freetype primitive > displaying batch of chars) > - then drop any historical bits you want > > Of course, you are free to completely drop support for slow machines, > but it must be consciously. > > > On Mon, Apr 21, 2014 at 7:32 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > when freetype is on do you think that it makes sense to have > strikeFont > proposed as default fonts? Like it is done right now, I get > bitmapVera even if I > want to see FreeType fonts. > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow" > >

April 22, 2014

Re: [Pharo-dev] updated documentation on magritte?

by Esteban Lorenzano

On 22 Apr 2014, at 20:20, stepharo <stepharo(a)free.fr> wrote: > Not that I know. > I started a chapter on the pharo for the entreprise (with the idea to base it on the seaside book) but I need help. > If you start writing a draft I will do a pass. I was fearing thatâ¦ but ok :) > > Stef > > On 22/4/14 09:28, Esteban Lorenzano wrote: >> Hi, >> >> is there an updated documentation on magritte? where can I find it? >> >> cheers, >> Esteban >> >> > >

April 22, 2014

Re: [Pharo-dev] Lost in spec

by Nicolai Hess

2014-04-22 13:56 GMT+02:00 Igor Stasenko <siguctua(a)gmail.com>: > i want to use different adaptor for TextModel, when opening my UI > so that when widget is built for it, it will be my own widget, > not PluggableTextMorph.. > > but i found it hard to do.. here what i tried: > > > I try to replace bindings, so at the stage when spec interpreted, it uses > my bindings: > > openWithSpec > > | old result | > old := SpecInterpreter bindings. > > SpecInterpreter bindings: TxAdapterBindings new. > > [ result := super openWithSpec ] > ensure: [ SpecInterpreter bindings: old ]. > ^ result > > > in TxAdapterBindings i initialize it same as morphic bindging, except from > text model binding: > #TextAdapter => #TxTextAdapter > > but it is never invoked nor used :( > > i understand the overall model, but it seems like not completely, > (else the above trick would work).. what do i miss? > > -- > Best regards, > Igor Stasenko. > You code works, it is just that the TextModel is not the first one that calls the spec interpreter. The first one is the WindowModel. And after a spec is "interpreted" spec interpreter calls self hardResetBindings and that one reinitialize the binding to MorphicAdapterBindings. nicolai

April 22, 2014

Re: [Pharo-dev] Confused by NewListExample

by Stephan Eggermont

- title toggling doesnât work - doesnât have a usable size - window title not set - dragging doesnât work - disallows selection in one place, allows it somewhere else - menu the same on list title - uses halts directly instead of calling a method on self displaying the action (open a dialog, show a growl)

April 22, 2014

Re: [Pharo-dev] Lost in spec

by Igor Stasenko

TxText-Athens-IgorStasenko.27 (TxText on smalltalkhub) just committed see TxApplicationWithToolbar TxApplicationWithToolbar new openWithSpec etc On 22 April 2014 20:21, stepharo <stepharo(a)free.fr> wrote: > Igor where is your code so that I can give a try? > > > > On 22/4/14 13:56, Igor Stasenko wrote: > >> i want to use different adaptor for TextModel, when opening my UI >> so that when widget is built for it, it will be my own widget, >> not PluggableTextMorph.. >> >> but i found it hard to do.. here what i tried: >> >> >> I try to replace bindings, so at the stage when spec interpreted, it uses >> my bindings: >> >> openWithSpec >> >> | old result | >> old := SpecInterpreter bindings. >> >> SpecInterpreter bindings: TxAdapterBindings new. >> >> [ result := super openWithSpec ] >> ensure: [ SpecInterpreter bindings: old ]. >> ^ result >> >> >> in TxAdapterBindings i initialize it same as morphic bindging, except >> from text model binding: >> #TextAdapter => #TxTextAdapter >> >> but it is never invoked nor used :( >> >> i understand the overall model, but it seems like not completely, >> (else the above trick would work).. what do i miss? >> >> -- >> Best regards, >> Igor Stasenko. >> > > > -- Best regards, Igor Stasenko.

April 22, 2014

Re: [Pharo-dev] Milliseconds in DateAndTime or TimeStamp

by roberto.minelli＠usi.ch

If done right, TimeStamp would have not caused any confusion. Now that I discovered that a TimeStamp is a DateAndTime with rounded seconds (read: non-sense) I agree with you. On Apr 22, 2014, at 6:42 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > TimeStamp is deprecated, because it creates too much confusion, you better use DateAndTime. > > On 22 Apr 2014, at 17:11, roberto.minelli(a)usi.ch wrote: > >> "TimeStamp now" rounds the timestamp, so #asNanoSeconds returns the seconds * 10e9. >> >> Doing âDateAndTime nowâ solves my issue, but this is a total non-sense. >> >> Cheers, >> R >> >> On Apr 22, 2014, at 4:54 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >>> Well, it has #asNanoSeconds, how finer can you go? >>> >>> Uko >>> >>> On 22 Apr 2014, at 17:13, roberto.minelli(a)usi.ch wrote: >>> >>>> Hi, >>>> >>>> I am wondering if there is the possibility to get milliseconds in a TimeStamp. >>>> >>>> I need to record fine-grained events and second-granularity is not enough. >>>> >>>> Cheers, >>>> Roberto >>> >>> >> >> > >

April 22, 2014

Re: [Pharo-dev] Lost in spec

by stepharo

Igor where is your code so that I can give a try? On 22/4/14 13:56, Igor Stasenko wrote: > i want to use different adaptor for TextModel, when opening my UI > so that when widget is built for it, it will be my own widget, > not PluggableTextMorph.. > > but i found it hard to do.. here what i tried: > > > I try to replace bindings, so at the stage when spec interpreted, it > uses my bindings: > > openWithSpec > > | old result | > old := SpecInterpreter bindings. > > SpecInterpreter bindings: TxAdapterBindings new. > > [ result := super openWithSpec ] > ensure: [ SpecInterpreter bindings: old ]. > ^ result > > > in TxAdapterBindings i initialize it same as morphic bindging, except > from text model binding: > #TextAdapter => #TxTextAdapter > > but it is never invoked nor used :( > > i understand the overall model, but it seems like not completely, > (else the above trick would work).. what do i miss? > > -- > Best regards, > Igor Stasenko.

April 22, 2014

Re: [Pharo-dev] updated documentation on magritte?

by stepharo

Not that I know. I started a chapter on the pharo for the entreprise (with the idea to base it on the seaside book) but I need help. If you start writing a draft I will do a pass. Stef On 22/4/14 09:28, Esteban Lorenzano wrote: > Hi, > > is there an updated documentation on magritte? where can I find it? > > cheers, > Esteban > >

April 22, 2014

Re: [Pharo-dev] Milliseconds in DateAndTime or TimeStamp

by Sven Van Caekenberghe

TimeStamp is deprecated, because it creates too much confusion, you better use DateAndTime. On 22 Apr 2014, at 17:11, roberto.minelli(a)usi.ch wrote: > "TimeStamp now" rounds the timestamp, so #asNanoSeconds returns the seconds * 10e9. > > Doing âDateAndTime nowâ solves my issue, but this is a total non-sense. > > Cheers, > R > > On Apr 22, 2014, at 4:54 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Well, it has #asNanoSeconds, how finer can you go? >> >> Uko >> >> On 22 Apr 2014, at 17:13, roberto.minelli(a)usi.ch wrote: >> >>> Hi, >>> >>> I am wondering if there is the possibility to get milliseconds in a TimeStamp. >>> >>> I need to record fine-grained events and second-granularity is not enough. >>> >>> Cheers, >>> Roberto >> >> > >

April 22, 2014

Versionner screencast

by Christophe Demarey

Hello, I made a small screencast on Versionner to explain how to use it: https://www.youtube.com/watch?v=S5Dbmmln8tA Regards, Christophe.

April 22, 2014