September 2013 - Pharo-dev - lists.pharo.org

Putting load on smalltalkhub

by Stephan Eggermont

Around 12.00 we managed to load and analyze upto 100 mczs/minute from Smalltalkhub. We hoped that we would not be able to overload Smalltalkhub from a home ADSL connection, using a single (non multi-threaded) Moose image. However, this seems to coincide with some failing jenkins builds. We apologize for any inconveniences we might have caused. What is the best way to get a copy? Or is our analysis wrong? Diego & Stephan

Sept. 18, 2013

Re: [Pharo-dev] [Pharo-users] Please help us by buying the book

by Volkert Barr

On 16.09.2013, at 16:24, Damien Cassou <damien.cassou(a)gmail.com> wrote: > Hi, > > please support our work on Pharo by buying the new Deep into Pharo book > > http://rmod.lille.inria.fr/deepIntoPharo/ > > Your money go to the Pharo Association, so it's worth it. I ordered a copy. Thanks for all the hard work .... Pharo is really fun ... BW, Volkert

Sept. 18, 2013

Lets Talk about Pharo Help tool

by Torsten Bergmann

>The help tool uses a treeMorph to display all topics in a tree like fashing, >and since each submorph in the tree is tied to a HelpTopic I could fetch the >hierarchical structure of HelpTopic from there, but the question is , is >this a good idea ? The navigation is UI related anyway, so there is nothing that would speak against this. I left out the "parent" or "owner" explicitly in my design, why should the water drop know the sea ;) It is IMHO more flexible and makes it easier (as you have seen with the wiki pragma). Thx T.

Sept. 18, 2013

Re: [Pharo-dev] Lets Talk about Pharo Help tool

by Igor Stasenko

I support you in your effort. I wrote some help pages for NB help (in NativeBoost-Help package), and using own subclasses of HelpTopic, which allow me to render the markdown.. (the problem is that markdown parser is now broken, and i needs to be fixed).. another thing is that it depends on petit-parser, but also , somehow on xml stuff.. it would be cool being able to write help using markdown syntax, without too much dependencies, so we can (hopefully) integrate it in base image. Also, what i don't like in current implementation is that it quite static: - a set of subtopics and topic contents are accessed only once from UI, and to see changes i had to close and reopen help window each time, which doesn't makes things faster. I tried to circumvent that in my subclasses, and had some little success. On 18 September 2013 12:23, kilon <thekilon(a)yahoo.co.uk> wrote: > Ok I started coding the project , I call it "Prometheas" here is the repo > > http://www.smalltalkhub.com/#!/~kilon/Prometheas > <http://www.smalltalkhub.com/#!/~kilon/Prometheas> > > I managed to add new buttons with icons, back, forth , right and left. Also > the title of the help tool now changes to the helpTopic selected. > > I want to use the up button to move to parent help topic , left and right > to > move previous and next page/topic. Probably i wont need down but I added it > just in case. I will tie all those buttons to shortcut keys so that you can > now navigate help using nothing but shortcuts. > > The problem I have is that the way Help tool is made it gives me the very > top topic , and the current topic. But I would also like to have a parent > for each topic. So when HelpTopic subtopic: is sent , it does not just add > HelpTopics to the HelpTopic but each subtopic is assigne the HelpTopic as > parent. > > This is crucial feature so that I can make those new buttons work. > > The tricky part here is that there is also the wiki style pragma that > generate topics. > > The help tool uses a treeMorph to display all topics in a tree like > fashing, > and since each submorph in the tree is tied to a HelpTopic I could fetch > the > hierarchical structure of HelpTopic from there, but the question is , is > this a good idea ? > > Or should hack the HelpTopic class to allow it to have a owner instance > variable ? > > I dont want to create messy code. I was thinking even creating my own > helpTopic classes etc, but I want old help to work with Prometheas too. > > I welcome any advice :) > > > > -- > View this message in context: > http://forum.world.st/Lets-Talk-about-Pharo-Help-tool-tp4707462p4708922.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- Best regards, Igor Stasenko.

Sept. 18, 2013

if Pharo is key for you

by Torsten Bergmann

kilon wrote: >How does "extending Pharo help tool " sounds ? :) Sounds good, but: I looked at your http://smalltalkhub.com/#!/~kilon/Prometheas today and unfortunately you follow the "same old way" of building UI's as I did in my original help browser implementation. It's up to you (since it is your project) but I would rather see a completely new help browser implementation based on Spec. Let me tell you why: I also wrote the Config browser for Pharo, initially "old style" with an #initWindow and then later converted it to be based on Spec with a #defaultSpec. It was much easier (even when there was no UI builder available at this time). It is now possible to combine it with the other tools AND use it in the new shiny UI builder. If you want to check load the latest version of the new UI painter: Gofer new smalltalkhubUser: 'ErwanDouaille' project: 'UIPainter'; configurationOf: 'UIPainter'; load. ((Smalltalk at: #ConfigurationOfUIPainter) project version: 'baseline-0.1') load go to "Tools" -> "UIPainter" and drag the MetacelloConfigurationBrowser or the MetacelloConfigurationBrowserPane from the "Model" node onto the canvas. So if a future help tool will be based on Spec as well it could easily be integrated into any future Pharo tool. So if you have cycles to spend on the help system please go for a Spec version, but as I said it is up to you. Thanks! Bye T.

