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

Re: [Pharo-project] [TODO] 1.2 full build broken since 5 days

by Dale Henrichs

I found the url ... thanks and nevermind:) ----- Original Message ----- | From: "Dale Henrichs" <dhenrich(a)vmware.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Tuesday, June 7, 2011 10:15:27 AM | Subject: Re: [Pharo-project] [TODO] 1.2 full build broken since 5 days | | I'm going to look into this issue ... where can I find the build | script that is used for Pharo-1.2? I want to duplicate the | operations done by Hudson and I can't seem to find a link to the | script anywhere on the site ... | | Dale | | ----- Original Message ----- | | From: "Norbert Hartl" <norbert(a)hartl.name> | | To: Pharo-project(a)lists.gforge.inria.fr | | Sent: Tuesday, June 7, 2011 1:47:56 AM | | Subject: Re: [Pharo-project] [TODO] 1.2 full build broken since 5 | | days | | | | | | Am 07.06.2011 um 10:37 schrieb Norbert Hartl: | | | | > I cannot reach the server so I cannot check. But I checked at the | | > weekend and wrote a mail to the pharo list. The build failed | | > because it couldn't load a file from Lukas' server. I could load | | > it via my browser. So triggering a new build will hopefully fix | | > it. | | > | | Ok, now I see. It has been restarted but there is another error. | | | | Norbert | | > Norbert | | > | | > Am 07.06.2011 um 09:47 schrieb Marcus Denker: | | > | | >> Hello, | | >> | | >> The 1.2 full build is broken since 5 days | | >> | | >> | | >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/ | | >> | | >> Someone needs to fix it. | | >> | | >> -- | | >> Marcus Denker -- http://www.marcusdenker.de | | >> INRIA Lille -- Nord Europe. Team RMoD. | | >> | | >> | | > | | > | | | | | | | |

June 7, 2011

Re: [Pharo-project] [TODO] 1.2 full build broken since 5 days

by Dale Henrichs

I'm going to look into this issue ... where can I find the build script that is used for Pharo-1.2? I want to duplicate the operations done by Hudson and I can't seem to find a link to the script anywhere on the site ... Dale ----- Original Message ----- | From: "Norbert Hartl" <norbert(a)hartl.name> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Tuesday, June 7, 2011 1:47:56 AM | Subject: Re: [Pharo-project] [TODO] 1.2 full build broken since 5 days | | | Am 07.06.2011 um 10:37 schrieb Norbert Hartl: | | > I cannot reach the server so I cannot check. But I checked at the | > weekend and wrote a mail to the pharo list. The build failed | > because it couldn't load a file from Lukas' server. I could load | > it via my browser. So triggering a new build will hopefully fix | > it. | > | Ok, now I see. It has been restarted but there is another error. | | Norbert | > Norbert | > | > Am 07.06.2011 um 09:47 schrieb Marcus Denker: | > | >> Hello, | >> | >> The 1.2 full build is broken since 5 days | >> | >> | >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/ | >> | >> Someone needs to fix it. | >> | >> -- | >> Marcus Denker -- http://www.marcusdenker.de | >> INRIA Lille -- Nord Europe. Team RMoD. | >> | >> | > | > | | |

June 7, 2011

Re: [Pharo-project] [update 1.3] #13254

by Gary Chambers

I've added a comment to http://code.google.com/p/pharo/issues/detail?id=4291 Modality is broken from MorphicUIManager. Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "Pharo Development" <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, June 07, 2011 5:02 PM Subject: [Pharo-project] [update 1.3] #13254 > > 13254 > ----- > > - Issue 4291: Choose color dialog modal does not work anymore. > http://code.google.com/p/pharo/issues/detail?id=4291 > > - Issue 4358: PluggableListMorph wrapper minor fix. > http://code.google.com/p/pharo/issues/detail?id=4358 > > Stef and Igor >

June 7, 2011

[Pharo-project] [update 1.3] #13254

