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

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

by StÃ©phane Ducasse

For me I got blue when I applied the fix. On Jan 13, 2011, at 10:45 AM, Torsten Bergmann wrote: > Stef wrote: >> indeed igor this is nice. >> Doru may be you could take this change for your look? > > Do you really think this orange is an improvement? > See attached comparision. Do we want to go back to colorfull > "toy" style a la Squeak? > > UI always depends on personal style but we should > take care to keep it looking professional. > > We should really hire a designer! do you have money? S.

Jan. 13, 2011

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

by Sven Van Caekenberghe

Martin, On 12 Jan 2011, at 19:13, mkobetic(a)gmail.com wrote: > I started looking at the Socket failures that I can reproduce and I can't wrap my head around the SocketReadingWritingTest>>setUp. Based on what I know about TCP sockets it doesn't make sense to me. AFAIK to get both ends of a connected TCP connection (lacking a socketpair call) I need 3 sockets. A listening socket, a client socket (doing connect) and finally the server socket that comes out as a result of accept on the listener. So I'd expect to see something like this in the setUp: > > | data input output listener socket1 socket2 process sync | > Socket initializeNetwork. > sync := Semaphore new. > listener := Socket newTCP. > listener listenOn: 9999. > process := [ [ socket1 := listener accept ] ensure: [ listener close ]. sync signal ] fork. > socket2 := Socket newTCP. > socket2 connectTo: (NetNameResolver localHostAddress) port: 9999. > sync wait. > output := socket1 reading. > input := socket2 writing. > > Surprisingly, the above doesn't work, while many of the Socket tests seem to pass for me despite my brain telling me that it can't possibly. Can anyone shed some light on this for me ? I have been playing around a little bit with your example and this works for me (Pharo 1.1.1 + Xtreams): | data input output listener socket1 socket2 process sync | data := #uninitialized. sync := Semaphore new. listener := Socket newTCP. listener listenOn: 9999 backlogSize: 10. process := [ [ socket1 := listener waitForAcceptFor: 10. socket1 waitForDataFor: 10. output := socket1 reading. data := output rest. sync signal ] ensure: [ listener close ] ] fork. socket2 := Socket newTCP. socket2 connectToHostNamed: 'localhost' port: 9999. input := socket2 writing. input write: 'Hello!'. sync wait. data asString Of course, you still have to close some sockets, but you get the idea. HTH, Sven PS: Yes, Socket (and friends) have some pretty confusing API, you have to stick to what you know that works ;-)

Jan. 13, 2011

Re: [Pharo-project] [Seaside] Re: html parser

by StÃ©phane Ducasse

Doru I started to write more comments, tests.... I started to write a ConfigurationOfSoup but I need more time or help. Soup allows you to do scraping of web site by navigating inside a limited set of nodes. Stef On Jan 13, 2011, at 11:32 AM, Tudor Girba wrote: > Thanks. > > Doru > > On 13 Jan 2011, at 10:55, Francois Stephany wrote: > >> Soup ? >> http://www.squeaksource.com/Soup >> >>> Is there a robust html parser in Pharo? As I understand, there would be one in VW called TwoFlowers, but I do not know the license. >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -- > www.tudorgirba.com > > "Don't give to get. Just give." > > > > > >

Jan. 13, 2011

Re: [Pharo-project] about text selection colors in 1.2

by StÃ©phane Ducasse

