- Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] JQueryWidgetbox and Metacello
by Torsten Bergmann Jan. 14, 2010

Jan. 14, 2010

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

1 0

[Pharo-project] Some notes we took during our experience
by StÃ©phane Ducasse Jan. 14, 2010

Jan. 14, 2010

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 - FilePackage -> Tools - TextDiffBuilder -> in its own package. Stef

4 8

[Pharo-project] [update 1.1] #11157
by Marcus Denker Jan. 14, 2010

Jan. 14, 2010

11157 ----- Issue 1491: ImageSegment has special code for Player Issue 1816: New tests for ImageSegment Mariano and Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] tabs with close button
by Tudor Girba Jan. 14, 2010

Jan. 14, 2010

Hi, Is there a Tab widget that offers the possibility of closing a tab (maybe with a small x button near each tab)? Cheers, Doru -- www.tudorgirba.com "There are no old things, there are only old ways of looking at them."

2 2

Re: [Pharo-project] [squeak-dev] Re: Flaw in SocketStream>>peek detected
by GÃ¶ran Krampe Jan. 14, 2010

Jan. 14, 2010

Hi all! I presume this bug is also in Pharo so I CCed. Andreas Raab wrote: > Igor Stasenko wrote: >> The fix is: >> >> --- ^inBuffer at: lastRead >> +++ ^inBuffer at: lastRead+1 >> >> >> but i'm not sure if something else won't break because of it ;) > > Extremely unlikely. It's pretty clear that peek is wrong here as > illustrated by: > > stream := SocketStream openConnectionToHostNamed: 'www.google.com' port: > 80. > stream nextPutAll:('GET / HTTP/1.0\\' copyReplaceAll: '\'with: String > crlf). > stream flush. > stream peek. > > This blows up and clearly it shouldn't. Yup, just fix it! :) Sorry for the bug guys. regards, GÃ¶ran

1 1

[Pharo-project] ConfigurationOfAlien
by Fernando olivero Jan. 14, 2010

Jan. 14, 2010

