August 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 42d3c8: 40173

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 42d3c876a9007da6ed918a004f1c7e564105a5d4 https://github.com/pharo-project/pharo-core/commit/42d3c876a9007da6ed918a00… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-17 (Sun, 17 Aug 2014) Changed paths: A Morphic-Widgets-Windows.package/GroupWindowMorph.class/instance/initialize/defaultColor.st M OpalCompiler-Core.package/IRBlockReturnTop.class/README.md M OpalCompiler-Core.package/IRPushArray.class/README.md M OpalCompiler-Core.package/IRPushClosureCopy.class/README.md M OpalCompiler-Core.package/IRRemoteTempAccess.class/README.md M OpalCompiler-Core.package/IRTempVector.class/README.md M OpalCompiler-Core.package/IRThisContextAccess.class/README.md M OpalCompiler-Core.package/ManifestOpalCompilerCore.class/README.md M OpalCompiler-Core.package/OCASTClosureAnalyzer.class/README.md M OpalCompiler-Core.package/OCAbstractLocalVariable.class/definition.st R OpalCompiler-Core.package/OCAbstractLocalVariable.class/instance/accessing/index.st R OpalCompiler-Core.package/OCAbstractLocalVariable.class/instance/initializing/index_.st R OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/as yet unclassified/lookupVarForDeclaration_.st M OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/initialization/initialize.st A OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/lookup/lookupVarForDeclaration_.st M OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/temp vars/addCopyingTempNamed_.st M OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/temp vars/addCopyingTemp_.st M OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/temp vars/addTemp_.st M OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/temp vars/addVectorTemp_.st M OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/temp vars/removeTemp_.st M OpalCompiler-Core.package/OCAbstractMethodScope.class/instance/temp vars/tempVars.st M OpalCompiler-Core.package/OCCopyingTempVariable.class/README.md M OpalCompiler-Core.package/OCInstanceScope.class/README.md M OpalCompiler-Core.package/OCRequestorScope.class/README.md M OpalCompiler-Core.package/OCShadowVariableWarning.class/instance/correcting/variable_shadows_.st M OpalCompiler-Core.package/OCTempVariable.class/README.md M OpalCompiler-Core.package/OCVectorTempVariable.class/README.md M OpalCompiler-Core.package/SyntaxErrorNotification.class/README.md M OpalCompiler-Core.package/extension/Symbol/instance/asMethodPreamble.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script172.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40172.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40173 http://files.pharo.org/image/40/40173.zip

Aug. 17, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 7f270c: 40172

by Marcus Denker

On 17 Aug 2014, at 11:47, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I noticed that the log messages are empty for some time now: > Yes, I saw that, too. We will fix it later today. 40172 ----- 13848 EyePatch for inspectors eye https://pharo.fogbugz.com/f/cases/13848 13820 Move #useAstColoring setting to the Shout settings group https://pharo.fogbugz.com/f/cases/13820 13852 MNU on ChangeSorter fileOut https://pharo.fogbugz.com/f/cases/13852 > On 17 Aug 2014, at 12:09, GitHub <noreply(a)github.com> wrote: > >> Branch: refs/heads/4.0 >> Home: https://github.com/pharo-project/pharo-core >> Commit: 7f270c8fa61c6734a71f0d97dd5a1befaf1ac1fd >> https://github.com/pharo-project/pharo-core/commit/7f270c8fa61c6734a71f0d97… >> Author: Jenkins Build Server <board(a)pharo-project.org> >> Date: 2014-08-17 (Sun, 17 Aug 2014) >> >> Changed paths: >> A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script171.st >> A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40171.st >> M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st >> M Shout.package/SHPreferences.class/class/settings/settingsOn_.st >> M Shout.package/SHRBTextStyler.class/class/configuration/enableAstHighlightSetting_.st >> M Spec-Inspector.package/AbstractEyeElement.class/instance/comparing/=.st >> M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOut.st >> >> Log Message: >> ----------- >> 40172 >> >> http://files.pharo.org/image/40/40172.zip >> >> > >

Aug. 17, 2014

