December 2018 - Pharo-dev - lists.pharo.org

Recommendation for password encryption?
by Mariano Martinez Peck Sept. 30, 2022

Sept. 30, 2022

Hi guys. Some time ago I asked about the best way to encrypt a password. Some of the recommendations I got was: 1) Generally for passwords you do not write a decrypt method for security purposes (eg you do not want people to be able to reverse engineer the encrypted password easily) 2) put a little salt 3) There is http://www.squeaksource.com/Cryptography/PasswordHashingFFI 4) I should not decrypt password but instead I should compare both encrypted versions to see if they are equal. My scenario is the following. I need to store database passwords in text files. So I don't want to let them as plain text. And while I understand 4), I think it's a different scenario than mine. I know that some database driver may allow you to directly send the encrypted password. But still...I have another similar scenario in which I have to store a password and then send it (unencrypted)...so I kind of really need a bi-directional encryption. Now..I would try to avoid having an external library + FFI. Any ideas what is the best thing I can do? And how could I solve 1) if I want bidirectional like in my case? Thanks in advance, -- Mariano http://marianopeck.wordpress.com

9 26

Re: [Pharo-project] Parsing and navigating Html
by Paul DeBruicker July 16, 2020

July 16, 2020

On 12/05/2010 06:02 AM, pharo-project-request(a)lists.gforge.inria.fr wrote: > From: St?phane Ducasse<stephane.ducasse(a)inria.fr> > Subject: [Pharo-project] Parsing and navigating Html > To:"Pharo-project(a)lists.gforge.inria.fr Development" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID:<1C53DFD8-3021-4233-BC83-CE8C1EA8D103(a)inria.fr> > Content-Type: text/plain; charset=us-ascii > > Hi > > I would like extract partial information from HTML pages. > So I started to play and fix HTMLParser. > > Now does anybody know alternatives? > > Second, does anybody develop a lib to query HTML structure as with the XMLSupport package? > > Stef The Soup package on SqueakSource.com works OK.

3 4

Re: [Pharo-dev] [Vm-dev] Image crashing on startup, apparently during GC
by Eliot Miranda June 3, 2019

June 3, 2019

Hi Damien, On Fri, Mar 23, 2018 at 12:38 PM, Damien Pollet <damien.pollet(a)gmail.com> wrote: > > Here are the files (image and various outputs). Running with --leakcheck > does mention a few object leaks (see output.txt); > Indeed the image is corrupt at start-up. See below. > I'm not sure where to get or how to build an assert VM. > When you build a phar. VM under build.macos64x64/pharo.cog.spur using the mvm script (mvm -A) you produce an assert VM in PharoAssert.app. > I also realized the VM I had was from this summer (the one that comes with > a 70 image with zeroconf). The output files I include were produced by the > VM at get.pharo.org/64/vmLatest70 > > https://www.dropbox.com/s/y8yqjuzd9nsvy1u/clap-broken.tar.gz?dl=0 > > On 20 March 2018 at 18:17, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > >> >> Hi Damien, >> >> On Tue, Mar 20, 2018 at 3:12 AM, Damien Pollet <damien.pollet(a)gmail.com> >> wrote: >> >>> >>> Hi, I have a Pharo image that crashes the VM on startup. The crash >>> report below seems to incriminate GC. Should I make it available somewhere >>> online? What's most convenient? >>> >> >> Don't care. Anywhere it can be downloaded from. Also, try running with >> -leakcheck 15, preferably in an assert VM and see if that gets you >> additional information. >> >> >>> >>> Process: Pharo [64892] >>> Path: /Users/USER/*/Pharo.app/Contents/MacOS/Pharo >>> Identifier: org.pharo.Pharo >>> Version: 5.0.201708271955 (5.0.201708271955) >>> >> Right. This VM is prior to the bug fixes in VMMaker.oscog-eem.2320: Spur: Fix a bad bug in SpurPlnningCompactor. unmarkObjectsFromFirstFreeObject, used when the compactor requires more than one pass due to insufficient savedFirstFieldsSpace, expects the corpse of a moved object to be unmarked, but copyAndUnmarkObject:to:bytes:firstField: only unmarked the target. Unmarking the corpse before the copy unmarks both. This fixes a crash with ReleaseBuilder class>>saveAsNewRelease when non-use of cacheDuring: creates lots of files, enough to push the system into the multi-pass regime. Pharo urgently needs to upgrade the VM to one more up to date than 2017 08 27 (in fact more up-to-date than opensmalltalk/vm commit 0fe1e1ea108e53501a0e728736048062c83a66ce, Fri Jan 19 13:17:57 2018 -0800). The bug that VMMaker.oscog-eem.2320 fixes can result in image corruption in large images, and can occur (as it has here) at start-up, causing one's work to be irretrievably lost. > Code Type: X86-64 (Native) >>> Parent Process: ??? [64888] >>> Responsible: Pharo [64892] >>> User ID: 501 >>> >>> Date/Time: 2018-03-19 20:27:03.906 +0100 >>> OS Version: Mac OS X 10.13.3 (17D102) >>> Report Version: 12 >>> Anonymous UUID: 6D022236-78DD-6676-117F-EADA56D5D1BE >>> >>> Sleep/Wake UUID: AC9E4E55-3CDB-4B4F-A6B4-51ACB1177154 >>> >>> Time Awake Since Boot: 28000 seconds >>> Time Since Wake: 6500 seconds >>> >>> System Integrity Protection: enabled >>> >>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread >>> >>> Exception Type: EXC_BAD_ACCESS (SIGABRT) >>> Exception Codes: KERN_INVALID_ADDRESS at 0x000000012b67c0b0 >>> Exception Note: EXC_CORPSE_NOTIFY >>> >>> VM Regions Near 0x12b67c0b0: >>> VM_ALLOCATE 000000011adfc000-00000001259fc000 [172.0M] >>> rw-/rwx SM=PRV >>> --> >>> STACK GUARD 0000700005613000-0000700005614000 [ 4K] >>> ---/rwx SM=NUL stack guard for thread 1 >>> >>> Application Specific Information: >>> abort() called >>> >>> Thread 0 Crashed:: Dispatch queue: com.apple.main-thread >>> 0 libsystem_kernel.dylib 0x00007fff53fbde3e __pthread_kill + 10 >>> 1 libsystem_pthread.dylib 0x00007fff540fc150 pthread_kill + 333 >>> 2 libsystem_c.dylib 0x00007fff53f1a312 abort + 127 >>> 3 org.pharo.Pharo 0x0000000104ed8997 sigsegv + 190 >>> 4 libsystem_platform.dylib 0x00007fff540eff5a _sigtramp + 26 >>> 5 ??? 000000000000000000 0 + 0 >>> 6 org.pharo.Pharo 0x0000000104e73558 markObjects + 464 >>> 7 org.pharo.Pharo 0x0000000104e72d40 fullGC + 72 >>> 8 org.pharo.Pharo 0x0000000104e92dea primitiveFullGC + >>> 45 >>> 9 org.pharo.Pharo 0x0000000104e52425 interpret + 26715 >>> 10 org.pharo.Pharo 0x0000000104e5c7f6 >>> enterSmalltalkExecutiveImplementation + 152 >>> 11 org.pharo.Pharo 0x0000000104e4be6c interpret + 674 >>> 12 org.pharo.Pharo 0x0000000104ed9cc1 >>> -[sqSqueakMainApplication runSqueak] + 394 >>> 13 com.apple.Foundation 0x00007fff2e6d696c >>> __NSFirePerformWithOrder + 360 >>> 14 com.apple.CoreFoundation 0x00007fff2c579127 >>> __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 >>> 15 com.apple.CoreFoundation 0x00007fff2c57904f >>> __CFRunLoopDoObservers + 527 >>> 16 com.apple.CoreFoundation 0x00007fff2c55b6a8 __CFRunLoopRun + >>> 1240 >>> 17 com.apple.CoreFoundation 0x00007fff2c55af43 >>> CFRunLoopRunSpecific + 483 >>> 18 com.apple.HIToolbox 0x00007fff2b872e26 >>> RunCurrentEventLoopInMode + 286 >>> 19 com.apple.HIToolbox 0x00007fff2b872a9f >>> ReceiveNextEventCommon + 366 >>> 20 com.apple.HIToolbox 0x00007fff2b872914 >>> _BlockUntilNextEventMatchingListInModeWithFilter + 64 >>> 21 com.apple.AppKit 0x00007fff29b3df5f _DPSNextEvent + >>> 2085 >>> 22 com.apple.AppKit 0x00007fff2a2d3b4c >>> -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] >>> + 3044 >>> 23 com.apple.AppKit 0x00007fff29b32d6d -[NSApplication >>> run] + 764 >>> 24 com.apple.AppKit 0x00007fff29b01f1a NSApplicationMain >>> + 804 >>> >>> -- >>> Damien Pollet >>> type less, do more [ | ] http://people.untyped.org/damien.pollet >>> >>> >> >> >> -- >> _,,,^..^,,,_ >> best, Eliot >> >> > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > -- _,,,^..^,,,_ best, Eliot

9 26

Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"
by Tim Mackinnon April 19, 2019

April 19, 2019

I noticed that recent Pharo 6.1 zero conf downloads show lots of these errors when you run the image in the terminal. Previous versions didnât do this - is this something to do with the latest vm upgrade? ./pharo-ui PagerDuty.image /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist' /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist' Tim

6 6

Pharo Downloads are sluggish
by Esteban Maringolo March 13, 2019

March 13, 2019

Is there a reason why the latest version of the builds linked from the website are not hosted in some CDN, Amazon S3 or similar? Maybe in Europe the speed is fast, but where I am (Argentina) it is really slow, the screenshot shows 3.5KB/s, it averages 10KB/s, with peaks of 40KB/s. This is an pitiful boarding experience, that will make many cancel it even before getting to open the downloaded launcher. [image: node-pharo.png] The screenshot shows that is not a problem with my home connection, which isn't the fastest but is "normal" for my use cases. Regards, Esteban A. Maringolo ps: When I finished writing this email, this was the progress... [image: image.png]

4 15

Pharo 7 RC - Changing to larger font breaks scrolling in code browsers
by Sven Van Caekenberghe Jan. 24, 2019

Jan. 24, 2019

Hi, Here is an annoying usability bug that I am experiencing and that sometimes drives me nuts. It has been there a while. Take a stock Pharo 7 RC image and don't change any setting. Browse the method #testAsDateAndTime as implemented by DateAndTimeTest. This is a (too) long (test) method. Any long method will do. You can scroll it fine in both the implementors and well as in the full browser. Now switch to 'Medium' sized 'predefined style' Standard Fonts using the Settings Browser. It is now close to impossible to scroll in the implementors or the full browser: not using the scroll bar arrows, not dragging the scroll bar, not clicking above/below the scroll bar, not using the scroll gesture (track pad, mouse pad, wheel), not using cursor keys inside the editor. Scrolling seems to happen automatically and goes on until the top or bottom. Can anyone replicate this ? Sven

2 2

Better management of encoding of environment variables
by Guillermo Polito Jan. 22, 2019

Jan. 22, 2019

Hi all, following the meeting we had here @Inria headquarters, I'll be backporting some of the improvements we did in the launcher this last month regarding the encoding of environment variables. I've opened for this issue https://pharo.fogbugz.com/f/cases/22658/ We have already studied possible alternatives with Pablo and Christophe and we have some conclusions and we propose some changes: API Proposal for OSEnvironment ========================= - *at: aVariableName * Gets the String value of an environment variable called `aVariableName` It is the system reponsibility to manage the encoding. Rationale: A common denominator for all platforms providing an already decoded string, because windows does not (compared to *nix systems) provide a encoded byte representation of the value. Windows has instead its own wide string representation. - *[optionally] rawAt: anEncodedVariableName* Gets the Byte value of an environment variable called `anEncodedVariableName`. It is the user responsibility to encode and decode argument and return values in the encoding of this preference. Rationale: Some systems may want to have the liberty to use different encodings, or even to put binary data in the variables. - *[optionally] at: aVariableName encoding: anEncoding* Gets the value of an environment variable called `aVariableName` using `anEncoding` to encode/decode arguments and return values. Rationale: *xes could potentially use different encodings for their environment variables or even use different encodings in different parts of their file system. Other Implementation details ========================= - VM primitives returning paths Strings should be carefuly managed to decode them, since they are actually C strings (so byte arrays) disguised as ByteStrings. - Windows requires calling the right *Wide version of the functions from C, plus the correct encoding routine. This could be implemented as an FFI call or by modifying the VM to do it properly instead of calling the Ascii version

9 23

