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

Re: [Pharo-project] Marking methods

by Bernat Romagosa

Hi Torsten, The problem with flagging is that you are modifying the source code, I'd prefer something provided by the IDE... 2011/10/25 Torsten Bergmann <astares(a)gmx.de> > Hi Bernat, > > if you put > > self halt > > into a method you will notice that it gets marked. > > You can also flag it by using: > > self flag: 'reviewed' > > in the sourcecode. > > Look for method #browserIcon:selector, this returns a > symbol (selector Icons are on OBMorphicIcons) > > You can adopt it to your own needs or implement it on > the class side as for instance TestCase class does. > > Also look at OBMethodIconFilter. > > Bye > T. > > > -- > NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! > Jetzt informieren: http://www.gmx.net/de/go/freephone > > -- Bernat Romagosa.

Oct. 25, 2011

[Pharo-project] Marking methods

by Torsten Bergmann

Hi Bernat, if you put self halt into a method you will notice that it gets marked. You can also flag it by using: self flag: 'reviewed' in the sourcecode. Look for method #browserIcon:selector, this returns a symbol (selector Icons are on OBMorphicIcons) You can adopt it to your own needs or implement it on the class side as for instance TestCase class does. Also look at OBMethodIconFilter. Bye T. -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

Oct. 25, 2011

[Pharo-project] Marking methods

by Bernat Romagosa

Hi list, I've been thinking for a while that it'd be great if we could somehow graphically mark methods in the browser. Like adding an icon next to their name or highlighting them in different colors. When reviewing code, I find myself going through methods and would love to be able to mark them once they've been reviewed, to prevent me from going through them again. Does anyone else have the same needs? How do you guys manage this? I thought about flagging methods, but that'd mean I'd have to read through all my methods again to remove the flags once I'm done with the revision. Cheers, -- Bernat Romagosa.

Oct. 25, 2011

Re: [Pharo-project] Website RSS feed broken?

by Max Leske

