February 2009 - Pharo-dev - lists.pharo.org

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

by Igor Stasenko

2009/2/24 Michael Rueger <m.rueger(a)acm.org>: > 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. > Yes! Yes! No direct refs to Sensor, please! :) > 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? > i'd really like to help but i currently swamped by own stuff :) > Michael > > _______________________________________________ > 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. 24, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Lukas Renggli

> PS Some bright person might want to code up some RB find templates to > look for methods > where if you use the closure VM it will possibly Â give you different > behaviour than with the > current VM. Wouldn't it also require to recompile all methods to get closures? Have a look at the senders of #fixTemps. I have 37 senders in the latest Pharo image. These are all places where people had to work around the shortcomings of the Squeak blocks. With block closures enabled these blocks should behave the same without fixing their temps. For more examples the Seaside code base has a vast collection of places where it has to work around missing closures. For portability reasons this is done using #fixCallbackTemps. > Unless of course everyone feels comfortable in turning block closures > on, and assuming nothing > will change? It could be that some code breaks, because closures behave subtly different. However if people depend on such code, then it is ambiguous and buggy in the first place. I think that closures should be included into mainstream VMs and images as fast as possible. It is a **major** annoyance that Squeak has no full block closures even in 2009. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 24, 2009

Re: [Pharo-project] looking for Unicode testers

by Igor Stasenko