Hi, just added ConfigurationOfAlien to the MetacelloRepository. To load Alien using Metacello configurations evaluate Gofer new url: 'http://www.squeaksource.com/MetacelloRepository' ; package: 'ConfigurationOfAlien'; load. (ConfigurationOfAlien project version:'1.0') load. ( John please update the ALIEN squeaksource page with the previous text ) Note: Using the available MAC VM i the pharo page, you should be able to run the test correctly. ( the alien plugin 'IA32ABI 7 May 2009 (e)', is compiled inside that vm, there's no need for the external one) Metacello question: If i want load Alien Examples, the package Alien-MacOSExamples, but don't want to add them to the above configuration , should i create a new #versionXXX method ? Or provide a class side method like for example ConfigurationOfAlien>>loadWithMaxOsExamples (ConfigurationOfAlien project version:'1.0') load:#('Alien-MacOsExamples') Saludos, Fernando

10 13

Re: [Pharo-project] [Vm-dev] SystemTracer64 progress
by Laval Jannik Jan. 14, 2010

Jan. 14, 2010

Hi David, I cannot write my changes. So you can have them in attachment. In these .cs, there is a merge with your version .15. And it works with Pharo. Cheers Jannik On Jan 12, 2010, at 04:55 , David T. Lewis wrote: > > Over the weekend I made some progress in getting SystemTracer updated > to do 64-bit image tracing. Previously SystemTracer64 did not work on > little-endian machines (Mantis 5240). This is corrected now, and the > code is on SqueakSource in project "SystemTracing". > > I can now trace a Squeak 3.10.2 image to 64-bit format on my Linux > AMD box (little endian), producing a runnable 64-bit image. For > an up to date Squeak trunk image, I can trace a 64 image that > loads and runs (display opens and things start working), but that > has problems with resuming its background processes (low space > watcher etc). Possibly it's related to the block closure changes, > although I believe there was an earlier report of a Pharo image > with block closures being successfully traced to 64 bit format. > > Dave >

2 2

[Pharo-project] Metacello configuration of Magma
by Miguel Enrique CobÃ¡ Martinez Jan. 14, 2010

Jan. 14, 2010

I have published the Metacello configuration of Magma in the MetacelloRepository of squeaksource.com. Take a PharoCore 10506 and evaluate in a workspace: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. Then load the default group that loads the Magma Client: ((Smalltalk at: #ConfigurationOfMagma) project version: '1.0r43') load this is equivalent to: ((Smalltalk at: #ConfigurationOfMagma) project version: '1.0r43') load: 'Client'. To load the Magma Server evaluate: ((Smalltalk at: #ConfigurationOfMagma) project version: '1.0r43') load: 'Server'. And to load the Magma Tester evaluate: ((Smalltalk at: #ConfigurationOfMagma) project version: '1.0r43') load: 'Tester'. This last one will load also OSProcess that is used by the Magma Tester to do the stress testing of Magma. Notes: - WriteBarrier is a package loaded by Magma. This requires NewCompiler as dependency but as NewCompiler is being rewritten currently, isn't loaded as a dependency. - Magma makes use of ProjectHistory that doesn't exist anymore in Pharo. Magma will fix this by conditionally testing for ProjectHistory by means of Smalltalk at: #ProjectHistory. - This is the first configuration for Magma and will be modified in response to the feedback you give me. - Currently the blessing is #development. Maybe this should be marked as #stable in order to load with: ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) load. This way it will install the latest non-development version available in MetacelloRepository without having to specify a version number. - This configuration executes a preLoadDoIt with the following code: Smalltalk at: #EventSensor put: InputEventSensor because EventSensor was removed from Pharo, but Magma add some methods to EventSensor class. I *really* need feedback about the risks of doing this. Any feedback is welcome. Enjoy! -- Miguel CobÃ¡ http://miguel.leugim.com.mx

1 0

[Pharo-project] regex gurus anyone? Method category refactoring?
by Stan Shepherd Jan. 14, 2010

Jan. 14, 2010

Hi, I'm looking at getting the window building tools to provide some information to a theme, so it can provide meaningful themeing (in the first instance window color) . So I have a list of the senders of #labelled:, that currently are sending virginal SystemWindows with no models. I'd like to do a regex on the scoped list, of the form (SystemWindow labelled: 'later') model: self. becomes (SystemWindow labelled: 'later' justSetModel: self) model: self. So the theme can see the model at the time it's asked to provide the color. ie (SystemWindow labelled: foo ) model: bar. becomes (SystemWindow labelled: foo justSetModel: bar) model: bar. Any takers on a regex for that? Also, how do you add all the methods changed to category *MyWindow-Changes in one go? Bear in mind no package browser in the dev or one click images. Thanks, ...Stan -- View this message in context: http://n2.nabble.com/regex-gurus-anyone-Method-category-refactoring-tp43901… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] EventSensor vs EventInputSensor
by Miguel Enrique CobÃ¡ Martinez Jan. 13, 2010

Jan. 13, 2010

I have a question about EventSensor. In Pharo doesn't exists anymore, it was replaced by InputEventSensor that has this class comment: An InputEventSensor is a replacement for the old Morphic EventSensor framework. It updates its state when events are received so that all state based users of Sensor (e.g., Sensor keyboard, Sensor leftShiftDown, Sensor mouseButtons) will work exactly as before. The usage of these funtions is discouraged. I am installing Magma on a Pharo core image and Magma uses EventSensor, by adding some methods to this class. As the class doesn't exist it shows the following message: This package depends on the following classes: EventSensor You must resolve these dependencies before you will be able to load these definitions: EventSensor classSide>>maMaterializeFromGraph:using: EventSensor>>maAsStorageObject EventSensor>>maUsesStandardStorage Select Proceed to continue, or close this window to cancel the operation. If before loading Magma I do Smalltalk at: #EventSensor put: InputEventSensor. Then everything works without warnings. Also the InputEventSensor receives the methods added by Magma. My questions are: Is this valid? Must this (the InputEventSensor in the slot of EventSensor in Smalltalk) be part of the image or will be a regresion to the situation before the deletion of EventSensor? What will be the correct way to handle this, change the Pharo/PharoCore with my hack or to ask Chris Muller, the maintainer of Magma to not use EventSensor but InputEvenSensor in the case of Pharo/PharoCore? Can I be reminded of the reasons to drop EventSensor in favor of InputEvenSensor? Thanks for the answers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

5 7