- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.3] #13146
by StÃ©phane Ducasse April 13, 2011

April 13, 2011

13146 ----- - Issue 3991: use them instead of UITheme current. Thanks Fernando Olivero. You were faster than me on this one but this is cool since I could review the code faster. Stef

1 0

[Pharo-project] Fwd: [Seaside] Should I become a Seasider?
by stephane ducasse April 13, 2011

April 13, 2011

we should have that in our success stories. Stef Begin forwarded message: > From: Sven Van Caekenberghe <sven(a)beta9.be> > Date: April 9, 2011 10:25:39 AM GMT+02:00 > To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> > Subject: Re: [Seaside] Should I become a Seasider? > Reply-To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> > > > On 09 Apr 2011, at 09:35, Johan Brichau wrote: > >> Well, to make a long story short, we did exactly that 2 years ago: www.inceptive.be >> Our two core projects are built using Seaside. One of them is already public: www.yesplan.be. The second one is going public by summer. >> >> In one project, we got started explicitly because we were offering a Seaside-based solution. The customer had very bad experiences with traditional software development houses and was explicitly looking for an agile team using a dynamic language to do the job. So, it's fair to say that this was a unique opportunity. However, Seaside and Smalltalk did deliver! In only a single man-year of working hours (not counting the designer), we had produced a working application that other "established" development houses had failed to deliver. Whenever we show the functionality of the application to partnering software producers, they are amazed by the productivity we had gotten. Ah... and it should mention that one person in our team of three had never done any Seaside.... >> >> But, in our second Seaside project, the customers don't care at all what technology is used. They want a good product! And, in my opinion, that is true for many other potential projects we have down the pipeline. For us, Seaside and Smalltalk are powerful tools we can use to leverage a better price and better product in comparison to competitors. In the end, that is what customers want. >> >> In other projects, we are exposed to .net, ios, objective-c, etc... and I generally miss a lot of the power and simplicity of Smalltalk. There is a lot of power in Smalltalk and the Smalltalk community when you look at Gemstone, Seaside, Pharo, Squeak, Visualworks, Cog, etc... ! >> >> There are (of course) occasions when I curse on Smalltalk in general: the lack of (or difficult) interoperability with non-Smalltalk based libraries and the relative small size of Smalltalk libraries is often the biggest hurdle. For every project we intend to do in Smalltalk, we have to carefully analyze the requirements and see if we can meet all of them in the Smalltalk environment. MS-Office interoperability, for example, is a nightmare. >> >> Bottomline: Seaside and Smalltalk are currently our core technologies but not our *only* technologies. You cannot start a business on a single technology and doing business is more than technology.... there are many factors playing a role. > > Yesplan seems very impressive, Johan, this is really looking more and more like a super Success Story. > I absolutely agree with your points/analysis: technology does matter, as does the team, but a great product/solution is the final delivery. > Thanks for sharing all this! > > Sven > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

1 0

[Pharo-project] [update 1.3] #13145
by Marcus Denker April 12, 2011

April 12, 2011

13145 ----- Issue 4000: Little improvement in MenuMorph Issue 3998: Cleanup MVC compatibility methods in Displayscanner Issue 4001: clean more unused postscript canvas methods -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3995 in pharo: alt+k when no window is open throws a debugger
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Accepted Owner: damien.c...(a)gmail.com Labels: Milestone-1.2.2 Type-ReportDefect Difficulty-Easy New issue 3995 by damien.c...(a)gmail.com: alt+k when no window is open throws a debugger http://code.google.com/p/pharo/issues/detail?id=3995 1- Download Pharo-1.2.1-OneClick 2- Open it 3- Close all open windows 4- press alt+k Debugger is coming

1 3

[Pharo-project] Issue 4001 in pharo: clean more unused postscript canvas methods
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: Closed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 4001 by marcus.d...(a)gmail.com: clean more unused postscript canvas methods http://code.google.com/p/pharo/issues/detail?id=4001 clean more unused postscript canvas methods in 13145 Attachments: CleanPostScriptCanvas.1.cs 707 bytes

1 0

[Pharo-project] Issue 3998 in pharo: Cleanup MVC compatibility methods in Displayscanner
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3998 by marcus.d...(a)gmail.com: Cleanup MVC compatibility methods in Displayscanner http://code.google.com/p/pharo/issues/detail?id=3998 Cleanup MVC compatibility methods in Displayscanner All unsent. ... reduces the use of #grafPort considerable. Attachments: CleanMvc.1.cs 1.2 KB

1 1

[Pharo-project] Issue 4000 in pharo: Little improvement in MenuMorph
by pharo＠googlecode.com April 12, 2011

April 12, 2011

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Nautilus New issue 4000 by Benjamin...(a)gmail.com: Little improvement in MenuMorph http://code.google.com/p/pharo/issues/detail?id=4000 Now, if a menu item is disabled, the submenu is not drawn Attachments: MenuItemSpec.1.cs 1.4 KB

1 1

[Pharo-project] [COTDC] 46 - SUnitUnloader
by laurent laffont April 12, 2011

April 12, 2011

Today: SUnitUnloader 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

2 2

Re: [Pharo-project] Please clarify which versions to report issues on
by Marcus Denker April 12, 2011

April 12, 2011

On Apr 12, 2011, at 9:33 PM, DougEdmunds wrote: > Where's the best place to get the most recent v 1.3 on any given day? > > Some choices appear to be: > > 1. https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/ > (but which link?) The latest image is this: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%20Core%201.3/la… > 2. http://www.pharo-project.org/pharo-download : the link to "PharoCore 1.3 > (just core)" Hudson needs to start somewhere, and loading 140 updates is to slow. So we checkpoint all 10-20 updates (good to have anyway), and that is linked here: http://www.pharo-project.org/pharo-download/unstable-core It tends to be a relatively un=broken image, too. The hudson one is build after *every* update, and can be in need of another update to be usable. (But that does not happen often) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Please clarify which versions to report issues on
by Marcus Denker April 12, 2011

April 12, 2011

On Apr 12, 2011, at 7:00 PM, DougEdmunds wrote: > If you start to open a new issue on > http://code.google.com/p/pharo/issues/list > this is what appears: > > "We are currently working on version 1.2, so please verify your issue with > the latest 1.2 Unstable version before reporting it - we improved a lot > the system." > We forgot to update this. So I updated it now. We are working on 1.3. 1.2 will only see fixes of real bugs of the kind that are extremely important. > But on http://www.pharo-project.org/pharo-download, the 'unstable' version > is listed as > Pharo 1.3 image (unstable), with a link to PharoCore 1.3 (just core). > > Is there another place to go to for 1.2 Unstable? Or should everything be > reported against 1.3? > 1.3 > If it is 1.3, can someone update the default text new issue info on > code.google.com? DONE -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1