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

Re: [Pharo-dev] could the log message be placed on top of the files in the commit?

by Nicolas Cellier

2015-05-02 22:15 GMT+02:00 stepharo <stepharo(a)free.fr>: > Hi > > could we put the log of the commit on top before the touched files? > > Stef > > -1 files are SO important ;)

May 2, 2015

could the log message be placed on top of the files in the commit?

by stepharo

Hi could we put the log of the commit on top before the touched files? Stef

May 2, 2015

Re: [Pharo-dev] TextMorph right-click?

by Nicolai Hess

2015-05-02 17:27 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > btw, can someone remind we of the semantics of "Pluggable" here, and what > you gain over the unplugged classes? > cheers -ben > MVC with pluggable controller ? You can plug in the model and define the controller behavrior by supplying the different setter/getter selectors. > > On Sat, May 2, 2015 at 9:19 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> I think this is a bug, introduced early in the move from squeak to pharo. >> (It used to work in squeak). >> Although we don't have any use of a "pure" TextMorph (I don't know of any >> place/project, >> either it uses String/LabelMorphs for texts or it uses another >> TextEditorMorph), without any pluggableXXXMorph around it, I think we >> should fix this. >> >> 2015-05-02 12:44 GMT+02:00 Ben Coman <btc(a)openinworld.com>: >> >>> >>> On Sat, May 2, 2015 at 5:31 PM, Stephan Eggermont <stephan(a)stack.nl> >>> wrote: >>> >>>> TextMorph new contents: 'Text'; openInWorld >>> >>> >>> I don't know anything about this area, but thought it would be >>> interesting to dig... >>> >>> There is only one implementor of #editView which is TextMorphEditView, a >>> subclass of TextMorph. But... >>> TextMorphEditView new contents: 'Text'; openInWorld >>> >>> right-click gives... "MessageNotUnderstood: receiver of "model" is nil" >>> in TextMorphEditView>>handleInteraction: >>> in this code... >>> self editor model: editView model. "For evaluateSelection, etc" >>> where /editView/ ivar is nil. Only TextMorphEditView>>setEditView: >>> stores into this, and this has only one sender: >>> PluggableTextMorph>>configureTextMorph: >>> >>> Then I notice method "PluggableTextMorph class >> on: text: accept:", >>> so creating the following with usual accessors with Transcript tracing >>> in them... >>> >>> Object subclass: #MyData >>> instanceVariableNames: 'text' >>> classVariableNames: '' >>> category: 'MyPlay' >>> >>> The following lets me edit and save... >>> (PluggableTextMorph on: (MyData new text: 'hello') text: #text >>> accept: #text:) openInWorld >>> >>> Though saving doesn't clear the yellow triangle and I don't yet know how >>> to restrict it to one line without a scroll bar (if you needed that?) >>> >> >> We have PluggableTextFieldMorph, that is used in >> UITheme>>#newTextEntryIn: aThemedMorph for: aModel get: getSel set: >> setSel class: aClass getEnabled: enabledSel help: helpText >> >> >>> >>> cheers -ben >>> >> >> >

May 2, 2015

Re: [Pharo-dev] TextMorph right-click?

by Nicolai Hess

2015-05-02 20:17 GMT+02:00 Stephan Eggermont <stephan(a)stack.nl>: > On 02/05/15 15:19, Nicolai Hess wrote: > >> I think this is a bug, introduced early in the move from squeak to pharo. >> (It used to work in squeak). >> Although we don't have any use of a "pure" TextMorph (I don't know of >> any place/project, >> either it uses String/LabelMorphs for texts or it uses another >> TextEditorMorph), without any pluggableXXXMorph around it, I think we >> should fix this. >> > > I have 23 references to TextMorph in a 40556 image. > I meant, we don't use TextMorphs alone, as a manipulateable morph. Every text editing happens through some pluggableXXX morph. > > In writing about Morphic in MorphicDraw, I am looking for the simplest > classes that work. That should help when translating later to Bloc. > > Stephan > > >

May 2, 2015

Re: [Pharo-dev] [Pharo-users] ZnEasy / UTF-8

by Sven Van Caekenberghe

