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

Re: [Pharo-dev] Refactoring File Package

by Guillermo Polito

The only encoder that makes a bit of noise to me is the ZnByteEncoder that contains a lot of mapping tables for mostly unused encodings (plus methods with metadata to recreate them)... El vie., 5 de jun. de 2015 a la(s) 6:30 p. m., Sven Van Caekenberghe < sven(a)stfx.eu> escribiÃ³: > > > On 05 Jun 2015, at 18:20, stepharo <stepharo(a)free.fr> wrote: > > > > Sven > > > > we were talking about splitting your package into two parts :) > > Would you be ok to get the basic encoders in a separate package? > > Zinc-Character-Encoding is already a separate package, it depends on > nothing. > Zinc-Resource-Meta is next up (containing URL and Mime-Type). > Both are completely independent of any HTTP stuff. > All this is by design. > > You probably mean that you want a separate config ? Right now they are > just a groups. > > > We were also thinking that NullEncoder could be called AsciiEncoder? > > Maybe, maybe not, let me think about that a bit. > > > Stef > > > >>> On 05 Jun 2015, at 18:09, Damien Cassou <damien.cassou(a)inria.fr> > wrote: > >>> > >>> > >>> Guillermo Polito <guillermopolito(a)gmail.com> writes: > >>> > >>>> Well, I made a cleaner implementation at the side with > >>>> > >>>> - a simple File object that is a sequential File as we all know > >>>> - a binary File stream on top of it that is composable with Zn > encoders and > >>>> other decorators > >>>> - a new interface to access Stdio streams > >>> that's really good news Guillermo. > >> Yes it is (need time to look at this in detail) > >> > >>> Is it ok to make File reading depend > >>> on Zinc? This sounds strange. Wouldn't that make bootstrapping harder? > >> It does not depend on the HTTP part, but on the Encoding part below it, > so that should be OK. > >> > >>> -- > >>> Damien Cassou > >>> http://damiencassou.seasidehosting.st > >>> > >>> "Success is the ability to go from one failure to another without > >>> losing enthusiasm." --Winston Churchill > >>> > >> > >> > > > > > > >

June 5, 2015

Re: [Pharo-dev] Refactoring File Package

by Sven Van Caekenberghe

> On 05 Jun 2015, at 18:20, stepharo <stepharo(a)free.fr> wrote: > > Sven > > we were talking about splitting your package into two parts :) > Would you be ok to get the basic encoders in a separate package? Zinc-Character-Encoding is already a separate package, it depends on nothing. Zinc-Resource-Meta is next up (containing URL and Mime-Type). Both are completely independent of any HTTP stuff. All this is by design. You probably mean that you want a separate config ? Right now they are just a groups. > We were also thinking that NullEncoder could be called AsciiEncoder? Maybe, maybe not, let me think about that a bit. > Stef > >>> On 05 Jun 2015, at 18:09, Damien Cassou <damien.cassou(a)inria.fr> wrote: >>> >>> >>> Guillermo Polito <guillermopolito(a)gmail.com> writes: >>> >>>> Well, I made a cleaner implementation at the side with >>>> >>>> - a simple File object that is a sequential File as we all know >>>> - a binary File stream on top of it that is composable with Zn encoders and >>>> other decorators >>>> - a new interface to access Stdio streams >>> that's really good news Guillermo. >> Yes it is (need time to look at this in detail) >> >>> Is it ok to make File reading depend >>> on Zinc? This sounds strange. Wouldn't that make bootstrapping harder? >> It does not depend on the HTTP part, but on the Encoding part below it, so that should be OK. >> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." --Winston Churchill >>> >> >> > >

June 5, 2015

Re: [Pharo-dev] Refactoring File Package

by stepharo

Yes this is really exciting. People we will need your help. PS: We are about to unload StringHolder and PseudoClasses :) 5 years that we dreamed about it. > Have you ever browsed the implementation of FileStream and checked > subclasses and friends? > > Well, I made a cleaner implementation at the side with > > - a simple File object that is a sequential File as we all know > - a binary File stream on top of it that is composable with Zn > encoders and other decorators > - a new interface to access Stdio streams > > Stdio stdin. > Stdio stdout. > ... > > All that with tests and comments. > > https://pharo.fogbugz.com/f/cases/15486/Refactor-File-Package > > Now, the system still has tons of references to the following classes > > FileStream -> 127 > StandardFileStream -> 24 > MultiByteFileStream -> 9 > > Most of them should be easily replaceable. Others may require wrapping > the binary file stream provided by a file with a Zn encoder or similar. > > So, if you have some minutes in your week and can replace 3, 4, 5 of > them, we will be a little step closer to simplify file handling and > dependencies :) > > Guille

June 5, 2015

