- Pharo-dev - lists.pharo.org

[Pharo-project] Zoomable UI

by Igor Stasenko

This is where, i think we should be heading: http://ahead.com And this is why i think, a graphics frameworks should be vector based, not a pixel based one. -- Best regards, Igor Stasenko AKA sig.

April 19, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released!

by Michael Haupt

Hi Igor, On Mon, Apr 19, 2010 at 7:21 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Computer always 'knows' what next operation it going to perform, and > don't need to use any precedence. ... enter quantum computers. :-P > If we ever will meet aliens, then to start communicating we, no doubt, > should use an universal rules & semantics, which can be interpreted > without any chances to be ambiguous. And precedence, obviously is not > a univesal :) Hear, hear! Best, Michael

April 19, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released!

by Igor Stasenko

On 19 April 2010 19:40, Michael Haupt <mhaupt(a)gmail.com> wrote: > Hi, > > On Mon, Apr 19, 2010 at 4:26 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> I am serious. If you can't learn the simplest syntax rules, you can't >> learn anything else. > > but Syntax, dearest Igor, is key! And Note The Capital "S"! > > You see, Lisp clearly sucks because it has too many brackets. Python > and Haskell are most unfavourable because they have whitespace with > semantics. Pascal, Modula-2, and Ada are way too verbose. Forth > organises programs in pages - now *that* is bureaucratic and > old-fashioned, aye? Smalltalk obviously doesn't know how to compute > with natural numbers properly. Smalltalk, Self, and Io share the > indignity of not even having proper keywords. Java, Scala, C, and C++ > ... don't even get me started, man: curly braces are sooooo 80s. > Erlang does not end sentences with an exclamation mark, it puts it in > their midst - how messy, bah. In Prolog, you have to write your own > rules, which makes it seem as if the language didn't have any: yuck! > > If you consider all these points wisely, you will inevitably come to > the conclusion that the only language with a proper, clear, civilised, > and tidy syntax out there is brainfuck. Some argue it's unacceptable > due to its name, but that is not a syntactical argument and hence > invalid. I win. > I agree. all languages having bright and dark sides. And people free to choose what they like (or not). I wonder, how a computer languages would look like for europeans, if they are first were invented by Chinese or Japanes cultures. ( you know, they would use glyphs in it ;). Still, there are an univestal laws and concepts which come from mathematics, and will not change depending on cultural/educational nuances: computers are finite state machines with strictly defined order of operations. Computer always 'knows' what next operation it going to perform, and don't need to use any precedence. If we ever will meet aliens, then to start communicating we, no doubt, should use an universal rules & semantics, which can be interpreted without any chances to be ambiguous. And precedence, obviously is not a univesal :) > Best, > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

April 19, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released!

by Michael Roberts

On Monday, April 19, 2010, Adrian Lienhard <adi(a)netstyle.ch> wrote: > On Apr 19, 2010, at 09:10 , StÃ©phane Ducasse wrote: > >> On Apr 19, 2010, at 1:56 AM, Stephen Taylor wrote: >> >>> Henrik Johansen wrote: >>> >>>> Gotta love reddit... >>> [...] >>>> - "I don't know what Smalltalk is, and the site doesn't tell me, not even the about page!" >>> >>> That one I think is legitimate - and not just for Pharo but for almost every Open Source project out there. I think every project's home page should keep first time in visitors in mind. (My very least favourite thing for the first page of a site is to see the project commit log - talk about unwelcoming!). >> >> Good remark. >> Thanks. >> Does anybody have some text we could reuse? > > I think that anybody that is enough interested will be able to type "Smalltalk" into Google. Next, people are going to ask what a programming language is, and we have to explain that too ;) > > Anyway, couldn't we just link the first occurrence of "Smalltalk" to en.wikipedia.org/wiki/Smalltalk? I already did that ;-) Cheers mike >>> And to say something positive - Pharo 1.0 looks great - solid and serious and workable. A couple of my co-workers have called my bluff and asked for a Smalltalk tutorial, and I'll be happy to show them Pharo. > > Thanks :) > > Cheers, > Adrian > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 19, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released!

by Michael Haupt

Hi, On Mon, Apr 19, 2010 at 4:26 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > I am serious. If you can't learn the simplest syntax rules, you can't > learn anything else. but Syntax, dearest Igor, is key! And Note The Capital "S"! You see, Lisp clearly sucks because it has too many brackets. Python and Haskell are most unfavourable because they have whitespace with semantics. Pascal, Modula-2, and Ada are way too verbose. Forth organises programs in pages - now *that* is bureaucratic and old-fashioned, aye? Smalltalk obviously doesn't know how to compute with natural numbers properly. Smalltalk, Self, and Io share the indignity of not even having proper keywords. Java, Scala, C, and C++ ... don't even get me started, man: curly braces are sooooo 80s. Erlang does not end sentences with an exclamation mark, it puts it in their midst - how messy, bah. In Prolog, you have to write your own rules, which makes it seem as if the language didn't have any: yuck! If you consider all these points wisely, you will inevitably come to the conclusion that the only language with a proper, clear, civilised, and tidy syntax out there is brainfuck. Some argue it's unacceptable due to its name, but that is not a syntactical argument and hence invalid. I win. Best, Michael

April 19, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released!

by Igor Stasenko