Re: [Pharo-dev] [pharo-project/pharo-core] 7f270c: 40172

by Sven Van Caekenberghe

I noticed that the log messages are empty for some time now: On 17 Aug 2014, at 12:09, GitHub <noreply(a)github.com> wrote: > Branch: refs/heads/4.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 7f270c8fa61c6734a71f0d97dd5a1befaf1ac1fd > https://github.com/pharo-project/pharo-core/commit/7f270c8fa61c6734a71f0d97… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2014-08-17 (Sun, 17 Aug 2014) > > Changed paths: > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script171.st > A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40171.st > M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > M Shout.package/SHPreferences.class/class/settings/settingsOn_.st > M Shout.package/SHRBTextStyler.class/class/configuration/enableAstHighlightSetting_.st > M Spec-Inspector.package/AbstractEyeElement.class/instance/comparing/=.st > M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOut.st > > Log Message: > ----------- > 40172 > > http://files.pharo.org/image/40/40172.zip > >

Aug. 17, 2014

[pharo-project/pharo-core] 7f270c: 40172

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 7f270c8fa61c6734a71f0d97dd5a1befaf1ac1fd https://github.com/pharo-project/pharo-core/commit/7f270c8fa61c6734a71f0d97… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-17 (Sun, 17 Aug 2014) Changed paths: A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script171.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40171.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Shout.package/SHPreferences.class/class/settings/settingsOn_.st M Shout.package/SHRBTextStyler.class/class/configuration/enableAstHighlightSetting_.st M Spec-Inspector.package/AbstractEyeElement.class/instance/comparing/=.st M System-Changes.package/ChangeSet.class/instance/filein%2Fout/fileOut.st Log Message: ----------- 40172 http://files.pharo.org/image/40/40172.zip

Aug. 17, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40172 Home: https://github.com/pharo-project/pharo-core

Aug. 17, 2014

Re: [Pharo-dev] MessageNotUnderstood: RBArgumentNode>>key

by Marcus Denker

On 17 Aug 2014, at 08:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 16 Aug 2014, at 17:21, Ben Coman <btc(a)openInWorld.com> wrote: > >> Gareth Cox wrote: >>> AST-Core changes seem to have broken Seaside REST. >>> I've sent messages to Seaside lists and various people but haven't got a response. >>> Pharo3, Seaside3.1 on Mac OS X. >>> -- >>> Gareth Cox >>> IT Manager/Developer >>> Inspired Org (PTY) Ltd >>> email: gareth(a)inspired.org >>> tell: +27 (0)21 531 5404 >>> cell: +27 (0)78 374 9035 >> >> I'm not familiar with either AST or Seaside, but a quick search found these on the issue trackers. Are they related? >> https://code.google.com/p/seaside/issues/detail?id=807 >> https://pharo.fogbugz.com/default.asp?13246 > > The issue 13246 is that, yes. > > > The implementation of #argumentNamesOf: course low-level details, in that case the AST. > > Now we changed the AST in Pharo3 to be the RB AST which provides a lot of compatibility methods, but not the one needed here. > (which makes no sense for the new AST) > > In the meantime added #argumentNames to CompiledMethod (because many clients need itâ¦ why should everyone do their own version?), > so in Pharo3 you can just write that method as: > > argumentNamesOf: aCompiledMethod > ^ aCompiledMethod argumentNames > The case https://code.google.com/p/seaside/issues/detail?id=807 needs to be re-opened. Marcus

Aug. 17, 2014

Re: [Pharo-dev] MessageNotUnderstood: RBArgumentNode>>key

by Marcus Denker