Happy new year!
by Esteban Lorenzano Jan. 2, 2019

Jan. 2, 2019

Hi list, Just that. I wish you all have a happy new year, and may it be even better than this one :) Esteban

6 5

New book: Pharo with Style
by Stephane Ducasse Jan. 1, 2019

Jan. 1, 2019

Hello Fellow Pharoers I'm happy to announce a new little book to improve the culture around Pharo. I will revise it in the future so you can feel free to send feedback and pull requests to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle Stef "The best way to predict the future is to invent" so I do it.

4 5

Esteban's ChangeLog week of 24 December 2018
by estebanlm＠gmail.com Dec. 31, 2018

Dec. 31, 2018

Hello! This is my weekly ChangeLog, from 24 December 2018 to 30 December 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=24/12/2018&to=30/12/2018 ChangeLog ========= 27 December 2018: ----------------- * Opened Pharo8.0 development * branch was already opened by Stef :) * opened issue tracker * updated documents to point to it * sent mails to list TODO: Update videos (we needed new ones anyway) cheers! Esteban

1 0

[Pharo 7.0] Build #91: Revert "21876 Re-evaluating of class definition with slots cleans the class instance variables"
by ci-pharo-ci-jenkins2＠inria.fr Dec. 30, 2018

Dec. 30, 2018

There is a new Pharo build available! The status of the build #91 was: FAILURE. The Pull Request #2145 was integrated: "Revert "21876 Re-evaluating of class definition with slots cleans the class instance variables"" Pull request url: https://github.com/pharo-project/pharo/pull/2145 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] About contribution process, people participation and communication (WAS: Re: [ANN] Pharo 8.0 development started)
by Ben Coman Dec. 30, 2018

Dec. 30, 2018

On Sun, 30 Dec 2018 at 23:28, Esteban Lorenzano via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > > Now, while the general direction was explained, I think I failed to > communicate several things. > For what I can think at this moment (for sure there are a lot more): > > - I failed to communicate that opening Pharo 8.0 branch didnât mean > closing Pharo 7.0 development, just to allow people doing big changes to > merge them. > - I failed to communicate correctly that having a release candidate (rc1) > meant âcode freezeâ (and then forbidding new changes except bug fixing). > Thanks for acknowledging this Esteban. In spite of the communication issue, the point I'd make in support of this arrangement is that historically we've done poorly with code-freezes, or even the lesser strength feature-freezes leading up to a release. A code freeze can be discouraging when integration of new features are delayed and can weaken such the code freeze. Opening the next-version-dev branch when the current-version freezes for release-candidate seems to facilitate pre-release stability - though the risk though of mind-share drifting to the next-version-dev branch needs to be managed. cheers -ben

1 0

Re: [Pharo-dev] [ANN] Pharo 8.0 development started
by Sean P. DeNigris Dec. 30, 2018

Dec. 30, 2018

Pharo Smalltalk Developers mailing list wrote > Iâm on holidays until 7/01 :P Esteban, thank you for all your incredible work on all these simultaneous big, hard problems! Now stop sending mails and go enjoy your holiday ;-) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

[Pharo 7.0] Build #90: 22855-Revert-PluggableTextMorph-changes
by ci-pharo-ci-jenkins2＠inria.fr Dec. 30, 2018

Dec. 30, 2018

There is a new Pharo build available! The status of the build #90 was: SUCCESS. The Pull Request #2144 was integrated: "22855-Revert-PluggableTextMorph-changes" Pull request url: https://github.com/pharo-project/pharo/pull/2144 Issue Url: https://pharo.fogbugz.com/f/cases/22855 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo 8.0 development started
by Esteban Lorenzano Dec. 30, 2018

Dec. 30, 2018

Hello all, We are preparing to release Pharo 7.0 (which will be in January, as soon as we finish some last details). And in the meantime impatient people has asked (and obtained) the aperture of Pharo 8.0 development! :) So you now can start making Pull Requests against Pharo8.0 branch :) Esteban

3 8

Re: [Pharo-dev] [Moose-dev] glamorous toolkit: v0.4.0
by Tudor Girba Dec. 29, 2018

Dec. 29, 2018

Hi, Thanks for the link. For some strange reason, I do not see the linked email in my inbox. I am happy to hear that you could install GT. > * The new interfaces and some demo of the graphical elements look > pretty good > * After just some operations including window resizing I just get the > Red Window of Death [1](https://i.imgur.com/Cbx7uyH.png). Indeed, that is a known problem: https://github.com/feenkcom/gtoolkit/issues/64 > * I like the little triangles to expand thing in the document and the > run buttons for embedded code, and the "embeddability" of elements > in the document in a tree like fashion, which of course could lead > to documents that embed pieces of documents, which embed pieces of > documentsâ¦ But the dual panel view of code in one side with > results in the right panel of old GT didn't tend to create such > "recursion". This dual modal view is the same of > Atom[2](https://is.gd/kegaso) and CodiMD[3](https://is.gd/wudugi) > for interactive documentation and I would like to see examples more > in that line... but I don't know how it suits the philosophy behind > Documenter, which seems more aligned to a modal non dual view of the > document where you enter into edit mode once you click a piece of > the document and into a view mode once you are out of it (instead of > the proposed dual view). Would be nice to see is such dual view can > be used to directly operate on the rendered view and see changes in > the markup (i.e resizing an image in the rendered view changes the > value on the edit view). Interesting observation. The linked tools as all other notebook technologies I saw rely on two distinct modes for edit and view that reside in two distinct widgets (editor and viewer). They do that because they simply cannot have it in one. Because of the design of Bloc we are not constrained to that. Instead, we build a seamless interface that is both optimized for viewing, and for editing with live preview that does not rely on an explicit render button. This approach enables direct manipulation without friction, and we think this is a significant advancement in this space. About the remark related "to documents that embed pieces of documents, which embed pieces of documentsâ: It is indeed possible to embed documents in documents, but I am not sure I understand where you see the issue appearing. Could you detail this part? > * I like the different view that a document can have, markup wise: > Pillar, Markdown, LaTeX, HTML, DeckJS AsciiDoc as is demoed in the > authoring part [4](https://i.imgur.com/Jc1T5Rm.png). Interestingly, those extensions exist in the old Inspector as well. > * Its difficult to travel between the panels of a playground. > Previously you just make click in the lower circle representing the > panel you want to go at it was done > [5](https://i.imgur.com/4CDAM2o.png), but now clicking on the upper > rectangle representing such panel has no effect > [6](https://i.imgur.com/8Obo3Ct.png). For now, you have to rely on horizontal scrolling using a trackpad or mouse. Alternatively, Shift+scroll should also work. The upper part is not yet ready. > * Auto-completion and shortcuts for selecting text doesn't work well > on code cells of the new playground. Selecting whole words with Ctrl > arrow doesn't work, neither using down arrows to choose from > suggestions and even you can end with previous suggestions floating > around your playground [7](https://i.imgur.com/4awyIft.png) > [8](https://i.imgur.com/7qXc64b.png). Indeed. These are known issues that we will tackle soon. > * The default data science example didn't work at all > [8](https://i.imgur.com/YhNb8el.png) Nice catch. Thanks. The path of the file is incorrect when the image is copied. >> Now, a clarification. The old GT was produced over a period of 4 years >> by an open-source team. The project had its own identity, and in 2014 >> the core of it was first integrated in Pharo. I say the core of it, >> because the visual part and other libraries are not in Pharo today. >> >> The full potential is found in Moose. In any case, during this >> process, GT got to be identified with Pharo and that was a good thing. >> The new GT is a product produced by feenk, a company. Much of the >> original team is still active in the new version, but now we commit to >> our product in a different way. The product is free and open-source, >> but itâs still a product with an identity and a goal. At present time, >> both the team, identity and goal are different than those of Pharo. >> >> Our goal is to offer a fundamentally new alternative to program >> (including comparing to what is possible now in Pharo). We are not >> looking for marginal improvements, and we are not aiming at backward >> compatibility. > I used Moose to build the first Grafoscopio versions, but there was a > lot of stuff that was related with software analysis that I didn't > really need for reproducible interactive documentation and publishing > nor for data science, activism and storytelling. So once old GT was > integrated into Pharo with Spec I used a more minimal setup to deliver a > more focused experience. > > I think that most times this relationship between Pharo and Moose can be > of creative tension, one pushing the boundaries and the other offering a > more stable experience where the innovations of the former are > integrated and debugged. But even after using Moose as a fully > integrated vision of what old GT have to offer in the back and front > end, I didn't see any migration path from previous Moose with the old GT > to the current GT, which is kind of worrisome. I understand the idea of > forks in FLOSS as a way of dealing with politics behind the FLOSS > movement and the relationship between different visions and actors > (individuals, communities, enterprises, foundations, associations and so > on). It has happened before with Squeak, Pharo and Cuis and I'm fine > with that. And I understand that a healthy relationship with the past > means sometimes to break with it and jump into the future. > > That's why I think that the role of for profit and non for profit > institutions is to balance a sense of momentum and stability around > FLOSS. I would like to see a more clear road map for GT, knowing ahead > where backward compatibility will be broken and why, which are the > visions and, more importantly, how to participate and where are the > boundaries. These are difficult tasks, but if the participation and > boundaries are explored collectively, you can also know about the first > ones (visions, versions, forks, compatibility). In that sense I think > that Pharo is putting a good example: we have a clear road map document > and participation process in the public repositories, there are public > channels for users and developers and the private companies know about > them, so they can put the boundaries about what is going to be done in > the open, with the community, and what is to be kept closed inside > company's frontiers and channels and the company's own velocity. I don't > know if Feenk is planing something similar for its new vision, product > and identity, and I don't know if the new alternative will have its own > non-profit organizations as a neutral entity for all players using GT, > but would be good to know about that, not because there are not people > willing to jump into the future, but we would like to know to which > future we're jumping on. Without that I think that is a safer bet for > myself to rely on Pharo and see how migration paths could ensure > compatibility with my own past and the one of my local community using > Pharo and GT based tools. I hope that the open source nature of both > products (Pharo and new GT) will ease the cross-pollination of the more > interesting ideas, even without sharing code, visions or UI. We do not regard our work as an evolution, and we are not concerned with backwards compatibility. We are not trying to be completely different to what we had before, but being compatible is simply not a goal. For example, extending oldInspector is usually a matter of a dozen lines. Extending the new Inspector works in a similar way, but with a slightly different API that is needed because of the new infrastructure. The migration is not a pain, and it can happen seamlessly as I described in the mail to Luke. I understand how from your point of view as a user of Pharo and oldGT you regard backward compatibility as important. However, we look at things differently. We think that development can be enhanced both from an efficiency and from a happiness point of view with a significant degree. When something like this is possible, the opportunities are different, too. For example, backward compatibility is about limiting costs. However, when the profit promise can be large, some costs can be worthwhile and are to be considered investments. What do we mean by profit? For example, what would it be worth for a company to have the non-technical people literally pair and understand the internal details of the domain model? Compared to what exists now, that can be invaluable and we think that following moldable development this will be a natural by product. Another example: what would it worth for a developer of a library to build a live documentation with a marginal effort that simply leverages the testing effort? It can be invaluable, and we think this is trivially possible. About the roadmap, here it is: we aim to build a complete development environment that will enable moldable development. We understand how this can appear vague. I think itâs not because I and my colleagues talk about it since many years now. People pay little attention, so now we set ourselves to deliver a concrete incarnation of what we think the future should look like. We set to create something that does not exist in other parts, and we simply do not quite know how this will look like in details. For example, we do know that we want to build a Coder or a Debugger, we even have advanced ideas and implementations, but we do not know exactly how it will look like and because of that we also do not quite know how long it will take. We have a particular way of approaching development that relies on fast feedback and storytelling, and at the end we always get surprised of where the journey takes us. For example, the current state of Documenter was simply difficult to imagine even 4 months ago, and in the process we threw away more code than is now released. So, we will not detail the concrete steps because we do not work like that. We do have a clear vision of what we think software development should be, and we will put forward our guiding principles shortly. About the governance process: GT is built by feenk and will continue to be so for the foreseeable future. We put things that we create in the open, we do so for free, and we welcome people to engage with us. >> To build this alternative we invested in a whole new stack. That is >> not a tiny challenge and getting it right requires many iterations and >> feedback. We say we are in alpha not because of inconveniences of >> installation but because we are still very much developing the product. >> >> We announced the first alpha version in September and since then much >> has changed. At present time, we did manage to reach a situation where >> downloading the distribution should run on Mac, Linux and Windows. >> Even so, the current version is only for people that do want to try >> knowing that there will be hurdles. > > I think that not only installation inconveniences is related alpha, but > also this jumping from old GT to new one without a clear migration path > (as is expected from alpha software and processes). I'm fine with that > too, but I think that once the new GT reaches beta status the backward > compatibility should be more important and meanwhile the non regard of > that should be stated more promptly for previous and future GT users. I > imagine that, at some point Feenk will provide its users and customers > with clear support and migration paths regarding its open source > products (kind of what happens with Canonical and the Long Term Support > versions of Ubuntu). As mentioned above, our focus is to build a new experience. It is likely that a typical Pharo user will not have much issues adapting to the new interface. A developer that depended on the old APIs will be somewhat impacted, but we do not expect a too large effort will be required to adopt the new world. Nevertheless, if itâs stability and predictability you are looking for, it is best to wait for now. >> A word about the user experience. The current version runs inside the >> Pharo UI because we need to bootstrap. But, our goal is to build a >> complete IDE on the new stack. If you want to judge the user >> experience, it is only meaningful to do it within the GT windows, and >> not by comparing it with the rest of the existing Pharo UI. >> >> Does this clarify the situation? > Yes, it does. It seems that a fork is coming, at least UI wise regarding > Pharo and new GT, but if the community knows about it, I'm fine with > that. I think this thread also clarifies what active users of old GT > will expect from upcoming versions of new (non alpha) GT regarding > compatibility, open processes, visions and so on. Hopefully we will > reach that place together. I do not think a new piece of code should be called a fork. At this point in time, GT and everything it comes with, loads cleanly in Pharo 7. Cheers, Doru > On Dec 29, 2018, at 5:10 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi Doru, > > This one is still pending: > > https://www.list.inf.unibe.ch/pipermail/moose-dev/2018-December/027542.html > > Of course we have slow days at end of year and I don't expect immediate > answer, but now that discussion was active is good to point some pending > conversation, even to be taken after holidays. > > Cheers, > > Offray > > On 29/12/18 6:38, Tudor Girba wrote: >> Hi Offray, >> >> I believe I replied to all your emails. If I missed one, please point me to it. >> >> Cheers, >> Doru >> >> >>> On Dec 28, 2018, at 5:12 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: >>> >>> >>> On 28/12/18 8:03, Tudor Girba wrote: >>>>> On Dec 28, 2018, at 1:08 PM, Kjell Godo <squeaklist(a)gmail.com> wrote: >>>>> >>>>> WOW >>>> :) >>>> >>>> What part of it do you like? >>>> >>>> Cheers, >>>> Doru >>> And which parts you don't? >>> >>> I wrote a long mail regarding good and no so good parts of the new GT >>> experience, including features possible forks, that I hope will be >>> answered also in detail, to keep the big picture. >>> >>> Cheers, >>> >>> Offray >>> >>> >>> >> -- >> www.feenk.com >> >> "You can inspect and adapt only what is explicit." >> >> -- www.feenk.com "No matter how many recipes we know, we still value a chef."

1 0

[Pharo 7.0] Build #89: 22842-Fix-externalBrowserTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 29, 2018

Dec. 29, 2018

There is a new Pharo build available! The status of the build #89 was: SUCCESS. The Pull Request #2135 was integrated: "22842-Fix-externalBrowserTest" Pull request url: https://github.com/pharo-project/pharo/pull/2135 Issue Url: https://pharo.fogbugz.com/f/cases/22842 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #88: 22827-Update-Calypso-Version
by ci-pharo-ci-jenkins2＠inria.fr Dec. 29, 2018

Dec. 29, 2018

There is a new Pharo build available! The status of the build #88 was: FAILURE. The Pull Request #2115 was integrated: "22827-Update-Calypso-Version" Pull request url: https://github.com/pharo-project/pharo/pull/2115 Issue Url: https://pharo.fogbugz.com/f/cases/22827 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0] Build #87: Improving the script to detect the version of the build.
by ci-pharo-ci-jenkins2＠inria.fr Dec. 29, 2018

Dec. 29, 2018

There is a new Pharo build available! The status of the build #87 was: FAILURE. The Pull Request #2134 was integrated: "Improving the script to detect the version of the build." Pull request url: https://github.com/pharo-project/pharo/pull/2134 Issue Url: https://pharo.fogbugz.com/f/cases/improving Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #86: Bottom21
by ci-pharo-ci-jenkins2＠inria.fr Dec. 29, 2018

Dec. 29, 2018

There is a new Pharo build available! The status of the build #86 was: SUCCESS. The Pull Request #2133 was integrated: "Bottom21" Pull request url: https://github.com/pharo-project/pharo/pull/2133 Issue Url: https://pharo.fogbugz.com/f/cases/Bottom21 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo Lambda Runtime
by Jan van de Sandt Dec. 29, 2018

Dec. 29, 2018

Hi, Last month Amazon extended their serverless runtime platform AWS Lambda with support for custom runtimes. I created a Pharo Lambda Runtime so now we can implement Lambda functions in Smalltalk and easily deploy them on the Lambda platform. Lamba has quite a large "free-tier", more than enough to do some experiments and to host small applications for free. See the GitHub project for more details https://github.com/jvdsandt/pharo-aws-toolbox Cheers, Jan.

7 10

Re: [Pharo-dev] [Moose-dev] glamorous toolkit: v0.4.0
by Tudor Girba Dec. 29, 2018

Dec. 29, 2018

Hi Offray, I believe I replied to all your emails. If I missed one, please point me to it. Cheers, Doru > On Dec 28, 2018, at 5:12 PM, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > > On 28/12/18 8:03, Tudor Girba wrote: >>> On Dec 28, 2018, at 1:08 PM, Kjell Godo <squeaklist(a)gmail.com> wrote: >>> >>> WOW >> :) >> >> What part of it do you like? >> >> Cheers, >> Doru > > And which parts you don't? > > I wrote a long mail regarding good and no so good parts of the new GT > experience, including features possible forks, that I hope will be > answered also in detail, to keep the big picture. > > Cheers, > > Offray > > > -- www.feenk.com "You can inspect and adapt only what is explicit."

