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

Refactoring File Package

by Guillermo Polito

Have you ever browsed the implementation of FileStream and checked subclasses and friends? Well, I made a cleaner implementation at the side with - a simple File object that is a sequential File as we all know - a binary File stream on top of it that is composable with Zn encoders and other decorators - a new interface to access Stdio streams Stdio stdin. Stdio stdout. ... All that with tests and comments. https://pharo.fogbugz.com/f/cases/15486/Refactor-File-Package Now, the system still has tons of references to the following classes FileStream -> 127 StandardFileStream -> 24 MultiByteFileStream -> 9 Most of them should be easily replaceable. Others may require wrapping the binary file stream provided by a file with a Zn encoder or similar. So, if you have some minutes in your week and can replace 3, 4, 5 of them, we will be a little step closer to simplify file handling and dependencies :) Guille

June 5, 2015

Re: [Pharo-dev] Roassal Camp Smalltalk

by Yuriy Tymchuk

But are there numbered version to refer to? Uko > On 05 Jun 2015, at 16:34, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > On Fri, Jun 5, 2015 at 3:29 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>> wrote: > Iâm interested in participating. Personally Iâd like to talk more about design decisions behind roassal ecosystem, release strategy and so on. Usually when I work with Roassal I have this issue that things are breaking because of rapid changes, or because of the differences between different parts of roassal. Maybe someone is also concerned about this, so we can discuss and maybe improve somethingâ¦ > > Yes I am also interested in this, right now I am actually using quite old version (month+) because I didn't have time to keep up. :) (Arguably 90% of my problems were from infamous composite shapes. :)) > > Peter > > Uko > > > On 04 Jun 2015, at 19:55, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > > > > Dear Colleagues and Friends, > > > > We are happy to announce we will organize a CampSmalltalk about the Roassal visualization engine, on _Sunday 12 July_. > > > > As far as we have seen, the interests are multiple. Here is a list of topics we will happy to work on: > > - Port of Roassal on VisualWorks > > - Using Roassal on Gemstone > > - HTML/JavaScript export > > - Improving Grapher, our charting library > > > > If you wish to participate, get in touch with us. Since we will probably have a sponsoring of the event, it would be nice to know how many will attend to ease the logistic and the pizza ordering :-) > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > >

June 5, 2015

Re: [Pharo-dev] Roassal Camp Smalltalk

by Peter UhnÃ¡k

On Fri, Jun 5, 2015 at 3:29 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Iâm interested in participating. Personally Iâd like to talk more about > design decisions behind roassal ecosystem, release strategy and so on. > Usually when I work with Roassal I have this issue that things are breaking > because of rapid changes, or because of the differences between different > parts of roassal. Maybe someone is also concerned about this, so we can > discuss and maybe improve somethingâ¦ > Yes I am also interested in this, right now I am actually using quite old version (month+) because I didn't have time to keep up. :) (Arguably 90% of my problems were from infamous composite shapes. :)) Peter > > Uko > > > On 04 Jun 2015, at 19:55, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > > Dear Colleagues and Friends, > > > > We are happy to announce we will organize a CampSmalltalk about the > Roassal visualization engine, on _Sunday 12 July_. > > > > As far as we have seen, the interests are multiple. Here is a list of > topics we will happy to work on: > > - Port of Roassal on VisualWorks > > - Using Roassal on Gemstone > > - HTML/JavaScript export > > - Improving Grapher, our charting library > > > > If you wish to participate, get in touch with us. Since we will probably > have a sponsoring of the event, it would be nice to know how many will > attend to ease the logistic and the pizza ordering :-) > > > > Cheers, > > Alexandre > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > >

June 5, 2015

Re: [Pharo-dev] [Pharo-users] Pharo 4 Image Freeze

by Nicolai Hess

2015-06-05 1:51 GMT+02:00 Martin McClure <martin(a)hand2mouse.com>: > On 06/04/2015 03:35 PM, Martin McClure wrote: > > On 06/04/2015 12:38 PM, stepharo wrote: > >> I passed the info to martin mcClure. > >> May be he will have a look at the issue. > > > > Well, I can reproduce the problem, in Windows. In Linux, my usual > > platform, the image does not hang. This suggests that the problem might > > be in the Windows VM. Is there a way to get trace output from the VM so > > I can see the sequence leading up to the hang, or a way to get a > > Smalltalk stack trace from a C debugger? > > Well, the "trace" option to the VM sounded promising, but all that > yields is an access violation while the image is loading. > > Regards, > > -Martin > > This happens on linux too, but not always. And the image does not freeze, but it looks like an endless loop of dnu: excerpt from the debug log: Message>>sentTo: Cooler(Object)>>doesNotUnderstand: #except Message>>sentTo: Cooler(Object)>>doesNotUnderstand: #except Message>>sentTo: Cooler(Object)>>doesNotUnderstand: #except Message>>sentTo: Cooler(Object)>>doesNotUnderstand: #except Message>>sentTo: Cooler(Object)>>doesNotUnderstand: #except Message>>sentTo: Cooler(Object)>>doesNotUnderstand: #except Message>>sentTo: Cooler(Object)>>doesNotUnderstand: #except Message>>sentTo: Cooler(Object)>>doesNotUnderstand: #except Message>>sentTo:

