- Pharo-dev - lists.pharo.org

tricks for XML parsing.

by stepharo

Hi guys these free books may be interesting for you http://aosabook.org/ http://aosabook.org/en/posa/parsing-xml-at-the-speed-of-light.html stef

July 13, 2016

Re: [Pharo-dev] What is the correct way to create new integration configuration?

by Tudor Girba

Thanks a lot, Juraj! Doru > On Jul 13, 2016, at 3:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > >> >> 13. 7. 2016 v 9:32, Marcus Denker <marcus.denker(a)inria.fr>: >> >> >>> On 13 Jul 2016, at 14:46, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: >>> >>> Hi, >>> >>> I am working on a new configuration for GTools. >>> >>> What is the correct way to integrate cases with a slice? >>> For example this one: https://pharo.fogbugz.com/f/cases/18471/GTTools-relies-on-hasSpecialSelecto… >>> It has slice in Pharo60Inbox. Should I copy commits to GToolkit repository? >>> >> This one is not yet integrated, I submitted a slice to not have to wait for GT, but with my pre-holiday stress I did not menage to actually >> get it in yet. >> >> So instead you can ignore the slice and just get these changes in. > > OK. I am preparing new configuration here: https://pharo.fogbugz.com/f/cases/18773/ > I am almost done. > I will take care of GTool integrations. So next time there is something to integrate, just ping me. Anyway, i will regularly check FogBugz. > >> >>> And how it happens that GToolkit repository has commits done by TheIntegrator? >> >> The auto-rewriting deprecations happen to rewrite code. This then is saved in the Pharo repo and needs to be merged. >> (or if it is the latest it can just be copied). >> >> The same happens if changes have to be done fast or if they cross-cut many packages. >> >> it is a bit of a messâ¦ for the future we need a unified way to handle thingsâ¦ the current approach with the configurations and >> external repositories is not good.. far too slow and far too much manual work. > > Thatâs true. It is a lot of manual work and it is also hard to know if I integrate it well, with all changes, etc. > > Cheers, > Juraj > >> >> Marcus -- www.tudorgirba.com www.feenk.com "When people care, great things can happen."

July 13, 2016

Re: [Pharo-dev] What is the correct way to create new integration configuration?

by Juraj Kubelka

> 13. 7. 2016 v 9:32, Marcus Denker <marcus.denker(a)inria.fr>: > > >> On 13 Jul 2016, at 14:46, Juraj Kubelka <juraj.kubelka(a)icloud.com <mailto:juraj.kubelka@icloud.com>> wrote: >> >> Hi, >> >> I am working on a new configuration for GTools. >> >> What is the correct way to integrate cases with a slice? >> For example this one: https://pharo.fogbugz.com/f/cases/18471/GTTools-relies-on-hasSpecialSelecto… <https://pharo.fogbugz.com/f/cases/18471/GTTools-relies-on-hasSpecialSelecto…> >> It has slice in Pharo60Inbox. Should I copy commits to GToolkit repository? >> > This one is not yet integrated, I submitted a slice to not have to wait for GT, but with my pre-holiday stress I did not menage to actually > get it in yet. > > So instead you can ignore the slice and just get these changes in. OK. I am preparing new configuration here: https://pharo.fogbugz.com/f/cases/18773/ <https://pharo.fogbugz.com/f/cases/18773/> I am almost done. I will take care of GTool integrations. So next time there is something to integrate, just ping me. Anyway, i will regularly check FogBugz. > >> And how it happens that GToolkit repository has commits done by TheIntegrator? > > The auto-rewriting deprecations happen to rewrite code. This then is saved in the Pharo repo and needs to be merged. > (or if it is the latest it can just be copied). > > The same happens if changes have to be done fast or if they cross-cut many packages. > > it is a bit of a messâ¦ for the future we need a unified way to handle thingsâ¦ the current approach with the configurations and > external repositories is not good.. far too slow and far too much manual work. Thatâs true. It is a lot of manual work and it is also hard to know if I integrate it well, with all changes, etc. Cheers, Juraj > > Marcus >

July 13, 2016

Re: [Pharo-dev] What is the correct way to create new integration configuration?

by Marcus Denker

