- Pharo-dev - lists.pharo.org

[Pharo-project] Re: about http://bugs.squeak.org/view.php?id=6336
by StÃ©phane Ducasse Sept. 24, 2008

Sept. 24, 2008

Thanks. Another problem with real atomic loading. Stef > Hi Stef, > > there is nothing special with the two change sets except their > fileIn order, since instances of Character are used while both of > them are loaded and compiled ... > > The 3.10 release team attempted to make .mcz out of them but failed > miserably, so I suggest you just file them in. > > Let me know how it worked for you; perhaps also see if before/after > the .image indeed gets smaller by ca. 300 KB. > > Ah, and before I forget: because of Association #hash #= (since 3.8 > or so, Marcus knows the problem), compilation of Unicode methods > take looong, since one of its class variables has a populated > SparseLarge* thing which is #hash'ed and #='ed when compiling access > to each class variable :( But this is a genaral problem, which just > manifests, when compiling Unicode, with pain. > > Cheers, > Klaus > > On Tue, 23 Sep 2008 21:52:35 +0200, StÃ©phane Ducasse wrote: > >> Hi klaus >> >> I would like to include the following in pharo >> about http://bugs.squeak.org/view.php?id=6336 >> >> can you tell me if I should pay attention to something in particular. >> >> Stef >> > >

2 1

[Pharo-project] about http://bugs.squeak.org/view.php?id=6336
by StÃ©phane Ducasse Sept. 23, 2008

Sept. 23, 2008

Hi klaus I would like to include the following in pharo about http://bugs.squeak.org/view.php?id=6336 can you tell me if I should pay attention to something in particular. Stef

1 0

Re: [Pharo-project] First pharo-dev with limited package set
by Bill Schwab Sept. 23, 2008

Sept. 23, 2008

Stef, How about a preference for both? I generally find the color annoying in workspaces, and _greatly_ appreciate shout in browsers and the debugger. There is a preference to disable automatic definition of workspace variables??? Great idea!!! I'm not a fan of them. 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 >>> stephane.ducasse(a)inria.fr 9/23/2008 11:08:17 AM >>> Damien I would go for the workspace with color. and we should set the pref to have to type | | to declare varaibles. stef On Sep 23, 2008, at 4:30 PM, Damien Cassou wrote: > On Tue, Sep 23, 2008 at 2:17 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> uh? does not work for me no idea what is a Smalltalk workspace. > > a workspace to write Smalltalk code as opposed to a workspace to > write text. > > At the beginning, the ShoutWorkspace replaced the Workspace but some > people complained. That's why there are two workspaces now. I've never > used the non-colored workspace: when I want to write text, I enclose > it in quotes. > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > _______________________________________________ > 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

2 1

Re: [Pharo-project] First pharo-dev with limited package set
by Bill Schwab Sept. 23, 2008

Sept. 23, 2008

Damien, I thought about that, but it all get colored the way I LIKE having my method comments colored - I do NOT<g> like that for my notes. Shout is very helpful, and the rendering speed and stability are nothing short of amazing. However, I want a choice in what I use for a workspace, and it is almost always going to be plain text. Having the two menu options is fine/preferred, but a preference would work too. 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 >>> damien.cassou(a)gmail.com 9/23/2008 9:30:05 AM >>> On Tue, Sep 23, 2008 at 2:17 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > uh? does not work for me no idea what is a Smalltalk workspace. a workspace to write Smalltalk code as opposed to a workspace to write text. At the beginning, the ShoutWorkspace replaced the Workspace but some people complained. That's why there are two workspaces now. I've never used the non-colored workspace: when I want to write text, I enclose it in quotes. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

2 1

[Pharo-project] Tree View in OmniBrowser
by David RÃ¶thlisberger Sept. 23, 2008

Sept. 23, 2008

Hello, It was very hard work, but finally and eventually I managed to integrate the tree view of Juraj in a reasonable way into OmniBrowser, so that we can use it for instance to browse packages. The package browser of OB-Enhancements is now using this tree in the first column to render packages on the first level and class categories on the second level. As this is a rather drastic change affecting also the underlying meta-model representing navigation in OB, I'd appreciate if some people give this a try and report any problems they might find to me. I extensively tested it, but you never know. I'm still working on some little things concerning this tree integration, mostly internal stuff, so nothing that should stand in way of using it already now. Just drop me a note if you encounter any problems, something that can still occur right now. Other recent enhancements include: - OB-TraitsIntegration is now part of OB-Enhancements as some people wanted to have it integrated in this package - mouse-over for icons in columns to get an explanation label - some icons are clickable, eg. to directly browse methods in superclasses - improvements in smart groups You need to load the following packages: OmniBrowser-dr.417 OB-Morphic-dr.54 OB-Standard-dr.351 OB-Enhancements-dr.207 ToDos: - refactor some of the code for the tree view - address several minor issues (eg. performance) - write more tests for tree view - integrate OmniBrowserFixes in OB-Enhancements Cheers, David

3 3

[Pharo-project] SharedQueue Fixes from OLPC distro
by StÃ©phane Ducasse Sept. 23, 2008

Sept. 23, 2008

http://tinlizzie.org/updates/etoys/updates 2009fixSharedQueue-b.. 2010fixSharedQueueAg..>

1 0

Re: [Pharo-project] Product Brand Pharo
by Bill Schwab Sept. 23, 2008

Sept. 23, 2008

