- Pharo-dev - lists.pharo.org

Re: [Pharo-project] forum.world.st is down

by Geert Claes

forum.world.st is back up again -- View this message in context: http://forum.world.st/forum-world-st-is-down-tp3421006p3421285.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 1, 2011

Re: [Pharo-project] forum.world.st is down

by Geert Claes

Nabble had hardware issues and have almost resolved the problem, the forum is back online but still sorting out the subdomain forum.world.st to point to the top level forum again. In the mean-time the forum is at: http://smalltalk.1294792.n4.nabble.com Apologies for the inconvenience on behalf of Nabble -- View this message in context: http://smalltalk.1294792.n4.nabble.com/forum-world-st-is-down-tp3421006p342… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 1, 2011

[Pharo-project] [ANN] XMLRPC Beta is out

by GermÃ¡n Arduino

Hi: xmlrpc beta version (including client and server) is out. To test, load ConfigurationOfXMLRPC and then evaluates: (ConfigurationOfXMLRPC project version: '1.0-Beta1') load: 'All'. The documentation is at: http://code.google.com/p/pharo-xmlrpc/ By now xmlrpc works in Pharo 1.1 and 1.2 but not in the lastest Squeak versions because the changes in HTTPSocket. This version relies in HTTPSocket at client level and in Komanche at server level. My intention is correct only bugs at this stage to think in new functions to possible new versions. Also a big refactoring is pending. Testers are welcome! -- ================================================= GermÃ¡n S. ArduinoÂ <gsa @ arsol.net>Â Â Twitter: garduino Arduino Software & Web HostingÂ Â http://www.arduinosoftware.com PasswordsProÂ http://www.passwordspro.com =================================================

April 1, 2011

Re: [Pharo-project] SMx ToDo

by Alain Plantec

Hi Farnando, maybe I've missed something, do you want to merge cuis morphic with Morphic of with SMxMorphic ? another question, SMxMorphic is really out-to-date regarding current cuis ? Alain Le 01/04/2011 16:04, Fernando Olivero a Ã©crit : > Alain, this is the notes i gathered so far. > > I list the Cuis morphs i believe we should integrate, and those which > we shouldn't. > > "Kernel" > LayoutMorph. > LayoutSpec. > Morph. > BorderedMorph. > PluggableMorph. > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "Common: merge?" > MouseClickState. "check". > MorphExtension. > GrafPort. > FormCanvas. > DamageRecorder. > EllipseMidpointTracer "for the GrafPort, check in Pharo?". > HandMorph. > PasteUpMorph. > WorldState. > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "basic Morphs" > ImageMorph. > RectangleMorph. > PolygonMorph. > StringMorph. > TransformMorph. > EllipseMorph. > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "basic widgets-cuis" > PluggableButtonMorph. > PluggableMessageCategoryListMorph. > BareTextMorph. > TextModelMorph. > > "basic widgets-common" > PluggableListMorph. > LazyListMorph. > PluggableListMorphByItem. > PluggableListMorphOfMany. > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "extra widgets" > SketchMorph. > FillInTheBlankMorph. > > "CUIS-extra-widgets" > OneLineEditorMorph. > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "Menus" > MenuItemMorph. > MenuLineMorph. > MenuMorph. > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "windows-common" > ScrollPane. > ScrollBar. > ScrollbarButton. > SystemWindow. > > "windows-new" > BrowserCommentTextMorph. > LayoutAdjustingMorph. > WindowEdgeAdjustingMorph. > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "other widgets" > ColorPickerMorph. > ProgressMorph. > ProgressBarMorph. > TranscriptMorph. > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "MorphicEvents" > "the same?" > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "ENHANCEMENTS" > "EditorState: Alains work that uses UndoManager, to provide unlimited > undos, and visual feedback or search and replace in the proper Text > presentation morphs" > "Add the icon management to THEME" > "Evaluate the polymorph features that are missing from (Cuis) Theme". > "more ?" > > "%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%" > "ommitted or removed" > HaloMorph. " and family, no halos for now" > BalloonMorph. "remove or replaced by a tooltip morph?, do we need a > special morph?" > MenuIcons. "moved to the themes in Pharo, themes own the icons to use" > UpdatingMenuItemMorph. "?" > TheWorldMenu. "pragma menu building on the WorldState in Pharo" > MinimalStringMorph. "no usage for now, omit until a real usage appears" > CurveMorph. "redundant maybe" > MVCMenuMorph. "removed MVC-morphic integration" > LimitedHeightTextMorph. "not used, only in examples, omit until a real > usage appears". > "LineMorph". "redundant: doesnt add behavior: remove?: replace by > PolygonMorph lineFrom:to: color: width:" > >