On 16 Aug 2014, at 17:21, Ben Coman <btc(a)openInWorld.com> wrote: > Gareth Cox wrote: >> AST-Core changes seem to have broken Seaside REST. >> I've sent messages to Seaside lists and various people but haven't got a response. >> Pharo3, Seaside3.1 on Mac OS X. >> -- >> Gareth Cox >> IT Manager/Developer >> Inspired Org (PTY) Ltd >> email: gareth(a)inspired.org >> tell: +27 (0)21 531 5404 >> cell: +27 (0)78 374 9035 > > I'm not familiar with either AST or Seaside, but a quick search found these on the issue trackers. Are they related? > https://code.google.com/p/seaside/issues/detail?id=807 > https://pharo.fogbugz.com/default.asp?13246 The issue 13246 is that, yes. The implementation of #argumentNamesOf: course low-level details, in that case the AST. Now we changed the AST in Pharo3 to be the RB AST which provides a lot of compatibility methods, but not the one needed here. (which makes no sense for the new AST) In the meantime added #argumentNames to CompiledMethod (because many clients need itâ¦ why should everyone do their own version?), so in Pharo3 you can just write that method as: argumentNamesOf: aCompiledMethod ^ aCompiledMethod argumentNames Marcus

Aug. 17, 2014

Re: [Pharo-dev] Why Bloc?

by Alain Plantec

Hello, I'm just back from holidays. To explain a bit more, Bloc is not done from scratch. For now, one can consider Bloc as a fork of the Morph class and few other system levels classes as HandMorph, WorldMorph ... They are progressively rewritten and simplified (we removed all HandMorph cache optimizations as an example). The good news is that, so far, morphic ui are still running ok within a Bloc world and you can dynamically switch from the morphic world to bloc worlds. Cheers Alain On 4 aoÃ»t 2014, at 21:28, stepharo <stepharo(a)free.fr> wrote: > > On 4/8/14 21:06, Sean DeNigris wrote: >> <not trolling, genuinely curious> >> When SimpleMorphic was released, the problem was that we didnât know how to integrate it into our existing Morphic. Also, the problem with starting with CUISâs Morphic was IIRC that it didnât properly handle internationalization. Now that weâre heading toward a total replacement anyway, why start from scratch when there are these projects, Morphic 3, and who-knows-what-else already available? >> </not trolling, genuinely curious> > > Sean > > (alain is on vacation without computer) So I will try to reply. > > First did you look at SimpleMorphic? > We did :) ESUG even paid for it while originally it was to support Morphic 3. > > Second, we read Cuis code. > > Third Alain did Miro. So he accumulated experience. > > Four Bloc is clean > local coordinates > no global hand ActiveHand, World. > one nice layout (based on anchor work of igor) > no fullbounds (you cannot draw outside a morph. Period!) > fully (yes fully pluggable halo - they are packaged in a different optional package) > > Now it is a long way to get something working for real. > So why bloc, we started to clean morphic with alain and we hit a wall. > Morphic is so heavy that trying to move inside is really difficult. > Now there is a risk that alain does not deliver so we should > - look at what he is doing > - we try to document the classes > - I'm trying to move some cleans/ideas from bloc to Morphic (introducing Margin, cleaning layoutFrame is a way to improve) > - Since bloc runs inside morphic, cleaning morphic reduces the morphic behavior that creeps in Bloc > > Here are some ideas to help > - for example, if you want to make bloc use Athens transformation > - write more tests > - write stupid examples > > - I'm cleaning menumorph and rewriting a menuMorph for Morphic with the hope that we can blocify the code > so that I can propose some simple MenuMorph to Bloc. > I'm busy with project proposal writing and other duties but if you want you can join. > > - I'm doing the same with theme and basic widgets. > - Can we do a simple button in Bloc? > - clean the one we have in Morphic > > > Alain would like to use Athens for the rendering of Bloc elements .... so this is another nice project to help. > > Stef > >

Aug. 16, 2014

Re: [Pharo-dev] MessageNotUnderstood: RBArgumentNode>>key

by Ben Coman

Aug. 16, 2014

MessageNotUnderstood: RBArgumentNode>>key

by Gareth Cox

AST-Core changes seem to have broken Seaside REST. I've sent messages to Seaside lists and various people but haven't got a response. Pharo3, Seaside3.1 on Mac OS X. -- Gareth Cox IT Manager/Developer Inspired Org (PTY) Ltd email: gareth(a)inspired.org <mailto:gareth@inspired.org> tell: +27 (0)21 531 5404 cell: +27 (0)78 374 9035

Aug. 16, 2014