- Pharo-dev - lists.pharo.org

[Pharo-project] On Win32 "metrics"
by Bill Schwab Oct. 1, 2008

Oct. 1, 2008

Hello all, I am not sure what "the system directory" means to a cross-platform tool, but either my knowledge of Squeak/Pharo or its reporting about the host were a little lacking today. Case in point: win2k uses win32\system32, xp uses windows\system32, but I did not find a clear way to make the right choice programmatically. In either case, one really should call SystemDirectory() or whatever it's called, because the system could be set up with other that defaults. I worked around the problem the way I have come to do: just put a win32 directory tree on the offending xp box - problem solved, or close enough for current purposes. Does Pharo already expose the needed information? All I found was 'NT' which I suspect is not enough, as I assume a 2k box will answer same. If there is yet no way to differentiate XP and 2k, how should we address it? A large part of me has little interest in keeping up with all the latest[*] "developments" in Windows - I want out!!! :) However, once I get out, I will no doubt have need to run things on non-liberated machines, as will others. Having good data on where to look for the guts of the OS would of value. Bill [*] ok, this one happened years ago, but they always find new things to break, and I am still using win2k where feasible to do so. Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

2 1

[Pharo-project] OSProcess under Pharo
by Bill Schwab Sept. 30, 2008

Sept. 30, 2008

Before doing something I might regret, I wanted to check with you about installing OSProcess, VMMaker(?), FFI, etc. Do you have anything to say "try it and report any problems?" Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029

2 1

[Pharo-project] OB's icon support improved
by David RÃ¶thlisberger Sept. 30, 2008

Sept. 30, 2008

Hi there, taking the suggestions from the "On icons" thread, I have now changed and extended the icons in columns like this: - Removed icons for extension methods ('+'), instead use italic font for the method name label if it's a extension method and additionally red color if it's an override (as Lukas suggested) - Use new icons for abstract method and super send (credits to Stef who did the hard work of drawing them). The new icons make clear whether an abstract method or a method sending super is redefined in subclasses or not (they get an additional triangle pointing down if they are redefined). For a complete list of supported icons see: http://smallwiki.unibe.ch/hermion/icons/ There are still some icons missing for rare situations, if someone volunteers to draw them, we'd be happy. ;) - Explaining labels for all icons (keep the mouse over them) - Most icons are clickable: Clicking on a super send icon brings you to the method in the superclass, clicking on a triangle down icon brings you to the overridding method in the subclass or gives you a list of candidates if there are several sub-implementations. This I consider as a very convenient extension. - Classes or Traits can implement the method #browserIcon (answering a symbol for the icon name) to define the icon they will get in the class column themselves If you have more suggestions or wishes concerning icons (or anything else), let me know. Current ideas include to introduce icons for trait classes and methods (trait methods are shown in italic right now, hence somehow conflicting with extension methods), or to have an icon for methods without any additional implementor. I would be interested to know whether you consider these ideas as valuable. To load the latest version of OB, you can use this Installer script: Installer wiresong project: 'ob'; install: 'OmniBrowser-dr.419'; install: 'OB-Standard-dr.355'; install: 'OB-Morphic-dr.57'; install: 'OB-Enhancements-dr.217'. Cheers, David

7 17

[Pharo-project] Fwd: [Seaside-dev] preliminary Seaside 2.9 alpha universe
by Adrian Lienhard Sept. 30, 2008

Sept. 30, 2008

The new and easy way to load Seaside takes up to 10 steps (see below). We should try to make this even less painful in Pharo. I assume, having Universes pre-loaded will already reduce half of the steps, but how can it be further simplified? Adrian Begin forwarded message: > From: "Philippe Marschall" <philippe.marschall(a)gmail.com> > Date: September 24, 2008 10:21:16 PM GMT+02:00 > To: "Seaside - developer list" <seaside- > dev(a)lists.squeakfoundation.org> > Subject: [Seaside-dev] preliminary Seaside 2.9 alpha universe > Reply-To: Seaside - developer list <seaside-dev(a)lists.squeakfoundation.org > > > > Hi > > Seaside 2.9 was always hard to load. We always said that we would fix > this and this is a preview of what we expect the solution to look > like. > > After some evaluation of what is available in Squeak we had only two > options, either start from scratch or use universes [1]. We decided to > give universes a shot. Universes is something like a debian > distribution universe for squeak. > > So how do you load this stuff: > 1. get Universes, if you don't already have it (3.10) > 1.1 get an XML parser [2] > 1.2 get universes [3] > 1.3 optionally the the OB universe browser [4] > 2. save the *.packages to your image directory > 3. load the attached .mcz > 4. evaluate UUniverse switchSystemToUniverse: UUniverse > seasideAndServers > 5. in the world menu open a "Universe Browser" either basic or > enhanced > 6. "update list from network" > 7. choose a distribution > 8. choose a server > > There are still some unsolved issues like the naming of alpha an beta > versions. We probably want website integration as well. One possible > change would be to move the tests to a separate tests category. > > [1] http://wiki.squeak.org/squeak/3785 > [2] http://www.squeaksource.com/universes.html > [3] http://www.squeaksource.com/XMLSupport.html > [4] http://www.squeaksource.com/OBUniverse.html > > Cheers > Philippe > _______________________________________________ > seaside-dev mailing list > seaside-dev(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