Thanks for the diff Stefan. That should certainly help. Max On 25.10.2011, at 07:45, Stefan Marr wrote: > > On 19 Oct 2011, at 00:20, Max Leske wrote: > >> I'm looking into it. > > > And it is still broken! > > The channel description should not change. It is meta data, and should describe, but not contain the content. > That is one thing that could confuse RSS readers like Google Reader. > > But even worse is probably that the links of the items change. The guids are stable as far as I can see. > > The diff of the versions is below. > > Please fix that. > > > > Thanks > Stefan > > > --- rss1.txt 2011-10-24 22:35:32.000000000 -0700 > +++ rss2.txt 2011-10-24 22:35:43.000000000 -0700 > @@ -1,18 +1,27 @@ > <?xml version="1.0" encoding="utf-8"?> > <?xml-stylesheet href="/_cmsbox_2.2.15_218/layout/default.css"?> > -<?xml-stylesheet href="/_cmsbox_27/design/screen.css"?> > +<?xml-stylesheet href="/_cmsbox_29/design/screen.css"?> > <rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"> > <channel> > <title>Pharo Open Source Smalltalk Ã¢â¬â News</title> > <link>http://www.pharo-project.org/news</link> > - <description>Pharo News Blog. Language of Languages. Pharo 1.3 and 1.4 status. Moose 4.4 release. Mailing list weekly summary #7. Pharo release 1.2.1.</description> > + <description>Pharo News Blog. JQueryMobile for Seaside. Language of Languages. Pharo 1.3 and 1.4 status. Moose 4.4 release. Mailing list weekly summary #7.</description> > <language>de-ch</language> > - <lastBuildDate>Tue, 18 Oct 2011 08:57:58 GMT</lastBuildDate> > - <pubDate>Tue, 18 Oct 2011 08:57:58 GMT</pubDate> > + <lastBuildDate>Mon, 24 Oct 2011 13:53:17 GMT</lastBuildDate> > + <pubDate>Mon, 24 Oct 2011 13:53:17 GMT</pubDate> > <webMaster>alienhard(a)netstyle.ch (board)</webMaster> > <generator>Cmsbox 2.0</generator> > <docs>http://www.rssboard.org/rss-specification</docs> > <item> > + <title>JQueryMobile for Seaside</title> > + <author>alienhard(a)netstyle.ch (board)</author> > + <link>http://www.pharo-project.org/news?dialog=jquerymobile-for-seaside</link> > + <pubDate>Mon, 24 Oct 2011 13:53:07 GMT</pubDate> > + <guid isPermaLink="false">a5d13cb7-ea0d-4209-981c-6f333872ed93</guid> > + <description><![CDATA[Nick Ager integrated JQuery Mobile with Seaside You can try it out at: http://jquerymobile]]></description> > + <content:encoded><![CDATA[<div class="part text tall"><p class="norm">Nick Ager integrated JQuery Mobile with Seaside<br/><br/> You can try it out at: <a class="open" title="http://jquerymobile.seasidehosting.st" href="http://jquerymobile.seasidehosting.st">http://jquerymobile.seasidehosting.st  </a><br/><br/>This work has been sponsored by Louis Andriese at "Delta Lloyd Online Innovations" and made available under the MIT licence. For more information, see Nick's post on the Seaside list <a class="open" title="http://lists.squeakfoundation.org/pipermail/seaside/2011-October/027772.html" href="http://lists.squeakfoundation.org/pipermail/seaside/2011-October/027772.html">here</a></p></div>]]></content:encoded> > + </item> > + <item> > <title>Language of Languages</title> > <author>alienhard(a)netstyle.ch (board)</author> > <link>http://www.pharo-project.org/news?dialog=language-of-languages</link> > @@ -69,7 +78,7 @@ > <item> > <title/> > <author>alienhard(a)netstyle.ch (board)</author> > - <link>http://www.pharo-project.org/news?dialog=unit3782</link> > + <link>http://www.pharo-project.org/news?dialog=unit1750</link> > <pubDate>Thu, 24 Mar 2011 20:19:44 GMT</pubDate> > <guid isPermaLink="false">5c8ac2aa-85c1-4a2f-98a0-1f6f2634fa6e</guid> > <description><![CDATA[]]></description> > @@ -78,7 +87,7 @@ > <item> > <title/> > <author>alienhard(a)netstyle.ch (board)</author> > - <link>http://www.pharo-project.org/news?dialog=unit330</link> > + <link>http://www.pharo-project.org/news?dialog=unit1114</link> > <pubDate>Thu, 24 Mar 2011 19:09:50 GMT</pubDate> > <guid isPermaLink="false">2ec9f57a-5efb-4e16-89ba-8dfce4fd991a</guid> > <description><![CDATA[]]></description> > @@ -114,7 +123,7 @@ > <item> > <title/> > <author>alienhard(a)netstyle.ch (board)</author> > - <link>http://www.pharo-project.org/news?article=unit359</link> > + <link>http://www.pharo-project.org/news?article=unit3127</link> > <pubDate>Tue, 27 Jul 2010 07:12:13 GMT</pubDate> > <guid isPermaLink="false">35e0919e-9c5a-4986-a981-3580482984e1</guid> > <description><![CDATA[]]></description> > @@ -125,7 +134,7 @@ > <author>alienhard(a)netstyle.ch (board)</author> > <link>http://www.pharo-project.org/news?article=pharo-news-3-pharo-1-0-released</link> > <pubDate>Thu, 15 Apr 2010 13:08:35 GMT</pubDate> > - <guid isPermaLink="false">d72aa037-8d47-408f-9357-5037e004ec98</guid> > + <guid isPermaLink="false">db824132-017a-4dc1-9443-903cb81a0fa0</guid> > <description><![CDATA[Pharo is a modern open-source Smalltalk language and environment]]></description> > <content:encoded><![CDATA[<div class="part text tall"><p class="norm">Pharo is a modern open-source Smalltalk language and environment. PharoÃ¢â¬â¢s goals are to provide a robust and clean core and to implement innovative extensions of the language and its environment. By providing a stable and small system and excellent developer tools, Pharo is an attractive platform for mission critical Smalltalk applications.</p></div><div class="part text tall"><p class="norm">Pharo 1.0 is the first release since the project started in May 2008. Many <a class="open" title="Success stories" href="javascript:void(0)">companies</a> have already successfully adopted Pharo. <a class="open" title="http://www.seaside.st" href="http://www.seaside.st">Seaside</a>, the Smalltalk web framework, switched to Pharo as their main development platform. A <a class="open" title="http://www.pharobyexample.org" href="http://www.pharobyexample.org">book on Pharo</a> has recently been published (also available as a free PDF). Pharo has a growing <a class="open" title="Get connected, get help, contribute" href="javascript:void(0)">community</a> and is supported by research institutions such as <a class="open" title="http://www.inria.fr" href="http://www.inria.fr">INRIA</a>. Pharo is licensed under the MIT License (with some original parts remaining under the Apache License).</p></div><div class="part text tall"><p class="norm">Download the <a class="open" title="http://gforge.inria.fr/frs/download.php/26828/Pharo-1.0-OneClick.zip" href="http://gforge.inria.fr/frs/download.php/26828/Pharo-1.0-OneClick.zip">Pharo 1.0 one-click image</a> and get started within seconds. Read more about <a class="open" title="Pharo version 1.0" href="javascript:void(0)">what this release offers</a>.</p></div><div class="part text tiny"><p class="pale"><a class="open" title="http://www.adrian-lienhard.ch" href="http://www.adrian-lienhard.ch">Adrian Lienhard</a>, April 15, 2010</p></div><div class="part cb-widget tiny cb-share"><a class="cb-mail" title="Share this article on E-Mail" rel="nofollow" href="http://www.pharo-project.org/news?recommend=pharo-news-3-pharo-1-0-released"><span>Share this article on E-Mail</span></a> <a rel="nofollow" class="cb-twitter" title="Share this article on Twitter" href="http://twitter.com/home?status=I'm+currently+reading+http://www.pharo-project.org/news?article=pharo-news-3-…"><span>Share this article on Twitter</span></a> <a rel="nofollow" class="cb-facebook" title="Share this article on Facebook" href="http://www.facebook.com/sharer.php?t=Pharo News #3: Pharo 1.0 released&u=http://www.pharo-project.org/news?article=pharo-news-3-pharo…"><span>Share this article on Facebook</span></a> <a rel="nofollow" class="cb-delicious" title="Share this article on Delicious" href="http://del.icio.us/post?title=Pharo News #3: Pharo 1.0 released&url=http://www.pharo-project.org/news?article=pharo-news-3-pha…"><span>Share this article on Delicious</span></a> <a rel="nofollow" class="cb-digg" title="Share this article on Digg" href="http://digg.com/submit?title=Pharo News #3: Pharo 1.0 released&url=http://www.pharo-project.org/news?article=pharo-news-3-pha…"><span>Share this article on Digg</span></a> </div>]]></content:encoded> > </item> > @@ -143,7 +152,7 @@ > <author>alienhard(a)netstyle.ch (board)</author> > <link>http://www.pharo-project.org/news?article=pharo-news-1</link> > <pubDate>Sat, 16 Jan 2010 15:26:12 GMT</pubDate> > - <guid isPermaLink="false">9ed28654-55a6-481b-aa7d-4d1460594d4b</guid> > + <guid isPermaLink="false">b642fed4-fac2-4158-bf4e-059b050f5b80</guid> > <description><![CDATA[Metacello Configurations for Pharo]]></description> > <content:encoded><![CDATA[<div class="part lead tall"><h6>Metacello Configurations for Pharo</h6></div><div class="part text tall"><p class="norm">Mariano Martinez Peck <a class="open" title="http://lists.gforge.inria.fr/pipermail/pharo-project/2010-January/019049.ht…" href="http://lists.gforge.inria.fr/pipermail/pharo-project/2010-January/019049.ht…">announced</a> Metacello configurations for Pharo. The goal is to define a catalog of packages that are stable and known to work in Pharo. The Pharo 1.0 and forthcoming versions can be built automatically from these configurations, which are stored in a dedicated <a class="open" title="http://www.squeaksource.com/MetacelloRepository.html" href="http://www.squeaksource.com/MetacelloRepository.html">repository on SqueakSource</a>.</p></div><div class="part lead tall"><h6>Pharo Screencasts</h6></div><div class="part text tall"><p class="norm">Laurent Laffont created a blog to publish Pharo screencasts. Contact Laurent if you want to share a screencast or if you have an idea for a new screencast that Laurent can produce.</p></div><div class="part link site tall"><a class="open" href="http://pharocasts.blogspot.com/">http://pharocasts.blogspot.com/</a></div><div class="part lead tall"><h6>New Productivity Tool</h6></div><div class="part text tall"><p class="norm">Romain Robbes <a class="open" title="http://n2.nabble.com/ANN-WorkingSet-td4286093.html" href="http://n2.nabble.com/ANN-WorkingSet-td4286093.html">announced</a> WorkingSet, a small tool that helps you navigate your code in Pharo. It tracks the entities you've changed recently, and lets you access them quickly.</p></div><div class="part lead tall"><h6>Companies using Pharo</h6></div><div class="part text tall"><p class="norm">We started collecting companies that are using Pharo. 20 are already on the list Ã¢â¬â certainly more to come soon! If your company is missing or if you have an interesting project to share, let us know!</p></div><div class="part link goto tall"><a class="open page" href="http://www.pharo-project.org/about/success-stories">http://www.pharo-project.org/about/success-stories</a></div><div class="part lead tall"><h6>New Pharo Mailing List</h6></div><div class="part text tall"><p class="norm">Since the traffic on the pharo-project mailing list is quite high and often related to the development of the Pharo core system, we created a new mailing list, <a class="open" title="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users" href="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users">pharo-users</a>, targeted to users of Pharo.</p></div><div class="part text tiny"><p class="pale"><a class="open" title="http://www.adrian-lienhard.ch" href="http://www.adrian-lienhard.ch">Adrian Lienhard</a>, January 16, 2010</p></div><div class="part cb-widget tiny cb-share"><a class="cb-mail" title="Share this article on E-Mail" rel="nofollow" href="http://www.pharo-project.org/news?recommend=pharo-news-1"><span>Share this article on E-Mail</span></a> <a rel="nofollow" class="cb-twitter" title="Share this article on Twitter" href="http://twitter.com/home?status=I'm+currently+reading+http://www.pharo-project.org/news?article=pharo-news-1"><span>Share this article on Twitter</span></a> <a rel="nofollow" class="cb-facebook" title="Share this article on Facebook" href="http://www.facebook.com/sharer.php?t=Pharo News #1&u=http://www.pharo-project.org/news?article=pharo-news-1"><span>Share this article on Facebook</span></a> <a rel="nofollow" class="cb-delicious" title="Share this article on Delicious" href="http://del.icio.us/post?title=Pharo News #1&url=http://www.pharo-project.org/news?article=pharo-news-1"><span>Share this article on Delicious</span></a> <a rel="nofollow" class="cb-digg" title="Share this article on Digg" href="http://digg.com/submit?title=Pharo News #1&url=http://www.pharo-project.org/news?article=pharo-news-1"><span>Share this article on Digg</span></a> </div>]]></content:encoded> > </item> > > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

