- Pharo-dev - lists.pharo.org

[Pharo-project] [OT] GTK3 directions - what about Morphic ?
by laurent laffont March 22, 2011

March 22, 2011

Hi, I've seen: - you can style GTK3 with CSS: http://gnomejournal.org/article/107/styling-gtk-with-css - GTK3 apps can be rendered in a web browser: http://blogs.gnome.org/alexl/2010/11/23/gtk3-vs-html5/ This sounds sexy. I wonder how hard it would be to have SimpleMorphic go in this direction. And whether this is useful or not. Laurent.

3 4

[Pharo-project] in 13101 it looks like I broke the toolbar. I need help
by StÃ©phane Ducasse March 22, 2011

March 22, 2011

hi guys can you have a look. Apparently the tool bar does not receive event. Stef

1 1

[Pharo-project] Pharo 2010 - Thank you!
by Sven Van Caekenberghe March 22, 2011

March 22, 2011

Since about the middle of 2010 I have been actively following Pharo and it has been an amazing time. These are my highlights, there are probably many others. 0.x became 1.0, then came 1.1 and finally 1.1.1. There has been amazing activity on 1.2. Seaside became 3.0. I learned how to deploy Seaside and manage it in production. I learned how to work efficiently with Monticello and SqueakSource. Hudson integration servers were customized and deployed for various Smalltalk projects and for Pharo itself. I learned how to build my own development and deployment images. I learned how to do load balancing and static content serving for Seaside. I love the Glamorous theme and the improved DejaVuBitmapFonts loader, I like the the Pro theme. I am successfully using Glorp and PostresV2. I am using the Cog VM every day. I simply love developing in Pharo. The Pharo community is just as great, from the leadership to the core developers, the dev image developers, the application and framework developers, those doing documentation, screencasts, help systems, the testers, to the countless people answering questions on this list. Thank you all ! Sven PS: I can't wait for 2011. PPS: Of course, part of the above are results of the greater Smalltalk community. Pharo is my view into this world.

6 20

Re: [Pharo-project] [COTDC] 34 - MCSystemCategoryParser -- help needed, seriously
by laurent laffont March 22, 2011

March 22, 2011

Hi people, almost no participation in COTDC last days. I'm not a Smalltalk guru and even 30mn to look at code is sometimes not enough for me to understand some stuff alone. I like COTDC because of http://code.google.com/p/pharo/wiki/CommentOfTheDayContest ==> documentation. But quality / good comment is needed and there's ~600 classes without comment remaining. So if we want a 100% good commented Pharo in 2 years from now, we should do it every day. Laurent Laffont On Mon, Mar 21, 2011 at 8:36 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Could it be: > > I parse PackageInfo statement from Monticello packages file. > > Laurent. > > > > On Mon, Mar 21, 2011 at 8:02 AM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Today: MCSystemCategoryParser >> >> >> Comment Of The Day Contest - One Day One Comment >> Rules: >> #1: Each day a not commented class is elected. Each day the best comment >> will be integrated with name of the author(s). >> #2: If you cannot comment it, deprecate it. >> Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest >> >> Laurent >> > >

3 4

[Pharo-project] Issue 3843 in pharo: isHealthy for HasedCollection
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: Accepted Owner: stephane...(a)gmail.com New issue 3843 by stephane...(a)gmail.com: isHealthy for HasedCollection http://code.google.com/p/pharo/issues/detail?id=3843 Some integrity checks for Dictionary and friends Attachments: HashedCollection-IntegrityCheck.2.cs 10.0 KB

1 4

Re: [Pharo-project] Issue 2672 in pharo: Remove UpdatingXXXMorph ....
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Updates: Labels: -Milestone-1.3 Comment #3 on issue 2672 by marcus.d...(a)gmail.com: Remove UpdatingXXXMorph .... http://code.google.com/p/pharo/issues/detail?id=2672 (No comment was entered for this change.)

1 0

Re: [Pharo-project] Issue 2543 in pharo: RealEstateAgent should be cleaned
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Updates: Labels: -Milestone-1.3 Comment #2 on issue 2543 by marcus.d...(a)gmail.com: RealEstateAgent should be cleaned http://code.google.com/p/pharo/issues/detail?id=2543 (No comment was entered for this change.)

1 0

[Pharo-project] Issue 3840 in pharo: ivar errorHandler in Process seems to be unused
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3840 by marcus.d...(a)gmail.com: ivar errorHandler in Process seems to be unused http://code.google.com/p/pharo/issues/detail?id=3840 errorHandler has just accessors. These are not sent in core.

1 2

[Pharo-project] [update 1.3] #13103
by Marcus Denker March 22, 2011

March 22, 2011

13103 ----- Issue 3821: makeStrong/makeWeak contains a bug Issue 3843: isHealthy for HasedCollection Issue 3840: ivar errorHandler in Process seems to be unused -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3821 in pharo: makeStrong/makeWeak contains a bug
by pharo＠googlecode.com March 22, 2011

March 22, 2011

Status: Accepted Owner: stephane...(a)gmail.com CC: siguc...(a)gmail.com, ryd...(a)gmail.com Labels: Milestone-1.3 New issue 3821 by stephane...(a)gmail.com: makeStrong/makeWeak contains a bug http://code.google.com/p/pharo/issues/detail?id=3821 makeStrong/makeWeak contains a bug, because it is using #becomeForward: but doesn't takes into account that subscription stored in a set , which is hash-based , so after become, the item will be at wrong position. So, we need to implement announcer>>replace: subscription with: newOne then a) we don't have to use become b) it will be thread safe, because you can protect replacement in subscription registry with monitor As an alternative, we can use Set instead of IdentitySet, and implement #hash and #== for subscriptions which don't changing when you switch between weak/strong. Then we can keep using #becomeForward: -- Best regards, Igor Stasenko AKA sig.

1 2