12 48

[Pharo-project] Fwd: Strange bug
by StÃ©phane Ducasse Sept. 30, 2008

Sept. 30, 2008

> > > > Hi > > ImageSegment discoverActiveClasses. > is cool and it lets you (by swapping method dict behind your back) > knowing which classes > have been involved in a certain action. > > as follow > Now ImageSegment discoverActiveClasses. > -- do something typical -- > ImageSegment activeClasses size printString , ' classes were active > out of ' , > Smalltalk allClasses size printString. > > Now if following > recoverFromMDFaultWithTrace > > you put > > Smalltalk at: #MDFaultDict put: Dictionary new. > > you get a strange error, tell you that there is syntax error > > Stef > > >

2 2

[Pharo-project] Senders and implementors list with package
by StÃ©phane Ducasse Sept. 30, 2008

Sept. 30, 2008

Hi david in the latest version of pharo when you browse the senders of a message you get the usual list but the items show in addition the package in the item after the category (which is useless to my eye). Could you add that to OB senders and implementors? Stef

1 0

[Pharo-project] Total image lockup when using middle/right click menu on world
by Simon Kirk Sept. 30, 2008

Sept. 30, 2008

Hi all. Not sure where I should report this. If I use the middle/right (depending on one's preferences) click World menu (the one with Project and Configuration sub-menus down towards the bottom third of the menu), when my mouse goes over the "Configuration" menu section, the entire image freezes irrevocably, at least on OSX (my VM). A few fast-hit alt-. efforts can bring up a debugger on the current process, but it too is frozen. Don't know if this was already something knew about. Sorry for the duplication if so. Cheers, Simon ****************************************************************************************************************************************** This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. ******************************************************************************************************************************************* Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA

3 6

[Pharo-project] [OB] Implementor
by Alexandre Bergel Sept. 30, 2008

Sept. 30, 2008

Hi! Pressing alt-m on a method that is implemented on a class-side prevents from opening a implementor method. I will open an issue. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 3

[Pharo-project] Integrate early and release often and tests was: Installer was: Fwd: [Seaside-dev] preliminary Seaside 2.9 alphauniverse
by Simon Kirk Sept. 29, 2008

Sept. 29, 2008

Hi all. Apropos of the conversation this subject line evolved from, I was thinking about this from Marcus: "Pharo will do it completely differently: release often, integrate as soon as possible, keep the bugtracker down to managable levels and do not be religiously backwards-compatible." This lead me to think various comments recently from Stef (I think - I apologise if I'm miss-paraphrasing, but I can't find the exact messages) about how to tell which tests have failed/passed etc as the versions go by. I submit that in order for early integration and regular release to work, it needs to be an "all tests green or nothing" situation. Of course, it's very difficult to make sure all the tests are passing, but I just ran *all* the tests in the system, and there's only one error and one failure. This is fantastic work! Not only that but the error is down to BookMorph (due for removal iirc?) and a #printString problem with Array, the latter of which *has* to be simple to fix. If this level of passing tests (or even better, all of them; not necessarily possible as various things like EToys are stripped out I imagine) is maintained, there's no need to tell what tests have changed state from version to version; moreover Pharo will be far the better for it, imho. Just my â¬0.02 :) Cheers, Simon ****************************************************************************************************************************************** This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. ******************************************************************************************************************************************* Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA

1 0

[Pharo-project] SqueakMap Packae Loader - nil object
by Dan Corneanu Sept. 29, 2008

Sept. 29, 2008

Hi, there is an exception when trying to open SqueakMap Package Loader in the latest pharo/pharo-dev images with the latests updates. The object instance variable of SMSqueakMap is nil. I'm not sure if I should have put an issue on the tracker or not. Best regards, Dan Corneanu.

3 2