April 2011 - Pharo-dev - lists.pharo.org

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

by StÃ©phane Ducasse

Henrik what is your answer to problem 1 Problem 1 - the second announcement was never sent, because the first one broke the second was blocked. >> we should make sure that if an announcement leads to an error, other annoucements on the same emit should pass Because we can get the system down just because one guy can register a bug.

April 2, 2011

[Pharo-project] fancier tab morph

by Tudor Girba

Hi, In the context of Glamour, I worked on a Morphic tab widget a bit more and here is the status (see the screenshots for some examples): - it computes the pages lazily only when you want to first show the page - it provides the possibility of closing the tab - it offers the possibility of rendering a toolbar for each page displayed to the right of the pages. If you want to play with them, you can: - download the latest moose image: http://hudson.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/… - execute the following to get an example of closable tabs: GLMBasicExamples new accumulator openOn: 42 - execute the following to get an example of tabs with different toolbars attached (to the right): GLMBasicExamples new tabsWithDifferentActions openOn: 42 There are still a couple of issues left: - When the title of a tab is too large, it pushes the bounds of the pane beyond what is visible. - Also, when we have multiple tabs, they again go overboard. - Similar things happen with the toolbar. However, the good news is that Gary is looking into this :) Cheers, Doru -- www.tudorgirba.com "Relationships are of two kinds: those we choose and those that happen. They both matter."

April 2, 2011

Re: [Pharo-project] Solarized Color Scheme

by Ethan Schoonover

Tudor Girba <tudor.girba@...> writes: > > the red in @param in java does not work so it is strange The red has been revised for beta2 (it's the only color I had an alternate for -- two alternates actually, one of which was further tested and will be the final color). The old red was L value 45 and was the only accent color that dark. Red is very challenging in general (particularly given the contraints I set in order to toggle light and dark) and I have truly spent *days* testing reds for this scheme. No kidding. I dreamt Lab and hex values. The new red is L 50 which translates to sRGB space as a much less saturatedÂ value. > I tested it with Sim Daltonism: > http://michelf.com/projects/sim-daltonism/ > It does pretty well (except for Protanopia). I'll take a look at that tool as well. For what it's worth, I did do some testing (loaded the scheme into colorschemer and simulated color blindness) as well during the development of Solarized. What I finally came back to was ensuring that L*a*b lightness was accurate and consistent. My assumption was that L lightness would translate to an equivalent L lightness (regardless of *a*b perceived value) in most color blindness, but this may not be an accurate assumption. This would at least retain readability. I try to limit colors to "value added" accents only. Feedback from those interested in this issue specifically is welcome. I'm sure I could do some more work in this area. Best, Ethan Schoonover es(a)ethanschoonover.com

April 2, 2011

Re: [Pharo-project] who is using softSqueak and standard Squeak

by Patrick Barroca

Hello, I published the theme on squeaksource, it loads in 1.2 and 1.3. Repo is http://www.squeaksource.com/PBASandbox I named it StandardUITheme, On Fri, Apr 1, 2011 at 8:57 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Thanks > > I want to rename, repackage, glamourous and remove the bubble oriented > color squeak look and keep one old sq colored for now. > On Apr 1, 2011, at 3:04 PM, Patrick Barroca wrote: > > > Hello, > > > > Just to say that I have now a simple theme extending UITheme with the > look of Glamourous and the support of squeak windows colour management. > > > > Since I worked in 1.2 I have yet to verify how this load in Pharo 1.3 and > then I will publish it ;) > > > > On Wed, Mar 30, 2011 at 3:50 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > > My first look yesterday night taught me that different windows colour > management is a basic behaviour of UITheme via #patchworkUIThemeColorFor:. > > > If I simply subclass UITheme and do nothing more I get more or less a > standard squeak theme with coloured windows minus some fills and borders > styles. > > > > > > From here I think I could try to make a simple theme with the look of > Glamourous one with support for squeak windows colour management. > > > Is this the right direction ? > > > > yes :) > > I plan to refactor/clean the theme package too. > > So if you have results let us know. > > > > Stef > > > > > > > > -- > > Patrick Barroca > > -- Patrick Barroca

April 1, 2011

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