Oct. 25, 2011

Re: [Pharo-project] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #update

by Hilaire Fernandes

Ben, Can you send me a saved sketch producing the error (not the whole image), I would like to see track and register the error on the bug tracler. Hilaire Le 24/10/2011 15:56, Ben Coman a Ã©crit : > Thanks for your comment Bill. I need to learn more about good exception > handling for my own applications. > What I was surprised about was that nil appeared to receive a #do: but > not raise an error, and that next step in execution was > OrderedCollection>>do: . Anyway, saving the sketch, closing the image, > and the next day opening the sketch has cleared the error. > > Ben > > Schwab,Wilhelm K wrote: >> Ben, >> >> I can't comment on the workings of Dr. Geo, but since you ask about >> #do:, nil, least surprise etc., I can tell you that errors are your >> friends. Note that there is a difference between sending #do: to nil >> (would you really expect "nothing" to know how to iterate its >> contents?) and sending #do: to a collection that contains elements, >> some of which happen to be nil? In the latter case, would it really >> be non-surprising to have nil elements treated differently from their >> peers? Would you have them treated differently only if nil encounters >> a problem doing what is asked of it? In that case, #do: would have to >> trap and suppress errors, at least for nil entries. >> >> All of that sounds pretty surprising to me. Eventually, it will to >> you too. Happy Smalltalking! >> >> Bill >> >> >> >> ________________________________________ >> From: >> pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] >> On Behalf Of Ben Coman [btc(a)openInWorld.com] >> Sent: Saturday, October 22, 2011 2:36 PM >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: [Pharo-project] >> [BUG]UndefinedObject(Object)>>doesNotUnderstand: #update >> >> I was using DrGeo for the first time from the bundled release 11.08 on >> Windows 7. About 30 minutes in I drew three equally intersecting >> circles, added a reflection line with each circle reflected. I added a >> free point with a middle (I think to a circle) and was trying to add a >> locus. >> >> When moving any of the points defining the circles I am getting a dozen >> or more cascading MNUs down the screen. Moving the reflection line >> still works okay. >> >> The error occurs in following method... >> DrGeo>>updateDirtyCostumes >> self presenter tool costumes do: [ :each | each update ]. >> self area changed >> >> In the debugger inspecting "self presenter tool costumes" returns nil. >> While I can't judge whether returning nil is valid here, as a Smalltalk >> newbie what I am really interested in is: >> >> 1. The semantics of sending a "do:" message to nil. By the principle of >> least surprise I would expect that it would do ...nothing, whereas here >> it tries later sending the "update" method to it. >> >> 2. Why in lines 0027 and 0641 is the "do:" method received by >> OrderedCollection and not UndefinedObject? Actually I can't see "do:" in >> the hierarchy of UndefinedObject, so why does UndefinedObject not raise >> a MNU for "do:" ? >> >> The image with the error is available at... >> http://blog.openinworld.com/miscfiles/DrGeo-updateDirtyCostumes-MNU-2011-10… >> >> >> The stack trace generated by the <Mail out bug report> menu item is >> below. I wasn't sure how much of it to cut or leave, so I've left it all. >> ------------------8<------------------------- >> 00000001 22 October 2011 10:27:03 pm >> 00000002 >> 00000003 VM: Win32 - IX86 - NT - Squeak3.10.2 of 11 February 2010 >> [latest update: #9314] >> >> >> >> >> >> > > > -- Education 0.2 -- http://blog.ofset.org/hilaire

