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

Re: [Pharo-dev] Where to start contributing

by Sergio Fedi

@Cyril I tried to do what you suggested, but the amount of cases to resolve is huge, I'm quite lost on where to begin, and most of them I don't understand how to solve them @Ben How do I do that reviewing you suggest? Which ones do you suggest I should begin reviewing? â If anyone else have more comments or suggestions on where and how I can contribute, please chime in.

May 4, 2015

Re: [Pharo-dev] Beyond resolving a case

by Cyril Ferlicot

Hi, for those kind of things you can start discussions on the mailing list and if the others find it good you can open new entry on fogbugz. If you plan to do it you can assign it to you, if you don't have the time you can assign it to "everyone". On 4 May 2015 at 02:23, Sergio Fedi <sergio.fedi(a)gmail.com> wrote: > How do we state and/or document that further work is needed after a Case? > > For example, some things I had in mind after finishing this case: > > While adding the About comment for the Versionner tool I've found that the > About should be modeled (at least to encapsulate the about text and the > about window title, but maybe also for other information such as the purpose > of the tool, the author, external link, further reading, etc). > > Should we generate a test for this About behaviour ? > > Should we move the About functionality up in the hierarchy and integrate it > more with the classes used to make Tools? > > I added a method that answers the tool name (as opposed to the tool class > name, usually used in the About title) > and I found out there was another implementor on another Tool, but which I > didn't understand the relationship with the Versionner. > Is there something that could be done? Maybe make an abstract method? > > Is there a place where to put all these comments and > questions/comments/ramblings? > If there is, where? -- Cheers Cyril Ferlicot

May 4, 2015

Beyond resolving a case

by Sergio Fedi

How do we state and/or document that further work is needed after a Case? For example, some things I had in mind after finishing this case: *While adding the About comment for the Versionner tool I've found that the About should be modeled (at least to encapsulate the about text and the about window title, but maybe also for other information such as the purpose of the tool, the author, external link, further reading, etc).* *Should we generate a test for this About behaviour ?* *Should we move the About functionality up in the hierarchy and integrate it more with the classes used to make Tools?* *I added a method that answers the tool name (as opposed to the tool class name, usually used in the About title)* *and I found out there was another implementor on another Tool, but which I didn't understand the relationship with the Versionner.* *Is there something that could be done? Maybe make an abstract method?* *Is there a place where to put all these comments and questions/comments/ramblings?* *If there is, where?*

May 4, 2015

Re: [Pharo-dev] Improving the About Text of Versionner

by Sergio Fedi

Ok, I added the case, submited the Slice and Resolved the case. https://pharo.fogbugz.com/f/cases/15480/Improving-the-About-information-of-… The final text is this: *Versionner is tool for creating configurations.* *A Configuration determines the dependencies between packages. More precisely, the dependency between a version of a package and a particular version of a required package.* *This tool is a GUI for Metacello that allows you to use a nice (but limited) tool instead of writing configurations by hand.* *Metacello is a package management system that declares dependencies between those packages in configuration classes.* *Monticello is our SCM system that groups code into packages.* *For a tutorial video on how to use Versionner:* * https://youtu.be/cFRJDuWL-Q0 <https://youtu.be/cFRJDuWL-Q0>* I hope I didn't make any mistakes. Cheers.

May 4, 2015

Re: [Pharo-dev] Improving the About Text of Versionner

by Sergio Fedi

May 4, 2015

Re: [Pharo-dev] build pharo vm on windows (old mingw package)

by phil＠highoctane.be