Gary, There are two topics here: (1) allowing ourselves and others to easily retrofit tools into the various menus; (2) building a fast and elegant GUI framework. BookMorphs are a (not terribly good) implementation attempts at the latter. For the newbie (or even us trying to get something done), it can be very helpful to have tools offered in the right places. Cleaner is better of course, but the "user" in the case is more interested in whether the tool works than in how the tool works. Set out to write your own helpful wizard, and elegance is appreciated. 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 >>> gazzaguru2(a)btinternet.com 09/23/08 7:16 AM >>> I remember doing a "Wizard" framework in VisualAge... shudders... Still, nice to have standardised support for such things rather than ad-hoc BookMorphs (for example). Regards, Gary. ----- Original Message ----- From: "Bill Schwab" <BSchwab(a)anest.ufl.edu> To: <pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, September 23, 2008 12:03 PM Subject: Re: [Pharo-project] Product Brand Pharo > Markus, > > Based on the discussion, I started noting how long it takes my images to > load; a splash screen might be in order; I also fear that by the time VM > loads and the GUI is able to draw itself, it is no longer needed :( > Still, I'd add it to the milestones, but probably late in the process. > > About help, I am not very sympathetic on the "no documentation" front. > Someone seeking to join us will quickly find tutorials, and can post > questions. Dolphin's MVP framework almost invariably had the newbie > expressing pain and confusion, followed by "why was this so hard last > week???" Conversely, the MS Office IDL for Automation has LOTS of > "help" - almost all of it useless. The message (pun intended) needs to > be "this is not trivial to learn, but very worth your time." Ensuring > that good tutorials are linked from our Wiki would be a nice gesture. > > Wizards in the IDE - that's a very good idea, and Dolphin helps it along > through the IDE extension framework, which is little more than events > triggered at the right time, off of each tool's class and giving the > needed instances for the code to make the desired changes. Dolphin's > view resources, and our lack of them, would require some adaptation. > However we do it, it would be a nice addition. The idea is to do > _something_ that allows each of us to provide hooks into the IDE w/o > having to alter the code. That way, building a new image and updating > an existing one will not destroy the extensions. > > 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 > > > _______________________________________________ > 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

2 1

Re: [Pharo-project] First pharo-dev with limited package set
by Bill Schwab Sept. 23, 2008

Sept. 23, 2008

Ok, but only if you allow a choice of which one to use. I am a HUGE fan of Shout, but I generally do not want a workspace trying to colorize my notes to myself. If I end up with enough code that the syntax is not clear, it probably belongs in a class and in a package or change set - at least I try to do that. 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 >>> adi(a)netstyle.ch 09/23/08 5:42 AM >>> Hi Damien, Thanks, looks good! Question: Does this include Universes? It's not listed below but I see the menu item (which does not work because of a deprecation warning). I think we need Universes mainly because Seaside will be packaged with Universes soon, and being able to easily load Seaside is a key requirement for Pharo. Another thing we need to look at (and I planned to do this) is the open menu. With all the additional packages in the dev version its even worse than before. For example there are 3(!) items for opening a workspace: Workspace Workspace (without colourisation) Shout Workspace There ought to be just one, and in the right place. Cheers, Adrian On Sep 23, 2008, at 09:52 , StÃ©phane Ducasse wrote: > This sounds good. > Now we should be able to see the overrides of ecompletion. > > Stef > > On Sep 23, 2008, at 8:20 AM, Damien Cassou wrote: > >> Hi, >> >> I've just released the first pharo-dev which contains a limited >> package set. See http://code.google.com/p/pharo/wiki/Packages for the >> list of packages we want in Pharo. >> >> You can download the image at >> https://gforge.inria.fr/frs/download.php/7404/pharo0.1-10074dev08.09.2.zip >> . >> >> Here is the list of packages included in this release: >> >> AST version 160 >> eCompletion version 0.90 >> OB-Enhancements version 0.203 >> OmniBrowser version 0.416 >> OmniBrowser-Morphic version 0.52 >> OmniBrowser-Refactory version 1.0 >> OmniBrowser-Regex version 0.9.1 >> OmniBrowser-Standard version 0.346 >> Pharo packages version 0.3 >> Refactoring Core version 5 >> RoelTyper version 0.60 >> Shout version 3.15-tween.72 >> ShoutWorkspace version 1-tween.2 >> VBRegex version 1.9 >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> _______________________________________________ >> 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 _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] Product Brand Pharo
by Bill Schwab Sept. 23, 2008

Sept. 23, 2008

Markus, Based on the discussion, I started noting how long it takes my images to load; a splash screen might be in order; I also fear that by the time VM loads and the GUI is able to draw itself, it is no longer needed :( Still, I'd add it to the milestones, but probably late in the process. About help, I am not very sympathetic on the "no documentation" front. Someone seeking to join us will quickly find tutorials, and can post questions. Dolphin's MVP framework almost invariably had the newbie expressing pain and confusion, followed by "why was this so hard last week???" Conversely, the MS Office IDL for Automation has LOTS of "help" - almost all of it useless. The message (pun intended) needs to be "this is not trivial to learn, but very worth your time." Ensuring that good tutorials are linked from our Wiki would be a nice gesture. Wizards in the IDE - that's a very good idea, and Dolphin helps it along through the IDE extension framework, which is little more than events triggered at the right time, off of each tool's class and giving the needed instances for the code to make the desired changes. Dolphin's view resources, and our lack of them, would require some adaptation. However we do it, it would be a nice addition. The idea is to do _something_ that allows each of us to provide hooks into the IDE w/o having to alter the code. That way, building a new image and updating an existing one will not destroy the extensions. 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

Re: [Pharo-project] Halt once; workspace(?) menu
by Bill Schwab Sept. 23, 2008

Sept. 23, 2008

Stef, The class can be more flexible than what is in Pharo, and FWIW, is not built into the system. Since it does not need to be built-in, that's a plus in my thinking. Not much of a difference, I must admit. 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

1 0