1 0

[Pharo 7.0] Build #85: 22848-Patch-to-avoid-breaking-iceberg
by ci-pharo-ci-jenkins2＠inria.fr Dec. 28, 2018

Dec. 28, 2018

There is a new Pharo build available! The status of the build #85 was: FAILURE. The Pull Request #2132 was integrated: "22848-Patch-to-avoid-breaking-iceberg" Pull request url: https://github.com/pharo-project/pharo/pull/2132 Issue Url: https://pharo.fogbugz.com/f/cases/22848 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Moose-dev] glamorous toolkit: v0.4.0
by Tudor Girba Dec. 28, 2018

Dec. 28, 2018

> On Dec 28, 2018, at 1:08 PM, Kjell Godo <squeaklist(a)gmail.com> wrote: > > WOW :) What part of it do you like? Cheers, Doru > On Thu, Dec 20, 2018 at 01:57 Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Luke, > > I am happy this looks exciting :). > > About the confusion part: The Glamorous Toolkit we are working on right now is a complete new world built on a complete new graphical stack that does is not based on the existing stack that ships with Pharo. It is not an evolution. It is a leap. > > The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. > > But, in the new world, we are bringing the concept much further. For example, Documenter provides a whole new kind of a tool that can mold to unify multiple workflows (like data notebooks, code documentation, or tutorials) right in the IDE. Coder provides the infrastructure for manipulating code that can mold its shape as you type. Transcript allows you to embed various widgets to transform the otherwise dull experience of a console into a live one. > > Behind the scenes GT comes with several engines. The Examples engine enables example-driven development which also bridges the gap between testing and documentation effort, especially when combined with Documenter. Releaser is able to release deeply nested projects. Phlow offers an engine that shares similarities with Glamour. Completer provides moldable completion. Visualizer offers a couple of visualization engines such as Mondrian. > > All of these are possible because of the underlying graphical stack made of Sparta/Bloc/Brick. > > All in all, we believe that the new GT enables a new way of programming. Individual features can be attractive, but our goal is to reshape the development experience. > > Does this address the concern? > > Cheers, > Doru > > > > On Dec 19, 2018, at 2:09 PM, Luke Gorrie <luke(a)snabb.co> wrote: > > > > On Fri, 14 Dec 2018 at 05:13, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Please do let us know what you think .. and, of course, what you feel. > > > > I'm feeling excited and confused :). > > > > Excited because I love seeing all these new demos streaming out and I'm itching to put new capabilities to work. > > > > Confused about the roadmap. How does this "new" Glamorous Toolkit relate to the "old" one that I learned about last year from the Moldable Tools thesis? Is this a new version or a complete rewrite? Is it backwards compatible or completely reimagined? Is adopting the new version a seamless process or is porting required? Are frameworks like Glamour still there behind the scenes or were they replaced? etc. > > > > > > <gt-documenter-magic-markup.gif><gt-0-4-0.png>_______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.feenk.com > > "Things happen when they happen, > not when you talk about them happening." > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

1 0

Re: [Pharo-dev] [Moose-dev] Re: glamorous toolkit: v0.4.0
by Tudor Girba Dec. 28, 2018

Dec. 28, 2018

Hi, The visualization you describe should be easily doable in the new world. Did you write the visualization in plain Roassal or with the RTMondrian API? Cheers, Doru > On Dec 28, 2018, at 11:32 AM, Luke Gorrie <luke(a)snabb.co> wrote: > > Thanks for the explanations! > > I like the separation between selecting (single-click) and spawning (double-click). The miller column panning is indeed working with a two-finger drag on the touchpad. I will need to test whether this gesture works when running GT on Linux and operating it on a Mac via VNC. That's the most common setup for our application. > > Spotter is not urgent for us. I have written some extensions for it but we aren't really using them much yet. If the inspector is working well then that's the main thing. > > I do have one very important Roassal visualization that I need to bring with me smoothly somehow. Question is whether to port if over to the new framework or somehow smoothly embed Roassal in the new GT? > > The visualization is for compile SSA intermediate representation code and looks like this: > > <Screen Shot 2018-12-28 at 11.25.06.png> > There are some important properties about this diagram: > > - These are two digraphs stacked on top of each other. > - Nodes are always placed below their parents. > - Y-position indicates the max number of edges to reach parent nodes. > - Extra edges (red) can create cycles and should be ignored for layout purposes. > - Nodes can be compound shapes i.e. colored opcode and optionally fused immediate operands in white. > - Each node is an object that can be selected and inspected in the next miller column. > > Can this be done in the new framework with similar effort to the old one? > > On Fri, 28 Dec 2018 at 09:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > Thanks for the feedback! > > I am happy you like the new possibilities and that you see the incentives to move to the new world :). > > The inspector part is working quite well. The main reason we call it an alpha is because of the missing pieces to get to a full environment. > > You noticed the issue of Spotter. The existing Spotter is the one that is included in the old GT and it lives in the Morphic world. When the focus is in the new inspector, that means that keybindings are handled by Bloc and this is a separate world from Morphic. At present time, we can embed Bloc in Morphic but not the other way around as we want no binding from Bloc to Morphic. For this reason, unhandled keys are not propagated from Bloc to Morphic and that is why pressing Shift+Enter does not open Spotter. > > So, we will have a Spotter, but that will be another implementation. Other unfinished tools are the Debugger and Coder, but these are likely less relevant for your use case. > > A few other missing pieces: > - some widgets such as a tree are not yet implemented. So, we do not yet have a tree view in inspector. > - the text editor requires a few enhancements for navigation support. > - scrollbar > > The Miller-columns interface can be scrolled with the touchpad left-right. Can you confirm? > > About clicking vs double-clicking: Indeed, we now distinguish between selecting and spawning. As soon as there is a page to the right, selecting will populate that page. However, if there is no page to the right, simply selecting in a list will not spawn, like in the old inspector. Like this, you can work on a page without the page scrolling from underneath you. Please note that between pages we have triangles which are actually buttons. Selecting in a list shows a triangle. Clicking on the triangle spawns. So, you can either double-click to spawn, or you can select and then click on the triangle. Once spawned, simple selection is enough. Does this clarify the situation? > > About Roassal: In the new GT we have GtMondrian which is similar to the one from Roassal. We do not yet have support for creating charts (like bar or line charts). > > About the porting strategy: When you have the new GT loaded, the old Inspector will get a _GT pane that will essentially embed the new views in the old inspector. These also allow for interaction. Like this, you can port at your pace and switch only when you are ready. > > Cheers, > Doru > > > > > On Dec 27, 2018, at 11:36 AM, Luke Gorrie <luke(a)snabb.co> wrote: > > > > ... Some comments and questions if I may: > > > > The "+" button to quickly maximize a panel is fantastic. I am often looking at complex visualizations that should really be full-screen and it was always too much trouble to "drag" them to full screen and back. > > > > Is the Spotter still a part of GToolkit? If not then what replaces it? (I can see that it is present in the image but Shift-Return doesn't seem to invoke it when the GTInspector window has focus.) > > > > Is it still possible to pan left-right between "miller columns"? I see the squares at the top representing panes but clicking and dragging them doesn't seem to do anything. > > > > How come a double-click is now needed to inspect an object? Is single-click going to have a new function? > > > > Once more - great work you guys are doing ! > > > > On Thu, 27 Dec 2018 at 11:06, Luke Gorrie <luke(a)snabb.co> wrote: > > Hi Doru, > > > > Thank you very much for the detailed explanation. > > > > I have spent some time with the alpha now. I think it is absolutely fantastic! > > > > I love the new narrative style of the UI. This ties everything together beautifully and makes it easy to explore. That's really what I am lacking in my application. Currently it simply opens to a blank quasi-playground and it is not obvious what to type or how to get started. I started writing a separate HTML manual but I don't think that's the right medium -- much better with something interactive in the image like the Documenter. > > > > Just clicking around everything seemed to work basically smoothly for me. Maybe it's already time for me to port over to the new GT? Or what do you think the most likely obstacles would be in transitioning to this alpha version? > > > > Currently my custom inspector extensions are mostly based on Roassal and List/Tree/Table views. I also have one or two Glamour browsers. Is that all still there in one form or another? > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.feenk.com > > "Every thing has its own flow." > > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "The coherence of a trip is given by the clearness of the goal."