Re: [Pharo-dev] Refactoring File Package

by stepharo

Sven we were talking about splitting your package into two parts :) Would you be ok to get the basic encoders in a separate package? We were also thinking that NullEncoder could be called AsciiEncoder? Stef >> On 05 Jun 2015, at 18:09, Damien Cassou <damien.cassou(a)inria.fr> wrote: >> >> >> Guillermo Polito <guillermopolito(a)gmail.com> writes: >> >>> Well, I made a cleaner implementation at the side with >>> >>> - a simple File object that is a sequential File as we all know >>> - a binary File stream on top of it that is composable with Zn encoders and >>> other decorators >>> - a new interface to access Stdio streams >> that's really good news Guillermo. > Yes it is (need time to look at this in detail) > >> Is it ok to make File reading depend >> on Zinc? This sounds strange. Wouldn't that make bootstrapping harder? > It does not depend on the HTTP part, but on the Encoding part below it, so that should be OK. > >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." --Winston Churchill >> > >

June 5, 2015

Re: [Pharo-dev] Roassal Camp Smalltalk

by stepharo

> Iâm interested in participating. Personally Iâd like to talk more about design decisions behind roassal ecosystem, release strategy and so on. Usually when I work with Roassal I have this issue that things are breaking because of rapid changes, or because of the differences between different parts of roassal. Maybe someone is also concerned about this, so we can discuss and maybe improve somethingâ¦ +1 I coudl also present a bit bloc because Roassal could ported to it :) > > Uko > >> On 04 Jun 2015, at 19:55, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >> Dear Colleagues and Friends, >> >> We are happy to announce we will organize a CampSmalltalk about the Roassal visualization engine, on _Sunday 12 July_. >> >> As far as we have seen, the interests are multiple. Here is a list of topics we will happy to work on: >> - Port of Roassal on VisualWorks >> - Using Roassal on Gemstone >> - HTML/JavaScript export >> - Improving Grapher, our charting library >> >> If you wish to participate, get in touch with us. Since we will probably have a sponsoring of the event, it would be nice to know how many will attend to ease the logistic and the pizza ordering :-) >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > >

June 5, 2015

Re: [Pharo-dev] Refactoring File Package

by Sven Van Caekenberghe

> On 05 Jun 2015, at 18:09, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > > Guillermo Polito <guillermopolito(a)gmail.com> writes: > >> Well, I made a cleaner implementation at the side with >> >> - a simple File object that is a sequential File as we all know >> - a binary File stream on top of it that is composable with Zn encoders and >> other decorators >> - a new interface to access Stdio streams > > that's really good news Guillermo. Yes it is (need time to look at this in detail) > Is it ok to make File reading depend > on Zinc? This sounds strange. Wouldn't that make bootstrapping harder? It does not depend on the HTTP part, but on the Encoding part below it, so that should be OK. > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill >

June 5, 2015

Re: [Pharo-dev] Refactoring File Package

by Damien Cassou

Guillermo Polito <guillermopolito(a)gmail.com> writes: > Well, I made a cleaner implementation at the side with > > - a simple File object that is a sequential File as we all know > - a binary File stream on top of it that is composable with Zn encoders and > other decorators > - a new interface to access Stdio streams that's really good news Guillermo. Is it ok to make File reading depend on Zinc? This sounds strange. Wouldn't that make bootstrapping harder? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

June 5, 2015

Re: [Pharo-dev] Roassal Camp Smalltalk

by Peter UhnÃ¡k

