January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] us the vm -memory in an image ?

by John M McIntosh

Personally I think you need to add an entry. I am currently am doing a statistical study in this area for a client, of course not all of the data/solution will flow back to the community unless agreed to by the client, however I'll supply some numbers & thoughts to take us from the 1996 values into 2010. Also there will an active memory policy that will adjust some things to avoid some interesting edge cases as an example of the solution that lurks. On 2010-01-15, at 6:19 PM, csrabak(a)bol.com.br wrote: > I would only add the item if we could agree these parameters are to used with such frequency to make the addition worthwhile. > > Do more users of Pharo feel in need to tweak these parameters before delivering their projects to users in production? > > -- > Cesar Rabak -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 16, 2010

[Pharo-project] Styles for Morphic

by Igor Stasenko

Hello guys, thinking, how to easily define styles, based on simple selection rules, i sketched the class, MorphStyle. The principle how it works is simple: - you creating a style, add adding actions to it - you then applying style to morph or group of morphs. Example: | style | style := MorphStyle new submorphs model: #Browser; color: Color red. style applyTo: World. Let me describe in detail, what it does, when you applying it: style applyTo: World. Style initializing its current selection to be a collection with single element - { World }. Next thing, which it does is applying any actions , which we specified during building the style, namely: 'submorphs' - replacing the current selection by gathering all submorphs of it, i.e. selection before: #( World ) selection after: #( World's submorphs ) 'model: #Browser' - filter the current selection and leave only those entries, which respond to #model and model class name is #Browser selection before: #( world's submorphs ) selection after: { Browser SystemWindow#1. Browser SystemWindow#2. Browser SystemWindow#3.Browser SystemWindow#4. } 'color: Color red'. - since there's no such method in MorphStyle, it is trapped by DNU handler and converted to a #sendMessage: action. A #sendMessage: action sends a specified message to current selection, i.e.: { Browser SystemWindow#1. .... Browser SystemWindow#N. } do: [:morph | message sendTo: morph ]. So, as result, if you doIt : | style | style := MorphStyle new submorphs model: #Browser; color: Color red. style applyTo: World. all browser windows color will be changed to red color. Some words about potential uses of this stuff. - theming, (through defining own style sheets). In contrast to existing implementation, we're free to define anything, which morph understands , not just colors, border or fillstyle, but also, layout, fonts, position etc etc. - defining styles in various ways: following snippet sets the 'browse' button color to red for all browser windows and illustrating how one style could reuse another one. | browseButton buttonStyle browsers | buttonStyle := MorphStyle new color: Color blue. browseButton := MorphStyle new allSubmorphs; has: #label equalTo: 'browse'. browsers := MorphStyle new model: #Browser. browseButton style: buttonStyle. "browseButton reusing buttonStyle" browsers style: browseButton. "browser style reusing browseButton style" browsers applyTo: World submorphs. It can be easily integrated with Morphic when using some global theme, all we need is: - add Morph>>applyThemeStyles ^ World currentTheme applyStylesTo: self - send #applyStyles to morph, when its added to World. Also, we could integrate it with toolbuilder which will allow us to define morph layouts, fonts, colors & initial properties more flexibly than currently are . Non-morphic builders could just ignore the #setStyles: message. Comments, suggestions , as always welcome. -- Best regards, Igor Stasenko AKA sig.

Jan. 16, 2010

Re: [Pharo-project] us the vm -memory in an image ?

by csrabak＠bol.com.br

I would only add the item if we could agree these parameters are to used with such frequency to make the addition worthwhile. Do more users of Pharo feel in need to tweak these parameters before delivering their projects to users in production? -- Cesar Rabak Em 15/01/2010 23:57, Alexandre Bergel <alexandre(a)bergel.eu > escreveu: > If it makes sense to have these parameters accessible for anyone > more than a very hacker, then I strongly suggest we find the correct > names for these and create meaningful name for getters/setters of > them! I haven't followed the discussion that closely, but I agree with you Cesar. Shall I add an entry in the bugtracker? Alexandre > > > Em 15/01/2010 07:57, Mariano Martinez Peck > escreveu: > > > > > > On Fri, Jan 15, 2010 at 10:51 AM, Laval Jannik > wrote: > > Hi, > > In some case I need to run my VM with more memory. > For now, I use the parameter "-memory" when I run the VM. > > Is it possible to define this value in the image ? > > > > I think you can do something like: > > SmalltalkImage current > vmParameterAt: 5 put: 100000; > vmParameterAt: 6 put: 35000; > vmParameterAt: 24 put: 16 * 1024 * 1024; > vmParameterAt: 25 put: 8 * 1024 * 1024. > > > But...I am not sure how to know each parameter number what exactly > is. Do you know where I can get that information? > > To see your current data I think you can do: > > SmalltalkImage current getVMParameters > > > Cheers > > Mariano > > > Then I can use it in a script. > > Cheers > > > --- > Jannik Laval > --- > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 16, 2010