On my mac I always use orange for selection else I do not see it and I'm not color blind. Stef On Jan 13, 2011, at 11:27 AM, Alain Plantec wrote: > Le 13/01/2011 11:16, Mariano Martinez Peck a Ã©crit : >> >> >> On Thu, Jan 13, 2011 at 10:39 AM, Alain Plantec <alain.plantec(a)free.fr <mailto:alain.plantec@free.fr>> wrote: >> >> Hi all, >> A friend of mine told me that it was very difficult for him to see >> the difference between the >> green and the blue colors. (Color blindness...) >> So, I would suggest to change the secondary selection color >> (green) to another color. >> >> >> yes, the green is very very difficult to see. > yes, this had to be changed >> >> What do you think ? which color ? >> >> >> light yellow? grey ? I don't know :( > for testing, you can change it from the setting browser >> >> Cheers >> Alain >> >> >> > >

Jan. 13, 2011

Re: [Pharo-project] Dirty MC Packages in Pharo-1.1.1-OneClickCogVM

by Schwab,Wilhelm K

Stef, True. But it also got caught, perhaps because it was where it had no business being. The great thing about configurations and Hudson is that the server will build multiple artifacts. I think among them should be some bloated images for reasons just like this. The core and a leaner dev would also be in the mix. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Thursday, January 13, 2011 3:27 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Dirty MC Packages in Pharo-1.1.1-OneClickCogVM why do you need method wrapper in dev? Again this goes with my mail about pushing metacello dsitributions versus pharo-dev+++ Stef On Jan 12, 2011, at 10:15 PM, Mariano Martinez Peck wrote: > yes, that was a hack I had to do becuase at that moment Cog didn't support well objects as methods, used by MethodWrappers, and when running its tests, it crashed. > we wanted to create a quick image so that people could start using cog and help testing it. > > this is not the case anymore in Pharo 1,2 > > so, if someone wants, the real solution is to create a new one click of 1.1.1 (without touching by hand method wrappers) and put new CogVMs. > > cheers > > mariano > > On Wed, Jan 12, 2011 at 8:10 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > Yesterday I downloaded Pharo-1.1.1-OneClickCogVM from > > https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip > > and I noticed it has two dirty MC packages (MethodWrappers and Tests). > > This is probably a glitch, but not nice and confusion for beginners. > > Sven > > >

Jan. 13, 2011

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

by HernÃ¡n Morales Durand

By the way you may use too MenuIcons createNewIconMethodsFromDirectory: 'C:\MyIcons\' filenames: #('icon1' 'icon2' ...) classified: '*myresourcespackage' Cheers, 2011/1/12 Dimitry Golubovsky <golubovsky(a)gmail.com>: > 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 > >

Jan. 13, 2011

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

by HernÃ¡n Morales Durand

Hi Dimitry, Recently I did a little tool which I've used as a general resource importer, it's in beta state but you may use it for your purposes. Basically it takes files in a directory and imports them as "resources" or methods in a Smalltalk class. A resource is simply a Dictionary in a class variable where your resource will be imported. So you may store the imported resources (in your case icons) 1) As methods in a library class. The naming of selectors is taken from the file name, lowercasing the first letter and including the extension letters if found. 2) As 'resources' in a class variable acting as an IdentityDictionary. Obviously importing as resources is a LOT faster because it doesn't encode the images and also doesn't compile methods. To import pictures located in a folder in a class MyPicturesClass1 as methods, evaluate: LDPictureLibraryImporter named: #MyPicturesClass1. To import pictures as resources LDPictureLibraryImporter new importAsResources; named: 'MyPicturesClass2'. After you've finished the importing as methods you may want to explore: | pics | pics := MyPicturesClass1 new. ( MyPicturesClass1 organization listAtCategoryNamed: #autogenerated ) collect: [: sel | pics perform: sel ] In the case of resources just evaluate MyPicturesClass2 resources To try it: http://www.squeaksource.com/LibraryImporter.html Cheers, 2011/1/12 Dimitry Golubovsky <golubovsky(a)gmail.com>: > 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 > > -- HernÃ¡n Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.

Jan. 13, 2011

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

by Tudor Girba

I tried to avoid a lengthy mail, but now I need to explain. UI design should be approached with the same rigor as system design. A community is better than an individual in producing solutions, but only when the effort is in concert under a shared vision. If the arguments are just about "I like this better", the process transforms into a design by committee which usually leads to poor results. So, let me share my "vision". The first thing that design should address is functionality (although visual appeal has a significant weight, too). In general, when you want to design something you should ask yourself why do you need to do that. The intention of the Glamour-Morphic-Theme package is to offer a look that uses a minimum amount of graphical variables while allowing you to focus on the main content - which is that thing that you work on, not that thing that you use for your work. I tried to start from zero and add a new variable (e.g., color) only when I could not distinguish something. There are still things that are superfluous (e.g., the border around all tabs, or the bulky shape of an expander), but I did not have enough time and Morphic expertise to do better. Now, orange vs blue is actually not just a matter of taste because your orange is not the same as my blue. There are two reasons: (1) it is stronger, and (2) it appears in more places (e.g., at the bottom of the scrollbar). This means that it will compete for my attention with more force. This might be your intention, but it is not mine because it takes away from my main focus which is the content. Suppose you would make the orange have the same visual weight as the current blue, then it would still not be the same because orange does not mean the same as blue in the cultural meaning it tends to raise. For example, blue is usually perceived as more neutral than other colors, and I want to use blue for this reason (and also because it is the color of Moose). So, all in all, I do not want GLMOrangeUITheme in the Glamour-Morphic-Theme package :), but I do invite people with a UI design interest to build a shared vision that matches the one of the overall Pharo. Doru On 13 Jan 2011, at 11:46, Igor Stasenko wrote: > On 13 January 2011 11:29, Tudor Girba <tudor.girba(a)gmail.com> wrote: >> Hi, >> >> On 13 Jan 2011, at 11:12, Igor Stasenko wrote: >> >>> On 13 January 2011 10:41, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>>> Of course, it is MIT and you can do what you want with it. I simply answered the question from Stef, and I meant that I won't include it in the code from the Glamour repository. If you do want to modify it in the mentioned direction, I would kindly ask you to use a different name to avoid confusion and conflicts - this theme is used by the Moose distribution. >>>> >>> >>> Can you clarify: >>> a) you don't want to modify Glamorous theme (GLMUITheme) by taking >>> all methods from GLMUITheme2. >> >> Yes >> >>> b) you don't want to add a GLMUITheme2 , which is a subclass of GLMUITheme >>> because these changes could live in GLMUITheme2, which is perfectly >>> fine, while keeping an original GLMUITheme >>> not changed. >>> And we can call GLMUITheme2 a 'Glamorous orange' >>> :) >> >> Yes :). It's true that technically it would work, but from an intention point of view it does not fit. Also, in general, except on very few occasions, I won't support adding anything that has a number at the end to distinguish the name :). >> > > Not a big deal.. > We can rename it to > GLMOrangeUITheme > > and make available to Pharo people? > Still no? :) > >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "The coherence of a trip is given by the clearness of the goal." >> > > > -- > Best regards, > Igor Stasenko AKA sig. > -- www.tudorgirba.com "To lead is not to demand things, it is to make them happen."

