July 2017 - Pharo-dev - lists.pharo.org

Improving formatting [was: Big claps for Epicea (small request!)]
by Eliot Miranda July 27, 2017

July 27, 2017

On Wed, Jul 19, 2017 at 2:16 PM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > format before diff is in the top 5 of my most hated default. > As an author, I try to write short methods and adhere to a standard format > (Kent Beck like). > > But I want the freedom to use derogation when the format helps > comprehension. > If I did the effort of using a special formatting, the last thing that I > want is a "smart" tool that undo my work. > The best time to format code is when we accept it, and only if there is a > quick way to undo/bypass if we don't like it. > > The formatter is dumb. > Let's illustrate it with literals among other things. > > I might want to write 16rBADA55, but I'm sure i never want to read > 12245589, it makes no sense ;) > (hey, this is a real example you can find in VMMaker sources, not just the > production of my ill brain). > I'd love to see literal nodes in the compilers be intelligent enough to know what base a literal number was in. It might be as simple as maintaining the literal characters that make up a token and printing using those, perhaps only if the token is a member of a particular set of classes. And remember this applies to numeric literals in Array and ByteArray literals too. > And if I make an effort to format a character encoding table on several > lines to have it readable > #( > line1 > line2 > ... > lineN ). > I'm pretty sure I never want to diff a single line with about 1024 > columns... > Th above approach might also handle this case well, although I wonder about comments. > > So please make this an option (with a default to false)! > > 2017-07-19 22:27 GMT+02:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> Hi Martin, >> >> Thank you VERY MUCH for Epicea. I just had a crash and it was way more >> comfortable to recover changes. >> >> One small request would be to allow "Pretty Print" in the diff to the >> changes to be applied. Many times I changed formatting etc so for when >> viewing changes, viewing with same formatting helps me to see the actual >> changes and not formatting changes. >> >> Thanks! >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- _,,,^..^,,,_ best, Eliot

5 4

GTInspector and sorting in dictionaries
by Holger Freyther July 27, 2017

July 27, 2017

Hey, I have a simple dictionary with class as the key and a number as value. In the inspector I try to sort it by the value. But it is doing an alphabetical sort and not numerical? I can change Dictionary>>#gtInspectorItemsIn: to pass a sortedBy: block when adding the value column but is "<" a general usable protocol? How would one specialize the sort depending on the data in the dictionary? Any ideas how to get numbers sorted intuitively without adding too much magic (trying to convert the string representation back to a number, custom GTTablePresentation, using "a value < b value" and use the string representation if that fails..)? cheers holger

2 1

Can I still download the old 64bit 6.0 vm?
by Tim Mackinnon July 25, 2017

July 25, 2017

Hi - since the update to pharo 6.1, my PharoLambda project has stopped building. Iâm trying to diagnose what is going wrong, and I wanted to zeroconf download the older Pharo6.0 vm and image - is that still possible? I seem to be getting an error with loading a metacello package as I am getting a null repository error. I am retrying now with a non minimal image to try and diagnose the issue, but thought it worth asking about version control of these things. Tim

1 1

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!
by Alistair Grant July 24, 2017

July 24, 2017

Hi Thierry, On Mon, Jul 24, 2017 at 10:23:49PM +0200, Thierry Goubier wrote: > Le 24/07/2017 ?? 17:05, Alistair Grant a ??crit : > >For Ubuntu users, the updated snap is also available: > > > >sudo snap install pharo --classic --candidate > > Hi Alistair, > > how one update the pharo snap (from 6.0 to 6.1)? sudo snap refresh pharo --candidate Just FYI: My understanding is that if 6.1 had already been pushed to stable, it would update automatically (according to the schedule you have, either by default or set explicitly). Cheers, Alistair > Thierry > > > > >Cheers, > >Alistair > > > >P.S. Should this message be sent to pharo-users as well?

1 0

New Launcher not working (Windows)
by Jan BlizniÄenko July 24, 2017

July 24, 2017

