Benjamin Pollack | 2 Oct 02:17 2014

ZnEasy and post:data:

Hey all,

This is probably me missing something, but: for an upcoming
presentation, I wanted to find the tersest way to demonstrate making an
HTTP POST.  Something equivalent to Python's

    requests.post('http://some/thing', data={'foo': 'bar', 'baz':
    'quux'})

The closest I could come up with for Pharo was

    ZnEasy post: 'http://some/thing' data:
    (ZnApplicationFormUrlEncodedEntity withAll: {
        'foo' -> 'bar'.
        'baz' -> 'quux'.
    } asDictionary)

I just wanted to verify that is, in fact, the shortest way to do this. 
I feel as if I'm almost certainly missing a utility method around the
ZnApplicationFormUrlEncodedEntity bit, and, especially for demos,
terseness matters.  (It's obviously trivial to write a utility method if
this *is* the shortest way to do this, but then people in the audience
won't be able to execute the resulting code snippet without the utility
method.)

Thanks,

--Benjamin

(Continue reading)

Esteban Lorenzano | 1 Oct 17:41 2014
Picon

IMPORTANT: Contributing to "Configurated" sub-projects

Hi, 

As you might or might not seen, we are moving Pharo into a different architecture: From a monolitic
"one-image-is-all", we are (very slowly) going into an small kernel and a set of sub-projects who will
populate the image and provide all required features. 
In general, the idea is that the final state, what we call "Pharo" will stay as an unity with all the
tools/frameworks/libraries you already know and love, but the building process will be completely
different, allowing us to better manage the release process and allowing users to build their own
versions of specific pharos (I can imagine, for example, morphic-less pharos used in server
applications, etc.).

Well... this direction we are taking just made his first change, that can annoy a bit the community, until we
find a new equillibrium :)
Until now, most changes, bugfixes, etc. were contributed using old know SLICES, who make a good job in this
monilitic approach. 
And starting now, there are certain subprojects that cannot be managed like that anymore and has to be
managed through regular contributions to their repositories. Then, responsible guys from those
projects will submit an "Integration request" (something like a pull request), when they consider is
necesary an update to Pharo. 

Those projects are, for now: 

- Zinc (responsible is Sven)
- GTools (responsibles are Doru and Andrei)
- OSWindow (responsible is Igor)

We hope, with time, to move all non-kernel code into their respective sub-projects, all with their
responsibles, but for now, we started with this ones :)