There sure are, look at ConfigurationOfRoassal2>>version*: and in my baseline I have something like ~~~~~~~~~~~ spec project: 'Roassal2' with: [ spec className: #ConfigurationOfRoassal2; versionString: '1.52'; repository: 'http://smalltalkhub.com/mc/ObjectProfile/Roassal2/main/' ]; ~~~~~~~~~~~ Peter On Fri, Jun 5, 2015 at 4:37 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > But are there numbered version to refer to? > > Uko > > On 05 Jun 2015, at 16:34, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > On Fri, Jun 5, 2015 at 3:29 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >> Iâm interested in participating. Personally Iâd like to talk more about >> design decisions behind roassal ecosystem, release strategy and so on. >> Usually when I work with Roassal I have this issue that things are breaking >> because of rapid changes, or because of the differences between different >> parts of roassal. Maybe someone is also concerned about this, so we can >> discuss and maybe improve somethingâ¦ >> > > Yes I am also interested in this, right now I am actually using quite old > version (month+) because I didn't have time to keep up. :) (Arguably 90% of > my problems were from infamous composite shapes. :)) > > Peter > >> >> Uko >> >> > On 04 Jun 2015, at 19:55, Alexandre Bergel <alexandre.bergel(a)me.com> >> wrote: >> > >> > Dear Colleagues and Friends, >> > >> > We are happy to announce we will organize a CampSmalltalk about the >> Roassal visualization engine, on _Sunday 12 July_. >> > >> > As far as we have seen, the interests are multiple. Here is a list of >> topics we will happy to work on: >> > - Port of Roassal on VisualWorks >> > - Using Roassal on Gemstone >> > - HTML/JavaScript export >> > - Improving Grapher, our charting library >> > >> > If you wish to participate, get in touch with us. Since we will >> probably have a sponsoring of the event, it would be nice to know how many >> will attend to ease the logistic and the pizza ordering :-) >> > >> > Cheers, >> > Alexandre >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> > >> >> >> > >

June 5, 2015

[pharo-project/pharo-core]

by GitHub

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

June 5, 2015

[pharo-project/pharo-core] 8d6c14: 50092

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 8d6c1469883bece21aa8a5de01bcc2fe81b84bbb https://github.com/pharo-project/pharo-core/commit/8d6c1469883bece21aa8a5de… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-05 (Fri, 05 Jun 2015) Changed paths: M Athens-Text.package/SimpleTextGlyphInfo.class/instance/initialization/loadFrom_.st M Balloon.package/ShortIntegerArray.class/instance/objects from disk/restoreEndianness.st M Balloon.package/ShortIntegerArray.class/instance/objects from disk/write_on_.st M FreeType.package/FT2GlyphSlot.class/instance/private/loadFrom_.st M FreeType.package/FT2Handle.class/instance/printing/printOn_.st M Fuel.package/FLEncoder.class/instance/encoding/encodeYourself.st M Fuel.package/FLWordObjectCluster.class/instance/serialize%2Fmaterialize/materializeInstanceWith_.st M Graphics-Display Objects.package/Form.class/instance/resources/readResourceFrom_.st M Graphics-Display Objects.package/Form.class/instance/resources/storeResourceOn_.st M Graphics-Files.package/PNGReadWriter.class/instance/accessing/nextImage.st M Graphics-Files.package/PNGReadWriter.class/instance/writing/nextPutImage_interlace_filter_.st M Graphics-Primitives.package/Bitmap.class/instance/accessing/copyFromByteArray_.st M Graphics-Primitives.package/Bitmap.class/instance/conversion/asByteArray.st M Graphics-Primitives.package/extension/ArrayedCollection/instance/restoreEndianness.st M Graphics-Transformations.package/MatrixTransform2x3.class/instance/objects from disk/restoreEndianness.st R Monticello-Tests.package/MCSerializationTest.class/instance/asserting/assertClass_providesServices_.st A Morphic-Core.package/DefaultExternalDropHandler.class/README.md A Morphic-Core.package/DefaultExternalDropHandler.class/class/initialization/initialize.st A Morphic-Core.package/DefaultExternalDropHandler.class/class/initialization/unload.st A Morphic-Core.package/DefaultExternalDropHandler.class/definition.st A Morphic-Core.package/DefaultExternalDropHandler.class/instance/private/chooseServiceFrom_.st A Morphic-Core.package/DefaultExternalDropHandler.class/instance/private/servicesForFileNamed_.st A Morphic-Core.package/DefaultExternalDropHandler.class/instance/private/unwantedSelectors.st A Morphic-Core.package/ExternalDropHandler.class/README.md A Morphic-Core.package/ExternalDropHandler.class/class/accessing/defaultHandler.st A Morphic-Core.package/ExternalDropHandler.class/class/accessing/defaultHandler_.st A Morphic-Core.package/ExternalDropHandler.class/class/accessing/lookupExternalDropHandler_.st A Morphic-Core.package/ExternalDropHandler.class/class/accessing/lookupServiceBasedHandler_.st A Morphic-Core.package/ExternalDropHandler.class/class/accessing/registerHandler_.st A Morphic-Core.package/ExternalDropHandler.class/class/cleanup/cleanUp.st A Morphic-Core.package/ExternalDropHandler.class/class/initialization/initialize.st A Morphic-Core.package/ExternalDropHandler.class/class/instance creation/type_extension_action_.st A Morphic-Core.package/ExternalDropHandler.class/class/private/chooseServiceFrom_.st A Morphic-Core.package/ExternalDropHandler.class/class/private/registeredHandlers.st A Morphic-Core.package/ExternalDropHandler.class/class/private/resetRegisteredHandlers.st A Morphic-Core.package/ExternalDropHandler.class/class/private/unwantedSelectors.st A Morphic-Core.package/ExternalDropHandler.class/definition.st A Morphic-Core.package/ExternalDropHandler.class/instance/accessing/extension.st A Morphic-Core.package/ExternalDropHandler.class/instance/accessing/handle_in_dropEvent_.st A Morphic-Core.package/ExternalDropHandler.class/instance/accessing/type.st A Morphic-Core.package/ExternalDropHandler.class/instance/initialize/type_extension_action_.st A Morphic-Core.package/ExternalDropHandler.class/instance/testing/matchesExtension_.st A Morphic-Core.package/ExternalDropHandler.class/instance/testing/matchesTypes_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50091.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50092.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50091.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50092.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R System-Support.package/DefaultExternalDropHandler.class/README.md R System-Support.package/DefaultExternalDropHandler.class/class/initialization/initialize.st R System-Support.package/DefaultExternalDropHandler.class/class/initialization/unload.st R System-Support.package/DefaultExternalDropHandler.class/definition.st R System-Support.package/DefaultExternalDropHandler.class/instance/private/chooseServiceFrom_.st R System-Support.package/DefaultExternalDropHandler.class/instance/private/servicesForFileNamed_.st R System-Support.package/DefaultExternalDropHandler.class/instance/private/unwantedSelectors.st A System-Support.package/EndianDetector.class/README.md A System-Support.package/EndianDetector.class/class/class initialization/initialize.st A System-Support.package/EndianDetector.class/class/endian/calcEndianness.st A System-Support.package/EndianDetector.class/class/endian/endianness.st A System-Support.package/EndianDetector.class/class/system startup/startUp_.st A System-Support.package/EndianDetector.class/class/testing/isBigEndian.st A System-Support.package/EndianDetector.class/class/testing/isLittleEndian.st A System-Support.package/EndianDetector.class/definition.st R System-Support.package/ExternalDropHandler.class/README.md R System-Support.package/ExternalDropHandler.class/class/accessing/defaultHandler.st R System-Support.package/ExternalDropHandler.class/class/accessing/defaultHandler_.st R System-Support.package/ExternalDropHandler.class/class/accessing/lookupExternalDropHandler_.st R System-Support.package/ExternalDropHandler.class/class/accessing/lookupServiceBasedHandler_.st R System-Support.package/ExternalDropHandler.class/class/accessing/registerHandler_.st R System-Support.package/ExternalDropHandler.class/class/cleanup/cleanUp.st R System-Support.package/ExternalDropHandler.class/class/initialization/initialize.st R System-Support.package/ExternalDropHandler.class/class/instance creation/type_extension_action_.st R System-Support.package/ExternalDropHandler.class/class/private/chooseServiceFrom_.st R System-Support.package/ExternalDropHandler.class/class/private/registeredHandlers.st R System-Support.package/ExternalDropHandler.class/class/private/resetRegisteredHandlers.st R System-Support.package/ExternalDropHandler.class/class/private/unwantedSelectors.st R System-Support.package/ExternalDropHandler.class/definition.st R System-Support.package/ExternalDropHandler.class/instance/accessing/extension.st R System-Support.package/ExternalDropHandler.class/instance/accessing/handle_in_dropEvent_.st R System-Support.package/ExternalDropHandler.class/instance/accessing/type.st R System-Support.package/ExternalDropHandler.class/instance/initialize/type_extension_action_.st R System-Support.package/ExternalDropHandler.class/instance/testing/matchesExtension_.st R System-Support.package/ExternalDropHandler.class/instance/testing/matchesTypes_.st M System-Support.package/SmalltalkImage.class/definition.st R System-Support.package/SmalltalkImage.class/instance/endian/calcEndianness.st R System-Support.package/SmalltalkImage.class/instance/endian/endianness.st R System-Support.package/SmalltalkImage.class/instance/endian/isBigEndian.st R System-Support.package/SmalltalkImage.class/instance/endian/isLittleEndian.st M System-Support.package/SmalltalkImage.class/instance/snapshot and quit/processShutDownList_.st R Tool-Changes.package/ChangeList.class/class/System-FileRegistry/browseCompressedChangesFile_.st M Tool-Changes.package/ChangeList.class/class/System-FileRegistry/fileReaderServicesForFile_suffix_.st R Tool-Changes.package/ChangeList.class/class/System-FileRegistry/serviceBrowseCompressedChangeFile.st M Tool-Changes.package/ChangeList.class/class/System-FileRegistry/services.st Log Message: ----------- 50092 15159 Move file drop handlers to morphic https://pharo.fogbugz.com/f/cases/15159 15701 Remove browse compressed changes https://pharo.fogbugz.com/f/cases/15701 15655 a MCWorkingCopy(ConfigurationOfRubric) https://pharo.fogbugz.com/f/cases/15655 15285 Clean endianness detection https://pharo.fogbugz.com/f/cases/15285 http://files.pharo.org/image/50/50092.zip

June 5, 2015