1 0

[Pharo 7.0] Build #84: 22833-PluggableTextMorph-and-co-should-be-removed
by ci-pharo-ci-jenkins2＠inria.fr Dec. 28, 2018

Dec. 28, 2018

There is a new Pharo build available! The status of the build #84 was: FAILURE. The Pull Request #2121 was integrated: "22833-PluggableTextMorph-and-co-should-be-removed" Pull request url: https://github.com/pharo-project/pharo/pull/2121 Issue Url: https://pharo.fogbugz.com/f/cases/22833 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Moose-dev] glamorous toolkit: v0.4.0
by Tudor Girba Dec. 28, 2018

Dec. 28, 2018

Hi, Thanks for the feedback! I am happy you like the new possibilities and that you see the incentives to move to the new world :). The inspector part is working quite well. The main reason we call it an alpha is because of the missing pieces to get to a full environment. You noticed the issue of Spotter. The existing Spotter is the one that is included in the old GT and it lives in the Morphic world. When the focus is in the new inspector, that means that keybindings are handled by Bloc and this is a separate world from Morphic. At present time, we can embed Bloc in Morphic but not the other way around as we want no binding from Bloc to Morphic. For this reason, unhandled keys are not propagated from Bloc to Morphic and that is why pressing Shift+Enter does not open Spotter. So, we will have a Spotter, but that will be another implementation. Other unfinished tools are the Debugger and Coder, but these are likely less relevant for your use case. A few other missing pieces: - some widgets such as a tree are not yet implemented. So, we do not yet have a tree view in inspector. - the text editor requires a few enhancements for navigation support. - scrollbar The Miller-columns interface can be scrolled with the touchpad left-right. Can you confirm? About clicking vs double-clicking: Indeed, we now distinguish between selecting and spawning. As soon as there is a page to the right, selecting will populate that page. However, if there is no page to the right, simply selecting in a list will not spawn, like in the old inspector. Like this, you can work on a page without the page scrolling from underneath you. Please note that between pages we have triangles which are actually buttons. Selecting in a list shows a triangle. Clicking on the triangle spawns. So, you can either double-click to spawn, or you can select and then click on the triangle. Once spawned, simple selection is enough. Does this clarify the situation? About Roassal: In the new GT we have GtMondrian which is similar to the one from Roassal. We do not yet have support for creating charts (like bar or line charts). About the porting strategy: When you have the new GT loaded, the old Inspector will get a _GT pane that will essentially embed the new views in the old inspector. These also allow for interaction. Like this, you can port at your pace and switch only when you are ready. Cheers, Doru > On Dec 27, 2018, at 11:36 AM, Luke Gorrie <luke(a)snabb.co> wrote: > > ... Some comments and questions if I may: > > The "+" button to quickly maximize a panel is fantastic. I am often looking at complex visualizations that should really be full-screen and it was always too much trouble to "drag" them to full screen and back. > > Is the Spotter still a part of GToolkit? If not then what replaces it? (I can see that it is present in the image but Shift-Return doesn't seem to invoke it when the GTInspector window has focus.) > > Is it still possible to pan left-right between "miller columns"? I see the squares at the top representing panes but clicking and dragging them doesn't seem to do anything. > > How come a double-click is now needed to inspect an object? Is single-click going to have a new function? > > Once more - great work you guys are doing ! > > On Thu, 27 Dec 2018 at 11:06, Luke Gorrie <luke(a)snabb.co> wrote: > Hi Doru, > > Thank you very much for the detailed explanation. > > I have spent some time with the alpha now. I think it is absolutely fantastic! > > I love the new narrative style of the UI. This ties everything together beautifully and makes it easy to explore. That's really what I am lacking in my application. Currently it simply opens to a blank quasi-playground and it is not obvious what to type or how to get started. I started writing a separate HTML manual but I don't think that's the right medium -- much better with something interactive in the image like the Documenter. > > Just clicking around everything seemed to work basically smoothly for me. Maybe it's already time for me to port over to the new GT? Or what do you think the most likely obstacles would be in transitioning to this alpha version? > > Currently my custom inspector extensions are mostly based on Roassal and List/Tree/Table views. I also have one or two Glamour browsers. Is that all still there in one form or another? > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Every thing has its own flow."

1 0

[Pharo 7.0] Build #83: 22841-Fix-printString-related-bugs
by ci-pharo-ci-jenkins2＠inria.fr Dec. 27, 2018

Dec. 27, 2018

There is a new Pharo build available! The status of the build #83 was: SUCCESS. The Pull Request #2131 was integrated: "22841-Fix-printString-related-bugs" Pull request url: https://github.com/pharo-project/pharo/pull/2131 Issue Url: https://pharo.fogbugz.com/f/cases/22841 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #82: 22826-senders-of-asNonTranslucentColor-should
by ci-pharo-ci-jenkins2＠inria.fr Dec. 27, 2018

Dec. 27, 2018

There is a new Pharo build available! The status of the build #82 was: SUCCESS. The Pull Request #2125 was integrated: "22826-senders-of-asNonTranslucentColor-should" Pull request url: https://github.com/pharo-project/pharo/pull/2125 Issue Url: https://pharo.fogbugz.com/f/cases/22826 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN][IMPORTANT] Pharo 8.0 issue tracker is MOVED to GitHub
by Esteban Lorenzano Dec. 27, 2018

Dec. 27, 2018

Hi, As part of our constant try to enhance process, we are moving the issue tracker to GitHub. You can now declare issues here: https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> FAQ: Q: Why we do this? A: - Because reuniting all development process in just one point will enhance traceability - â¦ and communication (there are a lot of conversations that now happens in different places (list, issue, PR). With this move we put issue and PR discussion in same place. - â¦ and people historically has complained that âthey need to log to fogbugz to just see the issuesâ - â¦ and this allows us to decommission one server we have now just to get the issues names when creating branches (and before slides). Q: Does that means fogbugz is bad? A: Not at all! It is a great tool and we are very grateful of it. Is just that we want to reunite our communication into a single point. Q: What will happen with issues reported in FogBugz? A: Pharo 7.0 issues will be taken as before. Pharo 8.0 issues need to be re-opened in GitHub. There are less than 25 right now and we ask people reporting it to move them again (maybe we would do it, but better is owners do). Q: How can we âbranch from issueâ now if we do not have FogBugz? A: We already added a tool âbranch from issueâ that uses GitHub issue tracker. This will be the same as before. And for the same price, we add that option to other projects: All GitHub projects now can benefit from âbranch from issueâ functionality. Cheers! Esteban

2 1

[Pharo 7.0] Build #81: 22802-ZipArchive-should-throw-specific-Error
by ci-pharo-ci-jenkins2＠inria.fr Dec. 27, 2018

Dec. 27, 2018

There is a new Pharo build available! The status of the build #81 was: FAILURE. The Pull Request #2119 was integrated: "22802-ZipArchive-should-throw-specific-Error" Pull request url: https://github.com/pharo-project/pharo/pull/2119 Issue Url: https://pharo.fogbugz.com/f/cases/22802 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #2: Removed obsolete Fuel package
by ci-pharo-ci-jenkins2＠inria.fr Dec. 27, 2018

Dec. 27, 2018

There is a new Pharo build available! The status of the build #2 was: FAILURE. The Pull Request #2122 was integrated: "Removed obsolete Fuel package" Pull request url: https://github.com/pharo-project/pharo/pull/2122 Issue Url: https://pharo.fogbugz.com/f/cases/22834 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #80: SUCCESS
by ci-pharo-ci-jenkins2＠inria.fr Dec. 27, 2018

Dec. 27, 2018

There is a new Pharo build available! The status of the build #80 was: SUCCESS. Could not extract further issue information from commit message: references to fogbugz moved to GitHub tracker Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo 7 changelog proposal
by Pavel Krivanek Dec. 26, 2018

Dec. 26, 2018

Hi, I'm trying to summarize the changelog for Pharo 7 (based on about 2500 merged PRs, not counting standalone commits to Iceberg and Calypso). If something more should be mentioned, please let me know. Revolutionary kernel changes - bootstrap - modular stateful traits - traits flattening in kernel packages - new sources file for every bootstrapped version, empty changes - new class builder - binary packages loading (Hermes) Infrastructure changes - switch to GitHub - Tonel code format - update building infrastructure to Jenkins 2 Code management - Calypso, the new system browser - new navigation model - faster UI - tabs toolbar instead of single source code panel - explicit commands instead of duplicated menu and shortcuts - extendable by plugins - suitable for the remote scenario - "dynamic protocols", support multiple tags per method - not required star convention for class extension - support multiple tags per class - visibility option for inherited methods - methods inherited from traits are not shown by default - variable view as the special mode for method group view. - better keyboard navigation - and many more Iceberg - a new friendly user interface - simplification of solving problems with repositories - workflow simplification - better GitHub, BitBucket, GitLab support - improved code merging and comparisons - new code serialization format (Tonel) - repositories metadata - documentation - better error handling, tags support - improved Iceberg-Metacello integration - credentials store Cleanups - remove Nautilus - remove UpdateStream - remove all Configurations - remove ShoreLine-Report - remove TxText - remove PluggableTabBarMorph - remove the old Compiler - remove Watery theme - remove Versionner - remove Komitter - remove LegacyWeakSubscription - continue on deprecation of FileStream - dead code cleanups - code organization cleanups - unify categorization of common methods - cleanups of object inspection protocol - start with Ring deprecation - better structure of packages - package comments Updates - Zinc - Epicea - FFI - Metacello - Fuel New - Calypso - integrate WebBrowser - integrate ReferenceFinder - Hermes - Refactoring 2 - Commander - ClassAnnotation Spec - ComposableModel renamed to ComposablePresenter - new calendar presenter - Spec-Demo - improve Spec linking to domain models Look & Feel - use the white theme by default - improve themes switching - main menu bar - new window management shortcuts - better support of fallback bitmap fonts - improved Inspector refreshing - Spotter is looking for opened windows - display scale factor - FastTable improvements VM interface - DoubleWord and DoubleByte arrays - add EncoderForSistaV1 - read-only literals support - improvements and fixes for 64-bit support - fixes for FullBlockClosure - support of the new bytecode set Reflectivity - breakpoints improvements - test coverage using metalinks - reflectivity and metalinks improvements Other - startup running in a fresh process - better pin messages - NewValueHolder and Model API unification - better working and image directories meaning separation - SortFunctions composable - better OSWindow support - convert rules to the Renraku architecture - class and method comments improvements - extensible Playground (pageActionOrder:) - optional password management for command line handlers - system dependencies tests - unify way to obtain package manifests

8 9

Downloading file with Zinc
by Stephane Ducasse Dec. 23, 2018

Dec. 23, 2018

Hi Sven I would like download files (pdf) with Zinc (not opening them in Pharo). I wonder how I can do it with zinc. Tx

4 5

stfx.eu down
by Sven Van Caekenberghe Dec. 23, 2018

Dec. 23, 2018

Hi, This evening I somehow broke my stfx.eu server while doing an ubuntu dist upgrade (an old AWS EC2 machine). This means several websites / web services hosted by that machine are down, most notably mc.stfx.eu (hosting several of my packages) and ws.stfx.eu (used for shared smalltalk workspaces). A couple of Zinc tests will also fail. For source code access, all my public repos exist both in an up to date form on GitHub (http://github.com/svenvc) as well in the original form in SmalltalkHub (http://smalltalkhub.com/#!/~SvenVanCaekenberghe) or SS3. The main problem there is that the distributed ConfigurationsOf and Catalog entries will still point to the original. This is not a problem with git's BaselineOf definitions. Although the machine will no longer boot, I managed to mount the original volume on another instance so I can still access the whole filesystem. This will make it possible to eventually recover most services. But this will take time as these things never happen when it is convenient. It will give me an opportunity to modernise the setup though, which is good. Sorry for the inconvenience. Sven

3 4

Re: [Pharo-dev] [Moose-dev] Re: glamorous toolkit: v0.4.0
by Ben Coman Dec. 21, 2018

Dec. 21, 2018

On Sat, 22 Dec 2018 at 06:03, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > I share your feeling of wonder and also concern Luke. > > In my case, I used (old) GT tools to prototype Grafoscopio and now that the PhD thesis is practically done and only dissertation is pending, I would like to prepare myself to migrate Grafoscopio to Pharo 7, including bug fixing, stability, improved functionality, Iceberg for code management (but supporting Fossil instead of Git). > > I think that there is a lot of possibilities in the new GT tools and I like some of them going into interactive documentation (a line I was trying to explore with Pharo using Grafoscopio). But anytime I tried to use it I stumble upon a stop: > > First time was something related with me having some kind of credential enabled in GitHub to simple use it. I lost a whole morning just enabling that and reporting it. Was this on Windows? What was the fix for worked for you? (sorry its easier to ask again than try to identify in the archives a previous mention) cheers -ben > It was related with some mozilla library for font redering that didn't work well at the end. > Today I tried with the prebuild Linux image and Pharo Launcher, but I got an error message about inability to determine proper VM and when I tried installing it from Pharo 7 I got something related with a MemoryFileWriteStream dependency to be resolved before proper installation. > > I understand that this is alpha software and demos look amazing, but just running them requires a lot of work that previous GT didn't require. > > This brings me this feeling that these jumps in Pharo put core of the user experience at risk (kind of) and you end wondering how much an old tech will be maintained once the jump to the new shinny stuff is done and which is the migration path. > > In my case, I would like to have something like a Zeroconf script that just takes care of the external libraries, VM and image, to have a real glipmse of the upcoming future, beside the Tweets (which look great BTW). Maybe it will happen in a year or two, once it is properly integrated with Pharo, Zeroconf and thought for "end users" of interactive documents, which don't want to enable GitHub stuff, deal with external rendering dependencies and so on. Now the experience of using GT is kind of hostile for that users. > > Anyway, keep the good work and sharing it. Hopefully at some point it will reach the beta status, where users like myself can use it smoothly and build on GT's promises and interesting features. > > Cheers, > > Offray > > On 21/12/18 10:59, Luke Gorrie wrote: > > On Thu, 20 Dec 2018 at 10:58, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. > > [...] >> >> Does this address the concern? > > > I am not sure yet :). > > Programming is not our main use case for GT. We are using GT as an object inspector (etc) for examining diagnostic data. We have a Smalltalk application that's similar to GDB and we are using GT as the front-end. > > In our world we use the Inspector and the Spotter but all of the Smalltalk programming views are hidden. GT is "molded" to be a diagnostic tool *instead of* a programming environment. Specifically, our main use case is inspecting/debugging the operation of a JIT compiler written in C. We have Smalltalk code to load binary coredumps from the JIT, decode them using DWARF debug information, and represent the application-level compiler data structures as Smalltalk objects. This way we can use GT to browse generated code, cross-reference profiler data, examine runtime compilation errors, etc. > > The "old" GT is awesome for this. I feel like this application is also very much in the spirit of the "moldable tools" thesis. Lots of diagnostic workflows ultimately boil down to drill-down inspecting and/or searching. > > I don't know where we stand with respect to the "new" GT though. I am talking about diagnostics, you are talking about programming. I am talking about zeros and ones, you are talking about feelings. I am maintaining a stable application, you are talking about rewrites. I am having a hard time whether I should be switching to the new GT in the immediate future, or waiting another year or two for it to mature, or planning to stick with the old GT. > > Hints would be appreciated :) > > I reiterate that I think you guys are doing fantastic work - some of the most interesting work in the programming universe to my mind. I hope that this discussion is useful for at least understanding the thought process of some users / potential users. > > Cheers! > -Luke > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

1 0

Re: [Pharo-dev] [Moose-dev] Re: glamorous toolkit: v0.4.0
by Tudor Girba Dec. 21, 2018

Dec. 21, 2018

Hi Offray, Thanks for describing your concerns. First, letâs address the technical part. Please go to gtoolkit.com and download the 64Bit distribution that includes the image and the VM. We will remove the standalone image option from the website until the VM situation gets clarified. Now, a clarification. The old GT was produced over a period of 4 years by an open-source team. The project had its own identity, and in 2014 the core of it was first integrated in Pharo. I say the core of it, because the visual part and other libraries are not in Pharo today. The full potential is found in Moose. In any case, during this process, GT got to be identified with Pharo and that was a good thing. The new GT is a product produced by feenk, a company. Much of the original team is still active in the new version, but now we commit to our product in a different way. The product is free and open-source, but itâs still a product with an identity and a goal. At present time, both the team, identity and goal are different than those of Pharo. Our goal is to offer a fundamentally new alternative to program (including comparing to what is possible now in Pharo). We are not looking for marginal improvements, and we are not aiming at backward compatibility. To build this alternative we invested in a whole new stack. That is not a tiny challenge and getting it right requires many iterations and feedback. We say we are in alpha not because of inconveniences of installation but because we are still very much developing the product. We announced the first alpha version in September and since then much has changed. At present time, we did manage to reach a situation where downloading the distribution should run on Mac, Linux and Windows. Even so, the current version is only for people that do want to try knowing that there will be hurdles. A word about the user experience. The current version runs inside the Pharo UI because we need to bootstrap. But, our goal is to build a complete IDE on the new stack. If you want to judge the user experience, it is only meaningful to do it within the GT windows, and not by comparing it with the rest of the existing Pharo UI. Does this clarify the situation? Cheers, Doru -- www.feenk.com "Every thing has its own flow." > On 21 Dec 2018, at 23:02, Offray Vladimir Luna CÃ¡rdenas <offray.luna(a)mutabit.com> wrote: > > Hi, > > I share your feeling of wonder and also concern Luke. > > In my case, I used (old) GT tools to prototype Grafoscopio and now that the PhD thesis is practically done and only dissertation is pending, I would like to prepare myself to migrate Grafoscopio to Pharo 7, including bug fixing, stability, improved functionality, Iceberg for code management (but supporting Fossil instead of Git). > > I think that there is a lot of possibilities in the new GT tools and I like some of them going into interactive documentation (a line I was trying to explore with Pharo using Grafoscopio). But anytime I tried to use it I stumble upon a stop: > > First time was something related with me having some kind of credential enabled in GitHub to simple use it. I lost a whole morning just enabling that and reporting it. It was related with some mozilla library for font redering that didn't work well at the end. > Today I tried with the prebuild Linux image and Pharo Launcher, but I got an error message about inability to determine proper VM and when I tried installing it from Pharo 7 I got something related with a MemoryFileWriteStream dependency to be resolved before proper installation. > I understand that this is alpha software and demos look amazing, but just running them requires a lot of work that previous GT didn't require. > This brings me this feeling that these jumps in Pharo put core of the user experience at risk (kind of) and you end wondering how much an old tech will be maintained once the jump to the new shinny stuff is done and which is the migration path. > > In my case, I would like to have something like a Zeroconf script that just takes care of the external libraries, VM and image, to have a real glipmse of the upcoming future, beside the Tweets (which look great BTW). Maybe it will happen in a year or two, once it is properly integrated with Pharo, Zeroconf and thought for "end users" of interactive documents, which don't want to enable GitHub stuff, deal with external rendering dependencies and so on. Now the experience of using GT is kind of hostile for that users. > > Anyway, keep the good work and sharing it. Hopefully at some point it will reach the beta status, where users like myself can use it smoothly and build on GT's promises and interesting features. > > Cheers, > > Offray >> On 21/12/18 10:59, Luke Gorrie wrote: >> On Thu, 20 Dec 2018 at 10:58, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. >> [...] >>> Does this address the concern? >> >> I am not sure yet :). >> >> Programming is not our main use case for GT. We are using GT as an object inspector (etc) for examining diagnostic data. We have a Smalltalk application that's similar to GDB and we are using GT as the front-end. >> >> In our world we use the Inspector and the Spotter but all of the Smalltalk programming views are hidden. GT is "molded" to be a diagnostic tool *instead of* a programming environment. Specifically, our main use case is inspecting/debugging the operation of a JIT compiler written in C. We have Smalltalk code to load binary coredumps from the JIT, decode them using DWARF debug information, and represent the application-level compiler data structures as Smalltalk objects. This way we can use GT to browse generated code, cross-reference profiler data, examine runtime compilation errors, etc. >> >> The "old" GT is awesome for this. I feel like this application is also very much in the spirit of the "moldable tools" thesis. Lots of diagnostic workflows ultimately boil down to drill-down inspecting and/or searching. >> >> I don't know where we stand with respect to the "new" GT though. I am talking about diagnostics, you are talking about programming. I am talking about zeros and ones, you are talking about feelings. I am maintaining a stable application, you are talking about rewrites. I am having a hard time whether I should be switching to the new GT in the immediate future, or waiting another year or two for it to mature, or planning to stick with the old GT. >> >> Hints would be appreciated :) >> >> I reiterate that I think you guys are doing fantastic work - some of the most interesting work in the programming universe to my mind. I hope that this discussion is useful for at least understanding the thought process of some users / potential users. >> >> Cheers! >> -Luke >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