Sept. 18, 2013

Re: [Pharo-dev] Lets Talk about Pharo Help tool

by kilon

Ok I started coding the project , I call it "Prometheas" here is the repo http://www.smalltalkhub.com/#!/~kilon/Prometheas <http://www.smalltalkhub.com/#!/~kilon/Prometheas> I managed to add new buttons with icons, back, forth , right and left. Also the title of the help tool now changes to the helpTopic selected. I want to use the up button to move to parent help topic , left and right to move previous and next page/topic. Probably i wont need down but I added it just in case. I will tie all those buttons to shortcut keys so that you can now navigate help using nothing but shortcuts. The problem I have is that the way Help tool is made it gives me the very top topic , and the current topic. But I would also like to have a parent for each topic. So when HelpTopic subtopic: is sent , it does not just add HelpTopics to the HelpTopic but each subtopic is assigne the HelpTopic as parent. This is crucial feature so that I can make those new buttons work. The tricky part here is that there is also the wiki style pragma that generate topics. The help tool uses a treeMorph to display all topics in a tree like fashing, and since each submorph in the tree is tied to a HelpTopic I could fetch the hierarchical structure of HelpTopic from there, but the question is , is this a good idea ? Or should hack the HelpTopic class to allow it to have a owner instance variable ? I dont want to create messy code. I was thinking even creating my own helpTopic classes etc, but I want old help to work with Prometheas too. I welcome any advice :) -- View this message in context: http://forum.world.st/Lets-Talk-about-Pharo-Help-tool-tp4707462p4708922.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 18, 2013

Re: [Pharo-dev] if Pharo is key for you

by kilon

How does "extending Pharo help tool " sounds ? :) I am struggling to learn how morphic really works, especially TreeMorph. -- View this message in context: http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4708917.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 18, 2013

Re: [Pharo-dev] Smalltalkhub => 503

by Stephan Eggermont

Yes, smalltalkhub is nice. And installing your own is very easy. I think more people should do so. It doesn't seem to be as solid as ss3, but can be installed much easier, and on legacy platforms (windows). Running your own mirror should not take that much space and capacity, and makes you less dependent on central infrastructure staying up. Stephan

Sept. 18, 2013

Re: [Pharo-dev] Smalltalkhub => 503

by Damien Cassou

On Wed, Sep 18, 2013 at 11:04 AM, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > I always commit in smalltalkhub and ss3.gemtalksystems. So if one is down, I > can use the other. for those who don't know, each commit you do from Pharo is saved locally on your hard drive (by default, in a package-cache directory). So, even when servers are down, you should have access to your mcz files. What I and some others do is to configure Pharo so that all images share the same package-cache directory. This way, you can change image frequently and still have all your mcz around. To do that, we create a file ~/.config/pharo/monticello.st and place the following in it: StartupLoader default executeAtomicItems: { StartupAction name: 'Monticello related stuff' code: [| sharedPackageCacheDirectory | FileStream stdout lf; nextPutAll: 'Executing Monticello related stuff for Pharo 3.0'; lf. sharedPackageCacheDirectory := '/home/cassou/Documents/smalltalk/cache'. sharedPackageCacheDirectory asFileReference ensureCreateDirectory. MCCacheRepository default directory: sharedPackageCacheDirectory asFileReference. MCDirectoryRepository defaultDirectoryName: sharedPackageCacheDirectory. FileStream stdout lf; nextPutAll: 'Finished'; lf]. }. In this file, you can also set the repositories you often use. That's very convenient if you don't want to copy your username and password all the time. Just before the last FileStream line, add: MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCHttpRepository) and: [each location includesSubstring: 'squeaksource.com']] thenDo: [:each | each user: 'dc'; password: 'XXXXX']. MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCHttpRepository) and: [each location includesSubstring: 'ss3.gemstone.com']] thenDo: [:each | each user: 'dc'; password: 'XXXXX']. MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCHttpRepository) and: [each location includesSubstring: 'source.squeak.org' ]] thenDo: [ :repo | repo user: 'DamienCassou'; password: 'XXXXX' ]. MCRepositoryGroup default repositories select: [:each | (each isKindOf: MCHttpRepository) and: [each location includesSubstring: 'smalltalkhub.com' ]] thenDo: [ :repo | repo user: 'DamienCassou'; password: 'XXXXX ]. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Sept. 18, 2013

Re: [Pharo-dev] Please help us by buying the book

by CÃ©drick BÃ©ler

> On Tue, Sep 17, 2013 at 3:18 PM, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: >> Just ordered too... > > > thank you very much CÃ©drick. It's cool you are still around! I guess I'll always be around ;-) I feel Smalltalk is like a relative a bit far from home right now but I spent so many good moments with him that I come and visit him from time to time ;-) Hope to see you all soon (Smalltalk party ?) See ya CÃ©drick > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Sept. 18, 2013