Oct. 25, 2011

Re: [Pharo-project] Jenkis small delay possible?

by Norbert Hartl

Am 25.10.2011 um 07:09 schrieb Benjamin: > You can put your config in another repo and add the listener on this repo changes > > > Maybe the simplest :) > No, the simplest is to leave it as it is. Do you really think it is worth the effort? A new repo and pseudo configuration commits just to prevent a few bogus "jenkins became unstable" mails? What is the problem with it? If you know that it can happen you can just look at it that way. In this particular case there is not only a broken build but also a new build in the queue. If you just develop the habbit to look after the last build you will see there is no problem. I have plenty of experience how this "clever tweaking" of the configuration management tools has the potential to make it really worse. Even the raise of the delay will get on someones nerves that tries to fix a configuration. That will lead to have to do a lot of builds until it works. For this use case the 5 minutes delay is already unbearable, etc. my 2,5 cents Norbert > > Ben > > On Oct 24, 2011, at 6:04 PM, Camillo Bruni wrote: > >> Can't you make it dependent on the configuration? >> Like that you would only fire a build after the configuration was pushed, which, hopefully, refers to packages that actually exist :) >> >> cami >> >> On 2011-10-24, at 13:15, Igor Stasenko wrote: >> >>> On 24 October 2011 11:23, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >>>> Marcus, the problem is that jenkis is working VERY well ;) Now, really, >>>> the thing is that I have a lot of packages, and when I change in several of >>>> them, when I commit the first package, Jenkis automatically fires up a >>>> build. That happens even before I can commit the rest of the packages. >>>> Hence...the build become unstabe, and just in the next build it becomes >>>> stable again... >>>> So...I was wondering, maybe we can put kind of delay ? so that Jenkis does >>>> not trigger a build immediatly, but say, after 5 minutes? (that gives me >>>> time to commit all packages) >>>> >>> >>> The solution is simple, as to me: >>> Do not commit the first, before you commit the rest :) >>> >>> Apparently, if jenkins watching for changes in PackageA, which depends >>> on PackageB, >>> first you should commit B, and only then A. >>> >>>> Thanks >>>> >>>> -- >>>> Mariano >>>> http://marianopeck.wordpress.com >>>> >>>> >>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> > >