by StÃ©phane Ducasse

13254 ----- - Issue 4291: Choose color dialog modal does not work anymore. http://code.google.com/p/pharo/issues/detail?id=4291 - Issue 4358: PluggableListMorph wrapper minor fix. http://code.google.com/p/pharo/issues/detail?id=4358 Stef and Igor

June 7, 2011

[Pharo-project] support for flattening-out traits for export?

by Torsten Bergmann

>Just a meta question..... What about real questions: - are Traits used these days - in which packages and why - how is the adoption rate I havent much used them by myself (mostly due to the lack of time to dig into it) but I would like to learn about the current state of Traits (is it used, maintained, usable). And yes - we can add lots of (language) features. But we should also discuss/measure/find out if they are usefull. Some of them help us moving forward others may stand in our way. And "Keep it simple" is always a good rule ... One great thing in languages like Smalltalk is that you can care about the problem ... and not so much about satisfying the compiler or knowing about the 10 most recent language features nailed to the language to circumvent problems from early language design. I think we should be more serious ... Marianos may have some valid points we should discuss. So let him tell us why he avoided Traits and what are the issues with tools. Let's listen and learn. >"he last time something serious was new in Smalltalk it was back in 1984" >"got killed by Java" >"Pharo is not about maintaining the past." Sorry Stef, but to me these are phrases and not releated to the question about the usefullness of Traits. Language features were not the reasons why Java took up. Back at the time it was small, free, multiplatform and available in the web (applets) when the web took up and no radical change for most programmers. In fact languages features are discussed these days for Java and we should discuss them too... Especially since Smalltalk is not a programming language ... more a dynamic object system on top of a VM with a language built in. Which path would we like to take with Pharo? Adding more language features to be comparable to other languages? Or even become a multilanguage platform/embed new languages similar to JVM and .NET VM (maybe with Helvetia)? What are our goals here? Bye T. -- NEU: FreePhone - kostenlos mobil telefonieren! Jetzt informieren: http://www.gmx.net/de/go/freephone

June 7, 2011

[Pharo-project] [update 1.3] #13253

by StÃ©phane Ducasse

13253 ----- - Issue 4319: VM parameter handling problems. Part two. Thanks Igor Stasenko. http://code.google.com/p/pharo/issues/detail?id=4319 Stef and Igor

June 7, 2011

Re: [Pharo-project] support for flattening-out traits for export?

by StÃ©phane Ducasse