1 0

How can I wrap a byteArray into a stream
by Stephane Ducasse Dec. 21, 2018

Dec. 21, 2018

Hi I'm fighting with super badly written code and my first reaction is a to be able to write tests and parametrize the code. I have some byteArray (contents of a CDB database) that I would like to manipulate using stream API. I'm looking for something like this ZnBinaryStream on: aByteArray; next; next; skip: 10; ... Stef

1 2

Re: [Pharo-dev] [Moose-dev] glamorous toolkit: v0.4.0
by Tudor Girba Dec. 21, 2018

Dec. 21, 2018

Hi, Thanks for detailing your thoughts. Indeed, I know about your application. Whatever you can do with the current GT you will be able to do with the new one. Except that for the new one you will be able to do extra things. Here are a few: - You can build and share documents that embed those inspector views. This can be useful for reporting or sharing diagnostics with your users. - Because the underlying rendering engine is much more powerful, you can express modern and interfaces that integrate with the rest of the environment smoothly. - You likely have to deal with log files that might get large. First, the new editor allows you to smoothly work with such files. But, you can go well beyond this. Imagine that you build a tooling that produces the same editor only the text is interactive, and you might even embed visual artifacts right in the text to bridge the gap between what you would see in a typical console. For example, this tweet shows the new Transcript used to debug an animation. For every animation frame, we output the text corresponding with the frame and we insert the graphical preview corresponding to that step. You look at GT from the point of view of an end-user. You likely like the fact that you could mold the environment to your context and that you could do this incrementally. It happens that the same principles and tools can be applied to the whole programming, and once you do that, you actually can fundamentally change the act of programming. In fact, the same thing applies to the old GT: we built the new GT using that version and we believe that this allowed us to work much faster than if we would have used more traditional tools. The new GT pushes the envelope significantly further. So, that is why we are excited about that perspective, but even if you do not spend much time programming in Pharo, you can still take advantage for the user point of view as described above :). Is this answer better? Cheers, Doru > On Dec 21, 2018, at 4:59 PM, Luke Gorrie <luke(a)snabb.co> wrote: > > On Thu, 20 Dec 2018 at 10:58, Tudor Girba <tudor(a)tudorgirba.com> wrote: > The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. > [...] > Does this address the concern? > > I am not sure yet :). > > Programming is not our main use case for GT. We are using GT as an object inspector (etc) for examining diagnostic data. We have a Smalltalk application that's similar to GDB and we are using GT as the front-end. > > In our world we use the Inspector and the Spotter but all of the Smalltalk programming views are hidden. GT is "molded" to be a diagnostic tool *instead of* a programming environment. Specifically, our main use case is inspecting/debugging the operation of a JIT compiler written in C. We have Smalltalk code to load binary coredumps from the JIT, decode them using DWARF debug information, and represent the application-level compiler data structures as Smalltalk objects. This way we can use GT to browse generated code, cross-reference profiler data, examine runtime compilation errors, etc. > > The "old" GT is awesome for this. I feel like this application is also very much in the spirit of the "moldable tools" thesis. Lots of diagnostic workflows ultimately boil down to drill-down inspecting and/or searching. > > I don't know where we stand with respect to the "new" GT though. I am talking about diagnostics, you are talking about programming. I am talking about zeros and ones, you are talking about feelings. I am maintaining a stable application, you are talking about rewrites. I am having a hard time whether I should be switching to the new GT in the immediate future, or waiting another year or two for it to mature, or planning to stick with the old GT. > > Hints would be appreciated :) > > I reiterate that I think you guys are doing fantastic work - some of the most interesting work in the programming universe to my mind. I hope that this discussion is useful for at least understanding the thought process of some users / potential users. > > Cheers! > -Luke > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Being happy is a matter of choice."

