Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
- 3 participants
- 144636 messages
TextHighlightByBounds
by Sean P. DeNigris
This is a weird class. It is a "definition of a clickable highlighted range
of text", but by point co-ordinates?! Why isn't this done using intervals
into the text? I discovered this while investigating whether DiffMorph could
wrap the text, but since the highlights are point-based, the highlights no
longer match up with the text.
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/TextHighlightByBounds-tp4836591.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
July 8, 2015
Re: [Pharo-dev] https://readthedocs.org/
by Damien Cassou
phil(a)highoctane.be <phil(a)highoctane.be> writes:
> How would we integrated pillar html output in here?
>
> https://readthedocs.org/
there is already a prototype Pillar's gitbook exporter that worked well when I
wrote it. This uses the Markdown exporter.
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
July 8, 2015
[pharo-project/pharo-core]
by GitHub
Branch: refs/tags/50161
Home: https://github.com/pharo-project/pharo-core
July 8, 2015
[pharo-project/pharo-core] d52cad: 50161
by GitHub
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: d52cad20f5a0ea149b6de6a14c6eadef93a7ea47
https://github.com/pharo-project/pharo-core/commit/d52cad20f5a0ea149b6de6a1…
Author: Jenkins Build Server <board(a)pharo-project.org>
Date: 2015-07-08 (Wed, 08 Jul 2015)
Changed paths:
M Gofer-Core.package/Gofer.class/instance/repositories/url_username_password_.st
R Gofer-Core.package/extension/ZnUrl/instance/asFileReferenceWithRelativePath.st
R Gofer-Core.package/extension/ZnUrl/instance/mcRepositoryAsUser_withPassword_.st
A Metacello-GitHub.package/MCGitHubRepository.class/class/accessing/urlSchemes.st
A Metacello-GitHub.package/MCGitHubRepository.class/class/instance creation/basicFromUrl_.st
A Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateFileRepositoryFromUrl.st
A Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateFiletreeRepositoryFromUrl.st
A Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateFtpRepositoryFromUrl.st
A Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateGitHubRepositoryFromUrl.st
A Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateHttpRepositoryFromUrl.st
A Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCanCreateHttpsRepositoryFromUrl.st
A Monticello-Tests.package/MCRepositoryTest.class/instance/tests/testCannotCreateDictionaryRepositoryFromUrl.st
A Monticello.package/MCFileBasedRepository.class/class/accessing/urlSchemes.st
A Monticello.package/MCFileBasedRepository.class/class/instance creation/basicFromUrl_.st
A Monticello.package/MCRepository.class/class/accessing/urlSchemes.st
A Monticello.package/MCRepository.class/class/instance creation/fromUrl_.st
A Monticello.package/extension/ZnUrl/instance/asFileReferenceWithRelativePath.st
A Monticello.package/extension/ZnUrl/instance/location.st
A MonticelloFileTree-Core.package/MCFileTreeRepository.class/class/accessing/urlSchemes.st
A MonticelloFileTree-Core.package/MCFileTreeRepository.class/class/instance creation/basicFromUrl_.st
A MonticelloRemoteRepositories.package/MCFtpRepository.class/class/accessing/urlSchemes.st
A MonticelloRemoteRepositories.package/MCFtpRepository.class/class/instance creation/basicFromUrl_.st
A MonticelloRemoteRepositories.package/MCHttpRepository.class/class/accessing/urlSchemes.st
A MonticelloRemoteRepositories.package/MCHttpRepository.class/class/instance creation/basicFromUrl_.st
M Reflectivity-Tests.package/ReflectiveMethodTest.class/README.md
M Reflectivity-Tests.package/ReflectiveMethodTest.class/definition.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/running/tearDown.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tagging/tagExec.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tagging/tagExec_.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - after/testAfterArray.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - after/testAfterBlock.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - after/testAfterLiteral.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - after/testAfterLiteralArray.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - after/testAfterMethod.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - after/testAfterSend.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - after/testAfterVariable.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - before/testAfterAssignment.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - before/testBeforeLiteral.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - before/testBeforeLiteralArray.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - before/testBeforeMethod.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - before/testBeforeReturn.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - before/testBeforeSend.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - before/testBeforeSequence.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - before/testBeforeVariable.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - before/testbeforeArray.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - error handling/testSetLinkIncompatibleReification.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - instead/testReplaceAssign.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - instead/testReplaceReturn.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - instead/testReplaceSend.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - instead/testReplaceVariableReadGlobal.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - instead/testReplaceVariableReadIvar.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - instead/testReplaceVariableReadTemp.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - instead/testReplaceVariableWrite.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkConditionReflectiveDisable.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkWithCondition.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkWithConditionInvalidation.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkWithMeta.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testLinkWithMetaDisabled.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testTwoLinks.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testTwoSendLinks.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testUninstallLink.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - links/testUninstallLinkAndRun.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyArguments.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyArguments2.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyGlobalName.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyGlobalValue.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyGlobalVariable.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyIvarName.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyIvarValue.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyIvarVariable.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyMethodArgs.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyMethodReceiver.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyMethodSelector.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyMethodThisContext.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyName.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyNewValue.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyNewValueAssignment.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyNode.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyObject.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyReturnValue.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifySendAll.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifySendReceiver.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifySendSelector.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifySendThisContext.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - reifications/testReifyTempValue.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - symbolic/testConditionArgument.st
R Reflectivity-Tests.package/ReflectiveMethodTest.class/instance/tests - symbolic/testSymbolicMetaObject.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/README.md
A Reflectivity-Tests.package/ReflectivityControlTest.class/definition.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/running/tearDown.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tagging/tagExec.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tagging/tagExec_.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterArray.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterAssignment.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterBlock.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterLiteral.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterLiteralArray.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterMethod.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterSend.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - after/testAfterVariable.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeAssignment.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeLiteral.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeLiteralArray.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeMethod.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeReturn.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeSend.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeSequence.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testBeforeVariable.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - before/testbeforeArray.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - instead/testReplaceAssign.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - instead/testReplaceReturn.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - instead/testReplaceSend.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - instead/testReplaceVariableReadGlobal.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - instead/testReplaceVariableReadIvar.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - instead/testReplaceVariableReadTemp.st
A Reflectivity-Tests.package/ReflectivityControlTest.class/instance/tests - instead/testReplaceVariableWrite.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/README.md
A Reflectivity-Tests.package/ReflectivityLinkTest.class/definition.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/running/tearDown.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tagging/tagExec.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tagging/tagExec_.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - condition/testLinkWithCondition.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - condition/testLinkWithConditionInvalidation.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - error handling/testSetLinkIncompatibleReification.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - metalevel/testLinkWithMeta.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - metalevel/testLinkWithMetaDisabled.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - reflective disable/testLinkConditionReflectiveDisable.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - reflective disable/testTwoLinks.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - reflective disable/testTwoSendLinks.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - reflective disable/testUninstallLink.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - reflective disable/testUninstallLinkAndRun.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - symbolic/testConditionArgument.st
A Reflectivity-Tests.package/ReflectivityLinkTest.class/instance/tests - symbolic/testSymbolicMetaObject.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/README.md
A Reflectivity-Tests.package/ReflectivityReificationTest.class/definition.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/running/tearDown.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tagging/tagExec.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tagging/tagExec_.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - allnodes/testReifyNode.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - allnodes/testReifyObject.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - assignment/testReifyNewValueAssignment.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - method/testReifyMethodArgs.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - method/testReifyMethodReceiver.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - method/testReifyMethodSelector.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - method/testReifyMethodThisContext.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - return/testReifyReturnValue.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - sends/testReifySendAll.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - sends/testReifySendArguments.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - sends/testReifySendArguments2.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - sends/testReifySendReceiver.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - sends/testReifySendSelector.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - sends/testReifySendThisContext.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyGlobalName.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyGlobalValue.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyGlobalVariable.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyIvarName.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyIvarValue.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyIvarVariable.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyTempName.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyTempNewValue.st
A Reflectivity-Tests.package/ReflectivityReificationTest.class/instance/tests - variables/testReifyTempValue.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50160.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50161.st
R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50160.st
A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50161.st
M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
Log Message:
-----------
50161
15925 Reflectivity: test refactoring
https://pharo.fogbugz.com/f/cases/15925
15910 Add a factory method fromUrl on MCRepository
https://pharo.fogbugz.com/f/cases/15910
http://files.pharo.org/image/50/50161.zip
July 8, 2015
Ecore Importer
by Brice GOVIN
Hi everybody,
does anyone know if there is an Ecore importer in Pharo? The idea is to import an ecore file (so an XMI) and to create Pharo classes in a given package directly.
At least, there could be an Ecore importer that create immediately a MooseModel ?
Regards,
--------------
Brice Govin
PhD student in RMoD research team at INRIA Lille
Software Engineer at THALES AIR SYSTEMS Rungis
ENSTA-Bretagne ENSI2014
64 chemin des boeufs 91220 PALAISEAU
July 8, 2015
Re: [Pharo-dev] merging in a filetree repository
by Thierry Goubier
2015-07-08 15:31 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>:
> > Then this means the make in GitFileTree-MergeDriver hasn't worked. When
> you did the make, what was the output?
>
> It is:
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> ~/Dropbox/Workspace/GitFileTree-MergeDriver> make
> mkdir pharo
> cd pharo; wget -O- get.pharo.org/30+vm | bash
> --2015-07-08 14:20:12-- http://get.pharo.org/30+vm
> Resolving get.pharo.org... 128.93.162.72
> Connecting to get.pharo.org|128.93.162.72|:80... connected.
> HTTP request sent, awaiting response... 200 OK
> Length: 2901 (2.8K) [text/html]
> Saving to: 'STDOUT'
>
> - 100%[=====================>] 2.83K --.-KB/s in 0s
>
> 2015-07-08 14:20:12 (146 MB/s) - written to stdout [2901/2901]
>
> Downloading the latest 30 Image:
> http://files.pharo.org/get-files/30/pharo.zip
> Pharo.image
> Downloading the latest pharoVM:
> http://files.pharo.org/get-files/30/pharo-mac-stable.zip
> pharo-vm/Pharo.app/Contents/MacOS/Pharo
> Downloading PharoV30.sources:
> http://files.pharo.org/get-files/30/sources.zip
> Creating starter scripts pharo and pharo-ui
> pharo/pharo pharo/Pharo.image --no-default-preferences eval --save Gofer
> new url: \'http://smalltalkhub.com/mc/ThierryGoubier/Alt30/main/\'\;
> package: \'GitFileTree-MergeDriver\'\; load
> a GoferLoad
> git config --global merge.mcVersion.driver "`pwd`/merge --version %O %A %B"
> git config --global merge.mcMethodProperties.name "GitFileTree
> MergeDriver for Monticello"
> git config --global merge.mcMethodProperties.driver "`pwd`/merge
> --methodProperties %O %A %B"
> git config --global merge.mcProperties.name "GitFileTree MergeDriver for
> Monticello"
> git config --global merge.mcProperties.driver "`pwd`/merge --properties %O
> %A %B"
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
And after that, what is your
git config --get merge.mcVersion.driver ?
> Please help :-)
>
I'm on it :)
Thierry
>
> Alexandre
July 8, 2015
Re: [Pharo-dev] merging in a filetree repository
by Thierry Goubier
2015-07-08 15:25 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>:
>
> On 08 Jul 2015, at 15:19, Thierry Goubier <thierry.goubier(a)gmail.com>
> wrote:
>
>
>
> 2015-07-08 15:11 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>:
>
>> > Our âcodingâ atoms are methods, not classes. Having method per file we
>> can trace the history of changes with method detail, not class.
>>
>> That I understand.
>>
>> > Now⦠you are complaining in the wrong problem.
>>
>> Well⦠Having one file per method seems to be very problematic after all.
>>
>
> It's not ;)
>
>
>>
>> > FileTree meta information (who causes your merge problems) is needed
>> *just* to keep monticello compatibility.
>> > Thatâs what is plain wrong and should be at least optional :)
>> >
>> > I would happily integrate a âPlainFileTreeâ protocol (without
>> monticello information) as an option, if someone provides such extension.
>> > Crap, I could make it myself if I have the time!⦠maybe next insomnia
>> night :P
>>
>> We can work on this next week. I am fed up to hear âwhy you guys are not
>> using github?"
>>
>
> It's extremely easy to do.
>
> Most of the code is ready for it.
>
> But since there is no real push to get Pharo under git for now, I've left
> it as it is. In part because some are using FileTree directly and they need
> that compatibility level.
>
>
> youâre wrong :)
> I feel the pain each time I need to provide a âwe are not ready yetâ.
>
You are not ready yet. I am long past the ready point ...
So I'm letting you wait for libcgit integration and the perfect time to be
ready.
>
> As I said⦠real reason we are not ready is because we are still trying to
> mix to words, in ways no one actually needs.
>
> So please⦠push!
>
I do :) Pushing for OSProcess corrections is that; GitFileTree as it is a
satisfactory solution for the time being.
>
> Esteban
>
> ps: and btw⦠there is no reason why we cannot keep âmc-file-treeâ along
> with a âplain-file-treeâ both alive. As I said⦠I just can image very few
> cases when we *actually* need that compatibility.
>
Yes, but, since all the issues have been resolved (merge and all), I don't
see the value ;)
The barriers are in the Pharo team choices at the moment.
Thierry
July 8, 2015
Re: [Pharo-dev] merging in a filetree repository
by Thierry Goubier
2015-07-08 15:24 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>:
> Thierry,
>
> >> $ git config --get merge.mcVersion.driver
> >
> > ~/HackathonSattose2015> git config --get merge.mcVersion.driver
> > pathToGitFileTree-MergeDriver/merge --version %O %A %B
>
> Any idea how I can merge then?
> Is this value what you expected?
>
No.
If you have your path for the merge command (something like
/User/Alexandre/GitFileTree-MergeDriver/merge ), then it should be:
~/HackathonSattose2015> git config --get merge.mcVersion.driver
/User/Alexandre/GitFileTree-MergeDriver/merge --version %O %A %B
To correct it, what you can do by hand is:
git config --global merge.mcVersion.driver
"/User/Alexandre/GitFileTree-MergeDriver/merge --version %O %A %B"
git config --global merge.mcMethodProperties.driver
"/User/Alexandre/GitFileTree-MergeDriver/merge --methodProperties %O %A %B"
git config --global merge.mcProperties.driver
"/User/Alexandre/GitFileTree-MergeDriver/merge --properties %O %A %B"
Don't forget to update the path !
Thierry
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
July 8, 2015
Re: [Pharo-dev] merging in a filetree repository
by Alexandre Bergel
> Then this means the make in GitFileTree-MergeDriver hasn't worked. When you did the make, what was the output?
It is:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
~/Dropbox/Workspace/GitFileTree-MergeDriver> make
mkdir pharo
cd pharo; wget -O- get.pharo.org/30+vm | bash
--2015-07-08 14:20:12-- http://get.pharo.org/30+vm
Resolving get.pharo.org... 128.93.162.72
Connecting to get.pharo.org|128.93.162.72|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2901 (2.8K) [text/html]
Saving to: 'STDOUT'
- 100%[=====================>] 2.83K --.-KB/s in 0s
2015-07-08 14:20:12 (146 MB/s) - written to stdout [2901/2901]
Downloading the latest 30 Image:
http://files.pharo.org/get-files/30/pharo.zip
Pharo.image
Downloading the latest pharoVM:
http://files.pharo.org/get-files/30/pharo-mac-stable.zip
pharo-vm/Pharo.app/Contents/MacOS/Pharo
Downloading PharoV30.sources:
http://files.pharo.org/get-files/30/sources.zip
Creating starter scripts pharo and pharo-ui
pharo/pharo pharo/Pharo.image --no-default-preferences eval --save Gofer new url: \'http://smalltalkhub.com/mc/ThierryGoubier/Alt30/main/\'\; package: \'GitFileTree-MergeDriver\'\; load
a GoferLoad
git config --global merge.mcVersion.driver "`pwd`/merge --version %O %A %B"
git config --global merge.mcMethodProperties.name "GitFileTree MergeDriver for Monticello"
git config --global merge.mcMethodProperties.driver "`pwd`/merge --methodProperties %O %A %B"
git config --global merge.mcProperties.name "GitFileTree MergeDriver for Monticello"
git config --global merge.mcProperties.driver "`pwd`/merge --properties %O %A %B"
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Please help :-)
Alexandre
>
> Okay, but we all agree this is very far from an ideal solution right?
>
> No, I disagree.
>
> I have been using it in production for the past 4 years, under conditions and constraints that Smalltalkhub and mcz can't handle (and never will).
>
>
> Also, if I understand correctly, at each new repository I need to create a file .gitattributes :
>
> *.package/monticello.meta/version merge=mcVersion
> *.package/*.class/methodProperties.json merge=mcMethodProperties
> *.package/*.class/properties.json merge=mcProperties
> *.package/*.extension/methodProperties.json merge=mcMethodProperties
> *.package/*.extension/properties.json merge=mcProperties
>
> Yes, only once.
>
> As you will setup also a .gitignore.
>
> You'll notice that some of the github hosted Pharo repositories already have that file set.
>
> Regards,
>
> Thierry
>
>
> Alexandre
>
>
> >
> >
> > > On Jul 8, 2015, at 2:21 PM, Otto Behrens <otto(a)finworks.biz> wrote:
> > >
> > > We have a .gitignore file that contains:
> > > version
> > > methodProperties.json
> > >
> > > So, we don't bother.
> > >
> > > The side effects of this are:
> > > Without methodProperties.json, you have the default author and
> > > meaningless timestamp.
> > > Without the version file, loading does not work properly. So we have a
> > > script that generates version files for each package before we load
> > > into the image. At first, this script counted versions for the package
> > > and got all the info from the git repository. But this was too
> > > expensive (because the file system became slow when traversing the git
> > > repo to find the meta data). So now, we just generate a version file
> > > with a fixed author, date & time now and a UUID & version number
> > > derived from the SHA1 of the .package directory.
> > >
> > > We get all the meta-information directly from the git repo, using git
> > > tools. This can be better with GitFileTree.
> > >
> > > So we really just use basics of Monticello & Metacello and do the rest
> > > externally from the image. We need to explore the available tools
> > > more.
> > >
> > > On Wed, Jul 8, 2015 at 12:18 PM, Alexandre Bergel
> > > <alexandre.bergel(a)me.com> wrote:
> > >> Hi!
> > >>
> > >> Do I still need to press the merge button in Monticello when I am working on a filtree git repository?
> > >> I understand that no since the merging has to be done by Git, and not by monticello.
> > >>
> > >> I tried to not do the merge in monticello, but I get some conflicts when doing the git merge. For example:
> > >>
> > >> CONFLICT (content): Merge conflict in Hackathon.package/monticello.meta/version
> > >> CONFLICT (content): Merge conflict in Hackathon.package/HProject.class/methodProperties.json
> > >> CONFLICT (content): Merge conflict in Hackathon.package/HClass.class/methodProperties.json
> > >>
> > >> Why do we need this methodProperties.json and version files? Shouldnât git handle this?
> > >>
> > >> How should I merge these files? Any experience?
> > >>
> > >> Cheers,
> > >> Alexandre
> > >>
> > >> --
> > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > >> Alexandre Bergel http://www.bergel.eu
> > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> > >>
> > >>
> > >>
> > >>
> > >
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> >
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
July 8, 2015
Re: [Pharo-dev] merging in a filetree repository
by Thierry Goubier
2015-07-08 15:15 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>:
> > Looks like a problem when installing the merge driver.
> >
> > pathToGitFileTree-MergeDriver shoudl not appear like that, so it seems
> the make used to install wasn't successful. Can you show the result of
> >
> > $ git config --get merge.mcVersion.driver
>
> ~/HackathonSattose2015> git config --get merge.mcVersion.driver
> pathToGitFileTree-MergeDriver/merge --version %O %A %B
>
>
Then this means the make in GitFileTree-MergeDriver hasn't worked. When you
did the make, what was the output?
> > Why do we need file tree? The simple fileout is not enough? Most of
> languages have one file per class. I do not see why we need to be different
> on that. Or maybe there is something obvious I am missingâ¦.
> >
> > FileTree is a standardised format, cross-smalltalk compatible, browsable
> on github, with a nice set of tests to make sure it keeps working across
> many revisions of Squeak, Gemstone and Pharo.
>
> Okay, but we all agree this is very far from an ideal solution right?
>
No, I disagree.
I have been using it in production for the past 4 years, under conditions
and constraints that Smalltalkhub and mcz can't handle (and never will).
>
> Also, if I understand correctly, at each new repository I need to create a
> file .gitattributes :
>
> *.package/monticello.meta/version merge=mcVersion
> *.package/*.class/methodProperties.json merge=mcMethodProperties
> *.package/*.class/properties.json merge=mcProperties
> *.package/*.extension/methodProperties.json merge=mcMethodProperties
> *.package/*.extension/properties.json merge=mcProperties
>
Yes, only once.
As you will setup also a .gitignore.
You'll notice that some of the github hosted Pharo repositories already
have that file set.
Regards,
Thierry
> Alexandre
>
>
> >
> >
> > > On Jul 8, 2015, at 2:21 PM, Otto Behrens <otto(a)finworks.biz> wrote:
> > >
> > > We have a .gitignore file that contains:
> > > version
> > > methodProperties.json
> > >
> > > So, we don't bother.
> > >
> > > The side effects of this are:
> > > Without methodProperties.json, you have the default author and
> > > meaningless timestamp.
> > > Without the version file, loading does not work properly. So we have a
> > > script that generates version files for each package before we load
> > > into the image. At first, this script counted versions for the package
> > > and got all the info from the git repository. But this was too
> > > expensive (because the file system became slow when traversing the git
> > > repo to find the meta data). So now, we just generate a version file
> > > with a fixed author, date & time now and a UUID & version number
> > > derived from the SHA1 of the .package directory.
> > >
> > > We get all the meta-information directly from the git repo, using git
> > > tools. This can be better with GitFileTree.
> > >
> > > So we really just use basics of Monticello & Metacello and do the rest
> > > externally from the image. We need to explore the available tools
> > > more.
> > >
> > > On Wed, Jul 8, 2015 at 12:18 PM, Alexandre Bergel
> > > <alexandre.bergel(a)me.com> wrote:
> > >> Hi!
> > >>
> > >> Do I still need to press the merge button in Monticello when I am
> working on a filtree git repository?
> > >> I understand that no since the merging has to be done by Git, and not
> by monticello.
> > >>
> > >> I tried to not do the merge in monticello, but I get some conflicts
> when doing the git merge. For example:
> > >>
> > >> CONFLICT (content): Merge conflict in
> Hackathon.package/monticello.meta/version
> > >> CONFLICT (content): Merge conflict in
> Hackathon.package/HProject.class/methodProperties.json
> > >> CONFLICT (content): Merge conflict in
> Hackathon.package/HClass.class/methodProperties.json
> > >>
> > >> Why do we need this methodProperties.json and version files?
> Shouldnât git handle this?
> > >>
> > >> How should I merge these files? Any experience?
> > >>
> > >> Cheers,
> > >> Alexandre
> > >>
> > >> --
> > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > >> Alexandre Bergel http://www.bergel.eu
> > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> > >>
> > >>
> > >>
> > >>
> > >
> >
> > --
> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> > Alexandre Bergel http://www.bergel.eu
> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> >
> >
> >
> >
> >
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
July 8, 2015