June 5, 2015

Re: [Pharo-dev] [Pharo-users] Pharo 4 Image Freeze

by Craig Latta

Hi Martin-- > ...the problem might be in the Windows VM. Is there a way to get > trace output from the VM so I can see the sequence leading up to the > hang, or a way to get a Smalltalk stack trace from a C debugger? You can evaluate, for example, printCallStack() from the Microsoft Visual C++ debugger console. Or make a snapshot at that point with primitiveSnapshot(), and poke around with the virtual machine simulator on your preferred host platform. -C -- Craig Latta netjam.org +31 6 2757 7177 (SMS ok) + 1 415 287 3547 (no SMS)

June 5, 2015

Re: [Pharo-dev] Roassal Camp Smalltalk

by Yuriy Tymchuk

Iâm interested in participating. Personally Iâd like to talk more about design decisions behind roassal ecosystem, release strategy and so on. Usually when I work with Roassal I have this issue that things are breaking because of rapid changes, or because of the differences between different parts of roassal. Maybe someone is also concerned about this, so we can discuss and maybe improve somethingâ¦ Uko > On 04 Jun 2015, at 19:55, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Dear Colleagues and Friends, > > We are happy to announce we will organize a CampSmalltalk about the Roassal visualization engine, on _Sunday 12 July_. > > As far as we have seen, the interests are multiple. Here is a list of topics we will happy to work on: > - Port of Roassal on VisualWorks > - Using Roassal on Gemstone > - HTML/JavaScript export > - Improving Grapher, our charting library > > If you wish to participate, get in touch with us. Since we will probably have a sponsoring of the event, it would be nice to know how many will attend to ease the logistic and the pizza ordering :-) > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

June 5, 2015

Re: [Pharo-dev] I need reviewer of https://pharo.fogbugz.com/default.asp?15646

by Ben Coman

You guys are moving so fast. I went to review it but it is already integrated :P Anyway I tried it and it worked well, load Stef's 15646 slice no problem. Well done Nicolai. cheers -ben On Wed, Jun 3, 2015 at 5:41 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-06-03 8:22 GMT+02:00 Marcus Denker <marcus.denker(a)inria.fr>: >> >> Indeedâ¦ this has to do something with caching: when looking a .mcz the >> system just takes the one it finds, which might be >> one with the same name but different. > > > here is a minimal change to the way it uses the cache, or omitting the cache > after the correct version > wasn't find in the cache. > > What do you think, may this work? > > nicolai > > > >> >> >> Maybe we could for real put (part of) the UID in the filename? >> >> In a disconnected system the case that the filename is the same for >> different files will always happen if the name is contructed >> as it is now. >> >> Marcus >> >> > On 02 Jun 2015, at 22:37, stepharo <stepharo(a)free.fr> wrote: >> > >> > I hate so much this bug.... >> > >> > >> > Le 1/6/15 15:04, Ben Coman a Ã©crit : >> >> Stef, I can now see all the dependent packages for the new slice, but >> >> I still have a strange error. However I'm not sure if its a bug or >> >> something unique at my end. >> >> >> >> Can someone try merging >> >> >> >> SLICE-Issue-15646-Cleaning-method-category-api-should-be-protocol-part-1-StephaneDucasse.1 >> >> >> >> What I see at top of stack is two calls to MCVersionMerger>>addVersion: >> >> >> >> MCVersionMerger>>addVersion: aVersion >> >> records add: (MCMergeRecord version: aVersion). >> >> aVersion dependencies >> >> do: [:ea | | dep satisfied | >> >> dep := ea resolve. >> >> satisfied := (records anySatisfy: [:r | r version = >> >> dep]). >> >> satisfied ifFalse: [self addVersion: dep]] "<<< race? >> >> " >> >> displayingProgress: [ :ea| 'Searching dependency: ', ea >> >> package name] >> >> "15646Note: variable /satisfied/ added for reporting/debugging" >> >> >> >> One level down from where the error occurs the debugger shows... >> >> >> >> /aVersion/ --> a >> >> >> >> MCVersion(SLICE-Issue-15646-Cleaning-method-category-api-should-be-protocol-part-1-StephaneDucasse.1) >> >> >> >> /ea/ --> a MCVersionInfo(DebuggerActions-StephaneDucasse.75) >> >> >> >> /dep/ --> nil >> >> >> >> /satisfied/ --> false >> >> >> >> and the following which contradicts the value in /satisfied/ >> >> >> >> (records anySatisfy: [:r | r version = dep]) --> true. >> >> >> >> so there seems to be a race such that the ifFalse block is improperly >> >> executed, such that the recursive call on top of stack has... >> >> >> >> /aVersion/-->nil >> >> >> >> hence MNU receiver of "dependencies" is nil. >> >> >> >> cheers -ben >> >> >> >> >> >> On Mon, Jun 1, 2015 at 10:36 AM, Ben Coman <btc(a)openinworld.com> wrote: >> >>> I tried, but it seems some packages are missing from the inbox. >> >>> cheers -ben >> >>> >> >>> On Sun, May 31, 2015 at 2:19 PM, stepharo <stepharo(a)free.fr> wrote: >> >>>> Hi >> >>>> >> >>>> I continued to clean that classes have categories and method >> >>>> protocols >> >>>> because it was not finished. >> >>>> This entry is just adding protocol in the classes that were missing >> >>>> it, >> >>>> adding comments, and fixing some local senders >> >>>> It does not remove the category API but puts it in a >> >>>> accessing-backward >> >>>> protocol and in a second step I will fix all the senders I can (ie >> >>>> not >> >>>> Metacello for example). >> >>>> Category is really overloaded and we get lost when trying to >> >>>> understand >> >>>> code. >> >>>> I want to rename RBRule 'category' into 'kind' for this reason. >> >>>> >> >>>> Stef >> >>>> >> >> >> > >> > >> >> >

