- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Presetting variables to Spec's TextModel.

by Nicolai Hess

This opens a text field where all "self ..." calls are evaluated for the morph object: |t| t:=TextModel new. t title:'evaluates for a morph'. t doItReceiver:(Morph new). t openWithSpec for example self openInWorld self color:Color red. will show the object and change the color. But yes, you can not set any variable binding. The workspace handles this on its own, there is no support for this in TextModel/TextAdapter 2014-10-04 21:20 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > I was looking at the Inspector and I saw the doItContext/doItReceiver but > it spans over several objects and I wasn't able to figure out how it > actually works / how to use it. (OpalCompiler was calling various methods > on the objects, so it was expecting some kind of structure). > > Could you give me an example? > > On Sat, Oct 4, 2014 at 9:15 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> >> Am 04.10.2014 17:09 schrieb "Peter UhnÃ¡k" <i.uhnak(a)gmail.com>: >> >> > >> > Hi, >> > >> > I'm trying to preset variables to TextModel but I'm not sure if/how can >> such thing be achieved. >> > >> > With Workspace (in pre-GT Pharo) I could do >> > >> > ws := Workspace openContents: 'a'. >> > b := Dictionary new. >> > b add: (WorkspaceVariable key: #a value: 42). >> > ws setBindings: b. >> > >> > Unfortunately Workspace isn't Spec's ComposableModel so I can't just >> reuse it. >> > Is something similar possible with TextModel? Perhaps somehow changing >> model to Workspace (without actually opening the workspace) or something? >> > >> > Inspector seems to do something like that but my investigation ended up >> in OpalCompiler which is way over my head. :( >> > >> > Thanks, >> > Peter >> >> I don't know how this works for variable binding, >> but you can set the doItReceiver: >> >> (that's how the inspector works) >> >> >> >

Oct. 4, 2014

Re: [Pharo-dev] Presetting variables to Spec's TextModel.

by Peter UhnÃ¡k

I was looking at the Inspector and I saw the doItContext/doItReceiver but it spans over several objects and I wasn't able to figure out how it actually works / how to use it. (OpalCompiler was calling various methods on the objects, so it was expecting some kind of structure). Could you give me an example? On Sat, Oct 4, 2014 at 9:15 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > Am 04.10.2014 17:09 schrieb "Peter UhnÃ¡k" <i.uhnak(a)gmail.com>: > > > > > Hi, > > > > I'm trying to preset variables to TextModel but I'm not sure if/how can > such thing be achieved. > > > > With Workspace (in pre-GT Pharo) I could do > > > > ws := Workspace openContents: 'a'. > > b := Dictionary new. > > b add: (WorkspaceVariable key: #a value: 42). > > ws setBindings: b. > > > > Unfortunately Workspace isn't Spec's ComposableModel so I can't just > reuse it. > > Is something similar possible with TextModel? Perhaps somehow changing > model to Workspace (without actually opening the workspace) or something? > > > > Inspector seems to do something like that but my investigation ended up > in OpalCompiler which is way over my head. :( > > > > Thanks, > > Peter > > I don't know how this works for variable binding, > but you can set the doItReceiver: > > (that's how the inspector works) > > >

Oct. 4, 2014

Re: [Pharo-dev] Presetting variables to Spec's TextModel.

by Nicolai Hess

