February 2011 - Pharo-users

StandardWindow and SystemWindow
by DougEdmunds Feb. 22, 2011

Feb. 22, 2011

I'm looking at the tutorial on GUIs at: http://book.pharo-project.org/book/GUI/PolymorphTutorial/Layout/?_s=J-fOIjG… The examples sometimes use StandardWindow and other times SystemWindow. When and why should I use SystemWindow? -- View this message in context: http://forum.world.st/StandardWindow-and-SystemWindow-tp3318409p3318409.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 1

[Pharo-project] Call for Pharo Support **important**
by StÃ©phane Ducasse Feb. 21, 2011

Feb. 21, 2011

Dear Pharoers We are pursuing an effort to bring Pharo to the next level: we will set up a consortium of pharo users and industrial partners. Our goal is to build a legal infrastructure that will be able to sustain the development of Pharo and improve its future. As an example, we would like to be able to collect funds (ways as to be determined - we foresee a membership model or moral license) to pay engineering tasks to be performed such as improving the virtual machine, network libraries, better JIT support. To make it short we would like to give a chance to our community to grow and structure itself so that Pharo can get stronger and that risk (truck factor) gets minimized. We are contacting you to know if your company/research group would be interested to support such effort. Showing such interest is strategically important for us and INRIA which could also support such effort. Attached is the letter of support that we will collect once signed and scanned ( stephane.ducasse(a)inria.fr / faxed at: 00 33 (0)3 59 57 78 50) Thanks for your support The Pharo Board M. Denker, S. Ducasse, and A. Lienhard

6 11

Re: [Pharo-users] [Pharo-project] [ANN] pharo focused sprint - bern, feb 26
by Mariano Martinez Peck Feb. 21, 2011

Feb. 21, 2011

On Tue, Feb 1, 2011 at 4:38 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > We would like to organize a Pharo Sprint on Saturday, February 26 at SCG, > University of Berne, Switzerland (room 107): > http://scg.unibe.ch/contact/maps > > Unlike other sprints, this would not be about fixing things from the > tracker, but about building something new and reviewing the situation around > one central topic. For this one, the main topic will be Morphic and the IDE. > Why? Because it is time to rethink our day-to-day tools and bring them > closer to this century (ok, maybe decade :)). It is Ok if you are not a > specialist. It is more important to want to participate and learn. The rest > will come in time. > > ***** Please let us know by mail if you plan to attend and what you would > wish to work on (see below). > > Proposed tasks (other tasks are possible in the same area): > - Enhancements of Morphic widgets: > --- TabGroupMorph with lazy pages, closable tabs, overflow handling and > toolbars (a start exists in Glamour) > --- High level support for collapsable panes (based on the input of Gary) > --- SearchMorph with multiple groups of items (like in Spotlight) > --- MorphTreeMorph integrated with GeneralScrollPane to allow for space > filling > --- BreadcrumbMorph > --- Hyperlinks in TextMorphs > - Test and enhance the current IDE > - Evaluate TextMorphs: NewTextMorph, PluggableTextMorph, > SMxPluggableTextMorph etc > - Prototype a new ToolSet solution > - Enhancements of Glamour and of the Glamorous Toolkit > --- Debugger > --- Coder > --- Multipage Workspace > --- CodeBubbles > - Develop WeakAnnouncement (start from the implementation of Lukas) > - Evaluate the various keybinding implementations > - Evaluate ToolBuilder > - Evaluate the path to adopt SimpleMorphic > > A second working topic is getting Monticello faster, but this will only be > tackled if there are enough people for the first one. > > Cheers, > Adrian and Doru > > > > -- > www.tudorgirba.com > > "Be rather willing to give than demanding to get." > > > > >

1 0

[ANN] Moose 4.3
by Tudor Girba Feb. 20, 2011

Feb. 20, 2011

