April 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Rectangle Center

by Tommaso Dal Sasso

On 29/04/15 15:18, Sean P. DeNigris wrote: > Natalia Tymchuk wrote >> Should it really be like that? > > The problem is that you can't have half-a-pixel if a dimension is odd > For these situations, I would use the method #floor or #rounded of the class Point, or create the method #roundedCenter, as Natalia suggested. Currently, the name of the class and the method communicate the wrong behavior. Tommaso > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Rectangle-Center-tp4822883p4822891.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 29, 2015

Re: [Pharo-dev] Rectangle Center

by Thierry Goubier

Le 29/04/2015 15:20, Natalia Tymchuk a Ã©crit : > Hello. > I found very interesting method. > > Should it really be like that? > Or maybe we need to rename this method as #roundedCenter and add the > normal #center with usual division? > Best regards, > Natalia > I believe I had to correct a bug with Roassal scaling and centering because of the rounding done in that method. Had to reimplement a proper center computation for rectangles in Roassal or Trachel. Thierry

April 29, 2015

Re: [Pharo-dev] Rectangle Center

by Sergio Fedi

It seems that the problem is not with the Rectangle per se, but the type of measure it uses. Maybe the responsibility of being always an Integer measure should be delegated to the measure itself. Like, instead of using numbers, you could use Measures (from Aconcagua) that are 100 pixels instead of 100 (Integer) I don't know if Aconcagua has implemented units that are always a certain type, yet. â

April 29, 2015

Re: [Pharo-dev] Tx: Bold Text

by Nicolai Hess

Am 29.04.2015 5:30 nachm. schrieb "Sean P. DeNigris" <sean(a)clipperadams.com >: > > What would be the proper (i.e. respecting the design) way to make text bold? Assign the proper Attribute? > The current attributes seem to be special cases which are hard-coded e.g. > font and foreground color are accessed explicitly during drawing... Arent these attributes applied to the spans during scanning? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Tx-Bold-Text-tp4822964.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

April 29, 2015

Re: [Pharo-dev] Tx: Bold Text

by Sean P. DeNigris

Nicolai Hess wrote > Assign the proper Attribute? Well AFAICT there is no bold attribute, but I tried setting the font to bold via "(LogicalFont familyName: 'Tahoma' pointSize: 9 + i) emphasis: 1; yourself." but it was rendered the same as before... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tx-Bold-Text-tp4822964p4822987.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 29, 2015

Re: [Pharo-dev] [pharo-project/pharo-core] 5c2208: 50021

by Esteban Lorenzano

> On 29 Apr 2015, at 17:08, Ben Coman <btc(a)openInWorld.com> wrote: > > > > On Wed, Apr 29, 2015 at 7:39 PM, GitHub <noreply(a)github.com <mailto:noreply@github.com>> wrote: > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core <https://github.com/pharo-project/pharo-core> > Commit: 5c2208342bfd2fb5ad4c955eca5100a9f6707759 > https://github.com/pharo-project/pharo-core/commit/5c2208342bfd2fb5ad4c955e… <https://github.com/pharo-project/pharo-core/commit/5c2208342bfd2fb5ad4c955e…> > Author: Jenkins Build Server <board(a)pharo-project.org <mailto:board@pharo-project.org>> > Date: 2015-04-29 (Wed, 29 Apr 2015) > > Log Message: > ----------- > 50021 > ConfigurationOfRubric > > http://files.pharo.org/image/50/50021.zip <http://files.pharo.org/image/50/50021.zip> > > > > > Mentioning only the Configuration is a bit opaque. Presumable there are several issues bound up in this Configuration. It would be useful to have those listed. Maybe hard to do? > cheers -ben there is some bug in some message extractionsâ¦ hard to catch because it does not happens all the time. Esteban

April 29, 2015

Re: [Pharo-dev] [Pharo5] Testers needed: AST based syntax highlighting

by Marcus Denker

> On 29 Apr 2015, at 17:25, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-04-29 16:46 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>>: > Hi, > > We need some people to test using the AST based highlighter instead of Shout. > > SHRBTextStyler useAstColoring: true. > > I got some DNU but I canât reproduce it anymore. > > Marcus > > > In (old) Workspace editing this > > 'a(b)'. > "ab". > > by just removing the first ' or " > -> UndefinedObject(Object)>>doesNotUnderstand: #doSemanticAnalysis > I think I fixed itâ¦ (will add a slice) > or removing the first " in a method comment > -> Syntax error unmatch " in comment > Ah, here the reason is that the Scanner creates an RBErrorToken (as it should, itâs the scanner). But we should not expose this, the parser has to create an AST with a RBParseErrorNode instead. Marcus

April 29, 2015

Re: [Pharo-dev] TimeStamp deprecation and related frameworks (GLORP, Grease, Magritte, Seaside...)

by Sven Van Caekenberghe

> On 29 Apr 2015, at 17:39, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > I started the migration of my apps to Pharo 4 and during the > transition the only thing that seems to cause issues are the > references to the TimeStamp class (particularly, its instantiators, > like #now, #current, etc.). > > However, there are frameworks like GLORP that use TimeStamp extensively. > > E.g. GLORP's <Dialect class>>#timeStampClass> returns TimeStamp, and > so does some other methods like Grease's #magritteTimeStampClass. > > What should be the proper way to update the references? > Simply changing the returned class of #timeStampClass-like methods > from TimeStamp to DateAndTime? Yes. TimeStamp is basically an empty subclass of DateAndTime. The only thing it ever did was use another print representation. All that is still available in DateAndTime. You won't lose any functionality by switching. I even think that DateAndTime is more ANSI, if you care about such a thing. > In the case of GLORP, which I'm updating too, TimeStamp use is more > extended, because it's also a datatype used to map table columns, but > using no timezone offset. I guess if we move to DateAndTime we should > preserve that behavior in order to not break anything. I don't understand this last point, could you elaborate ? As far as I see it, there is nothing TimeStamp did that DateAndTime cannot do. > What are your suggestions? > > Esteban A. Maringolo > > ps: I'm so tempted to fork from the GLORP package, rename as something > else (PLORM?) and refactor it mercilessly. That is something else ;-)

April 29, 2015

TimeStamp deprecation and related frameworks (GLORP, Grease, Magritte, Seaside...)

by Esteban A. Maringolo

I started the migration of my apps to Pharo 4 and during the transition the only thing that seems to cause issues are the references to the TimeStamp class (particularly, its instantiators, like #now, #current, etc.). However, there are frameworks like GLORP that use TimeStamp extensively. E.g. GLORP's <Dialect class>>#timeStampClass> returns TimeStamp, and so does some other methods like Grease's #magritteTimeStampClass. What should be the proper way to update the references? Simply changing the returned class of #timeStampClass-like methods from TimeStamp to DateAndTime? In the case of GLORP, which I'm updating too, TimeStamp use is more extended, because it's also a datatype used to map table columns, but using no timezone offset. I guess if we move to DateAndTime we should preserve that behavior in order to not break anything. What are your suggestions? Esteban A. Maringolo ps: I'm so tempted to fork from the GLORP package, rename as something else (PLORM?) and refactor it mercilessly.

April 29, 2015

Tx: Bold Text

by Sean P. DeNigris

What would be the proper (i.e. respecting the design) way to make text bold? The current attributes seem to be special cases which are hard-coded e.g. font and foreground color are accessed explicitly during drawing... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Tx-Bold-Text-tp4822964.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 29, 2015