On 19 April 2010 18:10, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Sig, > > Never argue with an idiot - others might not be able to tell the difference. Â I beg you to raise the level of your arguments beyond name calling. Â Whether you see it that way or not, you mention "childhood" and it's over. > I am not using reddit. And indeed, a flame wars it a least interesting thing i wanna be part of. The point is, that smalltalk gives a clear answer (as to me), why it has such syntax: uniformity, simplicity and consistency. While in many other languages such answer could be depicted as: because others do. So, a central question in such discussions should be _why_ some language having such rules, and those who don't bother asking it, but instead, from a very start saying that its awfully bad, not worth my attention :) > Bill > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko > Sent: Monday, April 19, 2010 9:27 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released! > > On 19 April 2010 16:53, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >> Sig, >> >> You are missing the point: I *agree* that supporting precedence rules would very likely be bad and I would probably argue against any such change. Â Where you are doing damage to us all is by ridiculing someone who is raising a valid concern rather than debating that person with reasoned arguments. >> > > I am serious. If you can't learn the simplest syntax rules, you can't learn anything else. > And i don't care about what such people thinking, because they will never try to think different. > They are found that moving in direction where crowd moves, is a best way. Its not interesting to them, if there are other directions, and some even doesn't interesting in what direction they are currently moving. They are told to move in that way and they moving. > > Fine. Let this mindless crowd go its way. I don't feel a loss. > >> Bill >> >> > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

April 19, 2010

Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released!

by Schwab,Wilhelm K

Sig, Never argue with an idiot - others might not be able to tell the difference. I beg you to raise the level of your arguments beyond name calling. Whether you see it that way or not, you mention "childhood" and it's over. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Igor Stasenko Sent: Monday, April 19, 2010 9:27 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] [Pharo-users] [ANN] Pharo 1.0 released! On 19 April 2010 16:53, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Sig, > > You are missing the point: I *agree* that supporting precedence rules would very likely be bad and I would probably argue against any such change. Â Where you are doing damage to us all is by ridiculing someone who is raising a valid concern rather than debating that person with reasoned arguments. > I am serious. If you can't learn the simplest syntax rules, you can't learn anything else. And i don't care about what such people thinking, because they will never try to think different. They are found that moving in direction where crowd moves, is a best way. Its not interesting to them, if there are other directions, and some even doesn't interesting in what direction they are currently moving. They are told to move in that way and they moving. Fine. Let this mindless crowd go its way. I don't feel a loss. > Bill > > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 19, 2010

Re: [Pharo-project] Fonts for dummies

by Henrik Johansen

On Apr 19, 2010, at 4:47 17PM, Henrik Johansen wrote: > > StrikeFonts take their glyphs from a bitmap, thus will have constant pixel sizes. (decentKern is used for italic glyphs though) > As far as I know, kerning is not done for StrikeFonts, the only related use is of ascentKern when making a bitmap for italic derivatives of basefonts. > Arr. Correction; the only place StrikeFonts use something with a name related to kerning is when doing something with Italics, can't remember exactly how, why, or what methods. :) In any case it's not the kerning you are looking for. Cheers, Henry

April 19, 2010

Re: [Pharo-project] Fonts for dummies

by Igor Stasenko

On 19 April 2010 17:16, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Hello all, > > What is the best way to create/access fonts? Â So far, TextStyle defaultFont seems to work. Â I was about to write that I was feeling lost otherwise when I recalled setting fonts by name in Migrate, and a comment therein reveals that I stole some preferences from Lukas who used LogicalFont. Â Perhaps specifying the family name following his example (with cues from exploring LogicalFont all) is the answer? > > What about what Microsoft (sorry...) calls font metrics? Â By involving a device context (canvas in our world), one can find out how big a particular string will be on the target device's resolution, and allowing for kerning. > > So far, I have found #heightOf: and #widthOf: in the Font hierarchy, which means they know nothing of the intended device, and do not (obviously anyway) seem to know about kerning. Â Are there glaringly missing features here, or is this simply an consequence of printing being done via PostScript and therefore still in terms of point sizes? > I think there is a _glaringly missing features here_. The fonts in squeak seems evolved from being a simple raster bitmaps, and don't quite well resembling a functionality beyond this. > Bill > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

April 19, 2010

Re: [Pharo-project] Fonts for dummies

by Henrik Johansen

On Apr 19, 2010, at 4:16 25PM, Schwab,Wilhelm K wrote: > > What about what Microsoft (sorry...) calls font metrics? By involving a device context (canvas in our world), one can find out how big a particular string will be on the target device's resolution, and allowing for kerning. > > So far, I have found #heightOf: and #widthOf: in the Font hierarchy, which means they know nothing of the intended device, and do not (obviously anyway) seem to know about kerning. Are there glaringly missing features here, or is this simply an consequence of printing being done via PostScript and therefore still in terms of point sizes? > > Bill StrikeFonts take their glyphs from a bitmap, thus will have constant pixel sizes. (decentKern is used for italic glyphs though) As far as I know, kerning is not done for StrikeFonts, the only related use is of ascentKern when making a bitmap for italic derivatives of basefonts. Changing StrikeFonts to include kerning info will mean rewriting the string-rendering primitive, so I wouldn't get my hopes up it is likely to happen anytime soon. For FreeTypeFonts, getWidthOf: uses AbstractFont>>pixelSize, which again uses TextStyle>>pointsToPixels: , which relies on TextStyles>>pixelsPerInch. pixelsPerInch _could_ be set based on information gathered at startup about resolution and screen size, but is not done currently, so a default of 96 is used. FreeTypeFont>> widthOfString:from:to: returns a width which takes kerning into account. (in theory, see the comment for clarifications) In essence, if those features are important to you: - Use FreeTypeFonts. - Set TextStyle pixelsPerInch: to a computed value at startup. Cheers, Henry

April 19, 2010