> On 13 Jul 2016, at 14:46, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > > Hi, > > I am working on a new configuration for GTools. > > What is the correct way to integrate cases with a slice? > For example this one: https://pharo.fogbugz.com/f/cases/18471/GTTools-relies-on-hasSpecialSelecto… <https://pharo.fogbugz.com/f/cases/18471/GTTools-relies-on-hasSpecialSelecto…> > It has slice in Pharo60Inbox. Should I copy commits to GToolkit repository? > This one is not yet integrated, I submitted a slice to not have to wait for GT, but with my pre-holiday stress I did not menage to actually get it in yet. So instead you can ignore the slice and just get these changes in. > And how it happens that GToolkit repository has commits done by TheIntegrator? The auto-rewriting deprecations happen to rewrite code. This then is saved in the Pharo repo and needs to be merged. (or if it is the latest it can just be copied). The same happens if changes have to be done fast or if they cross-cut many packages. it is a bit of a messâ¦ for the future we need a unified way to handle thingsâ¦ the current approach with the configurations and external repositories is not good.. far too slow and far too much manual work. Marcus

July 13, 2016

What is the correct way to create new integration configuration?

by Juraj Kubelka

Hi, I am working on a new configuration for GTools. What is the correct way to integrate cases with a slice? For example this one: https://pharo.fogbugz.com/f/cases/18471/GTTools-relies-on-hasSpecialSelecto… <https://pharo.fogbugz.com/f/cases/18471/GTTools-relies-on-hasSpecialSelecto…> It has slice in Pharo60Inbox. Should I copy commits to GToolkit repository? And how it happens that GToolkit repository has commits done by TheIntegrator? Thanks, Juraj

July 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ac9f62: 60149

by Marcus Denker

> On 13 Jul 2016, at 10:03, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> http://files.pharo.org/image/60/60149.zip >> >> > Strangely it did not build. Wasted already >1 hour on thisâ¦ > Now it is there. Marcus

July 13, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ac9f62: 60149

by Marcus Denker

> > http://files.pharo.org/image/60/60149.zip > > Strangely it did not build. Wasted already >1 hour on thisâ¦ Marcus

July 13, 2016

[pharo-project/pharo-core]

by GitHub

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

July 13, 2016

[pharo-project/pharo-core] ac9f62: 60149

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ac9f62ce8dea687da1b6f7675d47f43bee08dc65 https://github.com/pharo-project/pharo-core/commit/ac9f62ce8dea687da1b6f767… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-13 (Wed, 13 Jul 2016) Changed paths: A OpalCompiler-Core.package/AbstractCompiler.class/instance/accessing/encoderClass_.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/other-tests/testDifferentBlocksWithSameArgumentName.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/other-tests/testModulePrimitive.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/test - array compilation/testMultiElementArray.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/test - array compilation/testSimpleArray.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/test - block returning/testBlockReturning.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testBlockTemp.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testMethodArgument.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testMethodTemp.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testOneFloat.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testReturnBlockInMethod.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testSetUp.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testSteamContentsLimitedToSequenceableCollectionClass.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testToDoArgumentNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testToDoInsideTempNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testToDoOutsideTempNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testWhileModificationAfterNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testWhileModificationBeforeNotInlined.st M OpalCompiler-Tests.package/OCNewCompilerWithChangesFunctionalTests.class/instance/tests/testWhileWithTempNotInlined.st M Pharo-Help.package/PharoWelcomePage.class/class/accessing/title.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60148.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60149.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60148.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60149.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Examples.package/DynamicWidgetChange.class/instance/private/changeToButton.st M Spec-Examples.package/DynamicWidgetChange.class/instance/private/changeToList.st M System-Support.package/SystemVersion.class/instance/printing/shortVersionString.st Log Message: ----------- 60149 18390 System version should be "Pharo 6.0" instead of "Pharo6.0" and PharoWelcomePage should not hard code version https://pharo.fogbugz.com/f/cases/18390 18748 OpalCompiler Tests: OCNewCompilerWithChangesFunctionalTests should set encoder to OpalEncoderForV3PlusClosures https://pharo.fogbugz.com/f/cases/18748 15688 Remove ComposableModel>>#instantiateModels:s senders in Spec-Examples https://pharo.fogbugz.com/f/cases/15688 http://files.pharo.org/image/60/60149.zip

July 13, 2016

Re: [Pharo-dev] bloc status update: june 2016

by stepharo

For now it means that we can write "World new open" and we can use this to write tests. We have Bloc2 SDL worlds side by side and the goal is to have everything ready (tools and widgets) and to get rid of the morphic one. In Bloc1 we did not have other physical window so we had too many constraints and morphic infection points. But we could run Morphic inside Bloc. In Bloc2 this is not possible but we get a better event bubbling model and other possibilities. Stef Le 13/7/16 Ã 03:27, Brad Selfridge a Ã©crit : > Does this mean "worlds within worlds" or "worlds adjacent to other worlds". > If adjacent, will they be able to communicate with each other? > > > > > ----- > Brad Selfridge > -- > View this message in context: http://forum.world.st/bloc-status-update-june-2016-tp4901988p4906373.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

July 13, 2016