Just a meta question..... So what will people do when we will add slots? Leave/cry and complain as usual? When Common lisp got slots since 1990 and the world imagination got killed by Java, it makes me think. May be we are not a community to invent something after all. Especially if we are not ready because the last time something serious was new in Smalltalk it was back in 1984. Mariano this is not against you but in general. Pharo is not about maintaining the past. This notion of compatibility is doomed, because first VW does not ask pharo to add a feature in the language (like these wonderful namespaces or XML code format) Second, this means that nobody can evolve. While we have the tools to manage difference. So of course traits could be better but this is not by being negative on attempt to move our wonderful old community that we will make progress. Or may be the best way is just to tell us that we should better invest in Javascript and we will all look far cooler in fact. Stef On Jun 7, 2011, at 3:10 PM, Mariano Martinez Peck wrote: > Thanks Adrian. > > BTW, there is no way to fileout a whole Monticello package? it seems I have to manually do a fileout of each category, not package :( > > Eliot: we were discussing today with Martin and maybe we will get rid of Traits. The truth is that in our case we use them mostly for tests and we think that with a good refactor we can avoid using them without duplicating too much code. In fact, we suffer several problems with traits and the integration with tools like Monticello. And even more it makes porting more complicated. We cannot code that much now because we are preparing a paper for ESUG but we will give it a try. > > Taking into account all your knowledge and experience in general and with Parcels, we will LOVE to listen your feedback for Fuel. > > Cheers > > Mariano > > > On Tue, Jun 7, 2011 at 12:29 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > IIRC this can be achieved with two small changes: > > - Comment out the line "method isLocalSelector" from PackageInfo>>methods. This will flatten the traits into the classes, i.e., make all methods of a class being stored even if they come from a trait. > > - In addition you probably need to change PackageInfo>>classes to filter out all traits (like ... reject: #isTrait). > > HTH, > Adrian > > On Jun 7, 2011, at 08:11 , Mariano Martinez Peck wrote: > > > On Tue, Jun 7, 2011 at 12:47 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > > >> Hi All, > >> > >> if I want to export a package (Fuel!!) to a dialect without traits is > >> there anything to help me remove the trait info and just file-out the > >> composed code? > >> > >> > > Hi Eliot. Traits are only used in Fuel for testing. And really used for > > testing methods for classes and traits (not the basic methods). So, of > > course, you can directly fileout the Fuel package only without traits. > > > > One of the things I always wanted is what you are really asking, a way to > > fileout forgetting traits, just letting those methods directly in the > > classes. But I have no idea if that's possible. > > > > Finally, I was never really convinced about the Traits usage in Fuel. Mostly > > because some tools seem not to be happy with them...We should check how much > > difficult and what we loose removing them now.... > > > > Cheers > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > > > > > -- > Mariano > http://marianopeck.wordpress.com >

June 7, 2011

[Pharo-project] [update 1.3] #13252

by StÃ©phane Ducasse

13252 ----- - Issue 4319: VM parameter handling problems. Thanks Igor Stasenko. http://code.google.com/p/pharo/issues/detail?id=4319 Stef and igor next part follows

June 7, 2011

Re: [Pharo-project] support for flattening-out traits for export?

by Lukas Renggli

> Eliot: we were discussing today with Martin and maybe we will get rid of > Traits. The truth is that in our case we use them mostly for tests and we > think that with a good refactor we can avoid using them without duplicating > too much code. Alltogether? +1000 :-) -- Lukas Renggli www.lukas-renggli.ch

June 7, 2011

Re: [Pharo-project] [Pharo-users] [ANN] New Glorp Port

by Mariano Martinez Peck

We have a new issue tracker: http://code.google.com/p/dbxtalk/issues/list So...please, if there are bugs or wishes, writem them there. I have just added: http://code.google.com/p/dbxtalk/issues/detail?id=6 Cheers On Tue, Jun 7, 2011 at 9:13 AM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr>wrote: > thanks guillermo! > > Stef > > On Jun 7, 2011, at 4:57 AM, Guillermo Polito wrote: > > > I'm glad to announce a first stable version of the new Glorp Port, from > VW 7.7.1. > > > > The port has been integrated with the DBXTalk Driver (before known as > SqueakDBX), and tested on the following platforms: > > > > MySql: 872 tests run, 18 errors, 6 failures > > PostgreSQL: 872 tests, 18 errors, 6 failures > > Oracle: 872 tests, 21 errors, 5 failures. > > > > Most of the errors are caused by stuff the DBXTalk Driver does not > support yet, like LOBS. Also, there are some bugs yet I have to attack and > learn how to get rid of, hehe. > > > > One think to be careful of yet is the licencing (or how it should be > written). Glorp licence today is LGPL, but in the way to be MIT :). > > > > So, if you want to download and try it, evaluate in a workspace, in Pharo > 1.2 and 1.3, > > > > Gofer it > > squeaksource: 'DBXTalk'; > > package: 'ConfigurationOfGlorpDBX'; > > load. > > > > (ConfigurationOfGlorpDBX project version: #stable) load > > > > And start playing! > > > > I think I'll become the new port mantainer, so feedback, bug reports and > everything else is appreciated. > > > > BTW, documentation and some new tools are on the way too. > > > > > > Guille :) > > > -- Mariano http://marianopeck.wordpress.com

June 7, 2011