1 1

[Pharo 7.0] Build #79: 22828-MethodFinder-Enhancement
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #79 was: FAILURE. The Pull Request #2118 was integrated: "22828-MethodFinder-Enhancement" Pull request url: https://github.com/pharo-project/pharo/pull/2118 Issue Url: https://pharo.fogbugz.com/f/cases/22828 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #78: 22775-Reflectivity-package-is-dirty
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #78 was: SUCCESS. The Pull Request #2117 was integrated: "22775-Reflectivity-package-is-dirty" Pull request url: https://github.com/pharo-project/pharo/pull/2117 Issue Url: https://pharo.fogbugz.com/f/cases/22775 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #77: Changed references to FileStream standard IO streams to Stdio.
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #77 was: SUCCESS. The Pull Request #1966 was integrated: "Changed references to FileStream standard IO streams to Stdio." Pull request url: https://github.com/pharo-project/pharo/pull/1966 Issue Url: https://pharo.fogbugz.com/f/cases/22653 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #76: Fix for issue 22729
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #76 was: SUCCESS. The Pull Request #2045 was integrated: "Fix for issue 22729" Pull request url: https://github.com/pharo-project/pharo/pull/2045 Issue Url: https://pharo.fogbugz.com/f/cases/22729 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #75: 22658-Better-manage-encoding-of-environment-variables
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #75 was: FAILURE. The Pull Request #1980 was integrated: "22658-Better-manage-encoding-of-environment-variables" Pull request url: https://github.com/pharo-project/pharo/pull/1980 Issue Url: https://pharo.fogbugz.com/f/cases/22658 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #1: 22825-Introduce-opaque
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #1 was: FAILURE. The Pull Request #2113 was integrated: "22825-Introduce-opaque" Pull request url: https://github.com/pharo-project/pharo/pull/2113 Issue Url: https://pharo.fogbugz.com/f/cases/22825 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #74: 22825-Introduce-opaque
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #74 was: FAILURE. The Pull Request #2113 was integrated: "22825-Introduce-opaque" Pull request url: https://github.com/pharo-project/pharo/pull/2113 Issue Url: https://pharo.fogbugz.com/f/cases/22825 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #73: 22400-Delays-are-not-working-properly
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #73 was: FAILURE. The Pull Request #1873 was integrated: "22400-Delays-are-not-working-properly" Pull request url: https://github.com/pharo-project/pharo/pull/1873 Issue Url: https://pharo.fogbugz.com/f/cases/22400 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #72: 22785 Refactor FFICompilerPlugin
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #72 was: FAILURE. The Pull Request #2082 was integrated: "22785 Refactor FFICompilerPlugin" Pull request url: https://github.com/pharo-project/pharo/pull/2082 Issue Url: https://pharo.fogbugz.com/f/cases/22785 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #71: 22813 Integer should return isAbstract with true
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #71 was: SUCCESS. The Pull Request #2104 was integrated: "22813 Integer should return isAbstract with true" Pull request url: https://github.com/pharo-project/pharo/pull/2104 Issue Url: https://pharo.fogbugz.com/f/cases/22813 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #70: 22774-Add-comments-to-SUnit
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #70 was: SUCCESS. The Pull Request #2105 was integrated: "22774-Add-comments-to-SUnit" Pull request url: https://github.com/pharo-project/pharo/pull/2105 Issue Url: https://pharo.fogbugz.com/f/cases/22774 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #69: 22808 font infrastructure package should be fonts infrastructure
by ci-pharo-ci-jenkins2＠inria.fr Dec. 21, 2018

Dec. 21, 2018

There is a new Pharo build available! The status of the build #69 was: FAILURE. The Pull Request #2100 was integrated: "22808 font infrastructure package should be fonts infrastructure" Pull request url: https://github.com/pharo-project/pharo/pull/2100 Issue Url: https://pharo.fogbugz.com/f/cases/22808 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #68: 22805-FTTableMorph-has-too-big-minimal-height
by ci-pharo-ci-jenkins2＠inria.fr Dec. 20, 2018

Dec. 20, 2018

There is a new Pharo build available! The status of the build #68 was: SUCCESS. The Pull Request #2096 was integrated: "22805-FTTableMorph-has-too-big-minimal-height" Pull request url: https://github.com/pharo-project/pharo/pull/2096 Issue Url: https://pharo.fogbugz.com/f/cases/22805 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #67: 22821 Cleanup Exception class
by ci-pharo-ci-jenkins2＠inria.fr Dec. 20, 2018

Dec. 20, 2018

There is a new Pharo build available! The status of the build #67 was: SUCCESS. The Pull Request #2111 was integrated: "22821 Cleanup Exception class" Pull request url: https://github.com/pharo-project/pharo/pull/2111 Issue Url: https://pharo.fogbugz.com/f/cases/22821 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #66: 22819 Cleanup TestReviver
by ci-pharo-ci-jenkins2＠inria.fr Dec. 20, 2018

Dec. 20, 2018

There is a new Pharo build available! The status of the build #66 was: FAILURE. The Pull Request #2110 was integrated: "22819 Cleanup TestReviver" Pull request url: https://github.com/pharo-project/pharo/pull/2110 Issue Url: https://pharo.fogbugz.com/f/cases/22819 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Moose-dev] Re: glamorous toolkit: v0.4.0
by Tudor Girba Dec. 20, 2018

Dec. 20, 2018

Hi Luke, I am happy this looks exciting :). About the confusion part: The Glamorous Toolkit we are working on right now is a complete new world built on a complete new graphical stack that does is not based on the existing stack that ships with Pharo. It is not an evolution. It is a leap. The goal of the new GT is to propose a completely reshaped programming experience that enables moldable development. You will find the concepts from the old GT in the new world as well. For example, the Inspector is extensible in similar ways and the API is similar as well. But, in the new world, we are bringing the concept much further. For example, Documenter provides a whole new kind of a tool that can mold to unify multiple workflows (like data notebooks, code documentation, or tutorials) right in the IDE. Coder provides the infrastructure for manipulating code that can mold its shape as you type. Transcript allows you to embed various widgets to transform the otherwise dull experience of a console into a live one. Behind the scenes GT comes with several engines. The Examples engine enables example-driven development which also bridges the gap between testing and documentation effort, especially when combined with Documenter. Releaser is able to release deeply nested projects. Phlow offers an engine that shares similarities with Glamour. Completer provides moldable completion. Visualizer offers a couple of visualization engines such as Mondrian. All of these are possible because of the underlying graphical stack made of Sparta/Bloc/Brick. All in all, we believe that the new GT enables a new way of programming. Individual features can be attractive, but our goal is to reshape the development experience. Does this address the concern? Cheers, Doru > On Dec 19, 2018, at 2:09 PM, Luke Gorrie <luke(a)snabb.co> wrote: > > On Fri, 14 Dec 2018 at 05:13, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Please do let us know what you think .. and, of course, what you feel. > > I'm feeling excited and confused :). > > Excited because I love seeing all these new demos streaming out and I'm itching to put new capabilities to work. > > Confused about the roadmap. How does this "new" Glamorous Toolkit relate to the "old" one that I learned about last year from the Moldable Tools thesis? Is this a new version or a complete rewrite? Is it backwards compatible or completely reimagined? Is adopting the new version a seamless process or is porting required? Are frameworks like Glamour still there behind the scenes or were they replaced? etc. > > > <gt-documenter-magic-markup.gif><gt-0-4-0.png>_______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.feenk.com "Things happen when they happen, not when you talk about them happening."

1 0

[Pharo 7.0] Build #65: 22818 Cleanup Regex tests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 20, 2018

Dec. 20, 2018

There is a new Pharo build available! The status of the build #65 was: FAILURE. The Pull Request #2109 was integrated: "22818 Cleanup Regex tests" Pull request url: https://github.com/pharo-project/pharo/pull/2109 Issue Url: https://pharo.fogbugz.com/f/cases/22818 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #64: 22814-Broken-comments-on-Cursor
by ci-pharo-ci-jenkins2＠inria.fr Dec. 20, 2018

Dec. 20, 2018

There is a new Pharo build available! The status of the build #64 was: SUCCESS. The Pull Request #2106 was integrated: "22814-Broken-comments-on-Cursor" Pull request url: https://github.com/pharo-project/pharo/pull/2106 Issue Url: https://pharo.fogbugz.com/f/cases/22814 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #63: 22811 Fix comment in ExternalBrowser
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #63 was: SUCCESS. The Pull Request #2102 was integrated: "22811 Fix comment in ExternalBrowser" Pull request url: https://github.com/pharo-project/pharo/pull/2102 Issue Url: https://pharo.fogbugz.com/f/cases/22811 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #62: 22812 Clean the ImageCleaner
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #62 was: SUCCESS. The Pull Request #2103 was integrated: "22812 Clean the ImageCleaner" Pull request url: https://github.com/pharo-project/pharo/pull/2103 Issue Url: https://pharo.fogbugz.com/f/cases/22812 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #61: 22809 Cleanup MethodFinderTest and related sample classes
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #61 was: FAILURE. The Pull Request #2101 was integrated: "22809 Cleanup MethodFinderTest and related sample classes" Pull request url: https://github.com/pharo-project/pharo/pull/2101 Issue Url: https://pharo.fogbugz.com/f/cases/22809 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Catalog Entries
by Sven Van Caekenberghe Dec. 19, 2018

Dec. 19, 2018

Hi, So we have the Catalog with version specific repositories for ConfigurationOfXYZ packages/classes. I am assuming that we will be keeping this system for at least Pharo 7 and possibly 8. Can one define Catalog entries using BaselineOfXYZ ? Is that recommended ? Or should a mostly empty ConfigurationOfXYZ be used that internally refers to the BaselineOfXYZ ? Sven

7 26

[Pharo 7.0] Build #60: 22777 ManifestMonticello and ManifestRingMonticello should be tagged with "Manifest"
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #60 was: SUCCESS. The Pull Request #2076 was integrated: "22777 ManifestMonticello and ManifestRingMonticello should be tagged with "Manifest"" Pull request url: https://github.com/pharo-project/pharo/pull/2076 Issue Url: https://pharo.fogbugz.com/f/cases/22777 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #59: 22806 Small cleanups in EmbeddedFreeTypeFontInstallerTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 19, 2018

Dec. 19, 2018

There is a new Pharo build available! The status of the build #59 was: SUCCESS. The Pull Request #2099 was integrated: "22806 Small cleanups in EmbeddedFreeTypeFontInstallerTest" Pull request url: https://github.com/pharo-project/pharo/pull/2099 Issue Url: https://pharo.fogbugz.com/f/cases/22806 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Huge Critiques Area in Calypso in Pharo 7
by Denis Kudriashov Dec. 18, 2018

Dec. 18, 2018

Hi Petr. Setting would be nice. I did not know about it in Nautilus Ð²Ñ, 18 Ð´ÐµÐº. 2018 Ð³. Ð² 14:44, Petr Fischer via Pharo-dev < pharo-dev(a)lists.pharo.org>: > I have that feeling too - critiques pane is annoying + occupying too much > place - what about showing critiques inline only (in the line nubers and > breakpoint markers left pane)? > > This choice existed for the old Nautilus browser - but I can't find it for > Calypso. > > pf > > > I am seeing a huge (multiline, ~ 5 to 7 lines) high 'critiques' area at > the bottom of Calypso browsers in Pharo 7 (dl today), see screenshot: > > > > > > Why is that ? I can't resize it to be smaller. > > On a smaller screen this takes up way too much space. > > Can't we have a widget to remove/collapse that area ? Not a setting. > > > > Sven > > > >

