- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Aaah, the pain or ParagraphEditor refactoring ; -)

by Rob Rothwell

Michael, Do you mean: fullScreen: fullScreenOff fullScreenOn isFullScreen lastScreenModeSelected toggleFullScreen ??? I mean, that actually looks like something I can handle if you think of me like a first year apprentice who needs very specific instructions! Where do you want them to go? It's the whole change set thing that always takes me a while to figure out...! Rob On Mon, Feb 23, 2009 at 10:06 PM, Michael Rueger <m.rueger(a)acm.org> wrote: > Hi all, > > while further battling full unicode support I ended up refactoring > ParagraphEditor to the extend that there a no references to the inst var > sensor left. There are still a few references to the global Sensor though. > > With moving the model inst var down we could now basically get rid of > class Controller :-) > > Class KeyboardBuffer is gone already. > > All that needs to be done is moving the utility methods in > ScreenController to e.g. Display so we can remove that subclass of > Controller as well. > > Volunteers? > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 24, 2009

[Pharo-project] Aaah, the pain or ParagraphEditor refactoring ;-)

by Michael Rueger

Hi all, while further battling full unicode support I ended up refactoring ParagraphEditor to the extend that there a no references to the inst var sensor left. There are still a few references to the global Sensor though. With moving the model inst var down we could now basically get rid of class Controller :-) Class KeyboardBuffer is gone already. All that needs to be done is moving the utility methods in ScreenController to e.g. Display so we can remove that subclass of Controller as well. Volunteers? Michael

Feb. 24, 2009

Re: [Pharo-project] looking for Unicode testers

by Michael Rueger

Igor Stasenko wrote: > what is not very convenient is that copy/paste (as well as the rest of > keyboard shortcuts ) is not working when keyboard layout not english. If you could be so kind to tell me what comes back in slot 3 of the input event on your Russian keyboard if you simply type the equivalent of 'xcv' (without alt or ctrl)? I'm interested in what comes back on the keyDown and the keystroke event. Thanks Michael

Feb. 24, 2009

Re: [Pharo-project] suggestion for the category chooser

by Geert

Igor Stasenko wrote: > >> it would be nice to use things like browser's search bar, so when you >> start typing, a list pops up with >> suggested names. > Are you referring to the search bar which displays "C... (class search), i... (implementor search), #C... (class ref search), #s... (sender search)"? How does this search bar actually work? -- View this message in context: http://n2.nabble.com/suggestion-for-the-category-chooser-tp2371841p2375675.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 24, 2009

Re: [Pharo-project] Which Mondrian ?

by Alexandre Bergel

The last version of Mondrian should be in a usable state very soon. PERT diagram can be trivially modeled in Mondrian. What I can suggest, is to download the last version of Mondrian. Have a look at the class MOReadme. It contains few examples. Do not hesitate to get in touch with me privately for help. Cheers, Alexandre On 23 Feb 2009, at 22:26, David RÃ¶thlisberger wrote: > Hi CÃ©drick, > >> As I need to draw a PERT diagram, I decided to give Mondrian a try. >> >> I had a version (ported by Lukas [1]) used in OB which I started to >> use and read doc (code doc :) ). And I saw that Alexandre (Bergel) is >> working on improving another version [2]. >> >> So, which one to use (knowing that I use OB) ? I think there are >> differences... > > I will port the visualizations used in OB to the latest version Alex > is > working on, as soon as he finished his work. > Thus in the long run, OB will use Alex' version of Mondrian which is > (imo) still loosely based on the version Lukas originally ported > from VW. > > So I suggest you to use the latest version of Mondrian on Squeaksource > for new projects. > Alex can tell you more about its status. > > David > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 23, 2009

Re: [Pharo-project] Towards Pharo 1.0

by David Pennell

Milestone 3 includes - closures (may be with the changes of mathieu with a new image format) Didn't we pickup Eliot's recent closure work? If so, how do the two relate? On Mon, Feb 23, 2009 at 1:45 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi all, > > Marcus, Stef and I have been meeting today and we discussed how to > proceed for the first release (version 1.0). On the issue tracker we > tagged issues that we think should be fixed with "milestone-1.0". See > the following list: > > http://code.google.com/p/pharo/issues/list?q=milestone:1.0 > > If we missed something critical, please let us know. > > > > Furthermore, we updated the high-level milestones list that is on the > wiki (http://code.google.com/p/pharo/wiki/Milestones) The most > notable change is that we removed Alien FFI and moved it to milestone > 1.1. > > FUNCTIONAL REQUIREMENTS > â¢ (x) Integrate Polymorph > â¢ (x) Integrate TrueType? > â¢ (x) Refactor Traits API > â¢ ( ) default in-image font(s) > â¢ ( ) Main EToys removal, reorganize MorphicExtras?- > â¢ ( ) Package management system with stable and unstable > distributions > â¢ ( ) Remove SqueakMap? and Installer from core > > NON-FUNCTIONAL REQUIREMENTS > â¢ (x) First consistent version of the website > â¢ ( ) All tests green > â¢ ( ) Clean up package and class category organization > â¢ ( ) License clean (check OLPC changes) > â¢ ( ) Pharo one-click image (including developer tools, > GettingStarted information, screenshots, ...) > â¢ ( ) New sources file > > INFRASTRUCTURE > â¢ (x) Increase efficiency of producing new updates > â¢ ( ) Prepare second update stream to maintain released version > > > Cheers, > Adrian > > ___________________ > http://www.adrian-lienhard.ch/ > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 23, 2009

Re: [Pharo-project] suggestion for the category chooser

by Igor Stasenko

2009/2/22 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi > > I think that the category chooser could be improved to avoid to have > to type twice the category. > Right now > if I want to create a category I have to know up front whether it > exist or not > then I have to select new if it does not > else if naively I type the new cat the ui tells me well that it is > not defined > but in such a case I have to retype it. > > The solution could be > remove the fact that for new category we have to press new... > when the user enter the category whether it matches or not return the > string > that the user entered modulo with its matched string in the list. > > This way as a user I do not have to choose upfront. > I want to create a cat > I either select on the list > or I type and there is one which I can select > or I type and there is none in the list so we get a new one the I > typed. > it would be nice to use things like browser's search bar, so when you start typing, a list pops up with suggested names. > 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.

Feb. 23, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Alexandre Bergel

> â¢ ( ) New sources file I do not get this one. > â¢ ( ) Prepare second update stream to maintain released version Why would you need a second update stream? PharoInbox2 ? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 23, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Adrian Lienhard

Both are "mandatory": ( ) means not done yet (x) means completed For some reason, [ ] has some special meaning with the wiki syntax IIRC Cheers, Adrian On Feb 23, 2009, at 23:02 , Geert wrote: > > What happens with the requirements () which are not marked with (x) > to be > included in milestone version 1.0? Or are the (x) mandatory release > requirements and () optional? > > If the "default in-image font(s)" requirement is possible it may be > a good > idea since it is all part of the first impression. Anyhow, great > job so far > is all I can say :) > -- > View this message in context: http://n2.nabble.com/Towards-Pharo-1.0-tp2373983p2374656.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 23, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Marcus Denker

On 23.02.2009, at 23:02, Geert wrote: > > What happens with the requirements () which are not marked with (x) > to be > included in milestone version 1.0? Or are the (x) mandatory release > requirements and () optional? > no, (x) is done, () will be done :-) > If the "default in-image font(s)" requirement is possible it may be > a good > idea since it is all part of the first impression. Anyhow, great > job so far > is all I can say :) thanks! -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 23, 2009