December 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] 12259: FileSystem memory reads writesusing a binary stream by default

by Sven Van Caekenberghe

On 04 Dec 2013, at 13:14, Max Leske <maxleske(a)gmail.com> wrote: > Let me see what I can come up with. To be somewhat compatible with existing streams, your memory stream should have the concept of âi am binary or textualâ and be able to switch in-place between these two states (#binary, #ascii). Depending on its state it should then return bytes or characters (or collections thereof). Have a look at ZnLimitedReadStream>>#next and/or ZnBivalentWriteStream>>#nextPut: To be 100% correct, encoding should be selectable. But maybe a default to utf-8 would be enough. You could have a look at ZnCharacter[Read|Write]Stream for inspiration. My 2c. > On 03.12.2013, at 19:36, Damien Cassou <damien.cassou(a)gmail.com> wrote: > >> Thanks Max for the report. Do you have an idea on how we could solve the problem ? The previous behaviour was not acceptable either because the streams that came out of a memory filesystem were the only ones with binary content >> >> On Dec 3, 2013 5:35 PM, "Max Leske" <maxleske(a)gmail.com> wrote: >> Damien, Marcus >> >> this change breaks a lot of things in FileSystem-Git. I donât disagree with the idea that reading characters should be default (one could argue about itâ¦) but your change makes it IMPOSSIBLE to read bytes because unprintable characters are discarded! So if my ByteArray is a NULL terminated string, for instance, I can not check for the NULL termination anymore. >> >> Cheers, >> Max >

Dec. 4, 2013

[pharo-project/pharo-core]

by GitHub

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

Dec. 4, 2013

[pharo-project/pharo-core] 8868cb: 30620

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 8868cb330f982ca2d1c6041c3355a9dade9efbc9 https://github.com/pharo-project/pharo-core/commit/8868cb330f982ca2d1c6041c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-12-04 (Wed, 04 Dec 2013) Changed paths: M Komitter.package/KomitNewSlice.class/instance/accessing/remote.st M Komitter.package/Komitter.class/class/icon/iconData.st A SUnit-Core.package/extension/Deprecation/instance/sunitAnnounce_toResult_.st A SUnit-Tests.package/SUnitTest.class/instance/helpers/deprecatedMessage.st A SUnit-Tests.package/SUnitTest.class/instance/testing/raiseDeprecationWarnings.st A SUnit-Tests.package/SUnitTest.class/instance/testing/testIgnoreDeprecationWarnings.st A SUnit-Tests.package/SUnitTest.class/instance/testing/testRaiseDeprecationWarnings.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script275.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30620.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30620 12272 Better algorithm for finding the inbox https://pharo.fogbugz.com/f/cases/12272 12334 Nautilus codepane hides first lines if pin is set https://pharo.fogbugz.com/f/cases/12334 11423 Running unit tests that raise deprecation warnings makes them fail incomprehensibly https://pharo.fogbugz.com/f/cases/11423 http://files.pharo.org/image/30/30620.zip

Dec. 4, 2013

Re: [Pharo-dev] Komitter

by Yuriy Tymchuk

On 04 Dec 2013, at 14:56, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > On Wed, Dec 4, 2013 at 2:47 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) >> the repository problem is an issue with the credentials. >> The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P >> >> The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain. > > Yes, true. You can just add refresh button. E.i. for me itâs easier to press button rather then closing and opening window. > > I was thinking on that too, yep :) SourceTree works like that and none complains. Of course it has some auto-refresh, but we can survive without that. Uko > > > Uko > >> We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P >> >> Ben >> >> On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >>> Hi guys, >>> >>> Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day? >>> >>> Also why canât I access anything else when Komitter window is open? >>> >>> Uko >> > >

Dec. 4, 2013

Re: [Pharo-dev] [ANN] Roassal 3d

by Tudor Girba

Great! Doru On Wed, Dec 4, 2013 at 2:29 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Dear Friends and Colleagues, > > We are happy to (officially) announce Roassal 3d. Roassal 3d is about > creating and animating 3d scenes. It is meant to visualize data. Roassal 3d > recently got textures, translucence, additional layouts and various light > models. > > It would be great to receive feedback. Ronie worked very hard on making > Roassal3d happen. Milton has put quite some effort on writing documentation > and writing examples. A very preliminary version of the documentation may > be found on: > https://www.dropbox.com/s/mctbza5qfcdxbs3/Roassal3dtutorial.pdf > > The screenshots contained in this documentation should convey an accurate > feeling of what Roassal 3d is up to. > > Loading Roassal 3d in Pharo 3.0 is trivial, thanks to a configuration. > Simply open a workspace and do-it the following code: > Gofer new smalltalkhubUser: 'ronsaldo' project: 'roassal3d'; package: > 'ConfigurationOfRoassal3d'; load. (Smalltalk at: #ConfigurationOfRoassal3d) > loadDevelopment > > We are also looking for contributors to the documentation, we plan to have > a book chapter on it. Get in touch with us! > > Thanks to Usman, Jean-Baptiste, Igor for their help and contributions. > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 4, 2013

