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

Re: [Pharo-project] about GLMOrangeUITheme [WAS] Re: [update 1.2] #12302

by Igor Stasenko

On 14 January 2011 09:32, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > I agree that there should be only one, platform independent look-and-feel. I think the goal of such a theme would be to be slick and fast. > agreed. > Now, regarding the GLMOrangeTheme, the name is a bit confusing because the theme does a bit more than just setting a color. > agreed, usually if you look at other theme(s) for various UI frameworks they having a theme bundled with a number of presets, so the most elements of look and feel are the same, but colors are different. It is like subtheme in theme. That's why its good to support settings, so people could change them and save their own preset. So, users could pick a theme and then second level appears (if theme supports it), where they can pick a preset. > I like the idea of settings, and I will try to make the Glamorous Theme use it. > > Cheers, > Doru > > > -- Best regards, Igor Stasenko AKA sig.

Jan. 14, 2011

Re: [Pharo-project] about GLMOrangeUITheme [WAS] Re: [update 1.2] #12302

by Tudor Girba

Hi, I agree that there should be only one, platform independent look-and-feel. I think the goal of such a theme would be to be slick and fast. Now, regarding the GLMOrangeTheme, the name is a bit confusing because the theme does a bit more than just setting a color. I like the idea of settings, and I will try to make the Glamorous Theme use it. Cheers, Doru On 14 Jan 2011, at 00:58, Igor Stasenko wrote: > On 13 January 2011 21:57, Alain Plantec <alain.plantec(a)free.fr> wrote: >> Hi all, >> yes, I agree >> >> list selection and selection colors (and some others) can be changed from >> the setting browser. >> I think that in the core only the default theme should be present. >> The others should be packaged separately and loadable on-demand or >> when a package is loaded as it is for moose/glamour. > > +1 > i think we should get rid of all themes and leave only single default one. > > Actually today i was attempting to make sure that orange could be turned into > any other color of choice by picking a different color in settings. > Unfortunately its not so easy, because some widget do not honor / > using theme settings correctly. > > And theme by itself not always honors the settings. > > As a wish for future, i think we should fold all UI settings under a > per-theme settings, > so when user selects a concrete UI theme, then theme could control, > which UI Settings > it makes public and this allows to be modified, and which are not, and > should always use built-in (like window color or icons). > > Then theme could control whether it supports changing particular setting or not. > For instance i could use single color (orange) to define colors for > multiple things: > - Menu selection color > - Find replace selection color > ... others > > and to user show only 'Selection color' > > > >> Cheers >> Alain >> > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "Beauty is where we see it."

Jan. 14, 2011

Re: [Pharo-project] [update 1.2] #12297

by Tudor Girba