Hello It seems I am not able to open an image via new Launcher for Windows. I have downloaded new build of Pharo Launcher for Windows from https://ci.inria.fr/pharo/job/Launcher-Win/ ( pharo_installer-0.2.13.exe ) and it starts ok, downloads image ok, but I am unable to open it, although opening images works fine in older launcher ( pharo_installer-0.2.11.exe from 28. 2. 2017). First time I tried opening the image (double clicking on it in the list), loading bar "Determining Image version" showed up and remained frozen like that without any progress shown in the bar. I gave it 10 minutes, but no change, still stuck like that. UI was not responding, so I terminated it via alt+. Second time I tried opening the image via the Launcher, that "Determining" bar was there only for a second and then it was replaced by "Fetching VM to run Pharo 60 images" which seemed to be really fetching something, but after another second or two, it got stuck in the middle of the process and got an error "KeyNotFound: key '60' not found in Dictionary". Well, it seemed like I got further, so third time is a charm. This time, instead of previous error, I got "FileExists: File @C:\Users\User\Documents\Pharo\vms\60.zip", which is quite understandable since previous process did not successfully cleaned up after itself. I tried it repeatedly, tried it with both old (already existing) and new images (downloaded in new Launcher) and I tried removing whole Pharo folder in Documents, but every time I get stuck with one of those problems above. There is a PharoDebug.log with logs of interrput and errors mentioned above: PharoDebug.log <http://forum.world.st/file/n4956495/PharoDebug.log> Note that I can open those images just fine by opening them directly from Windows file explorer or via old Launcher, just not in the new Launcher. Windows 10 Pro v1703 64bit. Thank you Jan -- View this message in context: http://forum.world.st/New-Launcher-not-working-Windows-tp4956495.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 3

[pharo-project/pharo-core]
by GitHub July 24, 2017

July 24, 2017

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

1 0

[pharo-project/pharo-core] f35877: 60510
by GitHub July 24, 2017

July 24, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f35877b624a127a40c6abc4aad553ff063fab522 https://github.com/pharo-project/pharo-core/commit/f35877b624a127a40c6abc4a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-07-24 (Mon, 24 Jul 2017) Changed paths: A Iceberg-Libgit.package/IceLibgitLocalRepository.class/instance/accessing/setLongpaths_global_.st A Iceberg-Metacello-Integration.package/IceBitbucketRepositoryType.class/README.md A Iceberg-Metacello-Integration.package/IceBitbucketRepositoryType.class/class/accessing/type.st A Iceberg-Metacello-Integration.package/IceBitbucketRepositoryType.class/definition.st M Iceberg-Metacello-Integration.package/IceGithubRepositoryType.class/README.md M Iceberg-Metacello-Integration.package/IceGithubRepositoryType.class/definition.st M Iceberg-Metacello-Integration.package/IceGithubRepositoryType.class/instance/accessing/mcRepository.st A Iceberg-Metacello-Integration.package/IceGitlabRepositoryType.class/README.md A Iceberg-Metacello-Integration.package/IceGitlabRepositoryType.class/class/accessing/type.st A Iceberg-Metacello-Integration.package/IceGitlabRepositoryType.class/definition.st M Iceberg-Metacello-Integration.package/IceMetacelloPharoPlatform.class/instance/repository creation/createRepository_.st M Iceberg-Metacello-Integration.package/IceMetacelloRepositoryType.class/class/accessing/allTypes.st M Iceberg-Metacello-Integration.package/IceMetacelloRepositoryType.class/class/instance creation/for_.st A Iceberg-Metacello-Integration.package/IceMetacelloRepositoryType.class/class/testing/isAbstract.st A Iceberg-Metacello-Integration.package/IceProviderRepositoryType.class/README.md A Iceberg-Metacello-Integration.package/IceProviderRepositoryType.class/class/testing/isAbstract.st A Iceberg-Metacello-Integration.package/IceProviderRepositoryType.class/definition.st A Iceberg-Metacello-Integration.package/IceProviderRepositoryType.class/instance/accessing/mcRepository.st A Iceberg-Plugin-GitHub.package/IceGitHubPullRequestBrowser.class/instance/accessing/mergeBaseCommitFor_.st A Iceberg-Plugin-GitHub.package/IceGitHubPullRequestBrowser.class/instance/accessing/mergeBaseFor_.st M Iceberg-Plugin-GitHub.package/IceGitHubPullRequestBrowser.class/instance/building/addChangesTreeTo_with_.st M Iceberg-Plugin.package/IcePharoFogbugzModel.class/instance/initialization/initializeWidgets.st M Iceberg-Plugin.package/IcePharoFogbugzModel.class/instance/private/validateIssue_.st A Iceberg.package/IceCommitInfo.class/instance/accessing/compatibleTimestamp.st A Iceberg.package/IceRepository.class/instance/accessing/mergeBaseBetween_and_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60509.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60510.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60509.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60510.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60510 20268 update iceberg v0.5.5 https://pharo.fogbugz.com/f/cases/20268 http://files.pharo.org/image/60/60510.zip