April 1, 2011

Re: [Pharo-project] Issue 3934 in pharo: Add isDisplayed in SystemWindow

by Fernando Olivero

Also #isInWorld relates more to Morphic terminology, than #isDisplayed. So if Ben agrees, i propose rolling back this change. On Fri, Apr 1, 2011 at 8:58 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > may be this is the same. > > Stef > >> Is not #isInWorld not sufficient? >> >> Regards, Gary >> >> ----- Original Message ----- From: <pharo(a)googlecode.com> >> To: <pharo-project(a)lists.gforge.inria.fr> >> Sent: Friday, April 01, 2011 4:09 PM >> Subject: [Pharo-project] Issue 3934 in pharo: Add isDisplayed in SystemWindow >> >> >>> Status: FixProposed >>> Owner: Benjamin...(a)gmail.com >>> Labels: Nautilus >>> >>> New issue 3934 by Benjamin...(a)gmail.com: Add isDisplayed in SystemWindow >>> http://code.google.com/p/pharo/issues/detail?id=3934 >>> >>> isDisplayed >>> " Answer true if I am a submorph of World, ie if I am displayed " >>> >>> Attachments: >>> SystemWindow.BenjaminVanRyseghem.1.cs Â 303 bytes >>> >> >> > > >

April 1, 2011

Re: [Pharo-project] SimpleMorphic adoption schedule

by Tudor Girba

Hi Fernando, On 1 Apr 2011, at 20:55, StÃ©phane Ducasse wrote: > > On Apr 1, 2011, at 1:48 PM, Fernando Olivero wrote: > >> HI Tudor, i guess porting and updating SMx from the latest version >> in CUIS, would be made around next week. >> >> This would give us: new Morph kernel, significantly simplified layout, >> basic widgets simplified and unified ( for example only one class for >> buttons) and anti-alised rounded corners for windows and buttons( Juan >> implemented this taking ideas from Morphic3, way better than the OS >> native widgets, just take a look at CUIS ). >> >> Then >> >> * Integrating Alain's editor state into the text morphs views >> shouldn't take more than one day. >> >> ( I believe Glamour only requires up to here). > > fernando I do not think so. Glamour needs more. > But we should start and see. Indeed. Glamour needs at least: - MorphTreeMorph - GeneralScrollPane or a replacement that has the ability of filling the space on one dimension and scroll on the other (like a finder on Mac OS) - TextMorph with keybindings customizable all the way, and with announcements sent for every little action - strong TabMorph with toolbar (I will send an announcement soon about the widget I have in Glamour) >> >> * When Ben releases Nautilus, we would have to port it to SMx. ( to >> have standard browsers) >> * Polymorph and SMx merge, would take quite a while, depending on the >> amount of people we get involved. >> >> So i dont know how much would it take to replace entirely Morphic with >> SMx, having all the features of Polymorph also. Highly depends on the >> people involved in this effort. >> >> But having a simple version of SMx, is feasible within 15 days . and >> then gradually add pieces till we can trash any Old-Morphic >> dependance. So, when will this happen then? :) I have some time now and I can offer some testing. Cheers, Doru >> Fernando >> >> On Thu, Mar 31, 2011 at 12:56 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>> Hi Fernando, >>> >>> These are good news. >>> >>> I am very interested in using this in Glamour. Just one question: What is the expected schedule? >>> >>> Cheers, >>> Doru >>> >> > > -- www.tudorgirba.com "Some battles are better lost than fought."

April 1, 2011

Re: [Pharo-project] Announcement real problems - please read and comment.

by Henrik Sperre Johansen

