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

Re: [Pharo-project] Issue with deprecated method in ByteString

by Henrik Johansen

Don't divide a number by a ByteArray?;) Cheers, Henry Den 14. jan. 2010 kl. 19.25 skrev John Toohey <jt(a)parspro.com>: > Hi, > > Running some tests of my own app, I just got a deprecated warning > popup in the debugger. The method is #isZero in ByteString, and > isZero is called from SmallInteger #/. I'm using the 10506 Core > image. What can I do to fix this? > > -- > -JT > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 15, 2010

Re: [Pharo-project] Issue with deprecated method in ByteString

by Nicolas Cellier

Never divide by a string 2010/1/14 John Toohey <jt(a)parspro.com>: > Hi, > Running some tests of my own app, I just got a deprecated warning popup in > the debugger. The method is #isZero in ByteString, and isZero is called from > SmallInteger #/. I'm using the 10506 Core image. What can I do to fix this? > > -- > -JT > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2010

[Pharo-project] Issue with deprecated method in ByteString

by John Toohey

Hi, Running some tests of my own app, I just got a deprecated warning popup in the debugger. The method is #isZero in ByteString, and isZero is called from SmallInteger #/. I'm using the 10506 Core image. What can I do to fix this? -- -JT

Jan. 15, 2010

Re: [Pharo-project] Pharo-users mailing-list

by Igor Stasenko

2010/1/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi guys > > We know that some of you cannot handle the volume of our mailing-list. > We created a new mailing-list users > > Â Â Â Â Pharo-users -- A friendly place where any question about pharo is welcome > Â Â Â Â http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > we should probably blog on that on the web... > Hi Stef, the given link is in French. Not a problem for you perhaps, but for someone as ignorant as me, it is :) > Stef > > _______________________________________________ > 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

Re: [Pharo-project] custom ui theme

by Stan Shepherd

Tudor Girba wrote: > > Hi, > > I am trying to tweak a bit the way the splitters are drawn in the > watery2 theme. So, I created a subclass of UIThemeWatery2 uitheme, and > I just overrode resizer* and splitter* methods. > > However, when I make MyTheme beCurrent, the windows get painted in > Squeakish colors (blue, green) instead of gray. > > I am probably missing something, but I do not know what. What should I > do to get the gray back? > > Cheers, > Doru > > Hi Doru, you might try in MyTheme class>>newDefaultSettings ^super newDefaultSettings standardColorsOnly: true Seems like you could have overridden an override Good luck, ...Stan -- View this message in context: http://n2.nabble.com/custom-ui-theme-tp4391907p4393746.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 15, 2010

[Pharo-project] Pharo-users mailing-list

by StÃ©phane Ducasse

Hi guys We know that some of you cannot handle the volume of our mailing-list. We created a new mailing-list users Pharo-users -- A friendly place where any question about pharo is welcome http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users we should probably blog on that on the web... Stef

Jan. 15, 2010

Re: [Pharo-project] Comments on Metacello and ConfigurationOfExternalWebBrowser

by Mariano Martinez Peck

On Thu, Jan 14, 2010 at 9:53 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > >Two little remarks of the conf: you are using for FFI '1.0-baseline', not > a > >version, this means that it will ALWAYS bring the latest version (maybe > >unstable). That's why I always try to put a particular version that I know > >is stable. > > Thought about that again and looked at other examples. > > Now the baseline of ExternalWebbrowser depends on a baseline > of FFI. And the version itself uses the version. > See ConfiguratonOfExternalWebBrowser-tbn-5.mcz > > Torsten: Maybe it is not correct what I do but in your case, for example, I wouldn't put the baseline of FFI. project: 'FFI' with: [ spec className: 'ConfigurationOfFFI'; file: 'ConfigurationOfFFI'; version: '1.0-baseline'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]. I don't like to put ANYTHING related to version or baselines in a baseline method. I just want to put dependencies, groups, etc. So I would write: project: 'FFI' with: [ spec className: 'ConfigurationOfFFI'; file: 'ConfigurationOfFFI'; repository: ' http://www.squeaksource.com/MetacelloRepository' ]. Then, in the version method, I would put exactly what you did: spec project: 'FFI' with: '1.0'. So...in summary, form my point of view, is not necessary to put the baseline when defining the dependency to FFI. I insist that you should also send this kind of mails to Metacello mailing list :) This is similar to what Dale did in the seaside 3.0 config with > grease and follows the rules from #lesson11Blessing: > > "Since the latest #baseline version should reflect the most > up-to-date project structure, ... should load the absolute > bleeding edge of the project." > > > >Come on!!! That's not an excuse ;) > > Have access now - typos in the tutorial are fixed. Included > in 1.0-beta.20 of metacello conf. > > Just run > "ConfigurationOfMetacello loadLatestPackages" > > Coooool!!! Excellent. Thank you very much :) > > Bye > T. > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 15, 2010