Am 04.10.2014 17:09 schrieb "Peter UhnÃ¡k" <i.uhnak(a)gmail.com>: > > Hi, > > I'm trying to preset variables to TextModel but I'm not sure if/how can such thing be achieved. > > With Workspace (in pre-GT Pharo) I could do > > ws := Workspace openContents: 'a'. > b := Dictionary new. > b add: (WorkspaceVariable key: #a value: 42). > ws setBindings: b. > > Unfortunately Workspace isn't Spec's ComposableModel so I can't just reuse it. > Is something similar possible with TextModel? Perhaps somehow changing model to Workspace (without actually opening the workspace) or something? > > Inspector seems to do something like that but my investigation ended up in OpalCompiler which is way over my head. :( > > Thanks, > Peter I don't know how this works for variable binding, but you can set the doItReceiver: (that's how the inspector works)

Oct. 4, 2014

Re: [Pharo-dev] Seconds set of additions to GT-Inspector

by stepharo

Neat Stef On 4/10/14 20:41, Sven Van Caekenberghe wrote: > In Moose/GToolkit: > > === > Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.58 > Author: SvenVanCaekenberghe > Time: 4 October 2014, 8:39:58.350356 pm > UUID: 2d078975-c2ac-4fcf-af82-4dd3fc709016 > Ancestors: GT-InspectorExtensions-Core-TudorGirba.57 > > Customized GT-Inspector for Time, Date, DateAndTime and Duration by adding a Details tab listing various chronology aspects > === > > Sven > > >

Oct. 4, 2014

Re: [Pharo-dev] Presetting variables to Spec's TextModel.

by stepharo

May be this is the occasion to create a WorkspaceModel and support this behavior. Stef On 4/10/14 17:09, Peter UhnÃ¡k wrote: > Hi, > > I'm trying to preset variables to TextModel but I'm not sure if/how > can such thing be achieved. > > With Workspace (in pre-GT Pharo) I could do > > ws := Workspace openContents: 'a'. > b := Dictionary new. > b add: (WorkspaceVariable key: #a value: 42). > ws setBindings: b. > > Unfortunately Workspace isn't Spec's ComposableModel so I can't just > reuse it. > Is something similar possible with TextModel? Perhaps somehow changing > model to Workspace (without actually opening the workspace) or something? > > Inspector seems to do something like that but my investigation ended > up in OpalCompiler which is way over my head. :( > > Thanks, > Peter

Oct. 4, 2014

Seconds set of additions to GT-Inspector

by Sven Van Caekenberghe

In Moose/GToolkit: === Name: GT-InspectorExtensions-Core-SvenVanCaekenberghe.58 Author: SvenVanCaekenberghe Time: 4 October 2014, 8:39:58.350356 pm UUID: 2d078975-c2ac-4fcf-af82-4dd3fc709016 Ancestors: GT-InspectorExtensions-Core-TudorGirba.57 Customized GT-Inspector for Time, Date, DateAndTime and Duration by adding a Details tab listing various chronology aspects === Sven

Oct. 4, 2014

Re: [Pharo-dev] About ways to participate in community and general negativity

by Thierry Goubier

Le 04/10/2014 12:07, stepharo a Ã©crit : > >> NativeBoost is not unstable for me, but why libcgit is on a bleeding >> edge NativeBoost version then? > > I do not get what you want to say. May be restating will help me > understand. Last time I checked, libcgit was tied to an experimental NativeBoost version (or bleeding edge version). The changes needed by libcgit should have been integrated in Pharo instead. >> Athens is stable for me, but I believe that TxText requires a bleeding >> edge Athens. > > Igor improve Athens each time it is needed and it does not make athens > unstable. But basically TxText is on a fork of mainline Athens. It's the "Windows undocumented" approach: I'm on TxText, I need something from Athens, I just add the stuff to Athens; anyway, I'm not on the main Athens, I can get my own customized version. Now, when merging TxText, you'll have to merge a new Athens as well, and I hope that you won't find by then that this new Athens breaks Roassal. I can understand why you may want to work like that. From the outside, I'm not impressed by the process. >> Libcgit is like that: its Pharo 4 + Bleeding edge native boost not yet >> in Pharo 4 + libcgit (and from ESUG, I get that it will require an >> entire refactoring of Monticello and a complete new on disk format). >> It's really shaping up like a long, long term target. > So for you it would be better that we move faster :) > Not slowler. Not really. If you had a few million â¬ to burn, I'd say "perfect". With the amount of resources we have, I'm saying: this is really risky. And hard to contribute to, so I can't help. > You see if there is a bug in a cache on the system somehwere what can we > do. Igot told to alex to use another font and it solved the problem. > TxText will be pushed soon in Pharo 40. I tried to work on that cache issue because my demos with Roassal had the issue, but I couldn't find Igor's description in the archives. I know it's there... Igor, if you are listening, can you tell us again? Thierry

Oct. 4, 2014

Re: [Pharo-dev] About ways to participate in community and general negativity

by Thierry Goubier

Hi, Le 04/10/2014 11:54, Tudor Girba a Ã©crit : > And now you are starting to have the issue of handling slices on GT > from Pharo: do people have to register on Moose, resynchronize on GT > on Moose, push their slices there, wait for Moose to push a slice to > integrate on Pharo, wait for Pharo to integrate that slice? > > > Something like that. Only there is no wait time to integrate in Moose as > GT is a standalone project, and Moose simply integrates the latest > development version of all its dependencies. So, there is not that much > difference to integrating in Pharo. Once a new stable version of GT is > available, it will automatically be available in Pharo. I don't think this is the way to go. It raises an additional barrier to contributions to GT, such as: A - I tried GTPlayground on Pharo, I had a DNU, here is the issue I created. A - I pushed a slice with the corrections B - In GT development version we decided to go another way. We don't need your slice. Please wait for the next stable version and try again. Thank you for your contribution. A --- I'm not sure you'll get another contribution from A after that exchange ;) > I found that stepping through the opening sequence of GT to debug > MorphTreeMorph a pain and had to find another way to understand the > issue. > > Can you be more specific? What did you try to achieve and did not manage? I was trying to find out why a MorphTreeMorph would DNU upon GTDebugger opening ;) I gave up and went blindly into the MorphTreeMorph code instead, trying to solve it by luck. > I do have specific tools I can use in such circumstances that you > don't have. > > > What kind of tools? I would be interested in learning about them and the > analysis use cases they support. I have a trace tool for those situations (and also for parser work). My original use case was: - Finding the bug in an error correction decoding algorithm which worked without error, but with non-satisfying results: lower than expected SNR. - Has then been used very successfully to explain the algorithm. - Was then used as the basis for a hardware design methodology by dynamic code traces of multithreaded programs Other use cases I use it for: - Debugging code in Morphic (rectangles, MorphTreeMorph stuff, text editor errors) where halt makes the image unusable. - Debugging code in Parsers when the code of a reduction is not working properly (somewhere deep in the AST). Thierry