We are happy to announce the Moose Suite version 4.3: *http://moosetechnology.org/download* What is new: - New look and feel - New and flexible API to browse FAMIX models - Extensible Moose Finder - Enhanced Glamour engine to deal with complex actions - Enhanced FAMIX support for Java systems - Enhanced Glamour rendering for Morphic - Enhanced meta browser - Enhanced documentation of Mondrian - Enhanced XMLSupport - Enhanced Smalltalk importer A list of issues addressed in this release can be found at: *http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%20milestone=4.3* Have fun, The Moose Team

1 0

Removing Package from SqueakSource Project
by Runar Jordahl Feb. 18, 2011

Feb. 18, 2011

I have a (private) SqueakSource project where I want to remove a package. I changed my package names, and leaving the old package will probably only confuse users. I am unable to find a way to remove packages in the SqueakSource project. There is the possibility to delete the project, and recreate it under the same name, then publish the correct packages. Is this my only option? (I use Metacello so I know I can create configurations to ease the understanding of the project's contents. But I still want to remove packages...) Kind regards Runar

2 2

Pharo-Project mailing list digest
by Francois Stephany Feb. 18, 2011

Feb. 18, 2011

Hi, If you don't follow the Pharo-Project mailing list because of its high traffic, you are maybe interested in a digest of the past week. You can find one here: http://articles.tulipemoutarde.be/pharo-mailing-list-weekly-digest Please tell me if you have any remarks/demands/critics :) See you next week, Francois

4 6

polymorph question
by Werner Kassens Feb. 18, 2011

Feb. 18, 2011

hi, i make a text entry field with StandardWindow's method: newTextEntryFor: aModel getText: getSel setText: setSel getEnabled: enabledSel help: helpText how do i let that textentryfield verify the text for its validity (in its model) when one tries to leave that field and prevent the exiting from that field? or do i have to use another method (UITheme?) for this thing? werner

1 0

Pharo on LinkedIn ...
by Geert Claes Feb. 18, 2011

Feb. 18, 2011

We would like to invite those Pharoers who have a LinkedIn account to join our LinkedIn Pharo group. http://www.linkedin.com/e/hzbhb7-gkawp6l9-36/vgh/2558378/ -- View this message in context: http://forum.world.st/Pharo-on-LinkedIn-tp3312461p3312461.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 1

Dependencies and Monticello
by Andrew Black Feb. 17, 2011

Feb. 17, 2011

I probably don't understand how to use Monticello dependencies correctly. Here is the situation. Your help appreciated. I'm writing code that uses PetitParser. So, I added to my own package a dependency on PetitParser. Strangely, rather than linking to the PetitParser repository, this copies PetitParser into my repository when save a new version on my package. The problem is that I have found it necessary to change a few definitions in *PetitParser. (I would call these bug fixes, but that is a matter of opinion.) I didn't think that would be a problem; I put the overriding definitions into my package, and everything worked fine. That is, it worked fine until I started with a clean image and loaded my package. Monticello apparently loaded my package, and then loaded PetitParser. This over-wrote my (bug-fix) definitions with the original ones. Most of my tests failed. If I load my package a second time, them my definitions overwrite the ones from PetitParser, and all is well. I infer that Monticello packages are supposed to be load-order-independent. So, what is the right way to fix this problem (other than convincing Lukas that trimSpaces should, indeed, trimSpaces)? Andrew

5 5

Lint checks & automated clean-up of unnecessary code.
by Paul DeBruicker Feb. 15, 2011

Feb. 15, 2011

Hi - Is there some place I could read about how automate the fixing of various lint checks? In a package I've written I have some sloppy parts left over from trying things, then trying other things, then finally settling on another approach entirely. For instance I have 84 instances of "Temporary variables read AND written" (RBOnlyReadOrWrittenTemporaryRule). I have 300+ methods that are implemented but not sent (RBImplementedNotSentRule), 10 un-referenced classes (RBClassNotReferencedRule), etc..... I could definitely go through and delete the temp variables by hand but am hopeful that I could just nuke them all at once, then run my tests and see what, if anything, needs replacing/repairing. Thanks for any guidance you can provide. Paul

1 0