Hi Volkert, Thanks for the test case, it helped me figure out what the problem was. Basically, what Norbert said was 100% correct: the server code (Teapot) should have specified the charset or encoding of the mime-type it was using (so application/json;charset=utf-8 instead of just application/json). However, I thought I had changed the default to be utf-8, so I was surprised it was not picked up. It turned out utf-8 was the default for reading/writing http messages and their entities, but not so when manually constructing instances (like Teapot did). In code, json := '{''bank'':''RÃ©gion GenÃ¨ve RhÃ´ne''}'. entity := ZnEntity with: json type: 'application/json'. response := ZnResponse ok: entity. response encoder. did not return a ZnUTF8Encoder but a ZnNullEncoder. I changed that now. === Name: Zinc-HTTP-SvenVanCaekenberghe.428 Author: SvenVanCaekenberghe Time: 2 May 2015, 7:09:55.832482 pm UUID: 6376bd91-2a95-4265-bfff-e3c6626aee79 Ancestors: Zinc-HTTP-SvenVanCaekenberghe.427 Change ZnStringEntity>>#initializeEncoder to default to ZnUTF8Encoder unless ZnDefaultCharacterEncoder is set Change ZnEntityReader>>#readEntity to no longer use #withDefaultUtf8Decoder: (and remove it) Change ZnEntityWriter>>#writeEntity: to no longer use #withDefaultUtf8Encoder: (and remove it) Add ZnResponseTests>>#testDefaultUTF8Encoding === Name: Zinc-Tests-SvenVanCaekenberghe.226 Author: SvenVanCaekenberghe Time: 2 May 2015, 7:10:12.331593 pm UUID: 9010fbd6-bf9d-400e-b463-cb73920b79f6 Ancestors: Zinc-Tests-SvenVanCaekenberghe.225 Change ZnStringEntity>>#initializeEncoder to default to ZnUTF8Encoder unless ZnDefaultCharacterEncoder is set Change ZnEntityReader>>#readEntity to no longer use #withDefaultUtf8Decoder: (and remove it) Change ZnEntityWriter>>#writeEntity: to no longer use #withDefaultUtf8Encoder: (and remove it) Add ZnResponseTests>>#testDefaultUTF8Encoding === for now, in #bleedingEdge of Zinc HTTP Components. HTH, Sven > On 01 May 2015, at 15:53, volkert <volkert(a)komponentenwerkstatt.de> wrote: > > Here a stripped down example > > d := { 'bank' -> 'RÃ©gion GenÃ¨ve RhÃ´ne'. } asDictionary. > > teapot := Teapot configure: { > #defaultOutput -> #json. > #port -> 8081. > #debugMode -> true > }. > > teapot > GET: '/api/d' -> d; > exception: KeyNotFound -> (TeaResponse notFound body: 'asd'); > start. > > (ZnEasy get: 'http://localhost:8081/api/d') entity string. > > Pharo 4.0 / Teapot > > BW, > Volkert > > > > Am 01.05.2015 um 15:35 schrieb Sven Van Caekenberghe: >>> On 01 May 2015, at 15:15, volkert <volkert(a)komponentenwerkstatt.de> wrote: >>> >>> I thought UTF-8 is the default encoding in case JSON Documents, and so for the Content-Type: application/json. >>> >>> I added "setCharSetUTF8" this Teapot-Output and all works fine now. :-) >> Fine, but I still think this is strange, it should work by default too. >> But to understand what went wrong, I need an example (server+client) that I can run. >> >>> Danke, >>> Volkert >>> >>> Am 01.05.2015 um 14:20 schrieb Norbert Hartl: >>>> You need to look at the headers of the request. I would assume the sender sets an Content-Type: application/json without charset. In that moment it is uncertain what has to be done because the server needs to assume what charset it might be and this tasks seldomly works out good. >>>> In order to make it work set a content type of your entity this way >>>> >>>> ZnMimeType applicationJson setCharSetUTF8 >>>> >>>> Now you send a Content-Type of application/json;charset=utf-8 and the server knows which character decoder to use. That should be it. So please always assign a char set to your sending data to make it more reliable what happens on the other end. >>>> >>>> hope this helps, >>>> >>>> Norbert >>>>> Am 01.05.2015 um 14:13 schrieb volkert <volkert(a)komponentenwerkstatt.de>: >>>>> >>>>> I tried ZnClient new get: 'http://<removed>/api/atm/801813'; yourself and got. >>>>> >>>>> <fdchdjab.png> >>>>> >>>>> This is the Doc i see in Firefox. >>>>> >>>>> <fceagiec.png> >>>>> >>>>> The JSON is served with ZnServer / Teapot. ;-) >>>>> >>>>> Volkert >>>>> >>>>> >>>>> Am 01.05.2015 um 12:21 schrieb Sven Van Caekenberghe: >>>>>> Hi Volkert, >>>>>> >>>>>> Tip 1: use ZnClient and inspect the response in detail, more specifically to see whether the response content type specifies the encoding. >>>>>> >>>>>> ZnClient new get: ' >>>>>> http:// >>>>>> <removed>/api/atm/801813'; yourself. >>>>>> >>>>>> Tip 2: you could try to force override the default encoding using ZnDefaultCharacterEncoder (see the class comment). >>>>>> >>>>>> But recent Zn code defaults to UTF8 (see #withDefaultUTF8Decoding: and #withDefaultUTF8Encoding:). So I am curious to see the response headers. >>>>>> >>>>>> HTH, >>>>>> >>>>>> Sven >>>>>> >>>>>> >>>>>>> On 01 May 2015, at 11:54, volkert <volkert(a)komponentenwerkstatt.de> >>>>>>> wrote: >>>>>>> >>>>>>> Dear all, >>>>>>> >>>>>>> i am trying to get a JSON Document with ZnEasy. The Document is UTF-8 encoded. >>>>>>> >>>>>>> (ZnEasy get: ' >>>>>>> http:// >>>>>>> <removed>/api/atm/801813') entity string. >>>>>>> <gccacjeh.png> >>>>>>> >>>>>>> Any hints? >>>>>>> >>>>>>> Volkert >>>>>>> >>>>>>> >>>>>>> >> > >