1 0

Esteban's ChangeLog week of 17 July 2017
by estebanlm＠gmail.com July 24, 2017

July 24, 2017

Hello! This is my weekly ChangeLog, from 17 July 2017 to 23 July 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=17/7/2017&to=23/7/2017 ChangeLog ========= 20 July 2017: ------------- * I'm fixing the Pharo7 build process to finally get to the point where we can use easily the Iceberg-based process. We have two remaining problems: . Since we use plain filetree on the bootstrap process, we do not have version information of packages. . Also because of that (and because Iceberg uses metadataless format), we do not have correct timestamps. So, today (last two days, in fact), I fixed point 1, by adding a Pharo +hidden+ repository to iceberg and setting the package ancestors with correct version info. This way, all comparissons are fine :) Process is kind of complex to explain here, but basically we replace the +cypress.1+ info with a correct version with a commit reference. 19 July 2017: ------------- * I released [Iceberg v0.5.3](https://github.com/pharo-vcs/iceberg/releases/tag/v0.5.3) I needed this because the load/merge/pull times for large projects were innaceptable, mainly because after doing the pull into the local workingcopy, it was scanning all packages to see what changed and load them. This naive approach was ok for most of the projects, but those with many packages (like Pharo itself) were taking ages to perform a merge. Now we do it as the sync: we figure out packages that changed between your installed version and the upcoming version and we merge just that. Also, I fixed some other important issues: * +#isAncestorOf:+ was scanning all commits. Again, this worked for small projects. Big ones (as Pharo) were not scaling. * I created "system repository" concept. This is because Pharo7 will be dispatched with a Pharo repository but no local checkout. Then you will see an invalid project in iceberg window. This is not good because most of the times users will not care about it, but it will be annoying :) Now, if you are a Pharo developer, you can add to your startup actions this script: ---- Iceberg showSystemRepositories: true. IceRepository registry detect: [ :each | each name = 'pharo' ] ifFound: [ :each | each location: '/path/to/your/location/of/pharo-project/pharo' asFileReference ]. ---- with this, you will have always access to your Pharo repository. 17 July 2017: ------------- * I just cameback from a week off. I released a patch version of [Iceberg (0.5.2)](https://github.com/pharo-vcs/iceberg/tree/v0.5.2) mostly to fix an override problem, but incorporating some other contributions. cheers! Esteban

1 0

Epicea applying multiple changes
by Andrei Chis July 23, 2017

July 23, 2017

Hi, Is there some known bug in Epicea when applying multiple changes at once in Pharo 6? I had a few crashes lately and each time when recovering the changes by selecting multiple changes at once some changes are skipped. If I apply manually each change it works. Cheers, Andrei

7 7

Epicea feedback
by Jan BlizniÄenko July 23, 2017

July 23, 2017

Hello I'd like to thank you for creating the Epicea. It is way more user-friendly and dependable than previous change-handling tool. Browsing, applying and reverting changes is way easier. Just one note: It is not exactly clear from first look how to properly reapply changes after an image has been closed without saving. If I select all changes I want to apply without using any filter, those changes are reapplied in wrong order (if I changed a method two times, first the new version is applied and then the old one). As far as I understood, I have to use filter to show only latest changes, but I think it could be clearer in the UI that I need to do so (or something completely different?) for applying changes. Thank you Jan -- View this message in context: http://forum.world.st/Epicea-feedback-tp4952661.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

3 4