(I hope this mail is understandable... I feel I'm being super confusing :P)
(Continue reading)

GitHub | 1 Oct 15:45 2014

[pharo-project/pharo-core] 6d0d66: 40276

  Branch: refs/heads/4.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 6d0d667c65fb0ff32cad8d3e06f8614ab93d1543
      https://github.com/pharo-project/pharo-core/commit/6d0d667c65fb0ff32cad8d3e06f8614ab93d1543
  Author: Jenkins Build Server <board@...>
  Date:   2014-10-01 (Wed, 01 Oct 2014)

  Changed paths:
    A ConfigurationOfGTInspector.package/ConfigurationOfGTInspector.class/instance/versions/version103_.st
    A ConfigurationOfGTPlayground.package/ConfigurationOfGTPlayground.class/instance/versions/version103_.st
    A ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version272_.st
    A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version121_.st
    M Glamour-Morphic-Renderer.package/GLMMorphicPharoCodeRenderer.class/instance/callbacks/evaluateAndPopPrintSelection.st
    R Glamour-Morphic-Renderer.package/GLMMorphicRenderer.class/instance/rendering presentations/renderRubricSmalltalkCodePresentation_.st
    R Glamour-Morphic-Renderer.package/GLMMorphicRubricSmalltalkCodeRenderer.class/README.md
    R Glamour-Morphic-Renderer.package/GLMMorphicRubricSmalltalkCodeRenderer.class/definition.st
    R Glamour-Morphic-Renderer.package/GLMMorphicRubricSmalltalkCodeRenderer.class/instance/rendering/morph.st
    M Glamour-Morphic-Widgets.package/GLMErrorPopper.class/README.md
    A Glamour-Morphic-Widgets.package/GLMErrorPopper.class/class/examples/simpleErrorPopper.st
    M Glamour-Morphic-Widgets.package/GLMPopper.class/README.md
    A Glamour-Morphic-Widgets.package/GLMPopper.class/class/utils/installAlarmFor_.st
    M Glamour-Morphic-Widgets.package/GLMPopper.class/instance/private/updateWithString_from_.st
    M Glamour-Morphic-Widgets.package/GLMPopperNotificationStrategy.class/README.md
    M Glamour-Morphic-Widgets.package/GLMPopperNotificationStrategy.class/instance/as yet unclassified/notify_at_in_.st
    M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/README.md
    A Glamour-Morphic-Widgets.package/GLMPrintPopper.class/class/examples/selectionEvaluationPopper.st
    A Glamour-Morphic-Widgets.package/GLMPrintPopper.class/class/examples/simpleObjectPopper.st
    M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/public/evaluateAndOpenFromRubric_.st
    A Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/public/openFromRubric_withResult_.st
    M Glamour-Presentations.package/GLMPrintSelection.class/README.md
(Continue reading)

GitHub | 1 Oct 15:45 2014

[pharo-project/pharo-core]

  Branch: refs/tags/40276
  Home:   https://github.com/pharo-project/pharo-core
Sven Van Caekenberghe | 1 Oct 15:14 2014
Picon

GTPlayground Play Button Semantics

Was it a conscious decision to make the GTPlayground Play button act as 'play all' (evaluate the whole
workspace contents) ?

If so, why ?

I find it quite limiting that I cannot select some expression and 'play it'. A workspace/playground is like
a notebook containing lots of different things.

Sven

GitHub | 1 Oct 15:12 2014

[pharo-project/pharo-core]

  Branch: refs/tags/40275
  Home:   https://github.com/pharo-project/pharo-core
GitHub | 1 Oct 15:12 2014

[pharo-project/pharo-core] f82136: 40275

  Branch: refs/heads/4.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: f821362cb2335e34c3c60ad34adccd29882fc70c
      https://github.com/pharo-project/pharo-core/commit/f821362cb2335e34c3c60ad34adccd29882fc70c
  Author: Jenkins Build Server <board@...>
  Date:   2014-10-01 (Wed, 01 Oct 2014)

  Changed paths:
    A GroupManager.package/GroupAnnouncer.class/class/initialization/reset.st
    A GroupManager.package/GroupAnnouncer.class/class/instance creation/uniqueInstance.st
    M GroupManager.package/GroupAnnouncer.class/definition.st
    M Nautilus.package/Nautilus.class/instance/announcement/announcer.st
    R NautilusCommon.package/NautilusAnnouncer.class/README.md
    R NautilusCommon.package/NautilusAnnouncer.class/definition.st
    R OpalCompiler-Core.package/IRBlockReturnTop.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRInstVarAccess.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRInstruction.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRJump.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRJumpIf.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRLiteralVariableAccess.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRMethod.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRPop.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRPushArray.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRPushClosureCopy.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRPushDup.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRPushLiteral.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRReceiverAccess.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRRemoteTempAccess.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRReturn.class/instance/visiting/accept_.st
    R OpalCompiler-Core.package/IRSend.class/instance/visiting/accept_.st
(Continue reading)

Sven Van Caekenberghe | 1 Oct 15:08 2014
Picon

Confused about the GTInspector State Tab

I am confused about the GTInspector State tab. What is its definition ?

I would say that it shows the raw, fundamental, implementation form of the object, in essence what
EyeBasicInspector showed. And that additional tabs offer alternative, more user friendly views.

Why then does it not show all variable content and only named variables ?

Try inspecting a [Byte]String or [Byte]Array. The State view is useless, it just shows self. Some of these
have an items view, but not all.

How can I inspect an individual character of a String ? Or an individual byte ?

Consider a Float. The State view should show the two (meaningless) slots because that is how Floats are
(currently) implemented, and then another tab should show the sign, mantissa, exponent view.

In the Eye inspectors we also confused these two aspects in a single view, which is wrong in hindsight, IMHO.
It should be crystal clear for a user whether a slot is real or an alternative view of describing the same thing.

I could propose changes or a slice, but I think we should agree on the definition of 'State' first.

Sven

GitHub | 1 Oct 14:10 2014

[pharo-project/pharo-core] 7e5c91: 40274

  Branch: refs/heads/4.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 7e5c915040ac9fea3447288cfe9f26f3f1e4244f
      https://github.com/pharo-project/pharo-core/commit/7e5c915040ac9fea3447288cfe9f26f3f1e4244f
  Author: Jenkins Build Server <board@...>
  Date:   2014-10-01 (Wed, 01 Oct 2014)

  Changed paths:
    A Morphic-Examples.package/ClassListExample.class/class/examples/example.st
    A Morphic-Examples.package/ClassTreeExample.class/class/examples/example.st
    A Morphic-Examples.package/LazyClassListExample.class/class/examples/example.st
    A Morphic-Examples.package/PackageTreeExample.class/class/examples/example.st
    A Morphic-Examples.package/SimpleGridExample.class/class/examples/example.st
    A Morphic-Examples.package/SimplestClassListExample.class/class/examples/example.st
    A Morphic-Examples.package/SimplestClassListWithChunkExample.class/class/examples/example.st
    A Morphic-Examples.package/SimplestClassListWithPagerExample.class/class/examples/example.st
    A Morphic-Examples.package/SimplestPaginatedClassListExample.class/class/examples/example.st
    A Morphic-Widgets-NewList.package/NewListRenderer.class/instance/communication with model/commandKeyTypedIntoMenu_.st
    M Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/registerToAnnouncements.st
    M Nautilus.package/AbstractNautilusUI.class/instance/announcement registration/registerToTestAnnouncements.st
    A OpalDecompiler.package/extension/CompiledMethod/instance/gtInspectorDecompilerIn_.st
    R SUnit-Core.package/TestAnnouncer.class/README.md
    R SUnit-Core.package/TestAnnouncer.class/definition.st
    A SUnit-Core.package/TestCase.class/class/accessing/historyAnnouncer.st
    M SUnit-Core.package/TestCase.class/class/history/history_.st
    M SUnit-Core.package/TestCase.class/definition.st
    M SUnit-Core.package/TestResult.class/instance/history/updateResultsInHistory.st
    A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script274.st
    A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40274.st
    M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
(Continue reading)

GitHub | 1 Oct 14:10 2014

[pharo-project/pharo-core]

  Branch: refs/tags/40274
  Home:   https://github.com/pharo-project/pharo-core
GitHub | 1 Oct 12:27 2014

[pharo-project/pharo-core] 11e333: 40273

  Branch: refs/heads/4.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 11e333080d87e57dd8d889e4088b73ad3b1440bd
      https://github.com/pharo-project/pharo-core/commit/11e333080d87e57dd8d889e4088b73ad3b1440bd
  Author: Jenkins Build Server <board@...>
  Date:   2014-10-01 (Wed, 01 Oct 2014)

  Changed paths:
    A ConfigurationOfGTInspector.package/ConfigurationOfGTInspector.class/instance/versions/version101_.st
    A ConfigurationOfGTInspector.package/ConfigurationOfGTInspector.class/instance/versions/version102_.st
    A ConfigurationOfGTPlayground.package/ConfigurationOfGTPlayground.class/instance/versions/version101_.st
    A ConfigurationOfGTPlayground.package/ConfigurationOfGTPlayground.class/instance/versions/version102_.st
    A ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version271_.st
    A GT-InspectorExtensions-Core.package/extension/CollectionValueHolder/instance/announcer.st
    M GT-InspectorExtensions-Core.package/extension/Dictionary/instance/gtInspectorItemsIn_.st
    R GT-InspectorExtensions-Core.package/extension/GLMSystemWindow/instance/gtInspectorOpenTreeIn_.st
    M GT-InspectorExtensions-Core.package/extension/String/instance/gtInspectorTextIn_.st
    M GT-Playground.package/GTPlayground.class/instance/accessing/acceptContents_.st
    M GT-Playground.package/GTPlaygroundPage.class/instance/compatibility-tools/acceptContents_.st
    M Glamour-Morphic-Renderer.package/GLMMorphicPharoPlaygroundRenderer.class/instance/as yet unclassified/workspaceBindingsStrategy.st
    M Glamour-Morphic-Renderer.package/GLMMorphicSmalltalkCodeRenderer.class/instance/private/workspaceBindingsStrategy.st
    M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/initialization/initializeInspectButton.st
    M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/initialization/initializeTextMorph.st
    A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script273.st
    A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40273.st
    M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st

  Log Message:
  -----------
  40273
(Continue reading)


Gmane