Re: [Pharo-project] Toyota like process for 1.1

by csrabak＠bol.com.br

Em 15/01/2010 19:48, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> escreveu: > Hi guys > may be I'm wrong but I have the impression that fixing tests as > soon as they are broken in the Unstable branch could be better. Now > doing that may stall our energy. I think it would reduce the [apparent] speed of new functionality, but not "stall our energy" which I surmise is to have a cool but as bug free as possible Pharo Smalltalk. > So what do you think? Doing this way, as some red tests get on the pile without resolution we can get more attention to the issues. It's a mixture of the Toyota process with a Kanban for squashing the bugs! > May be an alternate process is to make progress and to do green > test session from time to time. Except if we could be _so_ assertive about the non importance of some of the non passing tests, I think the time to time should be as short as today! OK, as a concession could we try to have these gates about every two weeks? -- Cesar Rabak

Jan. 16, 2010

Re: [Pharo-project] us the vm -memory in an image ?

by Alexandre Bergel

> If it makes sense to have these parameters accessible for anyone > more than a very hacker, then I strongly suggest we find the correct > names for these and create meaningful name for getters/setters of > them! I haven't followed the discussion that closely, but I agree with you Cesar. Shall I add an entry in the bugtracker? Alexandre > > > Em 15/01/2010 07:57, Mariano Martinez Peck <marianopeck(a)gmail.com> > escreveu: > > > > > > On Fri, Jan 15, 2010 at 10:51 AM, Laval Jannik > <jannik.laval(a)inria.fr> wrote: > > Hi, > > In some case I need to run my VM with more memory. > For now, I use the parameter "-memory" when I run the VM. > > Is it possible to define this value in the image ? > > > > I think you can do something like: > > SmalltalkImage current > vmParameterAt: 5 put: 100000; > vmParameterAt: 6 put: 35000; > vmParameterAt: 24 put: 16 * 1024 * 1024; > vmParameterAt: 25 put: 8 * 1024 * 1024. > > > But...I am not sure how to know each parameter number what exactly > is. Do you know where I can get that information? > > To see your current data I think you can do: > > SmalltalkImage current getVMParameters > > > Cheers > > Mariano > > > Then I can use it in a script. > > Cheers > > > --- > Jannik Laval > --- > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 16, 2010

Re: [Pharo-project] us the vm -memory in an image ?

by csrabak＠bol.com.br

If it makes sense to have these parameters accessible for anyone more than a very hacker, then I strongly suggest we find the correct names for these and create meaningful name for getters/setters of them! my 0.0199999... -- Cesar Rabak Em 15/01/2010 07:57, Mariano Martinez Peck <marianopeck(a)gmail.com> escreveu: On Fri, Jan 15, 2010 at 10:51 AM, Laval Jannik <jannik.laval(a)inria.fr> wrote: Hi, In some case I need to run my VM with more memory. For now, I use the parameter "-memory" when I run the VM. Is it possible to define this value in the image ? I think you can do something like: SmalltalkImage current vmParameterAt: 5 put: 100000; vmParameterAt: 6 put: 35000; vmParameterAt: 24 put: 16 * 1024 * 1024; vmParameterAt: 25 put: 8 * 1024 * 1024. But...I am not sure how to know each parameter number what exactly is. Do you know where I can get that information? To see your current data I think you can do: SmalltalkImage current getVMParametersÂ Â Â Cheers Mariano Then I can use it in a script. Cheers --- Jannik Laval --- _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 16, 2010

[Pharo-project] OT: windows explorer weirdness workarounds?

by Schwab,Wilhelm K

Hello all, No good deed goes unpunished. This time, I'm having win 2008 thrown at me. The deal is not all bad, but I see that the Windows explorer is just as whacked up as on Vista (which you might recall I gleefully replaced with Ubuntu and have not looked back). The changes to the folder list and complete absense of a horizontal scrollbar (and associated jumping in place of same) are really driving me nuts. Have any of you found ways around these changes? So far, I have found plenty of posts complaining of the GUI changes, but none explaining how to fix it. Any pointers would be greatly appreciated. Bill

Jan. 16, 2010

Re: [Pharo-project] Smalltalk interactive tutorial in good English

by Igor Stasenko

