- Pharo-dev - lists.pharo.org

Re: [Pharo-project] glamorous theme :)

by Sven Van Caekenberghe

Laurent, On 07 Sep 2010, at 08:47, laurent laffont wrote: > Using Glamourous I hardly see which button is focused in System Browser between instance or class. > So I've made mistakes several times yesterday :) You could try my subclass, it tries to solve that problem (to my taste anyway; Des goÃ»ts et des couleurs, on ne dispute / discute pas). It is in SqueakSource ADayAtTheBeach package Pharo-Hacking-Sven (it has 2 subclasses, one for the Pro theme as well). Sven

Sept. 7, 2010

Re: [Pharo-project] WebClient License Update

by StÃ©phane Ducasse

Thanks. > Hi - > > After careful consideration I've decided to put WebClient under the MIT license, and updated the repository at http://www.squeaksource.com/WebClient.html to reflect the license change. > > If you're curious why I'm making the change, the answer is really that the code isn't all that unique and even though I'm not done with it it's good enough to be released and by now I simply get more benefits from it being thoroughly tested by as many people as possible. That and the (to me surprising) amount of interest that WebClient has received in combination with the (to me disturbing) lack of due diligence that many users of WebClient apparently have. I think we can all take away a lesson from this little incident that even if you find some random code on the net it doesn't mean it's up for grabs. > > Also, if I may be so bold, let me propose the "2 step process to eternal license happiness". It's really simple: > > [ ] Did we check the license of the package? > [ ] Did we contact the author of the package? > > If you check off the above two steps whenever you're about to use some third-party code, I think you'll find that situations like the one we've encountered here are virtually impossible. Attach the steps to the bug tracker if you must, but follow them. > > Since you know how to verify the license status on your own, let me add the second step of the process and once more repeat that I would rather keep WebClient an externally loadable package. If at all possible I urge you to look at what has been done with HTTPSocket in Squeak and adopt a similar approach; that is provide a minimal internal HTTP interface and allow third-party libraries (WebClient or other) to hook into this interface. we will look at that. And do not worry I think that everybody learn a lesson in the process. > There is really no need to have everything tied together at the hip; HTTPSocket is a reasonable facade for HTTP requests in the kernel. > > Regarding write access to the WebClient repository, I'm not a fan of making repos world-writable (this is really a sign of abandonware) but due to the license I'm fine with granting Sven and Philippe write access if they want it (drop me a note if you do). > > Cheers, > - Andreas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 7, 2010

[Pharo-project] WebClient License Update

by Andreas Raab

Hi - After careful consideration I've decided to put WebClient under the MIT license, and updated the repository at http://www.squeaksource.com/WebClient.html to reflect the license change. If you're curious why I'm making the change, the answer is really that the code isn't all that unique and even though I'm not done with it it's good enough to be released and by now I simply get more benefits from it being thoroughly tested by as many people as possible. That and the (to me surprising) amount of interest that WebClient has received in combination with the (to me disturbing) lack of due diligence that many users of WebClient apparently have. I think we can all take away a lesson from this little incident that even if you find some random code on the net it doesn't mean it's up for grabs. Also, if I may be so bold, let me propose the "2 step process to eternal license happiness". It's really simple: [ ] Did we check the license of the package? [ ] Did we contact the author of the package? If you check off the above two steps whenever you're about to use some third-party code, I think you'll find that situations like the one we've encountered here are virtually impossible. Attach the steps to the bug tracker if you must, but follow them. Since you know how to verify the license status on your own, let me add the second step of the process and once more repeat that I would rather keep WebClient an externally loadable package. If at all possible I urge you to look at what has been done with HTTPSocket in Squeak and adopt a similar approach; that is provide a minimal internal HTTP interface and allow third-party libraries (WebClient or other) to hook into this interface. There is really no need to have everything tied together at the hip; HTTPSocket is a reasonable facade for HTTP requests in the kernel. Regarding write access to the WebClient repository, I'm not a fan of making repos world-writable (this is really a sign of abandonware) but due to the license I'm fine with granting Sven and Philippe write access if they want it (drop me a note if you do). Cheers, - Andreas

Sept. 7, 2010

Re: [Pharo-project] glamorous theme :)

by laurent laffont

Hi Doru, Using Glamourous I hardly see which button is focused in System Browser between instance or class. So I've made mistakes several times yesterday :) I really like this theme, especially on a slow computer. Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ On Sat, Sep 4, 2010 at 11:18 PM, Tudor Girba <tudor.girba(a)gmail.com> wrote: > Hi, > > Over the past week I worked on a new theme for Pharo called the Glamorous > Theme :). The theme is developed in the context of the Glamour project, and > its goal is to create a look that: > - does not look like a specific operating system. In particular, the icons > should be operating system agnostic, because, for example, people in Windows > are confused by the red, yellow, green buttons of apple. > - uses a limited amount of colors and effects. > > It is still work in progress, but you can get the current version by > executing: > > Gofer new > squeaksource: 'Glamour'; > package: 'Glamour-Morphic-Theme'; > load. > GLMUITheme defaultSettings: nil. > GLMUITheme beCurrent. > GLMUITheme setPreferredWorldBackground. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Problem solving efficiency grows with the abstractness level of problem > understanding." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 7, 2010

Re: [Pharo-project] [ANN] Hudson for PharoCore

by Marcus Denker