May 2, 2015

Re: [Pharo-dev] TextMorph right-click?

by Stephan Eggermont

On 02/05/15 15:19, Nicolai Hess wrote: > I think this is a bug, introduced early in the move from squeak to pharo. > (It used to work in squeak). > Although we don't have any use of a "pure" TextMorph (I don't know of > any place/project, > either it uses String/LabelMorphs for texts or it uses another > TextEditorMorph), without any pluggableXXXMorph around it, I think we > should fix this. I have 23 references to TextMorph in a 40556 image. In writing about Morphic in MorphicDraw, I am looking for the simplest classes that work. That should help when translating later to Bloc. Stephan

May 2, 2015

[pharo-project/pharo-core]

by GitHub

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

May 2, 2015

[pharo-project/pharo-core] 7554e4: 50027

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 7554e430b71ac42468fa98995dd45df7f831237f https://github.com/pharo-project/pharo-core/commit/7554e430b71ac42468fa9899… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-05-02 (Sat, 02 May 2015) Changed paths: M ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/symbolic versions/stable_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version1213_.st M ConfigurationOfZincHTTPComponents.package/ConfigurationOfZincHTTPComponents.class/instance/accessing/stable_.st A ConfigurationOfZincHTTPComponents.package/ConfigurationOfZincHTTPComponents.class/instance/versions/version264_.st M Rubric.package/RubShoutStylerDecorator.class/README.md M Rubric.package/RubShoutStylerDecorator.class/definition.st M Rubric.package/RubShoutStylerDecorator.class/instance/accessing/next_.st M Rubric.package/RubShoutStylerDecorator.class/instance/private/aboutToBeUnplugged.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script635.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script636.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50026.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50027.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Zinc-HTTP.package/ZnClient.class/instance/private protocol/prepareRedirect.st M Zinc-HTTP.package/ZnCookie.class/instance/initialize-release/fromString_.st M Zinc-HTTP.package/ZnCredential.class/class/accessing/findRealmFor_.st M Zinc-HTTP.package/ZnDigestAuthenticator.class/class/accessing/parseAuthRequest_.st M Zinc-HTTP.package/ZnLogEvent.class/class/convenience/stopLoggingToTranscript.st A Zinc-Resource-Meta-Core.package/ZnMaximumNumberOfDictionaryEntries.class/README.md A Zinc-Resource-Meta-Core.package/ZnMaximumNumberOfDictionaryEntries.class/definition.st M Zinc-Resource-Meta-Core.package/ZnMimeType.class/class/instance creation/main_sub_.st M Zinc-Resource-Meta-Core.package/ZnMimeType.class/class/instance creation/main_sub_parameters_.st A Zinc-Resource-Meta-Core.package/ZnMultiValueDictionary.class/class/accessing/defaultLimit.st R Zinc-Resource-Meta-Core.package/ZnMultiValueDictionary.class/instance/accessing/defaultLimit.st M Zinc-Resource-Meta-Core.package/ZnMultiValueDictionary.class/instance/initialize-release/initialize_.st M Zinc-Resource-Meta-Core.package/ZnUrl.class/instance/accessing-path/closePath.st M Zinc-Resource-Meta-Core.package/ZnUrl.class/instance/comparing/=.st M Zinc-Resource-Meta-Core.package/ZnUrl.class/instance/comparing/equals_.st A Zinc-Resource-Meta-Tests.package/ZnMultiValueDictionaryTests.class/instance/testing/testDynamicLimit.st A Zinc-Resource-Meta-Tests.package/ZnUrlTests.class/instance/testing/testQueryRemoveAll.st M Zinc-Tests.package/ZnClientTests.class/instance/testing/testLogging.st A Zinc-Tests.package/ZnClientTests.class/instance/testing/testRelativeRedirect307.st Log Message: ----------- 50027 15457 Update Zinc to handle some deprecations in Pharo 5 https://pharo.fogbugz.com/f/cases/15457 15463 Rubric turns text to transparent when styling https://pharo.fogbugz.com/f/cases/15463 http://files.pharo.org/image/50/50027.zip