[Pharo-project] [ANN] JQueryWidgetbox and Metacello

by Torsten Bergmann

Hi, the JQuery Widget box project now switched to Metacello: - there is now a "ConfigurationOfJQueryWidgetBox" project/class in htp://squeaksource.com/MetacelloRepository - this configuration includes a baseline and a first version 1.0 - the old "loader" project (JQWidgetBox-Loader) - in http://squeaksource.com/JQueryWidgetBox can be used as before - it now internally uses Metacello How to get started: =================== We assume a clean image - for instance the latest pharo core (PharoCore-1.0-10506rc1.image) - without any Seaside here: A. THE OLD WAY -------------- To get the old loader (which is now ALWAYS loading the latest version from the metacello configuration) evaluate: Gofer new squeaksource: 'JQueryWidgetBox'; package: 'JQWidgetBox-Loader'; load. Answer yes - and see how Seaside 3.0 and the widget project is loaded. When finished start a webserver through WAKom startOn: 9092 and point browser to http://localhost:9092/browse/jquery-widgets This is working as before - but not as flexible as with Metacello. B. THE NEW (METACELLO) WAY -------------------------- First you need to load the Metacello configuration for the project Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfJQueryWidgetBox'; load. You can now decide to get: ========================== B.1. the latest version (including all tests, examples and widgets - similar to the old loader in A.) (Smalltalk at: #ConfigurationOfJQueryWidgetBox) loadLatestVersion B.2. a specific version (currently there is only one) ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project version: '1.0') load B.3. load a specific widget for your seaside project from Widget box version 1.0 (without tests and examples) ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project version: '1.0') load: 'JQWidgetBox-Growl-Core' B.4. load a specific widget for your seaside project from Widget box version 1.0 (including tests and examples) ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project version: '1.0') load: 'JQWidgetBox-Growl-Dev' B.5. load three widgets for your seaside project from Widget box version 1.0 (two with tests/examples and the first without tests/examples) ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project version: '1.0') load: #('JQWidgetBox-Growl-Core' 'JQWidgetBox-Calculator-Dev' 'JQWidgetBox-Calculator-Dev') B.6. load all the latest packages from the 1.0 baseline - with all widgets, respective tests and examples to do development ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project version: '1.0-baseline') load If an example for a widget is loaded it will automatically appear at http://localhost:9092/browse/jquery-widgets Things to note: =============== If one wraps and adds new jquery widgets to the widget box project he must now add it in the metacello configuration. The old loader project should stay unchanged and remains for compatibility reasons. Have fun, T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Jan. 14, 2010

Re: [Pharo-project] Some notes we took during our experience

by Mariano Martinez Peck

On Thu, Jan 7, 2010 at 4:02 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi > > marcus jannik and me got fun and fixed some cycles. > > Here are some extra notes I took > > - PreferenceBrowserMorph and friends should be removed. > - MethodReference could be closer to CompiledMethod (to avoid cycle > with tools when in fact people > just wanted to report aCompiled method list and return a > methodReference list). > - Services -> split into Services-Morphic and Services-Core -> but > services should be removed for now > > - Symbol could has its own scanning function (isLiteralSymbol) to > avoid to depend on Scanner > - URL should be replaced by URI > - WordArrayForSegment -> ImageSegment > Done in 11157 :) Cheers Mariano > - FilePackage -> Tools > - TextDiffBuilder -> in its own package. > > Stef > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 14, 2010

Re: [Pharo-project] [ANN] WorkingSet

by Mariano Martinez Peck

> On a sidenote, it seems that installing WrokingSet deactivates the shortcut > to Algernon (shift-return). Can someone confirm? > > > Yes, I can :( I really like algernon and I would like to use both at the same time. Do you know if this can be fixed Romain ? Cheers Mariano > > > > What I would like to have now is a better window placement, with > possibilities to tile windows. > > Has anybody done something like that already? > > I think that StÃ©phane did a bit of hacking at one point :) > I know the logic is in the RealEstateAgent class. > > At one time, I thought that making the window appears with the title bar > right under the mouse pointer could be a good idea. If the window placement > does not suite you, you can click and move the window. Besides, if you open > windows through the world menu, that means you clicked in an empty space > right before, so good location to start. > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 14, 2010