Jan. 13, 2011

Re: [Pharo-project] [squeak-dev] Xtreams up to date

by Sven Van Caekenberghe

Hi Martin, On 12 Jan 2011, at 01:08, mkobetic(a)gmail.com wrote: > Hope it's OK to cross-post this, I figured there might be interested people on both sides. I finished the updates of the Xtreams port to match the VW version, so everything (that is available) should work as advertised in the documentation (http://code.google.com/p/xtreams/) > > Besides the implementation updates this last round of changes includes: > > * repackaging to match the docs and VW better, the dialect specific parts are now (mostly) gathered in Xtreams-Support > > * there is now a Gofer expression on the project page (http://www.squeaksource.com/Xtreams.html) to help people loading it, it shouldn't be hard to keep it up to date it shouldn't change very much > > * the source code is now identical between the dialects as much as possible, to help keeping it up to date. > > * one significant API change is that we renamed XTIncomplete to Incomplete to make code that uses Xtreams more portable. This is the only class that is very prominent in the API and hard to avoid in any sufficiently complex application, hopefully this is acceptable. > > I don't anticipate any significant changes in the port for next little while. I'd like to play with Squeak FFI next to see if I can bring the cryptographic streams from Xtreams-Xtras over and then see what it would take to get Xtreams-SSH2 running on Squeak and how it would perform. If you're curious how it went on VW side, I wrote about that in a blog post here: http://www.cincomsmalltalk.com/userblogs/cst/blogView. > > If you find bugs or issues, feel free to file an issue on the google project page (http://code.google.com/p/xtreams/issues/list) I'm monitoring both of these lists now as well and will try to answer any questions promptly. > > Cheers! > > Martin Thank you for all this work, this is a really interesting project, I am glad you are putting in the effort to bring this to Pharo/Squeak. I tried the Gofer script to load Xtreams into a fresh Pharo 1.1.1 #11414. This went OK for two issues: XTSqueakEncoder class>>initialize(name is shadowed) - more a warning I guess XTReadStream>>detect: (NotFoundError is Undeclared) - it seems other #detect: implementors just do self error: 'Not Found', but a real exception would be better Running all tests, I get 718 OK out of 731; 13 errors: Most of these are with sockets. I tried to look at one of the others XTFileReadingWritingTest>>#testWriteFromCollectionAt | data | data := #[1 2 3 4 5 6 7]. self assert: (self output write: 4 from: data at: 1) = 4. self assert: (self input read: 4) = (data first: 4). self assert: (self output write: 3 from: data at: 5) = 3. self assert: (self input read: 3) = (data last: 3) The failure is at the last assertion. If I understand the code correctly, you write to a file in 2 steps (and yes the file contains the data). The input stream is created lazily, after the first write. But it seems strange to me to expect an open reading file stream to see newly written data ? Closing/reopening input works as expected. So you are also testing a particular OS feature here IMHO. Maybe this works on some OS's but it does not seem to work for me (Mac OS X, Cog VM), but other elements might be involved (caching/buffering at various levels, vm, primitives, ..). I think all the non-socket failures have the same issue. Sven

Jan. 13, 2011

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

by Igor Stasenko

On 13 January 2011 11:29, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > On 13 Jan 2011, at 11:12, Igor Stasenko wrote: > >> On 13 January 2011 10:41, Tudor Girba <tudor.girba(a)gmail.com> wrote: >>> Of course, it is MIT and you can do what you want with it. I simply answered the question from Stef, and I meant that I won't include it in the code from the Glamour repository. If you do want to modify it in the mentioned direction, I would kindly ask you to use a different name to avoid confusion and conflicts - this theme is used by the Moose distribution. >>> >> >> Can you clarify: >> a) you don't want to modify Glamorous theme (GLMUITheme) by taking >> all methods from GLMUITheme2. > > Yes > >> b) you don't want to add a GLMUITheme2 , which is a subclass of GLMUITheme >> because these changes could live in GLMUITheme2, which is perfectly >> fine, while keeping an original GLMUITheme >> not changed. >> And we can call GLMUITheme2 a Â 'Glamorous orange' >> :) > > Yes :). It's true that technically it would work, but from an intention point of view it does not fit. Also, in general, except on very few occasions, I won't support adding anything that has a number at the end to distinguish the name :). > Not a big deal.. We can rename it to GLMOrangeUITheme and make available to Pharo people? Still no? :) > Cheers, > Doru > > -- > www.tudorgirba.com > > "The coherence of a trip is given by the clearness of the goal." > -- Best regards, Igor Stasenko AKA sig.

Jan. 13, 2011