- Pharo-dev - lists.pharo.org

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

PluggableTextMorph vs PluggableTextEditorMorph

by Nicolai Hess

What is the difference between (or different use cases for) PluggableTextMorph and PluggableTextEditorMorph ? Do we need both? The only difference I see: You can not toggle enabled/disabled a PluggableTextMorph, whereas a PluggableTextEditorMorph can be disabled. nicolai

April 29, 2015

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

by Nicolai Hess

2015-04-29 16:46 GMT+02:00 Marcus Denker <marcus.denker(a)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 or removing the first " in a method comment -> Syntax error unmatch " in comment

April 29, 2015

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

by Ben Coman

On Wed, Apr 29, 2015 at 7:39 PM, GitHub <noreply(a)github.com> wrote: > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 5c2208342bfd2fb5ad4c955eca5100a9f6707759 > > https://github.com/pharo-project/pharo-core/commit/5c2208342bfd2fb5ad4c955e… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2015-04-29 (Wed, 29 Apr 2015) > > Log Message: > ----------- > 50021 > ConfigurationOfRubric > > 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

April 29, 2015

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

by Nicolai Hess

2015-04-29 16:46 GMT+02:00 Marcus Denker <marcus.denker(a)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 > Another difference is, that classes aren't recognized until they are fully named: SHRBTextStyler useAstColoring: true. Workspace new open In the new Workspace, start typing Label the word is marked red, although it should be blue, with italic emphasis.

April 29, 2015

[pharo-project/pharo-core] 45e6fc: 50022

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 45e6fcc2e2967495b986c9c0ab5b0c84ec29675a https://github.com/pharo-project/pharo-core/commit/45e6fcc2e2967495b986c9c0… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-04-29 (Wed, 29 Apr 2015) Changed paths: R KernelTests.package/ObjectTest.class/instance/tests - introspection/testWriteToSlotOf.st A Play.package/GG.class/README.md A Play.package/GG.class/definition.st A Play.package/TT.class/README.md A Play.package/TT.class/definition.st M Reflectivity-Tests.package/MetaLinkTest.class/instance/tests - hooks/testHaltHook.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkWithMeta.st A Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkWithMetaDisabled.st M Reflectivity-Tests.package/ReflectivityExamples.class/instance/examples/exampleMethod.st M Reflectivity.package/MetaLink.class/instance/ast/encloseInBlock_.st M Reflectivity.package/MetaLink.class/instance/ast/hook.st R Reflectivity.package/MetaLink.class/instance/ast/metaAwareHook.st A Reflectivity.package/MetaLink.class/instance/ast/wrapInContext_.st A Reflectivity.package/RFObjectReification.class/README.md A Reflectivity.package/RFObjectReification.class/class/plugin interface/key.st A Reflectivity.package/RFObjectReification.class/class/plugin interface/nodes.st A Reflectivity.package/RFObjectReification.class/definition.st A Reflectivity.package/RFObjectReification.class/instance/code generation/genForRBProgramNode.st A Reflectivity.package/RFReification.class/README.md A Reflectivity.package/RFReification.class/class/accessing/allKeys.st A Reflectivity.package/RFReification.class/class/accessing/for_.st A Reflectivity.package/RFReification.class/class/plugin interface/key.st A Reflectivity.package/RFReification.class/class/plugin interface/nodes.st A Reflectivity.package/RFReification.class/definition.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script630.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script631.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50021.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50022.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/RelationSlot.class/instance/code generation/emitStore_.st M Slot.package/Slot.class/instance/code generation/emitStore_.st Log Message: ----------- 50022 15447 Links with MetaContext https://pharo.fogbugz.com/f/cases/15447 15436 emitStore: should not send writeToSlot:of: https://pharo.fogbugz.com/f/cases/15436 15444 OldClassBuilderAdapter: move checks into SlotClassBuilder (first step) https://pharo.fogbugz.com/f/cases/15444 http://files.pharo.org/image/50/50022.zip

April 29, 2015