2010/1/15 Michael Roberts <mike(a)mjr104.co.uk>: > hey this is really neat! > > I can offer you some corrections or perhaps suggestions for better > phrasing. Â just my native 2p if it helps. > > As a general comment, i know it would be more work, if you could get > some emphasis e.g bold, italics it would really make the expressions > and names of classes or methods stand out. > > ---Welcome--- > I suppose you have called me to learn Smalltalk. > --> > You must want me to help you learn Smalltalk! > > ---Doing vs printing--- > You've just executed a Smalltalk instruction > --> > You've just executed a Smalltalk expression > Expressions usually get evaluated, code is running or get executed. > > ---Doing vs printing 2--- > It's a Do It which print the result > --> > It's a Do It which prints the result > > > ---basic types numbers--- > you know how to execute Smalltalk code > --> > you now know how to execute Smalltalk code > > ---basic types characters--- > A Character can be instanciated > --> > A Character can be instantiated > > --basic types string--- > Use single quotes to create a String instance > --> > Use single quotes to create a String. > the original is more precise , i think > ---basic types dynamic array--- > Dynamic Array are created at execution time: > --> > Dynamic Arrays are created at execution time: > > > ---unary messages--- > Unary messages have the following form: > Â Â anObject aMethod name > --> > anObject aMethodName > > --keyword messages-- > The message is between:and: sent to Number object > --> > The message is between:and: sent to the Number 4 > > ---message syntax: execution order--- > Between similar messages, expressions are executed from left to right > --> > Between messages of similar precedence, expressions are executed from > left to right > > ---parentheses--- > Use parentheses to change order > --> > Use parentheses to change order of evaluation > > ---mathematical precedence--- > A message does not know mathematical precedence. Simplicity has a price :) > --> > (rephrase ?) > Traditional precedence rules from mathematics do not follow in > Smalltalk. Â The simplicity has a price ;) > It might surprise you that precedence rules you know from mathematics > do not apply here. Â This has a price as you can see... > Complexity has a price: first you have to learn it in school, second you have to unlearn it to understand that all messages in smalltalk always follow a simple left-to-right precedence rule, without exceptions. ;) > ---conditionals--- > Conditionals are just message sent to Boolean objects > --> > Conditionals are just messages sent to Boolean objects > > ---loops--- > Loops are messages send to collections, high-level iterators > --> > Loops are messages sent to collections, high-level iterators > this sounds wrong to me. Loops not necessary work deal collections. By maybe in mentioned in context with collections? > ---iterators--- > Here we want to print all the numbers of the Transcript (a console) > --> > Here we want to print all the numbers on the Transcript (a console) > > ---() vs []--- > --> > I know what you are trying to articulate here, but this page doesn't > really work since your 'annotation' is not syntactic and therefore > your learning style breaks. > pehaps have a think about this slide > > cheers > Mike > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Jan. 15, 2010

[Pharo-project] Package Browser and Pharo

by Alexandre Bergel

Hi! David arrived today and will spend few days among us. I would like to define a roadmap on how to improve the state of O2PackageBrowser. The main problem people have with O2PackageBrowser is the overrides made by O2PackageBrowser right? These overrides break OB. This is something we will fix. I would like that people who are using O2PackageBrowser to add their wishes and bug report on code.google please. Add David and me as Cc. We will look for the entries by entering O2 in the search field. Cheers, Alexandre

Jan. 15, 2010

Re: [Pharo-project] Putting Algernon and WorkingSet in a Dev image

by Simon Denier

On 15 janv. 2010, at 23:03, Mariano Martinez Peck wrote: > > > 2010/1/15 Simon Denier <Simon.Denier(a)inria.fr> > > On 15 janv. 2010, at 21:20, Mariano Martinez Peck wrote: > >> >> >> On Fri, Jan 15, 2010 at 5:55 PM, Romain Robbes <romain.robbes(a)gmail.com> wrote: >> yes it has overrides ... >> >> that's because as far as I know, there's no keyboard shortcut management facility >> in Pharo. If there was one, I suppose Algernon and WorkingSet would coexist. >> >> >> So...all your overrides are due to the shortcuts? I think it is not fear to "forbid" a package to be included in a Dev image if we don't provide from the core a way to manage shortcuts. So: >> >> 1) Or we let this projects to be installed in the Dev image >> >> 2) We fix the problem with the shortcuts. >> >> Romain: can you tell us where exactly the problem is ? maybe someone can give you a hand. > > > Taking a look at that, there are 2 overrides in WorkingSet > > > How did you detect that ? Manually, using an extension-aware browser (O2Package, MC browse package, or the package environment) to detect extensions, then check history in the versions browser. > > Impressive. You should be a detective :) A few years ago, I was called the human debugger during a project :) Now I try to restrain from this kind of sessions though, it's time consuming. -- Simon

Jan. 15, 2010