On Sep 6, 2010, at 9:05 PM, Sean P. DeNigris wrote: > > > Marcus Denker-4 wrote: >> >> >> http://rmod.lille.inria.fr/hudson/ >> >> Report for 1.1: >> http://rmod.lille.inria.fr/hudson/job/PharoCore1.1/lastBuild/testReport/ >> >> Report for 1.2: >> http://rmod.lille.inria.fr/hudson/job/PharoCore1.2/lastBuild/testReport/ >> > > All links show: > > Unavailable (HTTP 503) >> Serious error. All shortcuts have disappeared. Screen. Mind. Both are >> blank. Yes... we are working with inria to have a dedicated (virtual) server for that. Using the server of the website just adds things that can go wrong an make the rmod website inaccessible. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Sept. 7, 2010

Re: [Pharo-project] UbiquiTalk running in Pharo 1.1

by Levente Uzonyi

On Mon, 6 Sep 2010, Miguel Enrique CobÃ¡ MartÃnez wrote: > snip "Installer AFAIK does a lot of things, so in a way it was bloated, that was the reason for gofer showing up (also the fact that installer didn't unload packages and gofer does, I think)." Installer can unload Monticello packages (besides being able to load stuff from sources which are not used by Pharo users) and I'm pretty sure it does it the same way as Gofer does (this is a feature of MC). Levente

Sept. 7, 2010

Re: [Pharo-project] [Moose-dev] glamorous theme :)

by StÃ©phane Ducasse

First we should be able to load them int 1.2 core and anymorphic has a refernece to OB task or something. Personnally (except for the corner button I prefer anymorphic but this is a question of choice). Stef On Sep 6, 2010, at 10:10 PM, Adrian Lienhard wrote: > So, so now we have 2 themes that appear to be better than the one we use now... I suggest to choose one, maybe adapt it slightly, and integrate it into Pharo 1.2. > > Personally, I prefer Glamorous over the Pro theme [1] (I just miss the round corners like Alex :). The dark buttons of the Pro theme look cool at first, but they are very dominant. > > How do we proceed? > > Cheers, > Adrian > > [1] Polymorph-Themes-Pro package in the PharoInbox repositrory > > > > > On Sep 6, 2010, at 16:41 , Alexandre Bergel wrote: > >>>> http://homepage.mac.com/svc/Screenshots/Screenshot-20100905T111347.png >>>> >>> No round corners! kewl! :)) >> >> I would prefer round corners. >> >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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

Sept. 7, 2010

Re: [Pharo-project] UbiquiTalk running in Pharo 1.1

by Sean P. DeNigris

Miguel Enrique CobÃ¡ MartÃnez-2 wrote: > > But metacello doesn't need to be installed in the image. > Yes. I'm being impatient - I sometimes find myself wanting to just "check something out" quickly in Squeak and don't feel like waiting for Metacello to load, which often takes longer than the project I wanted to load in the first place! Miguel Enrique CobÃ¡ MartÃnez-2 wrote: > > Installer AFAIK does a lot of things, so in a way it was bloated, that > was the reason for gofer showing up (also the fact that installer didn't > unload packages and gofer does, I think). > > But installer is used mainly to install packages from squeaksource, just > as gofer, and the other possible uses are seldom, if ever, used. > But that is the reason of keeping Installer loaded, just in case, you > know ;) > Thanks for the background. Sean -- View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2528911.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 6, 2010

Re: [Pharo-project] Single instance executables

by Chris Muller

Perhaps Denis meant the file would be deleted when the image is exited. So only the presence of the file would need to be checked for upon startup.. On Sat, Sep 4, 2010 at 5:40 AM, Douglas Brebner <squeaklists(a)fang.demon.co.uk> wrote: > Â On 04/09/2010 08:25, Denis Kudriashov wrote: >> >> You could open some file for write at image startup. When its failed >> you know that another image already started >> > > That only works on Windows. Unix will allow you to open a file for writing > multiple times simultaneously. > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 6, 2010

Re: [Pharo-project] UbiquiTalk running in Pharo 1.1

by Miguel Enrique CobÃ¡ MartÃnez

El lun, 06-09-2010 a las 14:26 -0700, Sean P. DeNigris escribiÃ³: > > Miguel Enrique CobÃ¡ MartÃnez-2 wrote: > > > > This begs for a ConfigurationOfUbiquiTalk :) > > > > Yes, I didn't want to "take the time" to make one, and it probably took > longer to list it all out, lol. > > One of the complications is that Squeak 4.1, which I also work in, does not > include Metacello by default, so I have to write an Installer script. But metacello doesn't need to be installed in the image. Installer ss project: 'MetacelloRepository'; install: 'ConfigurationOfUbiquiTalk'; will install the configuration and the configuration autobootstrap Metacello in the image if not installed. > I > still find it confusing and frustrating that there are both Gofer and > Installer. Why don't we standardize on one or merge them? Long story, is like the bike shed topic. Every one has an opinion, including me :). Installer AFAIK does a lot of things, so in a way it was bloated, that was the reason for gofer showing up (also the fact that installer didn't unload packages and gofer does, I think). But installer is used mainly to install packages from squeaksource, just as gofer, and the other possible uses are seldom, if ever, used. But that is the reason of keeping Installer loaded, just in case, you know ;) But well, the configuration install metacello if needed. That was my point. Also, we would love to see one more configuration in the repository. Also, this permits other configuration to use it without knowing its internals (that is, what packages depends on) Cheers and thanks for the work! > > Sean > -- > View this message in context: http://forum.world.st/UbiquiTalk-running-in-Pharo-1-1-tp2400767p2528894.html > 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 -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Sept. 6, 2010