1 0

Huge Critiques Area in Calypso in Pharo 7
by Sven Van Caekenberghe Dec. 18, 2018

Dec. 18, 2018

I am seeing a huge (multiline, ~ 5 to 7 lines) high 'critiques' area at the bottom of Calypso browsers in Pharo 7 (dl today), see screenshot: Why is that ? I can't resize it to be smaller. On a smaller screen this takes up way too much space. Can't we have a widget to remove/collapse that area ? Not a setting. Sven

3 5

[Pharo 7.0] Build #58: 22797 deprecated file does not exist should be moved to deprecated70 package
by ci-pharo-ci-jenkins2＠inria.fr Dec. 18, 2018

Dec. 18, 2018

There is a new Pharo build available! The status of the build #58 was: FAILURE. The Pull Request #2092 was integrated: "22797 deprecated file does not exist should be moved to deprecated70 package" Pull request url: https://github.com/pharo-project/pharo/pull/2092 Issue Url: https://pharo.fogbugz.com/f/cases/22797 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

possible QA rule - cascading to class
by Ben Coman Dec. 18, 2018

Dec. 18, 2018

In case someone close to managing the QA rules is interested... on discord it was suggested that this form of cascading might be a trap for newcomers. x := MyClass new; foo I've never seen similar in practice, so it might make a good QA rule. It currently raises "Sends unknown message to global" but I'd guess a more specific message that actually mentions "cascading" could be possible. cheers -ben

2 1

[Pharo 7.0] Build #57: 22780 Fix uncategorized classes in MonticelloGUI
by ci-pharo-ci-jenkins2＠inria.fr Dec. 18, 2018

Dec. 18, 2018

There is a new Pharo build available! The status of the build #57 was: FAILURE. The Pull Request #2078 was integrated: "22780 Fix uncategorized classes in MonticelloGUI" Pull request url: https://github.com/pharo-project/pharo/pull/2078 Issue Url: https://pharo.fogbugz.com/f/cases/22780 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #56: 22760 RBRefactoryClassChange should define #isAbstract with true
by ci-pharo-ci-jenkins2＠inria.fr Dec. 18, 2018

Dec. 18, 2018

There is a new Pharo build available! The status of the build #56 was: FAILURE. The Pull Request #2084 was integrated: "22760 RBRefactoryClassChange should define #isAbstract with true" Pull request url: https://github.com/pharo-project/pharo/pull/2084 Issue Url: https://pharo.fogbugz.com/f/cases/22760 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #55: 22801 Small cleanups in TRBProgramNodeVisitor
by ci-pharo-ci-jenkins2＠inria.fr Dec. 18, 2018

Dec. 18, 2018

There is a new Pharo build available! The status of the build #55 was: SUCCESS. The Pull Request #2093 was integrated: "22801 Small cleanups in TRBProgramNodeVisitor" Pull request url: https://github.com/pharo-project/pharo/pull/2093 Issue Url: https://pharo.fogbugz.com/f/cases/22801 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #54: 22793 Cleanup AndreasSystemProfilerTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 17, 2018

Dec. 17, 2018

There is a new Pharo build available! The status of the build #54 was: SUCCESS. The Pull Request #2088 was integrated: "22793 Cleanup AndreasSystemProfilerTest" Pull request url: https://github.com/pharo-project/pharo/pull/2088 Issue Url: https://pharo.fogbugz.com/f/cases/22793 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #53: 22796 Fix testResettingTheSelection
by ci-pharo-ci-jenkins2＠inria.fr Dec. 17, 2018

Dec. 17, 2018

There is a new Pharo build available! The status of the build #53 was: FAILURE. The Pull Request #2091 was integrated: "22796 Fix testResettingTheSelection" Pull request url: https://github.com/pharo-project/pharo/pull/2091 Issue Url: https://pharo.fogbugz.com/f/cases/22796 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #52: 22792 Cleanup MessageTallyTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 17, 2018

Dec. 17, 2018

There is a new Pharo build available! The status of the build #52 was: FAILURE. The Pull Request #2087 was integrated: "22792 Cleanup MessageTallyTest" Pull request url: https://github.com/pharo-project/pharo/pull/2087 Issue Url: https://pharo.fogbugz.com/f/cases/22792 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #51: 22791 Cleanup TextDiffBuilderTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 17, 2018

Dec. 17, 2018

There is a new Pharo build available! The status of the build #51 was: FAILURE. The Pull Request #2086 was integrated: "22791 Cleanup TextDiffBuilderTest" Pull request url: https://github.com/pharo-project/pharo/pull/2086 Issue Url: https://pharo.fogbugz.com/f/cases/22791 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #50: 22794 Cleanup testExtractAllKinds
by ci-pharo-ci-jenkins2＠inria.fr Dec. 17, 2018

Dec. 17, 2018

There is a new Pharo build available! The status of the build #50 was: FAILURE. The Pull Request #2089 was integrated: "22794 Cleanup testExtractAllKinds" Pull request url: https://github.com/pharo-project/pharo/pull/2089 Issue Url: https://pharo.fogbugz.com/f/cases/22794 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo image don't restart
by Trussardi Dario Romano Dec. 17, 2018

Dec. 17, 2018

Ciao, i have a Ubuntu system where i defined a Pharo 7.0 - 64bit image managed with PharoLauncher. I work with it for a month and all work fine. Now after a save the image the system begin unstabled. When the mouse go on the windows summary bar ( at the bottom of the Pharo window ) the image go down. The first time i can launch the same image from the PharoLauncher, but after a new image save ( the image go down ) i can't relaunch the image. When i do the launch the pharoLauch shell report: I have some important work in the image ( and i don't have a backup ) Some consideration? Thanks, Dario

4 18

[Pharo 7.0] Build #49: 22786 - Unused result in testExecutionOfWrongFFIMethodShouldRaiseAnError
by ci-pharo-ci-jenkins2＠inria.fr Dec. 16, 2018

Dec. 16, 2018

There is a new Pharo build available! The status of the build #49 was: FAILURE. The Pull Request #2081 was integrated: "22786 - Unused result in testExecutionOfWrongFFIMethodShouldRaiseAnError" Pull request url: https://github.com/pharo-project/pharo/pull/2081 Issue Url: https://pharo.fogbugz.com/f/cases/22786 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #48: 22782-Bag-comments-deserve-executable-comments
by ci-pharo-ci-jenkins2＠inria.fr Dec. 16, 2018

Dec. 16, 2018

There is a new Pharo build available! The status of the build #48 was: SUCCESS. The Pull Request #2080 was integrated: "22782-Bag-comments-deserve-executable-comments" Pull request url: https://github.com/pharo-project/pharo/pull/2080 Issue Url: https://pharo.fogbugz.com/f/cases/22782 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #47: 22778 Tag Monticello-OldDataStreamCompatibility in Manifest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 15, 2018

Dec. 15, 2018

There is a new Pharo build available! The status of the build #47 was: SUCCESS. The Pull Request #2077 was integrated: "22778 Tag Monticello-OldDataStreamCompatibility in Manifest" Pull request url: https://github.com/pharo-project/pharo/pull/2077 Issue Url: https://pharo.fogbugz.com/f/cases/22778 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo & Windows 10
by John Brant Dec. 15, 2018

Dec. 15, 2018

Is anyone using a recent Pharo with Windows 10? I'm using Pharo-7.0.0+rc1.build.44.sha.d3be1c018447fa5f7ba666cea7aff396f36d4309 (64 Bit) and am getting crashes whenever I try to commit anything using Iceberg. This seems to be a recent issue -- if I open an image from a few weeks ago, it works. Also, when I reopen the image, and the try to open the "Code Changes" it fails with: ------------------------ GrafPort(Object)>>error: GrafPort(BitBlt)>>copyBits GrafPort>>copyBits GrafPort>>image:at:sourceRect:rule: FormCanvas>>image:at:sourceRect:rule: FormCanvas(Canvas)>>drawImage:at:sourceRect: FormCanvas(Canvas)>>drawImage:at: HiRulerBuilder>>form HiRulerController>>buildRulerForm HiRulerController>>refreshRuler HiRulerController>>values: HiRulerController>>updateFromTree [ hiedraRulerController updateFromTree ] in EpLogNodeGraphPresenter>>initializeHiedraController in Block: [ hiedraRulerController updateFromTree ] BlockClosure>>cull: BlockClosure>>cull:cull: BlockClosure>>cull:cull:cull: BlockClosure>>cull:cull:cull:cull: [ :announcement :ann | aBlock cull: announcement newValue cull: announcement oldValue cull: announcement cull: ann ] in CollectionValueHolder(Model)>>whenChangedDo: in Block: [ :announcement :ann | ... BlockClosure>>cull:cull: [ action cull: anAnnouncement cull: announcer ] in AnnouncementSubscription>>deliver: in Block: [ action cull: anAnnouncement cull: announcer ] BlockClosure>>on:do: BlockClosure>>on:fork: AnnouncementSubscription>>deliver: [ "Ensure delivery to remaining announcements" subscription deliver: anAnnouncement ] in SubscriptionRegistry>>deliver:to:startingAt: in Block: [ "Ensure delivery to remaining announcements" sub...etc... BlockClosure>>ifCurtailed: SubscriptionRegistry>>deliver:to:startingAt: SubscriptionRegistry>>deliver:to: SubscriptionRegistry>>deliver: Announcer>>announce: CollectionValueHolder(NewValueHolder)>>valueChanged: ------------------------ This issue existed in the image I have from a few weeks ago. I've tried using the latest vm's from both files.pharo.org and bintray.com. John Brant

4 4

[Pharo 7.0] Build #46: 22756-Yourself-comment-is-wrong-
by ci-pharo-ci-jenkins2＠inria.fr Dec. 15, 2018

Dec. 15, 2018

There is a new Pharo build available! The status of the build #46 was: SUCCESS. The Pull Request #2079 was integrated: "22756-Yourself-comment-is-wrong-" Pull request url: https://github.com/pharo-project/pharo/pull/2079 Issue Url: https://pharo.fogbugz.com/f/cases/22756 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #45: 22723-Ugly-triangles-in-trees-with-medium-fontsUntitled
by ci-pharo-ci-jenkins2＠inria.fr Dec. 15, 2018

Dec. 15, 2018

There is a new Pharo build available! The status of the build #45 was: SUCCESS. The Pull Request #2038 was integrated: "22723-Ugly-triangles-in-trees-with-medium-fontsUntitled" Pull request url: https://github.com/pharo-project/pharo/pull/2038 Issue Url: https://pharo.fogbugz.com/f/cases/22723 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #44: 22772-chooseExistingFileReferenceextensionspathpreview-returning-wrong-FileReference
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #44 was: FAILURE. The Pull Request #2075 was integrated: "22772-chooseExistingFileReferenceextensionspathpreview-returning-wrong-FileReference" Pull request url: https://github.com/pharo-project/pharo/pull/2075 Issue Url: https://pharo.fogbugz.com/f/cases/22772 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #43: 22744 Package manifest ManifestFuel should be tagged and commented
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #43 was: FAILURE. The Pull Request #2052 was integrated: "22744 Package manifest ManifestFuel should be tagged and commented" Pull request url: https://github.com/pharo-project/pharo/pull/2052 Issue Url: https://pharo.fogbugz.com/f/cases/22744 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #42: 22754-Exception-while-opening-a-MCSubDirectoryRepository
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #42 was: SUCCESS. The Pull Request #2062 was integrated: "22754-Exception-while-opening-a-MCSubDirectoryRepository" Pull request url: https://github.com/pharo-project/pharo/pull/2062 Issue Url: https://pharo.fogbugz.com/f/cases/22754 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #41: 22764 Cleanup EmbeddedFreeType-Tests and EmbeddedFreeType
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #41 was: SUCCESS. The Pull Request #2068 was integrated: "22764 Cleanup EmbeddedFreeType-Tests and EmbeddedFreeType" Pull request url: https://github.com/pharo-project/pharo/pull/2068 Issue Url: https://pharo.fogbugz.com/f/cases/22764 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Pharo image don't restart
by dario.trussardi＠tiscali.it Dec. 14, 2018

Dec. 14, 2018