[image: Inline image 1] Pharo.exe - 5 363 606 bytes Phil On Sun, May 3, 2015 at 1:17 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-05-01 23:05 GMT+02:00 phil(a)highoctane.be <phil(a)highoctane.be>: > >> Did you tried this ? >> >> https://github.com/pharo-project/pharo-vm/blob/master/README-Win32.md >> >> (I wrote that thing a while ago). >> >> >> http://sourceforge.net/projects/mingw/files/Automated%20MinGW%20Installer/m… >> was where I got the env from. >> >> I've got a PharoVM built with gcc 4.8.1 >> > > Can you check that this vm does not depend on the mingw runtime. > (I managed to create a vm that opens, but if I start this without the > mingw installation directory in my path, > I get the following error: > libgcc_s_dw2-1.dll is missing ) > > The vm from the build server works even without a local mingw installation. > > >> >> Uploading the thing in dropbox. >> >> Will send a link when done. >> >> Phil >> >> >> On Fri, May 1, 2015 at 9:04 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: >> >>> >>> >>> 2015-04-30 11:33 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> arenât you able to install an older version of gcc in your newer >>>> version of mingw? >>>> >>> >>> hm, downgrading the compiler was suprisingly easy. But I have still the >>> same error. >>> This is the gcc version information: >>> >>> Using built-in specs. >>> COLLECT_GCC=c:\MinGW\bin\gcc.exe >>> >>> COLLECT_LTO_WRAPPER=c:/mingw/bin/../libexec/gcc/mingw32/4.6.2/lto-wrapper.exe >>> Target: mingw32 >>> Configured with: ../gcc-4.6.2/configure >>> --enable-languages=c,c++,ada,fortran,objc,obj-c++ --disable-sjlj-exceptions >>> --with-dwarf2 --enable-shared --enable-libgomp --disable-win32-registry >>> --enable-libstdcxx-debug --enable-version-specific-runtime-libs >>> --build=mingw32 --prefix=/mingw >>> Thread model: win32 >>> gcc version 4.6.2 (GCC) >>> >>> >>> Anyone knows what could be the problem ? Stacktrace from the crash, this >>> happens >>> directly after the start: >>> >>> #0 0x772359dd in ntdll!RtlpNtMakeTemporaryKey () >>> from C:\Windows\system32\ntdll.dll >>> #1 0x77201d8f in ntdll!EtwSetMark () from C:\Windows\system32\ntdll.dll >>> #2 0x77236a37 in ntdll!RtlpNtMakeTemporaryKey () >>> from C:\Windows\system32\ntdll.dll >>> #3 0x771fa3ef in ntdll!EtwSetMark () from C:\Windows\system32\ntdll.dll >>> #4 0x771c6766 in wcsnicmp () from C:\Windows\system32\ntdll.dll >>> #5 0x76cdc484 in KERNEL32!HeapFree () from >>> C:\Windows\system32\kernel32.dll >>> #6 0x6c24c4d7 in free () from C:\Windows\system32\crtdll.dll >>> #7 0x00850000 in ?? () >>> #8 0x00542065 in glob_match () >>> #9 0x00542604 in __mingw_glob () >>> #10 0x00540f17 in _setargv () >>> #11 0x004011ca in __mingw_CRTStartup () >>> #12 0x004012d5 in WinMainCRTStartup () >>> >>> >>> >>> >>> >>> nicolai >>> >>> >>> >>> >>>> I do not have time right now to update the build into a new compiler, >>>> sorry (also, that is not always trivial/desired, he) >>>> >>>> Esteban >>>> >>>> > On 30 Apr 2015, at 08:38, Nicolai Hess <nicolaihess(a)web.de> wrote: >>>> > >>>> > I managed to trash my mingw build environment >>>> > -> uninstalled /removed mingw/mingsys >>>> > -> reinstall from current mingw-installer >>>> > -> bad idea >>>> > >>>> > I can build a pharo windows vm but it immediately crashes on startup. >>>> I suspect >>>> > some changes between gcc 4.6 (old environment) gcc 4.8 (new >>>> environment). >>>> > (I think there are some changes related to file globbing (I managed >>>> to get >>>> > the vm somehow working to not crash on startup but on shutdown >>>> instead - with >>>> > _CRT_glob = 0. And gcc-4.8 uses dfferent (dwarf vs. sjlj ) exception >>>> handling, don't know if this is >>>> > related). >>>> > >>>> > I tried to find a ming-installer for the old version but could not >>>> find anything and >>>> > I tried to manually setup a ming installation from the old packages >>>> (dozen of packages >>>> > for mingw / core-utils / bintutils /msys from different places (no >>>> fun)). >>>> > >>>> > 1) did anyone get a windows vm from mingws current version (with gcc >>>> 4.8) working? >>>> > >>>> > 2) can someone package/zip and upload an old mingw installation >>>> (maybe that one that >>>> > is used on the build server? >>>> > >>>> > >>>> > regards >>>> > nicolai >>>> >>>> >>> >> >

May 3, 2015

Re: [Pharo-dev] TxText: More Cleaning and Questions

by Sean P. DeNigris

Sean P. DeNigris wrote > a bit of cleaning... > Issue 15475: TxText Cleanup for Pharo 5.0 #2 Finally passed validation! Okay to include? ----- Cheers, Sean -- View this message in context: http://forum.world.st/TxText-More-Cleaning-and-Questions-tp4823894p4824054.… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 3, 2015

Re: [Pharo-dev] New Versionner Tool and Authentication

by Sean P. DeNigris

EstebanLM wrote > Iâm sorry for the mess. Don't be! This is a great feature. I'm happy to test it :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/New-Versionner-Tool-and-Authentication-tp4824032p4824… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 3, 2015

Re: [Pharo-dev] could the log message be placed on top of the files in the commit?

by Nicolas Cellier

2015-05-03 18:54 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > do you guys know that if you press in the link provided, for example: > > > https://github.com/pharo-project/pharo-core/commit/cf09b156e5bc943d6b99a340… > > you will have all the diffs well organised and for free? > > Esteban > > ps: in fact, if possible, I wouldnât publish even the list of files > changedâ¦ just the commit message and the link > > Yes, message and link would be just enough. And while asking, maybe more atomic commits (single issue at a time). > On 03 May 2015, at 18:23, stepharo <stepharo(a)free.fr> wrote: > > > Code diffs would be more valuable, but adopting the tools of file lovers > must come with a cost ;) > > > Yes I would love that too. > I just want to compile a list of changes automatically. > May I can do in the scriptLoader instead of reparsing git. > > >

May 3, 2015

Re: [Pharo-dev] New Versionner Tool and Authentication

by Esteban Lorenzano

yesâ¦ is a bug who should be fixed if you install bleedingEdgeâ¦ Iâm sorry for the mess. Esteban > On 03 May 2015, at 19:29, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > It seems maybe the "commit Xyz patch" tool is creating new instances of > repositories instead of using the existing ones? Even though I am logged > into sthub/Pharo/TxText, when I try to commit a config and new package > versions for packages, dialogs pop up to enter my username and password, and > even if I fill them out the credentials don't seem to be accepted. After > cancelling, I can copy them over from my cache in the MC browser, so I'm > definitely logged in. Any ideas? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/New-Versionner-Tool-and-Authentication-tp4824032.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

May 3, 2015