On 01.04.2011 21:07, StÃ©phane Ducasse wrote: > Hi guys > > We found a problem with ben and RPackage. > Here is the scenario and may be you can help us finding the right solutions. > > Nautilus renames a class > the class got renamed > -> an announcement is raised > - nautilus gets notified, it asks rpackageOrganizer (which also listens to the same event) > -> rpackageOrg breaks because the class if was referting to does not exist anymore. This sounds like mess in logic. You ask package of class that is in the process of being renamed? Why would you expect this to work? Use more announcements to represent multiple steps in renaming process, for example both ClassRenaming and ClassRenamed. Changing it's package is something you do as an action that should be _part_ of renaming, while updating it's location is something you would do _after_ renaming is complete. > Problem 2 > If rappckageOrganizer would be reached before Nautilus we would not get any problem (beside the problem 1). > > - we spent one hour playing with alternatives. > We thought that if RPackage would points to classes a rename would not break the system. > While this is true for class, the same problem will occur for method rename since compiled method are not shared and a new compiled method > is compiled. > > - If RPackage was as deep inside the system as superclass/subclass, the invariant would be directly maintained by the system > and we would not have to rely on announcement. But now we should find a solution. > > >> may be we should be able to say that an announcement has a priority. > Typically we would like to say that when RPackageOrganizer register interests it should be served first. > we could have a systemLevel priority that could be specified on registration. > > what do you think? Bad, bad, bad, bad, baaaaaad idea. I know from experience that once you concede that announcement listener order should matter, you are setting yourself up to fail. Although you know one listener _HAS_ to respond first, there will always be someone else who want to respond "firstester". Not to mention the logic in this case becomes next to impossible to follow/debug/ maintain, as you've already experienced. For a proper solution, introduce more Announcements for actions which should happen in different phases of a process, as explained above. Cheers, Henry PS. I was unable to load RPackage. The initialize method of PackageOrganizer in RPackage-Core calls registerInterestToSystemAnnouncement, which is an extensions in RPackage-SystemIntegration. PPS. There's a neat method called #on:send:to:, which would be perfect for the different actions in RPackage-SystemIntegration. PPPS. Is the code for Nautilus available anywhere?

April 1, 2011

Re: [Pharo-project] Solarized Color Scheme

by Tudor Girba

Hi, On 1 Apr 2011, at 20:53, StÃ©phane Ducasse wrote: > the red in @param in java does not work so it is strange > same remarks for ruby. > Now the text color is nice and lavande are nice but I wonder for color blind people I tested it with Sim Daltonism: http://michelf.com/projects/sim-daltonism/ It does pretty well (except for Protanopia). Cheers, Doru > On Apr 1, 2011, at 1:27 PM, Tudor Girba wrote: > >> Interesting link. Thanks. >> >> Cheers, >> Doru >> >> >> On 1 Apr 2011, at 13:22, Sven Van Caekenberghe wrote: >> >>> I remember there were some discussions about (theme / syntax highlighting) colors on this list in the past, and someone said that picking good colors is an art. I came across this site: >>> >>> http://ethanschoonover.com/solarized >>> >>> And it seems to me that this could be a good basis for a professional color scheme in one of Pharo's look and feels. As a fan / user of Glamorous, using the light theme on top of it would seem great. >>> >>> I am just posting this as a way to bookmark this link and because it might be useful. >>> >>> Solarized is MIT licensed. >>> >>> Sven >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Problem solving efficiency grows with the abstractness level of problem understanding." >> >> >> >> > > -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

April 1, 2011

[Pharo-project] http://www.mirandabanda.org/files/Cog/VM/VM.r2378/

by Eliot Miranda

Hi All, these fix the recent FFI bug and revert the HostWindowPlugin and SoundPlugin to the trunk VMs (away from the Teleplace versions). http://www.mirandabanda.org/files/Cog/VM/VM.r2378/ enjoy. Eliot

April 1, 2011

Re: [Pharo-project] Issue 3939 in pharo: Small DSA refactorings from squeak

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3939 by nicolas....(a)gmail.com: Small DSA refactorings from squeak http://code.google.com/p/pharo/issues/detail?id=3939 Name: SLICE-Issue-3939-DSA-refactorings-nice.1 Dependencies: System-Hashing-nice.13

April 1, 2011