Done. Doru On 14 Jan 2011, at 09:06, StÃ©phane Ducasse wrote: > doru > could push a new version in the inbox? > > Stef > > On Jan 13, 2011, at 11:09 PM, Tudor Girba wrote: > >> I like the simple border around the windows. I adopted it in the Glamorous Theme :) >> >> Cheers, >> Doru >> >> >> On 13 Jan 2011, at 19:36, Igor Stasenko wrote: >> >>> here is updated version of it. >>> more consistent colors >>> (note the ">" button now not highlighted by default, >>> also added thin border for lists >>> and thin border for system windows, >>> and removed 1pixel-wide shadow for system window. >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> <GLMOrangeUITheme.st><GLMOrangeUITheme.png> >> >> -- >> www.tudorgirba.com >> >> "Relationships are of two kinds: those we choose and those that happen. They both matter." >> >> >> >> >> >> > > -- www.tudorgirba.com "Value is always contextual."

Jan. 14, 2011

Re: [Pharo-project] Issue 3522 in pharo: wiki like help contents

by pharo＠googlecode.com

Comment #9 on issue 3522 by aplan...(a)gmail.com: wiki like help contents http://code.google.com/p/pharo/issues/detail?id=3522 SLICE-Issue-3522-wiki-like-help-contents in InBox Thanks a lot Torsten, I let you test it and tag this issue as fixed if its ok.

Jan. 14, 2011

Re: [Pharo-project] [update 1.2] #12297

by StÃ©phane Ducasse

doru could push a new version in the inbox? Stef On Jan 13, 2011, at 11:09 PM, Tudor Girba wrote: > I like the simple border around the windows. I adopted it in the Glamorous Theme :) > > Cheers, > Doru > > > On 13 Jan 2011, at 19:36, Igor Stasenko wrote: > >> here is updated version of it. >> more consistent colors >> (note the ">" button now not highlighted by default, >> also added thin border for lists >> and thin border for system windows, >> and removed 1pixel-wide shadow for system window. >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> <GLMOrangeUITheme.st><GLMOrangeUITheme.png> > > -- > www.tudorgirba.com > > "Relationships are of two kinds: those we choose and those that happen. They both matter." > > > > > >

Jan. 14, 2011

Re: [Pharo-project] How to bundle an application with icons?

by Fernando Olivero

Hi Dimitry , i've did an external icon family importer and manager. It's in squeaksource, under the name of ExternalIconFamily. Gofer it squeaksource: 'ExternalIconFamily'; package: 'ExternalIconFamily'; load. This framework allows importing and managing any external icon family. Once imported , the icon family is reified into the image, as a subclass of ExternalIconFamily. As an example it comes with a tiny subset of the Oxygen icon family imported. Try out this examples: ExternalIconFamilyOxygenTinySubsetExample openAllIcons morph := ImageMorph named: 'apply' size: 64 familyNamed: 'OxygenTinySubsetExample'. morph openInWorld. I've posted a couple of screenshots to the mailing list last year, with Examples for the complete set of Oxygen icons, the tango icons and the World Flag icons. If you want i can upload the generated classes , filed out in .st files. Let me know if it works for you! Fernando pd: Smalltalk and Metaprogramming rocks! The importer is heavily based on programmatically adding class methods. pd: look at the squeaksource page for more detail on creating your own families. I should create a help system book also. On Thu, Jan 13, 2011 at 7:43 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I know that fernando was building an infrastructure for icons. > But I did not see him recently on the list. > > Stef > > On Jan 12, 2011, at 3:50 PM, Dimitry Golubovsky wrote: > >> Hi, >> >> Suppose I need to bundle a Pharo application (a package) I am >> developing with some custom icons: is there any "standard"/ >> agreed-upon method to do that in Pharo? >> >> For example the MenuIcons class includes byte strings (automatically I >> assume) converted from some external PNG files that show up as icons >> with menu items: which tool can be used to create a class with set of >> icons for an arbitrary application? >> >> If I want to reuse icons for standard actions in my application, which >> is the proper way to access menu icons other than to directly access >> these stored images? >> >> Thanks. >> >> PS Other than the "by example" books (both Squeak and Pharo) which >> give some basics of building GUI for applications, are there any >> general guidelines for GUI building in these systems? >> >> -- >> Dimitry Golubovsky >> >> Anywhere on the Web >> > > > On Thu, Jan 13, 2011 at 3:45 PM, Dimitry Golubovsky <golubovsky(a)gmail.com> wrote: > OK, great. Thanks everybody who answered. > > The response from HernÃ¡n mentioning the > createNewIconMethodsFromDirectory: method looks interesting. > > I'll try the other methods too. > > Thanks. > > -- > Dimitry Golubovsky > > Anywhere on the Web > >

Jan. 14, 2011

Re: [Pharo-project] Socket question (Was Re: Xtreams up to date)

by mkobetic＠gmail.com

BTW, would this snippet be useful as a basic Socket smoke test ? Or is that already covered somewhere ? | input output listener process sync | sync := Semaphore new. listener := Socket newTCP. listener listenOn: 9999 backlogSize: 10. process := [ [ input := listener waitForAcceptFor: 10. sync signal ] ensure: [ listener close ] ] fork. output := Socket newTCP. output connectTo: #[127 0 0 1] port: 9999. sync wait. [ #( 64 1024 2048 4096 8192 ) do: [:dataSize || data | data := ByteArray new: dataSize. 1 to: data size do: [:i | data at: i put: (i - 1) \\ 256]. 1 to: 10 do: [:each | output sendData: data]. 1 to: 10 do: [ :each || result index | index := 1. result := ByteArray new: dataSize. [ index := index + (input receiveDataInto: result startingAt: index). index > dataSize ] whileFalse. result = data ifFalse: [ result halt]]] ] ensure: [ output close. input close ]

Jan. 14, 2011

Re: [Pharo-project] Socket question (Was Re: Xtreams up to date)

by mkobetic＠gmail.com

OK, with two minor tweaks the socket streams started to behave better for me. The whole suite passes sometimes, although the results get often spoiled by transient failures which suggest a race condition in transform write stream. I think it's the the same one I occasionally see on VW side although it's quite rare there. But the fact that it comes up more frequently on Squeak side should help figuring it out, since it makes it more reproduceable. We'll see.

Jan. 14, 2011

Re: [Pharo-project] Issue 3522 in pharo: wiki like help contents

by pharo＠googlecode.com

Updates: Cc: stephane.ducasse Comment #8 on issue 3522 by Torsten....(a)astares.de: wiki like help contents http://code.google.com/p/pharo/issues/detail?id=3522 (No comment was entered for this change.)

Jan. 14, 2011

Re: [Pharo-project] Issue 3522 in pharo: wiki like help contents

by pharo＠googlecode.com

Comment #7 on issue 3522 by Torsten....(a)astares.de: wiki like help contents http://code.google.com/p/pharo/issues/detail?id=3522 Attached is the new code WikiStyleHelp.6.cs wich allows to use two pragmas: <wikiStyleHelp:> AND <wikiStyleHelp:syntax:> First one is only a shortcut for <wikiStyleHelp: 'blah' syntax: #pier> since #pier is the default syntax (and the only one that is currently supported here). Feel free to work on WikiStyleHelpBuilder to support other syntaxes if required (maybe the help builder should delegate to syntax helper classes or the like). Also attached is a Foo.st example with two annotated methods that demonstrates the use of the pragmas. You can load Foo.st first, since it is pragma based AND DOEST NOT DEPEND on help system in any way. Attachments: Foo.st 911 bytes WikiStyleHelp.6.cs 6.5 KB

Jan. 14, 2011