Re: [Pharo-dev] Komitter

by Esteban Lorenzano

On Wed, Dec 4, 2013 at 2:47 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> > wrote: > > I did not annonce it yet since some features are missing, and few bugs > needs to be fixed (actually the slice are waiting to be integrated :P) > the repository problem is an issue with the credentials. > The slice is in the issue tracker. If you want to not bump this, set your > credentials from MC browser once and for all :P > > The window is modal since otherwise, it needs to be kept in sync with the > system, which is a pain. > > > Yes, true. You can just add refresh button. E.i. for me itâs easier to > press button rather then closing and opening window. > I was thinking on that too, yep :) > > Uko > > We already discuss the fact itâs modal, so maybe it will disappear soon > since we are still not strongly convinced in one way or the other :P > > Ben > > On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi guys, > > Iâm very impressed with the new Komitter tool that Iâve found in Pharo > today. Itâs a really important tool that we really need. Itâs amazing that > you can at last see what is changed and pick what you want to commit. Also > the startup gear animation is cool. Only one question: should I complain > about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ > when trying to commit, or itâs work in progress and everything is changing > each day? > > Also why canât I access anything else when Komitter window is open? > > Uko > > > >

Dec. 4, 2013

Re: [Pharo-dev] Komitter

by Yuriy Tymchuk

Thanks once more for your effort. This is a really important tool for me. Uko On 04 Dec 2013, at 14:52, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > I will give a try later today :P > > Ben > > On 04 Dec 2013, at 14:47, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> >> On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> >>> I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) >>> the repository problem is an issue with the credentials. >>> The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P >>> >>> The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain. >> >> Yes, true. You can just add refresh button. E.i. for me itâs easier to press button rather then closing and opening window. >> >> Uko >> >>> We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P >>> >>> Ben >>> >>> On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> >>>> Hi guys, >>>> >>>> Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day? >>>> >>>> Also why canât I access anything else when Komitter window is open? >>>> >>>> Uko >>> >> >

Dec. 4, 2013

Re: [Pharo-dev] Komitter

by Benjamin

I will give a try later today :P Ben On 04 Dec 2013, at 14:47, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > >> I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) >> the repository problem is an issue with the credentials. >> The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P >> >> The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain. > > Yes, true. You can just add refresh button. E.i. for me itâs easier to press button rather then closing and opening window. > > Uko > >> We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P >> >> Ben >> >> On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >>> Hi guys, >>> >>> Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day? >>> >>> Also why canât I access anything else when Komitter window is open? >>> >>> Uko >> >

Dec. 4, 2013

Re: [Pharo-dev] StartupAction and StartupLoader

by Benjamin

I do not think so :P Ben On 04 Dec 2013, at 14:45, Roberto Minelli <roberto.minelli(a)usi.ch> wrote: > Hi, > > Is there any way to specify the order of the preferences? > > Now I put a couple of .st files in my ~/Library/Preferences/pharo folder containing calls to > > StartupLoader default executeAtomicItems: { > StartupAction > name: 'Setting my preferences...' > code: [ â¦ ] > > and I am wondering if there is a way to specify the order in which those files are accessed. > > Cheers, > R

Dec. 4, 2013

Re: [Pharo-dev] Komitter

by Yuriy Tymchuk

On 04 Dec 2013, at 14:42, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > I did not annonce it yet since some features are missing, and few bugs needs to be fixed (actually the slice are waiting to be integrated :P) > the repository problem is an issue with the credentials. > The slice is in the issue tracker. If you want to not bump this, set your credentials from MC browser once and for all :P > > The window is modal since otherwise, it needs to be kept in sync with the system, which is a pain. Yes, true. You can just add refresh button. E.i. for me itâs easier to press button rather then closing and opening window. Uko > We already discuss the fact itâs modal, so maybe it will disappear soon since we are still not strongly convinced in one way or the other :P > > Ben > > On 04 Dec 2013, at 14:35, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >> Hi guys, >> >> Iâm very impressed with the new Komitter tool that Iâve found in Pharo today. Itâs a really important tool that we really need. Itâs amazing that you can at last see what is changed and pick what you want to commit. Also the startup gear animation is cool. Only one question: should I complain about getting "MCKomitSubmitter(Object)>>doesNotUnderstand: #repositoryâ when trying to commit, or itâs work in progress and everything is changing each day? >> >> Also why canât I access anything else when Komitter window is open? >> >> Uko >

Dec. 4, 2013