The PharoDebug.log. You can view it? Dario ................................................ Questo messaggio contiene i seguenti allegati: PharoDebug.log[15.24 MB] Dimensioni totali dei file inviati:15.24 MB Per scaricarli fai click sul link seguente: http://mail.tiscali.it/bigattachments/?c=dab58fa12765311a72d7a919d118e2b1 Allega Maxi Ã¨ il servizio di Tiscali WebMail che permette di allegare file, fino a 2GB, senza problemi di superamento dei limiti delle normali caselle e-mail. Ti ricordiamo che questo link sara' valido fino al giorno 17/12/2018 ................................................ Con OpenStar hai Giga, SMS e i minuti che vuoi da 4,99â¬ al mese, per sempre. Cambi gratis quando e come vuoi e in piÃ¹ hai 10â¬ di credito omaggio e 6 mesi di INFINTY! http://tisca.li/myopen

1 0

[Pharo 7.0] Build #40: 22769-KeyboardKey-classunixVirtualKeyTable-uses-KeyTable-instead-of-UnixKeyTable-
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #40 was: FAILURE. The Pull Request #2074 was integrated: "22769-KeyboardKey-classunixVirtualKeyTable-uses-KeyTable-instead-of-UnixKeyTable-" Pull request url: https://github.com/pharo-project/pharo/pull/2074 Issue Url: https://pharo.fogbugz.com/f/cases/22769 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #39: 22728-Add-enough-informations-to-Metacello-to-load-a-project-from-a-gitlab-deployed-with-non-default-ssh-port
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #39 was: SUCCESS. The Pull Request #2041 was integrated: "22728-Add-enough-informations-to-Metacello-to-load-a-project-from-a-gitlab-deployed-with-non-default-ssh-port" Pull request url: https://github.com/pharo-project/pharo/pull/2041 Issue Url: https://pharo.fogbugz.com/f/cases/22728 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #38: 22767 Categorize uncategorized classes in Tool-Finder
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #38 was: SUCCESS. The Pull Request #2070 was integrated: "22767 Categorize uncategorized classes in Tool-Finder" Pull request url: https://github.com/pharo-project/pharo/pull/2070 Issue Url: https://pharo.fogbugz.com/f/cases/22767 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #37: 22766-Transcript-window-is-leaking
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #37 was: SUCCESS. The Pull Request #2071 was integrated: "22766-Transcript-window-is-leaking" Pull request url: https://github.com/pharo-project/pharo/pull/2071 Issue Url: https://pharo.fogbugz.com/f/cases/22766 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

glamorous toolkit: v0.4.0
by Tudor Girba Dec. 14, 2018

Dec. 14, 2018

Hi, Things are moving fast in the glamorous land. We now reached v0.4.0: https://gtoolkit.com There are several significant advances in this version. The first thing to note is that v0.4.0 is a reproducible version that can be loaded with: Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit:v0.4.0/src'; load. https://github.com/feenkcom/gtoolkit/releases/tag/v0.4.0 The version was created with Releaser the new member of GT that is able to release deeply nested projects: https://twitter.com/girba/status/1073407418460225536 The rest of the environment has seen a few key changes as well: - Documenter received support for dynamic markup edit. This is an almost magic ability that makes the markup appear when the cursor nears the markup. With this we have reached a seamless experience that supports both viewing without markup and editing on demand. https://twitter.com/feenkcom/status/1067879286143676419 - Playground uses Coder and snippets are now collapsable. https://twitter.com/feenkcom/status/1070806168459767809 - The Inspector updates when the code changes. https://twitter.com/feenkcom/status/1072581283925159936 https://twitter.com/feenkcom/status/1072107898900238337 - The Meta view from Inspector was enhanced to show the super classes and method categories, each of these act list filters. On top of that, we can also filter methods by name. https://twitter.com/feenkcom/status/1072223641583149057 A more complete list of issues we addressed is found here: https://github.com/feenkcom/gtoolkit/milestone/2?closed=1 Please do let us know what you think .. and, of course, what you feel. Have fun, The feenk team -- www.feenk.com âHow do you feenk today?"

1 0

LibC system pops up a CMD.exe window in Windows 10 (Pharo 6.1)
by Christopher Fuhrman Dec. 13, 2018

Dec. 13, 2018

Hello, My Git data mining API in Pharo 6.1 uses "LibC uniqueInstance system: 'some commands'" which has an annoying side effect of popping up a window (which steals the GUI focus in Windows 10). Maybe it's the same on MacOS and Linux? As such, I can't use my Windows PC to do anything else when the mining process is running (it can take several minutes). I'm not able to use Pharo's OSProcess or OSSubprocess because they don't support Windows (yet?). I tried creating a separate Windows Desktop (feature of Windows 10), but the CMD.EXE window manages to pop up there, too - almost seems like a windows bug. Does anyone know of a way to have the LibC window not pop up? Cheers, Christopher

5 9

Application entrypoints
by Ben Coman Dec. 13, 2018

Dec. 13, 2018

A question was asked on discord... "I know how to start the lights out example, and feed my objects test data with the testing framework, but how does one start something like ChineseCheckers? How does one find the entry point? Is there a convention on naming a starting place?" I remember having similar thoughts when starting in Pharo. One convention I have seen is that amongst all the classes presumably prefixed "CC" one class would stand out being named for the application without the prefix. e.g. class "ChineseCheckers". That is only a narrow chance for a namespace conflict, the the risk still remains. I suggested another path would have a package tag "Application" (i.e. "ChineseCheckers-Application") that contains a single class which has an #open method on the class-side. The tag "Application" sorts high up on the package-tags and is self-descriptive. But I've not seen that used before, so while I think its a good idea, its not really a convention. Conventions are only useful if they are broadly understood. So I'm wondering what other things people do to draw attention to their application entry points. cheers -ben

4 3

Problem loading a branch of my pharo fork in an image
by Thomas Dupriez Dec. 13, 2018

Dec. 13, 2018

Hello, I loaded a branch of my pharo fork in an image using iceberg, but the method I was interested in did not change for some reason (my branch's latest commit changes this method, but these changes were not visible in the image I loaded my branch in). Does someone has an idea of what could have happened? Did I do something wrong? Here's what I did step-by-step if that helps: - fresh pharo 7 image - open iceberg - repair repository "pharo" - Clicked "Clone again this repository" - Chose "Clone remote repository", and put the url of my pharo fork: "https://github.com/dupriezt/pharo" - ok - wait for loading bar to complete - pharo repo is marked as "Fetch required. Unknown 67dc1e8" - repair repository "pharo" - chose "Discard local changes and checkout an existing branch" - chose the branch "BreakpointBrowser" from the "origin" remote - Clicked "checkout" on the checkout preview window - wait for loading bar to complete - browse the method WorldState class>>debugOn: - It is different from the last commit I made to this branch (https://github.com/dupriezt/pharo/commit/ead94e32f138eb435a95cd889f77ca39d4…) Thomas Dupriez

1 1

â¹Programmingâº 2019 Combined Call for Workshop Submissions
by Fabio Niephaus Dec. 13, 2018

Dec. 13, 2018

=========================================================================== â¹Programmingâº 2019 Combined Call for Workshop Submissions =========================================================================== To build a community and to foster an environment where participants can exchange ideas and experiences related to practical software development, â¹Programmingâº will host a number of workshops, during the days before the main conference. The workshops will provide a collaborative forum to exchange recent and/or preliminary results, to conduct intensive discussions on a particular topic, or to coordinate efforts between representatives of a technical community. They are intended as a forum for lively discussion of innovative ideas, recent progress, or practical experience on programming and applied software development in general for specific aspects, specific problems, or domain-specific needs. We also encourage practical, hands-on workshops in which participants actually experience one or several aspects of practical software development. The following workshops are co-located with â¹Programmingâº 2019. MoreVMsâ19: Workshop on Modern Language Runtimes, Ecosystems, and VMs --------------------------------------------------------------------------- MoreVMsâ19 aims to bring together industrial and academic programmers to discuss the design, implementation, and usage of modern languages and runtimes. Possible topics include reuse of language runtimes, modular implementation, language design, and compilation strategies. Call: https://2019.programming-conference.org/track/MoreVMs-2019 Extended Abstract Deadline: 11 Jan 2019 PX/19 5th Edition of the Programming Experience Workshop --------------------------------------------------------------------------- The Programming Experience (PX) Workshop is about what happens in that room when programmers sit down in front of computers and produce code, especially in an exploratory way. We are interested in this experience of programming and how to improve and evolve it. Call: https://2019.programming-conference.org/track/px-2019-papers Submission Deadline: 27 Jan 2019 VPT 2019: Seventh International Workshop on Program Transformation and Verification --------------------------------------------------------------------------- The aim of the workshop is to bring together researchers working in the fields of Program Verification and Program Transformation. There is a great potential for beneficial interactions between these two area. The workshop will provide a forum where researchers from these fields may interact and foster new developments. The workshop solicits research, position, application, and system description papers with a special emphasis on case studies, demonstrating viability of the interactions between the research fields of program transformation and program verification in a broad sense. Call: http://refal.botik.ru/vpt/vpt2019/ Submission Deadline: 8 Jan 2019 LANGETIâ19: Languages and Tools for Next Generation Testing --------------------------------------------------------------------------- The LANGETI workshop invites for submission of research papers and tool demonstrations developing new languages and tools that explore novel techniques to test next generation applications. We specially encourage new ideas on testing and its application domain that will spark discussion during the workshop. Call: https://2019.programming-conference.org/track/langeti-2019-papers Submission Deadline: 11 Jan 2019 PASSâ19: Workshop on Programming Across the System Stack (PASS) â19 --------------------------------------------------------------------------- PASSâ19 seeks contributions at the interaction of programming languages and computer systems, such as programming abstractions for emerging platforms, runtime performance and energy optimization, software tool support for systems, systems-level reasoning and verification, language-based security, and systems programming and debugging. Call: https://2019.programming-conference.org/home/PASS-2019 Submission Deadline: 15 Jan 2019 ICW 2019: Interconnecting Code Workshop --------------------------------------------------------------------------- Modern computer systems are often loosely coupled compositions of heterogeneous components. An important part of modern programming is the art, science, and engineering of interconnecting disparate code components to offer larger services in a reliable and scalable manner. The goal of this workshop is to facilitate an ongoing discussion, and advance the state of the art of interconnecting code. Call: https://2019.programming-conference.org/track/icw-2019-papers Initial Abstract Deadline: 11 Jan 2019 Salon des RefusÃ©s 2019 --------------------------------------------------------------------------- Salon des RefusÃ©s was an 1863 exhibition of artworks rejected from the official Paris Salon. We bring the same to programming research, creating a space for interesting ideas that are difficult to reduce to a proof or a naive measurement. Call: https://shift-society.org/salon/call-for-papers Submission Deadline: 7 Jan 2019 MiniPLoP 2019 --------------------------------------------------------------------------- Patterns are a systematic way to capture the experience of experts about good designs or best practices and document these nuggets of wisdom in an accessible way for peers. You can submit papers with 2-3 patterns for a discussion in a Writerâs Workshop session. Call: https://2019.programming-conference.org/track/PLOP-2019-papers Submission Deadline: 31 Jan 2019 ProWebâ19: 3rd International Workshop on Programming Technology for the Future Web --------------------------------------------------------------------------- ProWebâ19 is a forum for researchers and practitioners to share and discuss advances in programming technology (i.e., frameworks, libraries, programming languages, program analyses and development tools) for implementing web applications and for maintaining their quality over time, as well as experience reports about the use of state-of-the-art technology for the web. Call: https://2019.programming-conference.org/track/proweb-2019-papers Submission Deadline: 15 Jan 2019

1 0

[Pharo 7.0] Build #36: 22762 Cleanup TextEditorTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 13, 2018

Dec. 13, 2018

There is a new Pharo build available! The status of the build #36 was: FAILURE. The Pull Request #2066 was integrated: "22762 Cleanup TextEditorTest" Pull request url: https://github.com/pharo-project/pharo/pull/2066 Issue Url: https://pharo.fogbugz.com/f/cases/22762 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #35: 22763 Tag classes in Text-Diff package
by ci-pharo-ci-jenkins2＠inria.fr Dec. 13, 2018

Dec. 13, 2018

There is a new Pharo build available! The status of the build #35 was: SUCCESS. The Pull Request #2067 was integrated: "22763 Tag classes in Text-Diff package" Pull request url: https://github.com/pharo-project/pharo/pull/2067 Issue Url: https://pharo.fogbugz.com/f/cases/22763 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

periodic auto actions on bug tracker
by Ben Coman Dec. 13, 2018

Dec. 13, 2018

I support the auto-closing of old tickets to avoid bug bankruptcy. Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance. It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you? Try socializing it on the pharo-dev mail list. Issues going twelve months without interaction will be auto-closed". Then its not a bad surprise to new users when their ticket is auto-closed. cheers -ben

4 4