June 5, 2015

[pharo-project/pharo-core]

by GitHub

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

June 5, 2015

[pharo-project/pharo-core] 3644df: 50091

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 3644dfe1d264321165012d6ac63c5f73d5617e83 https://github.com/pharo-project/pharo-core/commit/3644dfe1d264321165012d6a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-05 (Fri, 05 Jun 2015) Changed paths: M FreeType.package/FT2Handle.class/class/class initialization/initialize.st R FreeType.package/FT2Handle.class/class/system startup/shutDown_.st M FreeType.package/FT2Handle.class/class/system startup/startUp_.st M Monticello.package/MCFileBasedRepository.class/instance/accessing/versionFromFileNamed_.st A Monticello.package/MCFileBasedRepository.class/instance/accessing/versionFromRepositoryFromFileNamed_.st M Monticello.package/MCFileBasedRepository.class/instance/interface/versionWithInfo_ifAbsent_.st A Monticello.package/MCFileBasedRepository.class/instance/private/loadNotCachedVersionFromFileNamed_.st A Monticello.package/MCFileBasedRepository.class/instance/private/updateCachedVersionFromFileName_with_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50090.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50091.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50090.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50091.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/browseImplementorsShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/browseReferencesShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/browseSendersShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/browseShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/browseVersionsShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/methodNamesContainingItShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/methodStringContainingItShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code search/querySymbolShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/argAdvanceShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/debugItShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/displayIfFalseShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/displayIfTrueShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/doItShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/fileItInShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/inspectItShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/pasteInitialsShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/printItShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - code/removeShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/acceptShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/cancelShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/compareToClipboardShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/copySelectionShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/cutShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/duplicateFromSelectionShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/exchangeSelectionShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/formatCodeShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/indentShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/makeCapitalizedShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/makeLowercaseShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/makeUppercaseShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/outdentShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/pasteShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/redoShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/selectAllShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/selectUndoShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/swapCharsShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/toggleCommentOnSelectionOrLine.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor edit/undoShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/backwardWordShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/cursorEndShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/cursorHomeShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/findAgainShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/findShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/forwardWordShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/lineEndShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/lineStartShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/searchShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor navigation/setSearchStringShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/changeStyleShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/decreaseKerningShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/increaseKerningShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/normalEmphasisShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/openFontAlignmentMenuShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/openFontColorMenuShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/openFontMenuShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/strokethroughShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/toggleBoldEmphasisShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/toggleItalicEmphasisShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - editor style/underlineShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps - window/closeWindowShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/acceptShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseImplementorsShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseReferencesShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseSendersShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseVersionsShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/cancelShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/closeWindowShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/copySelectionShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/cursorEndShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/cursorHomeShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/cutShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/doItShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/findAgainShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/findShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/formatCodeShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/inspectItShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/pasteShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/printItShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/redoShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/removeShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/selectAllShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/setSearchStringShortcut.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/toggleCommentOnSelectionOrLine.st R Tool-Base.package/PharoShortcuts.class/instance/keymaps/undoShortcut.st Log Message: ----------- 50091 15700 rollback latest font changes, until we have a real solution https://pharo.fogbugz.com/f/cases/15700 15686 add missing editor shortcuts to class PharoShortcuts https://pharo.fogbugz.com/f/cases/15686 15698 do not load package from cache if version info differs https://pharo.fogbugz.com/f/cases/15698 http://files.pharo.org/image/50/50091.zip

June 5, 2015

Re: [Pharo-dev] how can we use Spotter to find reference to a class without scrolling down?

by Stephan Eggermont

On 02/06/15 22:08, stepharo wrote: > I often know that I want to look not for the class, its package or > methods.... > but that I want to get the references to a class. > > Is there a syntax that I can use to instruct spotter about my needs? When in spotter, I might want cmd-m to scope down to implementors, cmd-n senders, cmd-b browse the currently selected. And perhaps cmd-r references? Stephan

June 5, 2015