Oct. 25, 2011

Re: [Pharo-project] How to encrypt a password?

by Milan Mimica

On 25 October 2011 04:43, mail list <mail.list(a)ficonab.com> wrote: > Someone may have already replied as I am writing this on a plane but > generally for passwords you do not write a decrypt method for security > purposes (eg you do not want people to be able to reverse engineer the > encrypted password easily) > > You just compare encrypted passwords to see if they are equal. > eg > password:= SecureHashAlgorithm new hashMessage: aClearTextPass. > > then later on you check > password = SecureHashAlgorithm new hashMessage: aPasswordAttempt. > To make it slightly more secure, you can put a little salt in it: salt := 'Some random string I just cam up with 123' password:= SecureHashAlgorithm new hashMessage: salt, aClearTextPass. check: password = SecureHashAlgorithm new hashMessage: salt, aPasswordAttempt. That way you make it more difficult for the attacker to brute-force guess the password when the user supplies a weak password. -- Milan Mimica http://sparklet.sf.net

Oct. 25, 2011

Re: [Pharo-project] Website RSS feed broken?

by Stefan Marr

On 19 Oct 2011, at 00:20, Max Leske wrote: > I'm looking into it. And it is still broken! The channel description should not change. It is meta data, and should describe, but not contain the content. That is one thing that could confuse RSS readers like Google Reader. But even worse is probably that the links of the items change. The guids are stable as far as I can see. The diff of the versions is below. Please fix that. Thanks Stefan --- rss1.txt 2011-10-24 22:35:32.000000000 -0700 +++ rss2.txt 2011-10-24 22:35:43.000000000 -0700 @@ -1,18 +1,27 @@ <?xml version="1.0" encoding="utf-8"?> <?xml-stylesheet href="/_cmsbox_2.2.15_218/layout/default.css"?> -<?xml-stylesheet href="/_cmsbox_27/design/screen.css"?> +<?xml-stylesheet href="/_cmsbox_29/design/screen.css"?> <rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"> <channel> <title>Pharo Open Source Smalltalk Ã¢â¬â News</title> <link>http://www.pharo-project.org/news</link> - <description>Pharo News Blog. Language of Languages. Pharo 1.3 and 1.4 status. Moose 4.4 release. Mailing list weekly summary #7. Pharo release 1.2.1.</description> + <description>Pharo News Blog. JQueryMobile for Seaside. Language of Languages. Pharo 1.3 and 1.4 status. Moose 4.4 release. Mailing list weekly summary #7.</description> <language>de-ch</language> - <lastBuildDate>Tue, 18 Oct 2011 08:57:58 GMT</lastBuildDate> - <pubDate>Tue, 18 Oct 2011 08:57:58 GMT</pubDate> + <lastBuildDate>Mon, 24 Oct 2011 13:53:17 GMT</lastBuildDate> + <pubDate>Mon, 24 Oct 2011 13:53:17 GMT</pubDate> <webMaster>alienhard(a)netstyle.ch (board)</webMaster> <generator>Cmsbox 2.0</generator> <docs>http://www.rssboard.org/rss-specification</docs> <item> + <title>JQueryMobile for Seaside</title> + <author>alienhard(a)netstyle.ch (board)</author> + <link>http://www.pharo-project.org/news?dialog=jquerymobile-for-seaside</link> + <pubDate>Mon, 24 Oct 2011 13:53:07 GMT</pubDate> + <guid isPermaLink="false">a5d13cb7-ea0d-4209-981c-6f333872ed93</guid> + <description><![CDATA[Nick Ager integrated JQuery Mobile with Seaside You can try it out at: http://jquerymobile]]></description> + <content:encoded><![CDATA[<div class="part text tall"><p class="norm">Nick Ager integrated JQuery Mobile with Seaside<br/><br/> You can try it out at: <a class="open" title="http://jquerymobile.seasidehosting.st" href="http://jquerymobile.seasidehosting.st">http://jquerymobile.seasidehosting.st  </a><br/><br/>This work has been sponsored by Louis Andriese at "Delta Lloyd Online Innovations" and made available under the MIT licence. For more information, see Nick's post on the Seaside list <a class="open" title="http://lists.squeakfoundation.org/pipermail/seaside/2011-October/027772.html" href="http://lists.squeakfoundation.org/pipermail/seaside/2011-October/027772.html">here</a></p></div>]]></content:encoded> + </item> + <item> <title>Language of Languages</title> <author>alienhard(a)netstyle.ch (board)</author> <link>http://www.pharo-project.org/news?dialog=language-of-languages</link> @@ -69,7 +78,7 @@ <item> <title/> <author>alienhard(a)netstyle.ch (board)</author> - <link>http://www.pharo-project.org/news?dialog=unit3782</link> + <link>http://www.pharo-project.org/news?dialog=unit1750</link> <pubDate>Thu, 24 Mar 2011 20:19:44 GMT</pubDate> <guid isPermaLink="false">5c8ac2aa-85c1-4a2f-98a0-1f6f2634fa6e</guid> <description><![CDATA[]]></description> @@ -78,7 +87,7 @@ <item> <title/> <author>alienhard(a)netstyle.ch (board)</author> - <link>http://www.pharo-project.org/news?dialog=unit330</link> + <link>http://www.pharo-project.org/news?dialog=unit1114</link> <pubDate>Thu, 24 Mar 2011 19:09:50 GMT</pubDate> <guid isPermaLink="false">2ec9f57a-5efb-4e16-89ba-8dfce4fd991a</guid> <description><![CDATA[]]></description> @@ -114,7 +123,7 @@ <item> <title/> <author>alienhard(a)netstyle.ch (board)</author> - <link>http://www.pharo-project.org/news?article=unit359</link> + <link>http://www.pharo-project.org/news?article=unit3127</link> <pubDate>Tue, 27 Jul 2010 07:12:13 GMT</pubDate> <guid isPermaLink="false">35e0919e-9c5a-4986-a981-3580482984e1</guid> <description><![CDATA[]]></description> @@ -125,7 +134,7 @@ <author>alienhard(a)netstyle.ch (board)</author> <link>http://www.pharo-project.org/news?article=pharo-news-3-pharo-1-0-released</link> <pubDate>Thu, 15 Apr 2010 13:08:35 GMT</pubDate> - <guid isPermaLink="false">d72aa037-8d47-408f-9357-5037e004ec98</guid> + <guid isPermaLink="false">db824132-017a-4dc1-9443-903cb81a0fa0</guid> <description><![CDATA[Pharo is a modern open-source Smalltalk language and environment]]></description> <content:encoded><![CDATA[<div class="part text tall"><p class="norm">Pharo is a modern open-source Smalltalk language and environment. PharoÃ¢â¬â¢s goals are to provide a robust and clean core and to implement innovative extensions of the language and its environment. By providing a stable and small system and excellent developer tools, Pharo is an attractive platform for mission critical Smalltalk applications.</p></div><div class="part text tall"><p class="norm">Pharo 1.0 is the first release since the project started in May 2008. Many <a class="open" title="Success stories" href="javascript:void(0)">companies</a> have already successfully adopted Pharo. <a class="open" title="http://www.seaside.st" href="http://www.seaside.st">Seaside</a>, the Smalltalk web framework, switched to Pharo as their main development platform. A <a class="open" title="http://www.pharobyexample.org" href="http://www.pharobyexample.org">book on Pharo</a> has recently been published (also available as a free PDF). Pharo has a growing <a class="open" title="Get connected, get help, contribute" href="javascript:void(0)">community</a> and is supported by research institutions such as <a class="open" title="http://www.inria.fr" href="http://www.inria.fr">INRIA</a>. Pharo is licensed under the MIT License (with some original parts remaining under the Apache License).</p></div><div class="part text tall"><p class="norm">Download the <a class="open" title="http://gforge.inria.fr/frs/download.php/26828/Pharo-1.0-OneClick.zip" href="http://gforge.inria.fr/frs/download.php/26828/Pharo-1.0-OneClick.zip">Pharo 1.0 one-click image</a> and get started within seconds. Read more about <a class="open" title="Pharo version 1.0" href="javascript:void(0)">what this release offers</a>.</p></div><div class="part text tiny"><p class="pale"><a class="open" title="http://www.adrian-lienhard.ch" href="http://www.adrian-lienhard.ch">Adrian Lienhard</a>, April 15, 2010</p></div><div class="part cb-widget tiny cb-share"><a class="cb-mail" title="Share this article on E-Mail" rel="nofollow" href="http://www.pharo-project.org/news?recommend=pharo-news-3-pharo-1-0-released"><span>Share this article on E-Mail</span></a> <a rel="nofollow" class="cb-twitter" title="Share this article on Twitter" href="http://twitter.com/home?status=I'm+currently+reading+http://www.pharo-project.org/news?article=pharo-news-3-…"><span>Share this article on Twitter</span></a> <a rel="nofollow" class="cb-facebook" title="Share this article on Facebook" href="http://www.facebook.com/sharer.php?t=Pharo News #3: Pharo 1.0 released&u=http://www.pharo-project.org/news?article=pharo-news-3-pharo…"><span>Share this article on Facebook</span></a> <a rel="nofollow" class="cb-delicious" title="Share this article on Delicious" href="http://del.icio.us/post?title=Pharo News #3: Pharo 1.0 released&url=http://www.pharo-project.org/news?article=pharo-news-3-pha…"><span>Share this article on Delicious</span></a> <a rel="nofollow" class="cb-digg" title="Share this article on Digg" href="http://digg.com/submit?title=Pharo News #3: Pharo 1.0 released&url=http://www.pharo-project.org/news?article=pharo-news-3-pha…"><span>Share this article on Digg</span></a> </div>]]></content:encoded> </item> @@ -143,7 +152,7 @@ <author>alienhard(a)netstyle.ch (board)</author> <link>http://www.pharo-project.org/news?article=pharo-news-1</link> <pubDate>Sat, 16 Jan 2010 15:26:12 GMT</pubDate> - <guid isPermaLink="false">9ed28654-55a6-481b-aa7d-4d1460594d4b</guid> + <guid isPermaLink="false">b642fed4-fac2-4158-bf4e-059b050f5b80</guid> <description><![CDATA[Metacello Configurations for Pharo]]></description> <content:encoded><![CDATA[<div class="part lead tall"><h6>Metacello Configurations for Pharo</h6></div><div class="part text tall"><p class="norm">Mariano Martinez Peck <a class="open" title="http://lists.gforge.inria.fr/pipermail/pharo-project/2010-January/019049.ht…" href="http://lists.gforge.inria.fr/pipermail/pharo-project/2010-January/019049.ht…">announced</a> Metacello configurations for Pharo. The goal is to define a catalog of packages that are stable and known to work in Pharo. The Pharo 1.0 and forthcoming versions can be built automatically from these configurations, which are stored in a dedicated <a class="open" title="http://www.squeaksource.com/MetacelloRepository.html" href="http://www.squeaksource.com/MetacelloRepository.html">repository on SqueakSource</a>.</p></div><div class="part lead tall"><h6>Pharo Screencasts</h6></div><div class="part text tall"><p class="norm">Laurent Laffont created a blog to publish Pharo screencasts. Contact Laurent if you want to share a screencast or if you have an idea for a new screencast that Laurent can produce.</p></div><div class="part link site tall"><a class="open" href="http://pharocasts.blogspot.com/">http://pharocasts.blogspot.com/</a></div><div class="part lead tall"><h6>New Productivity Tool</h6></div><div class="part text tall"><p class="norm">Romain Robbes <a class="open" title="http://n2.nabble.com/ANN-WorkingSet-td4286093.html" href="http://n2.nabble.com/ANN-WorkingSet-td4286093.html">announced</a> WorkingSet, a small tool that helps you navigate your code in Pharo. It tracks the entities you've changed recently, and lets you access them quickly.</p></div><div class="part lead tall"><h6>Companies using Pharo</h6></div><div class="part text tall"><p class="norm">We started collecting companies that are using Pharo. 20 are already on the list Ã¢â¬â certainly more to come soon! If your company is missing or if you have an interesting project to share, let us know!</p></div><div class="part link goto tall"><a class="open page" href="http://www.pharo-project.org/about/success-stories">http://www.pharo-project.org/about/success-stories</a></div><div class="part lead tall"><h6>New Pharo Mailing List</h6></div><div class="part text tall"><p class="norm">Since the traffic on the pharo-project mailing list is quite high and often related to the development of the Pharo core system, we created a new mailing list, <a class="open" title="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users" href="http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users">pharo-users</a>, targeted to users of Pharo.</p></div><div class="part text tiny"><p class="pale"><a class="open" title="http://www.adrian-lienhard.ch" href="http://www.adrian-lienhard.ch">Adrian Lienhard</a>, January 16, 2010</p></div><div class="part cb-widget tiny cb-share"><a class="cb-mail" title="Share this article on E-Mail" rel="nofollow" href="http://www.pharo-project.org/news?recommend=pharo-news-1"><span>Share this article on E-Mail</span></a> <a rel="nofollow" class="cb-twitter" title="Share this article on Twitter" href="http://twitter.com/home?status=I'm+currently+reading+http://www.pharo-project.org/news?article=pharo-news-1"><span>Share this article on Twitter</span></a> <a rel="nofollow" class="cb-facebook" title="Share this article on Facebook" href="http://www.facebook.com/sharer.php?t=Pharo News #1&u=http://www.pharo-project.org/news?article=pharo-news-1"><span>Share this article on Facebook</span></a> <a rel="nofollow" class="cb-delicious" title="Share this article on Delicious" href="http://del.icio.us/post?title=Pharo News #1&url=http://www.pharo-project.org/news?article=pharo-news-1"><span>Share this article on Delicious</span></a> <a rel="nofollow" class="cb-digg" title="Share this article on Digg" href="http://digg.com/submit?title=Pharo News #1&url=http://www.pharo-project.org/news?article=pharo-news-1"><span>Share this article on Digg</span></a> </div>]]></content:encoded> </item> -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Oct. 25, 2011