2009/2/24 Michael Rueger <m.rueger(a)acm.org>: > 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. > I tried something like this [ | event | event := Sensor peekEvent. event ifNotNil: [ ((event first = 2) and: [event fourth = 1] ) ifTrue: [ Transcript show: (event third printStringRadix: 16); cr. ] ] ] repeat but it not shows anything :( Have a snippet which i can run to show key codes? > Thanks > > Michael > > _______________________________________________ > 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. 24, 2009

[Pharo-project] [ANN] prebuilt #10243

by Marcus Denker

http://gforge.inria.fr/frs/download.php/18189/Pharo0.1Core-10243.zip CHANGELOG: ========== ------------------------------------------------- update10237 Issue 464: Added subclass: and subclass:instanceVariableNames: Issue 456: 7272: BlockContext equality test is missing Issue 518: -94 asInteger --> 94 SUnit-al.59: Make edge case where method is an object work. Tests-al.41: Clean up TestObjectsAsMethods (do a proper tearDown) ------------------------------------------------------ update10238 Issue 425: TransferMorph eats events (Mantis #7251) Issue 585: Add floatAt:bigEndian: in order to read IEEE 32 bits single precision float in byte arrays Issue 515: lowSpaceWatcher causes DNU interruptName:preemptedProcess: Kernel-AlexandreBergel.260: the menu in pluggabletext editor has been extended with tallyIt ScriptLoader-david_roethlisberger.761: fixed #loadOBAlpha and #loadSuperOB in ScriptLoader System-david_roethlisberger.221 Tools-david_roethlisberger.141: extended SystemNavigation and ToolSet to browse implementors and senders in dedicated browsers instead of showing them in a generic message list browser Traits-damiencassou.261: Implements TraitBehavior>>poolDictionaryNames for polymorphic use with classes ------------------------------------------------------ update10239 Issue 542: Message sent but not implemented: SimpleButtonDelayedMenuMorph Issue 544: Message sent but not implemented: HostSystemMenusProxy Issue 418: CMD + o on the pharo desk returns a DNU Issue 129: Object>>isTransparent (#method not yet removed, that will follow) ------------------------------------------------------ update10240 Issue 588: remove Object>>#isTransparent Issue 589: Project switching gives DNU Issue 592: add Unix epoch creation/conversion methods to DateAndTime Issue 593: fix seaside29 loading script Issue 590: fix some methods for newcompiler (. after method name) ------------------------------------------------------ update10241 - Traits implementation refactoring (no sharing of compiled methods and source) - New tests for Traits MOP - ScriptLoader fixes (cleanUpForRelease, loadOneAfterTheOther:merge:silently:) ------------------------------------------------------ update10242 Issue 598: remove SquishedNameMorph Issue 597: remove #isNonZero Issue 458: Decompiler bug : (MCMergeBrowser >> #conflictSelectionDo:) decompile Issue 3: Utilities offerCommonRequests Issue 481: [Pending Etoy Cleaning] Object>> updateThresholdForGraphicInViewerTab Issue 492: [Pending Etoy Cleaning] Morph>>defaultValueOrNil Issue 599: SmaCC cant find silence in Sound Library Issue 583: Move UpdatingRectangleMorph out of etoy package ------------------------------------------------------ update10243 Issue 600: remove non-ascii from String>> asCharacter, recompile PluggableTextMorph>>drawOn: -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 24, 2009

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

by Igor Stasenko

2009/2/24 Geert <geert.wl.claes(a)gmail.com>: > > > 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? > no i talking about web browser.. sorry wasn't specific :) > > -- > 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. > > > _______________________________________________ > 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. 24, 2009

Re: [Pharo-project] Towards Pharo 1.0

by John M McIntosh

On 23-Feb-09, at 11:15 PM, Marcus Denker wrote: > > On 24.02.2009, at 00:40, David Pennell wrote: > >> 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? > > Yes. (so either this is an error or for confusing the enemy ;-) Ok, well Eliot pushed the closure code out the door, we need to build VMs to exploit it. I've not been able to build the macintosh os-x carbon VM based on it yet. Spent the day trying to integrate Craig's Spoon work with most current VMMaker. Tomorrow (tuesday) I'll see about building a new closure VM. I note this will be a 4.0.0 VM to note the change from a non-closure to closure VM PS Some bright person might want to code up some RB find templates to look for methods where if you use the closure VM it will possibly give you different behaviour than with the current VM. Unless of course everyone feels comfortable in turning block closures on, and assuming nothing will change? -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Feb. 24, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Marcus Denker

On 23.02.2009, at 23:07, Alexandre Bergel wrote: >> â¢ ( ) New sources file > > I do not get this one. Do we ship Pharo with Squeak39.sources or Pharo1.sources? > > >> â¢ ( ) Prepare second update stream to maintain released version > > > Why would you need a second update stream? PharoInbox2 ? No. that what happens when you press "update"... 1.0 will get important bugfixes even while 1.1 is under development. (There are some serious users involved in Pharo, e.g. companies that plan to use it in production, or university people who want to torture their students with it). Marcus -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 24, 2009

Re: [Pharo-project] Towards Pharo 1.0

by Marcus Denker

On 24.02.2009, at 00:40, David Pennell wrote: > 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? Yes. (so either this is an error or for confusing the enemy ;-) > If so, how do the two relate? Very similar. Marcus > > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 24, 2009

Re: [Pharo-project] [SPAM] Pharo-project Digest, Vol 10, Issue 100

by Provoost, P (Paul)

Sorry, had to reply: the mailing list is considered spam otherwise by my email server .. _____________________________________________________________ This email (including any attachments to it) is confidential, legally privileged, subject to copyright and is sent for the personal attention of the intended recipient only. If you have received this email in error, please advise us immediately and delete it. You are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept responsibility for any loss or damage arising from the viruses in this email or attachments. We exclude any liability for the content of this email, or for the consequences of any actions taken on the basis of the information provided in this email or its attachments, unless that information is subsequently confirmed in writing. If this email contains an offer, that should be considered as an invitation to treat. _____________________________________________________________

Feb. 24, 2009

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

by Michael Rueger

Rob Rothwell wrote: > Michael > > Can you try this then and tell me if I got it right? Sorry I am not Seems to work in my image. > savvy enough to combine the removal of the class with the rest of the You could simply append the remove to the file using a text editor. Michael

Feb. 24, 2009