Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- 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
June 2016
- 812 messages
[pharo-project/pharo-core]
by GitHub
Branch: refs/tags/60071
Home: https://github.com/pharo-project/pharo-core
June 8, 2016
[pharo-project/pharo-core] 11de06: 60071
by GitHub
Branch: refs/heads/6.0
Home: https://github.com/pharo-project/pharo-core
Commit: 11de06e4f8e1c4531220b256565e19993f106c68
https://github.com/pharo-project/pharo-core/commit/11de06e4f8e1c4531220b256…
Author: Jenkins Build Server <board(a)pharo-project.org>
Date: 2016-06-08 (Wed, 08 Jun 2016)
Changed paths:
M NautilusRefactoring.package/extension/TClassDescription/instance/sourceCodeRefactoring_.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60070.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60071.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60070.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60071.st
M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
Log Message:
-----------
60071
18440 ConfgurationOfGTDebugger needs update
https://pharo.fogbugz.com/f/cases/18440
18355 Change refactoring label from Rename temporary to Rename temporary/parameter
https://pharo.fogbugz.com/f/cases/18355
http://files.pharo.org/image/60/60071.zip
June 8, 2016
Re: [Pharo-dev] IMPORTANT: Proposal to create a github team for Voyage and MongoTalk
by Yanni Chiu
On Wed, Jun 8, 2016 at 5:54 AM, Esteban Lorenzano <estebanlm(a)gmail.com>
wrote:
>
> So, we wanted to create âPharoNoSQL" team, and move all thereâ¦
>
> Opinions?
Excellent idea, for all the reasons you pointed out. Having Voyage/GemStone
is a great idea too.
--
Yanni
June 8, 2016
Re: [Pharo-dev] endless loop again
by David T. Lewis
On Wed, Jun 08, 2016 at 11:11:13AM +0200, Sven Van Caekenberghe wrote:
>
> > On 08 Jun 2016, at 10:40, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote:
> >
> >
> >> On 04 Jun 2016, at 9:13 , stepharo <stepharo(a)free.fr> wrote:
> >>
> >>
> >>
> >> Le 3/6/16 ?? 19:16, Esteban A. Maringolo a ??crit :
> >>> Regarding the first part of your email, about UI lockups, it is almost
> >>> unavoidable, because in Pharo almost everything happens in the main
> >>> thread, as you pointed out.
> >> Yes. This is all my point.
> >
> > IMHO, all Pharo beginner tutorials should start by showing off Cmd - dot (or Alt - dot, on Win / Linux).
> >
> > Not just because it's cool, but because it's necessary :)
> >
> > Cheers,
> > Henry
>
> Very true.
>
> Yet, and I have already mentioned this years ago, it is technically totally possible to properly detect massive stack growth, before things get out of control. Sadly, VM people think this is not needed (or too costly).
>
Hi Sven,
I think that I remember this topic being discussed from time to time, but
I cannot recall specifics. Do you have a pointer to any discussions on the
mailing lists? I'm sure that there would be interest in doing this if it
can be done in an efficent manner.
Thanks,
Dave
> Consider the following in Common Lisp (LispWorks):
>
> CL-USER 1 > (defun fac (n) (if (< n 2) 1 (* n (fac (1- n)))))
> FAC
>
> CL-USER 2 > (fac 5)
> 120
>
> CL-USER 3 > (fac 100)
> 93326215443944152681699238856266700490715968264381621468592963895217599993229915608941463976156518286253697920827223758251185210916864000000000000000000000000
>
> CL-USER 4 > (fac 400)
>
> Stack overflow (stack size 31744).
> 1 (continue) Extend stack by 50%.
> 2 (abort) Return to level 0.
> 3 Return to top loop level 0.
>
> Type :b for backtrace or :c <option number> to proceed.
> Type :bug-form "<subject>" for a bug report template or :? for other options.
>
> CL-USER 5 : 1 > :c 1
>
> Stack overflow (stack size 48128).
> 1 (continue) Extend stack by 50%.
> 2 (abort) Return to level 0.
> 3 Return to top loop level 0.
>
> Type :b for backtrace or :c <option number> to proceed.
> Type :bug-form "<subject>" for a bug report template or :? for other options.
>
> CL-USER 6 : 1 > :c 1
> 64034522846623895262347970319503005850702583026002959458684445942802397169186831436278478647463264676294350575035856810848298162883517435228961988646802997937341654150838162426461942352307046244325015114448670890662773914918117331955996440709549671345290477020322434911210797593280795101545372667251627877890009349763765710326350331533965349868386831339352024373788157786791506311858702618270169819740062983025308591298346162272304558339520759611505302236086810433297255194852674432232438669948422404232599805551610635942376961399231917134063858996537970147827206606320217379472010321356624613809077942304597360699567595836096158715129913822286578579549361617654480453222007825818400848436415591229454275384803558374518022675900061399560145595206127211192918105032491008000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
>
> CL-USER 7 > (defun infinite () (cons 'a (infinite)))
> INFINIT
>
> CL-USER 8 > (infinite)
>
> Stack overflow (stack size 80896).
> 1 (continue) Extend stack by 50%.
> 2 (abort) Return to level 0.
> 3 Return to top loop level 0.
>
> Type :b for backtrace or :c <option number> to proceed.
> Type :bug-form "<subject>" for a bug report template or :? for other options.
>
> CL-USER 9 : 1 > :a
>
> CL-USER 10 >
>
> Just having an upper limit to the stack catches 99% of infinite loops - that would be nice to have.
>
> This has existed for 10s of years AFAIK.
>
> Sven
>
> PS: Of course, the stack size can be set larger to begin with, if necessary. I believe it is even per execution thread.
>
June 8, 2016
Re: [Pharo-dev] Story of one small fix
by Sean P. DeNigris
Andrei Chis wrote
> Did you edited the configurations and their dependencies by hand? Since
> some time I never update them by hand, only use versioner
[Reminder]: Anyone using Git (like me for all my personal projects) can not
use Versionner because it does not handle Baselines. This will become more
and more of a problem.
-----
Cheers,
Sean
--
View this message in context: http://forum.world.st/Story-of-one-small-fix-tp4899815p4899885.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
June 8, 2016
Re: [Pharo-dev] Importing a GNU Smalltalk project into Pharo
by Dimitris Chloupis
I dont see many people who use a smalltalk that is not a smalltalk , the
same way a human is not an arm, wanting to come to pharo and locked in an
IDE and Enviroment. But then there are a tiny amount of them out there
anyway, judging from their mailing list that is barely alive.
Gnu Smalltalk is like keeping the cherry and throwing away the cake. I
think its far more important to attrack the right kind of people who
believe or seek the smalltalk ideal.
On Wed, Jun 8, 2016 at 8:31 AM Max Leske <maxleske(a)gmail.com> wrote:
> Very interesting question, especially since we want people to move to
> Pharo.
>
>
> http://stackoverflow.com/questions/37690985/importing-a-gnu-smalltalk-proje…
>
> Cheers,
> Max
>
June 8, 2016
[pharo-project/pharo-core] 6d8aae: 60070
by GitHub
Branch: refs/heads/6.0
Home: https://github.com/pharo-project/pharo-core
Commit: 6d8aae286bf21bd60393af09739ba3fcb86d80be
https://github.com/pharo-project/pharo-core/commit/6d8aae286bf21bd60393af09…
Author: Jenkins Build Server <board(a)pharo-project.org>
Date: 2016-06-08 (Wed, 08 Jun 2016)
Changed paths:
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/README.md
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/definition.st
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/api projectSpec/baseline_.st
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/data/removedExtendedClassesPerPackage.st
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/pre-post-load-do-its/installPlugin.st
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/pre-post-load-do-its/preLoadDoIt.st
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/pre-post-load-do-its/removeCrapOf_from_.st
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/pre-post-load-do-its/removeRenrakuCrap.st
R BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/pre-post-load-do-its/uninstallObsoletePlugin.st
R BaselineOfRenraku.package/BaselineOfRenraku.class/README.md
R BaselineOfRenraku.package/BaselineOfRenraku.class/definition.st
R BaselineOfRenraku.package/BaselineOfRenraku.class/instance/baseline/baseline_.st
R BaselineOfRenraku.package/BaselineOfRenraku.class/instance/pre-post-load-do-its/resetRuleManager.st
R BaselineOfRenraku.package/BaselineOfRenraku.class/instance/pre-post-load-do-its/unsubscribeReEngine.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/README.md
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/class/catalog/catalogChangeLog.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/class/catalog/catalogContactInfo.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/class/catalog/catalogDescription.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/class/catalog/catalogKeyClassesAndExample.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/class/catalog/catalogKeywords.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/definition.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/development_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/stable_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/pre3%5F1%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F1%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F1%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F1%5F2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F2%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F2%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F2%5F2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F2%5F3_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F2%5F4_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F2%5F5_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F3%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F4%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F4%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F4%5F2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F5%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F5%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F6%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v0%5F6%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F0%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F1%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F1%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F1%5F2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F1%5F3_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F1%5F4_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F2%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F2%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F2%5F2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F3%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F4%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F4%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F4%5F2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F4%5F3_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v1%5F5%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F0%5F0%5Frc1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F0%5F0%5Frc2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F0%5F0%5Frc3_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F0%5F0%5Frc4_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F0%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F0%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F1%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F2%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F2%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F3%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F3%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F3%5F2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F3%5F3_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F3%5F4_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F3%5F5_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F3%5F6_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F4%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F5%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F5%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F5%5F2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F6%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F6%5F1_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F6%5F2_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F6%5F3_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F6%5F4_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F6%5F5_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F6%5F6_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F6%5F7_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v3%5F0%5F0_.st
R ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v3%5F0%5F1_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/README.md
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/definition.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/symbolic versions/development_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/symbolic versions/stable_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/pre0%5F14%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F1%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F10%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F11%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F11%5F1_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F11%5F2_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F11%5F3_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F11%5F4_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F11%5F5_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F11%5F6_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F12%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F12%5F1_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F12%5F2_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F13%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F2%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F2%5F1_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F2%5F2_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F2%5F3_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F2%5F4_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F3%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F3%5F1_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F3%5F2_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F3%5F3_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F3%5F4_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F4%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F4%5F1_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F5%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F6%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F7%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F8%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F8%5F1_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F8%5F2_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F9%5F0_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F9%5F1_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F9%5F2_.st
R ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F9%5F3_.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60069.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60070.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60069.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60070.st
M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
Log Message:
-----------
60070
18442 ConfigurationOfGToolkitCore needs update
https://pharo.fogbugz.com/f/cases/18442
18441 ConfigurationOfGTPlaygroundCore needs update
https://pharo.fogbugz.com/f/cases/18441
18439 Remove QA git leftovers
https://pharo.fogbugz.com/f/cases/18439
http://files.pharo.org/image/60/60070.zip
June 8, 2016
[pharo-project/pharo-core]
by GitHub
Branch: refs/tags/60070
Home: https://github.com/pharo-project/pharo-core
June 8, 2016
Re: [Pharo-dev] Playground and text evaluation printing result default.
by Ben Coman
On Wed, Jun 8, 2016 at 2:01 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
> Hi,
>
>> On Jun 8, 2016, at 2:04 AM, Ben Coman <btc(a)openinworld.com> wrote:
>>
>> On Wed, Jun 8, 2016 at 5:39 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote:
>>> Hi Sven,
>>>
>>> If I understand correctly, Stef talks about the case of building tests in the debugger. There he tries an expression and then wants to capture the result of the expression as an assertion in the code so he wants to paste the result directly. It is a different scenario than the one of capturing results that we store as comments for further reference.
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>>> On Jun 7, 2016, at 4:50 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote:
>>>>
>>>> The #printString of most objects is not valid Pharo syntax, it makes sense to put those into comments, so that the overall syntax of the workspace/playground is maintained and syntax highlighting can operate normally.
>>
>> This might be too much a corner case, but I wonder...
>> If the domain object provided a sufficiently distinguishing
>> printString, then a shortcut that appended the CTRL-P result....
>> printString = 'aDomainObject(''identiferâ')
>
> I cannot quite picture what you mean. Could you elaborate. It sounds intriguing?
Simple example (perhaps poor because its integers) is...
3+4
select it, <ctrl-p> <ctrl-enter>
==>
3 +4 printString = '7'.
more involved... actually nothing like a concrete example to flesh out
ideas. The generated string should include "printString equals:"
rather than "printString =" , or even "equalsPrintString"
Object subclass: #Person
instanceVariableNames: 'name age'
classVariableNames: ''
package: 'AAAAA'
Person>>named: aString age: anInteger
name := aString.
age := anInteger
Person>>printOn: aStream
super printOn: aStream.
aStream
nextPut: $( ;
nextPutAll: name;
nextPut: $).
PersonTest>>setUp
people := {
Person new named: 'John' age: 5).
Person new named: 'Peter' age: 7) }
PersonTest>>testAge
self assert: (people detect: [ :p | p age = 5 ])
<ctrl-p><ctrl-enter> ==> equalsPrintString: 'a Person(John)'.
Maybe using the printString is a bit fragile. If it changes you need
to edit all the tests. Although you could be able to just use
<ctrl-p><ctrl-enter> again and visually check the new and old results.
Maybe some other magic could happen like look up the returned value in
instance variables and insert a code reference
<ctrl-p><ctrl-enter> ==> equals: (People at: 1)
cheers -ben
>
>> to the selected text might provide an interesting workflow for
>> developing tests in the debugger.
>> Maybe it could be CTRL-P + CTRL-T (for test) ?
>
> I proposed Cmd+p Cmd+v (from paste).
>
> Cheers,
> Doru
>
>
>> A video demo of such might provide a good example of programming in an
>> immersive environment. What other environment could do this?
>> cheers -ben
>>
>>
>>
>>
>>
>>>>
>>>> A result printed as a comment is also easy to select (by double-clicking next to the $" on the inside).
>>>>
>>>> All this makes sense for literal programming (assuming that is what you are after).
>>>>
>>>> What is the use case for not doing it like that ? Why do you want the comments gone ?
>>>>
>>>>> On 07 Jun 2016, at 13:03, Ben Coman <btc(a)openinworld.com> wrote:
>>>>>
>>>>> On Tue, Jun 7, 2016 at 2:09 PM, stepharo <stepharo(a)free.fr> wrote:
>>>>>>
>>>>>>
>>>>>> Le 5/6/16 à 23:00, Tudor Girba a écrit :
>>>>>>>
>>>>>>> Hi Stef,
>>>>>>>
>>>>>>> The quotes appear only when you add the result in the playground.
>>>>>>
>>>>>>
>>>>>> No need to explain I'm not idiot and I know it.
>>>>>>>
>>>>>>> The typical use case for this is to keep track of several results.
>>>>>>
>>>>>> No need to explain I'm not idiot and I know it.
>>>>>>>
>>>>>>> In this situation you do not want to modify the code to not affect the
>>>>>>> highlighting and this is why it gets in a comment.
>>>>>>
>>>>>> This is fun because I never ever needed it. But this is probably what
>>>>>> everybody else is doing that since this is the default.
>>>>>> I just write simple code and tests. Indeed I'm not that smart.
>>>>>>
>>>>>> But your tools only embedd your scenario and let the other users forced to
>>>>>> adapt.
>>>>>>
>>>>>> Well you do not want but I do.
>>>>>> I spent my evening removing quotes while writing tests.
>>>>>>
>>>>>> What I hate with the GTTools is that you want to teach me how I should work.
>>>>>> Sorry but good tools do not do that.
>>>>>> Good tools empower the users and not constraint them.
>>>>>>
>>>>>> I work a lot faster when I do not have to remove the wonderful comments or
>>>>>> when I have to copy and paste.
>>>>>> This commenting is breaking the flow of efficient people. May be GT team do
>>>>>> not work write tests in the
>>>>>> debugger but I do most of the time and I'm forced by the environment to
>>>>>> remove quotes all over the places.
>>>>>>>
>>>>>>> If you want to copy the content without quotes, you can do:
>>>>>>> Cmd+p -> popup
>>>>>>> Cmd+c -> selects the current line and copies the text
>>>>>>> Esc
>>>>>>> Cmd+v
>>>>>>
>>>>>> Sorry but I do not want.
>>>>>> I just want to print and modify directly.
>>>>>> 7 keystrokes vs 2
>>>>>>>
>>>>>>> Perhaps we can add another keybinding like Shift+Enter for adding the text
>>>>>>> without quotes.
>>>>>
>>>>> I just had a play with this, and another option might be <ctrl-enter>,
>>>>> since the <ctrl> key is still selection from doing <ctrl-P> so there
>>>>> is not much difference in hand movements between <enter> and
>>>>> <ctrl-enter>
>>>>>
>>>>> cheers -ben
>>>>>
>>>>>>
>>>>>> And why not the inverse.
>>>>>> By default printing is printing and if you want to do something else then
>>>>>> you have a special binding.
>>>>>
>>>>>
>>>>>
>>>>>> Now I'm upset with this general attitude (Oh I will teach how you can be a
>>>>>> nice user) that I will turn them off
>>>>>> or go and hack my own settings. Still I'm amazingly sad about this state of
>>>>>> affair.
>>>>>> All these story about GT is hurting me because of this attitude: we are so
>>>>>> smart and we thought a lot and we will teach you
>>>>>> how you should work... and at the end I the end-user has to adapt.
>>>>>> Look at the Spotter discussions: you looked for the graal and I was just
>>>>>> telling to you that I cannot find
>>>>>> simple information such as class refs!
>>>>>>
>>>>>> So what saddens me the most is that
>>>>>> - you pretend to have end-user trying your tools but I have impression
>>>>>> that they are not real power users
>>>>>> or this is yourself and it means that you are never exposed to other
>>>>>> people.
>>>>>> I can still not use Spotter because the way I put my hand on my
>>>>>> keyboard. So should change
>>>>>> - 1 my hands
>>>>>> - 2 my brain
>>>>>> - 3 my keyboard
>>>>>> - 4 do not use the tools?
>>>>>> - funnily enough if I would not have complain aggressively then it looks
>>>>>> like we would have the same than before.
>>>>>>
>>>>>> Your flow is not mine and I go faster my way but your tools force me to get
>>>>>> slow.
>>>>>> I do not have the time to produce a video but I would even if it would give
>>>>>> a bad press to Pharo.
>>>>>> I will do a presentation in the rmod team. Because people do not watch
>>>>>> themselves why acting.
>>>>>>
>>>>>> Good tools empower the users not constraint them.
>>>>>>
>>>>>> GTTools feel often like an overengineer guitar that would have hampered
>>>>>> Jimmy Hendrix to do crazy solos.
>>>>>>
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Doru
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> On Jun 5, 2016, at 10:20 PM, stepharo <stepharo(a)free.fr> wrote:
>>>>>>>>
>>>>>>>> Hi
>>>>>>>>
>>>>>>>> I would like to know if there is a setting to remove the "" when printing
>>>>>>>> the result of an expression.
>>>>>>>>
>>>>>>>> I know that playground has been thought to help me, but today I watched
>>>>>>>> myself removing the comments
>>>>>>>>
>>>>>>>> code so often that I would like to get a setting because such wrapping of
>>>>>>>> results is really boring for me.
>>>>>>>>
>>>>>>>> I'm spending my time removing them and I start to wonder why they are any
>>>>>>>> useful.
>>>>>>>>
>>>>>>>> I would help me to write fast tests for example in the debugger.
>>>>>>>>
>>>>>>>> Stef
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> --
>>>>>>> www.tudorgirba.com
>>>>>>> www.feenk.com
>>>>>>>
>>>>>>> "What we can governs what we wish."
>>>>
>>>>
>>>
>>> --
>>> www.tudorgirba.com
>>> www.feenk.com
>>>
>>> "It's not what we do that matters most, it's how we do it."
>>>
>>>
>>
>
> --
> www.tudorgirba.com
> www.feenk.com
>
> "If you interrupt the barber while he is cutting your hair,
> you will end up with a messy haircut."
>
>
June 8, 2016
Re: [Pharo-dev] IMPORTANT: Proposal to create a github team for Voyage and MongoTalk
by Sabine Manaa
Hi Esteban,
a few days ago, I started reading about Pharo/Github because I am
interested in administering my code in github, too.
I stopped then, because I loose time, which I can not spend in development
of my application.
I thought, I will do that later - when there will be more automated support
for github within Pharo.
Also, from the beginning of administering my code in github, I have to pay
for it, because my project is not public.
But in the long run, I have to do this and learn it and I am looking
forward to it.
And getting code for mongo from github does not mean, putting my stuff
there immediately, too.
For me it would be the first github learning step.
It would help to have a description, what to do to get the code then from
github instead of sthub, but I am sure you will do that.
I mean not only get code from catalog but also through my
configurationOf....
I would be happy to help if I can.
Regards
Sabine
2016-06-08 11:54 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>:
> Hi,
>
> (this mail is intended to Voyage/MongoTalk users and collaborators)
>
> Iâm spending a couple of days in Cologne, at 2Denker offices and I was
> talking Norbert about organisation of Voyage and the NoSQL drivers⦠As a
> conclusion, we want to propose to move the Voyage and MongoTalk development
> to github, into a common team where other NoSQL drivers can eventually
> arrive (Voyage will incorporate other backends that might well be there).
>
> One reason from this is that I do not consider appropriate to keep Voyage
> into my repository, because is more a community project than a personal
> one. I want others to be able to participate more and I think this is the
> right step (also Dale is porting it to Gemstone soâ¦)
>
> Using github we can benefit of their tools to improve our process (issue
> tracker, travis and appveyor, etc.) and we will improve project visibility.
>
> So, we wanted to create âPharoNoSQL" team, and move all there⦠then we
> will close sthub projects to avoid confusion and we will handle
> configurations and baselines same way as Yuriy does with QualityAssistance
> (so it will be available through catalog as always).
>
> Opinions?
>
> Esteban
June 8, 2016