Re: [Pharo-project] Jenkis small delay possible?

by Benjamin

You can put your config in another repo and add the listener on this repo changes Maybe the simplest :) Ben On Oct 24, 2011, at 6:04 PM, Camillo Bruni wrote: > Can't you make it dependent on the configuration? > Like that you would only fire a build after the configuration was pushed, which, hopefully, refers to packages that actually exist :) > > cami > > On 2011-10-24, at 13:15, Igor Stasenko wrote: > >> On 24 October 2011 11:23, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >>> Marcus, the problem is that jenkis is working VERY well ;) Now, really, >>> the thing is that I have a lot of packages, and when I change in several of >>> them, when I commit the first package, Jenkis automatically fires up a >>> build. That happens even before I can commit the rest of the packages. >>> Hence...the build become unstabe, and just in the next build it becomes >>> stable again... >>> So...I was wondering, maybe we can put kind of delay ? so that Jenkis does >>> not trigger a build immediatly, but say, after 5 minutes? (that gives me >>> time to commit all packages) >>> >> >> The solution is simple, as to me: >> Do not commit the first, before you commit the rest :) >> >> Apparently, if jenkins watching for changes in PackageA, which depends >> on PackageB, >> first you should commit B, and only then A. >> >>> Thanks >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > >

Oct. 25, 2011

Re: [Pharo-project] Jenkis small delay possible?

by Yanni Chiu

On 24/10/11 12:04 PM, Camillo Bruni wrote: > Can't you make it dependent on the configuration? Like that you would > only fire a build after the configuration was pushed, which, > hopefully, refers to packages that actually exist :) If the configuration you want to build is the baseline (i.e. the latest package versions), then there will always be a time window where the set of packages would be inconsistent. I suppose you could trigger a build based on the configuration, but in the case of the baseline you would just "touch" the configuration (i.e. commit, but no actual change) - a "poor man's" atomic commit.

Oct. 25, 2011