Oct. 4, 2014

Presetting variables to Spec's TextModel.

by Peter UhnÃ¡k

Hi, I'm trying to preset variables to TextModel but I'm not sure if/how can such thing be achieved. With Workspace (in pre-GT Pharo) I could do ws := Workspace openContents: 'a'. b := Dictionary new. b add: (WorkspaceVariable key: #a value: 42). ws setBindings: b. Unfortunately Workspace isn't Spec's ComposableModel so I can't just reuse it. Is something similar possible with TextModel? Perhaps somehow changing model to Workspace (without actually opening the workspace) or something? Inspector seems to do something like that but my investigation ended up in OpalCompiler which is way over my head. :( Thanks, Peter

Oct. 4, 2014

[pharo-project/pharo-core] 20c723: 40283

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 20c723f14050000eddda34bf9776128447cf51fc https://github.com/pharo-project/pharo-core/commit/20c723f14050000eddda34bf… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-04 (Sat, 04 Oct 2014) Changed paths: A CollectionsTests.package/StringTest.class/instance/testing - converting/testWithFirstCharacterDownshifted.st A CollectionsTests.package/StringTest.class/instance/testing/testCharactersExactlyMatching.st M Fuel.package/FLIteratingCluster.class/instance/analyzing/addReferenceFrom_to_.st A Fuel.package/FLLargeIdentityDictionary.class/instance/accessing/at_ifAbsentPut_.st M Fuel.package/FLRectangleCluster.class/instance/serialize%2Fmaterialize/materializeReferencesOf_with_.st A Fuel.package/extension/Array/instance/fuelReplacement.st A Fuel.package/extension/IdentitySet/instance/fuelReplacement.st A Fuel.package/extension/NBExternalHandle/instance/fuelReplacement.st A Fuel.package/extension/Rectangle/instance/fuelSetOrigin_corner_.st A FuelTests.package/FLContextSerializationTest.class/README.md A FuelTests.package/FLContextSerializationTest.class/class/closures for testing/blockClosureContextTesting.st A FuelTests.package/FLContextSerializationTest.class/class/closures for testing/blockClosureContextTestingWithSender_.st A FuelTests.package/FLContextSerializationTest.class/class/closures for testing/blockClosureContextWithOutPointerTesting.st A FuelTests.package/FLContextSerializationTest.class/class/running/thisContextSample.st A FuelTests.package/FLContextSerializationTest.class/definition.st A FuelTests.package/FLContextSerializationTest.class/instance/running/setUp.st A FuelTests.package/FLContextSerializationTest.class/instance/tests/testContext.st A FuelTests.package/FLContextSerializationTest.class/instance/tests/testContextThisContext.st A FuelTests.package/FLContextSerializationTest.class/instance/tests/testContextWithClosure.st A FuelTests.package/FLContextSerializationTest.class/instance/tests/testContextWithClosureAndSender.st A FuelTests.package/FLContextSerializationTest.class/instance/tests/testContextWithClosureContextWithOutPointerTesting.st A FuelTests.package/FLContextSerializationTest.class/instance/tests/testContextWithNilPc.st A FuelTests.package/FLContextSerializationTest.class/instance/tests/testContextWithSender.st A FuelTests.package/FLContextSerializationTest.class/instance/tests/testContextWithTemp.st A FuelTests.package/FLContextSerializationTest.class/instance/tests/testDoIt.st M FuelTests.package/FLHeaderSerializationTest.class/instance/tests/testPostMaterializationActions.st M FuelTests.package/FLHeaderSerializationTest.class/instance/tests/testPreMaterializationActions.st R FuelTests.package/FLMethodContextSerializationTest.class/README.md R FuelTests.package/FLMethodContextSerializationTest.class/class/closures for testing/blockClosureContextTesting.st R FuelTests.package/FLMethodContextSerializationTest.class/class/closures for testing/blockClosureContextTestingWithSender_.st R FuelTests.package/FLMethodContextSerializationTest.class/class/closures for testing/blockClosureContextWithOutPointerTesting.st R FuelTests.package/FLMethodContextSerializationTest.class/class/running/thisContextSample.st R FuelTests.package/FLMethodContextSerializationTest.class/definition.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/running/setUp.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testContext.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testContextWithClosureAndSender.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testContextWithNilPc.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testContextWithSender.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testContextWithTemp.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testDoIt.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testMethodContext.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testMethodContextThisContext.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testMethodContextWithClosure.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testMethodContextWithClosureAndSender.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testMethodContextWithClosureContextWithOutPointerTesting.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testMethodContextWithNilPc.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testMethodContextWithSender.st R FuelTests.package/FLMethodContextSerializationTest.class/instance/tests/testMethodContextWithTemp.st A FuelTests.package/FLSerializationTest.class/instance/class-factory/newSubclassNamed_of_instanceVariableNames_classVariableNames_.st A Graphics-Tests.package/PointTest.class/instance/tests-arithmetic/testAbs.st A Graphics-Tests.package/PointTest.class/instance/tests-arithmetic/testReciprocal.st A Graphics-Tests.package/PointTest.class/instance/tests-converting/testAsFloatPoint.st A Graphics-Tests.package/PointTest.class/instance/tests-converting/testAsIntegerPoint.st A Graphics-Tests.package/PointTest.class/instance/tests-converting/testAsPoint.st A Graphics-Tests.package/PointTest.class/instance/tests-converting/testIsPoint.st A Graphics-Tests.package/PointTest.class/instance/tests-geometry/testToIntersectsTo.st A Graphics-Tests.package/PointTest.class/instance/tests-point functions/testCrossProduct.st A Graphics-Tests.package/PointTest.class/instance/tests-point functions/testDist.st A Graphics-Tests.package/PointTest.class/instance/tests-point functions/testEightNeighbors.st A Graphics-Tests.package/PointTest.class/instance/tests-point functions/testFlipByCenterAt.st A Graphics-Tests.package/PointTest.class/instance/tests-point functions/testInsideTriangleWithWith.st A Graphics-Tests.package/PointTest.class/instance/tests-transforming/testNegated.st A Graphics-Tests.package/PointTest.class/instance/tests-truncation and roundoff/testIsIntegerPoint.st A Graphics-Tests.package/RectangleTest.class/instance/tests-accessing/testArea.st A Graphics-Tests.package/RectangleTest.class/instance/tests-rectangle functions/testPointNearestTo.st A Graphics-Tests.package/RectangleTest.class/instance/tests-rectangle functions/testSideNearestTo.st A Graphics-Tests.package/RectangleTest.class/instance/tests-rectangle functions/testWithBottom.st A Graphics-Tests.package/RectangleTest.class/instance/tests-rectangle functions/testWithHeight.st A Graphics-Tests.package/RectangleTest.class/instance/tests-rectangle functions/testWithTop.st A Graphics-Tests.package/RectangleTest.class/instance/tests-rectangle functions/testWithWidth.st A Graphics-Tests.package/RectangleTest.class/instance/tests-transforming/testFlipByCenterAt.st R Morphic-Base.package/MenuSpec.class/README.md R Morphic-Base.package/MenuSpec.class/definition.st R Morphic-Base.package/MenuSpec.class/instance/accessing/help.st R Morphic-Base.package/MenuSpec.class/instance/accessing/help_.st R Morphic-Base.package/MenuSpec.class/instance/accessing/name.st R Morphic-Base.package/MenuSpec.class/instance/accessing/name_.st M Morphic-Base.package/PluggableMenuItemSpec.class/README.md M Morphic-Base.package/PluggableMenuItemSpec.class/definition.st A Morphic-Base.package/PluggableMenuItemSpec.class/instance/accessing/help.st A Morphic-Base.package/PluggableMenuItemSpec.class/instance/accessing/help_.st A Morphic-Base.package/PluggableMenuItemSpec.class/instance/accessing/name.st A Morphic-Base.package/PluggableMenuItemSpec.class/instance/accessing/name_.st M Morphic-Base.package/PluggableMenuSpec.class/README.md M Morphic-Widgets-Extra.package/CalendarMorph.class/instance/announcing/onChoiceSend_to_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script283.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40283.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40283 14159 Update Fuel https://pharo.fogbugz.com/f/cases/14159 14155 Replace Announcer>>#on:send:to:s senders in Morphic-Widgets-Extra https://pharo.fogbugz.com/f/cases/14155 14131 Improving some little tests in the system https://pharo.fogbugz.com/f/cases/14131 14117 merge menuSpec and menuItemSpec https://pharo.fogbugz.com/f/cases/14117 http://files.pharo.org/image/40/40283.zip

Oct. 4, 2014