May 2, 2015

Re: [Pharo-dev] Improving the About Text of Versionner

by Ben Coman

Except, can someone advise, is Versioneer Slice based or Configuration based? cheers -ben On Sun, May 3, 2015 at 12:14 AM, Ben Coman <btc(a)openinworld.com> wrote: > Look good Sergio. Per Sven's comments, I think its worth you opening an > issue for this and a submitting it as a slice to be integrated. > cheers -ben > > On Sat, May 2, 2015 at 11:15 PM, Sven Van Caekenberghe <sven(a)stfx.eu> > wrote: > >> Hi Sergio, >> >> It is great that you want to contribute ! >> >> Have you seen http://pharo.org/contribute and more specifically >> http://pharo.org/contribute-propose-fix ? >> >> It is a bit of work to get started, but once you have everything set up >> and understand the process, the next contribution will go much faster! >> >> Sven >> >> > On 02 May 2015, at 16:34, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: >> > >> > This seemed a fairly easy change so I can keep honing my contributing >> skills. >> > >> > I came up with this About text for the tool. >> > >> > Below is a screenshot on how it looks: >> > >> > <About_text_of_Versionner.png> >> > â >> > >> > Here's the text: >> > >> > Versionner is a GUI for Metacello that allows you to use a nice (but >> limited, as are most GUI tools) tool instead of writing configs by hand. >> > >> > Metacello is a package management system that declares dependencies >> between >> > those packages in configuration classes. >> > >> > Monticello is our SCM system that groups code into packages. >> > >> > For a tutorial video on how to use Versionner: >> > https://youtu.be/cFRJDuWL-Q0 >> > >> >> >> >

May 2, 2015

Re: [Pharo-dev] Improving the About Text of Versionner

by Ben Coman

Look good Sergio. Per Sven's comments, I think its worth you opening an issue for this and a submitting it as a slice to be integrated. cheers -ben On Sat, May 2, 2015 at 11:15 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi Sergio, > > It is great that you want to contribute ! > > Have you seen http://pharo.org/contribute and more specifically > http://pharo.org/contribute-propose-fix ? > > It is a bit of work to get started, but once you have everything set up > and understand the process, the next contribution will go much faster! > > Sven > > > On 02 May 2015, at 16:34, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: > > > > This seemed a fairly easy change so I can keep honing my contributing > skills. > > > > I came up with this About text for the tool. > > > > Below is a screenshot on how it looks: > > > > <About_text_of_Versionner.png> > > â > > > > Here's the text: > > > > Versionner is a GUI for Metacello that allows you to use a nice (but > limited, as are most GUI tools) tool instead of writing configs by hand. > > > > Metacello is a package management system that declares dependencies > between > > those packages in configuration classes. > > > > Monticello is our SCM system that groups code into packages. > > > > For a tutorial video on how to use Versionner: > > https://youtu.be/cFRJDuWL-Q0 > > > > >

May 2, 2015