Re: [Pharo-project] Understanding regular expression matching

'(\d+)' asRegex search: 'value: 6474 mm'; subexpression: 1. answers 6474. See - http://www.pharocasts.com/2010/05/dynamic-finder-with-doesnotunderstand.html - https://gforge.inria.fr/frs/download.php/26818/Regex.pdf Laurent Laffont - @lolgzs Pharo Smalltalk Screen

Re: [Pharo-project] A new GUI visual designer

Hi. I wrote these Widgets and the Morphic Designer mostly from scratch. There is almost no stacking of libraries. ;) Widgets need Signals and Animations which I also wrote from scratch and which do not have any dependencies other than Squeak 4.1 and later. For now, I reused: - PluggableTextMor

Re: [Pharo-project] what is the goal of warpImage: aForm transform:aTransform

So for me I would remove it. We should get lightweight at the Morphic level to be able to redesign it and then after we can readd functionality when needed. Stef > This appears to haved been used by KedamaMorph in Squeak for scaling (rather > than using an intermediate Form). > Probably worth k

Re: [Pharo-project] Hudson and Squeaksource statistics

I do not think so. Squeaksource was always instable. Then soon we will have a cool server (in about two or three months). Now hudson automatic builds are **really** important to us (they are the basis for software engineering practices with a stress on engineering) so do not spoil our fun, you wi

Re: [Pharo-project] about FS: a roadmap

- renamed workingDirectory into workingDirectoryPath - added FSDiskFileSystem class>>workingDirectory - renamed working into workingDirectory. - deprecate working - better printOn: for DirectoryEntry - comments allChildren, allFiles, allDirectories, children, files, directories, childDirectorie

[Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

Hi guys let us do another pass at cleaning and realigning the system. Could we agree to deprecate caseOf: and caseOf:otherwise:? it will simply the compiler, decompiler and also we do not need that at all. | z | z := {[#a]->[1+1]. ['b' asSymbol]->[2+2]. [#c]->[3+3]}. #b caseOf: z => "| z | z :=

Re: [Pharo-project] about FS: a roadmap

- first cut at rename support - for FSReference and FSFileSystem (only FSDiscFilesystem). - added fullName to FSPath, FSReference, FSLocator - more comments - should do MemoryFS rename: - deprecate childDirectories and childFiles to use directories and files instead. Stef

Re: [Pharo-project] List weekly digest

This is cool. Thank you ! Could you put it directly on pharo-project.org website ? Or may be there is a way to use RSS in pharo-project.org to display the weekly news ? Laurent On Fri, Feb 11, 2011 at 10:55 PM, Francois Stephany < tulipe.mouta...@gmail.com> wrote: > Hi, > > I've posted a small

Re: [Pharo-project] A new GUI visual designer

On Feb 11, 2011, at 5:23 PM, Tobias Pape wrote: > Hi again > > Am 2011-02-11 um 14:26 schrieb Stéphane Ducasse: >>> >> How do they compare with announcements and event and #changed >> >> In the case of the UIBuilder of void, there are new widgets that extend >> existing ones but >> It would

Re: [Pharo-project] A new GUI visual designer

tobias if you want to think that I'm an asshole and I do not want to have a better UI, you are free to think that. Now this is not the case. So if you can read my mail with the eyes of somebody that fight daily to make the system nicer, better, smaller So there is an engineering

Re: [Pharo-project] A new GUI visual designer

Hi marcel thanks for this post > > Hi. > > I wrote these Widgets and the Morphic Designer mostly from scratch. There is > almost no stacking of libraries. ;) Good news. Now do they replace in functionality existing ones? I mean - do they are new? - can/should they replace exis

Re: [Pharo-project] A new GUI visual designer

I was rereading that and I will take me time to deeply understand the table. > Had you read the Wiki, you would know. > “convenient, lightweight and thread-safe callbacks” > https://www.hpi.uni-potsdam.de/hirschfeld/trac/SqueakCommunityProjects/wiki/signals > https://www.hpi.uni-potsdam.de/hirsch

Re: [Pharo-project] Hudson and Squeaksource statistics

> See www.squeaksource.com: >>> "Most Downloads: Pharo, Seaside, Seaside 3.0, Moose, ..." >>> >>> Side effect of the Hudson builds ;) >> >> Hm, maybe this is the cause of the recent performance problems of >> squeaksource.com. > > Each Hudson job retains its own package-cache directory, which is

Re: [Pharo-project] List weekly digest

excellent Francois if we could have this summary weekly it would be a **huge** contribution to the community. I know that adrian, geert, sean and dmitri were talking about a blog on pharo-project so I imgaine that you could join efforts. Stef > Hi, > > I've posted a small digest of past week a

[Pharo-project] Issue 3697 in pharo: UI Enhancements

Status: Fixed Owner: stephane...@gmail.com Labels: Milestone-1.3 New issue 3697 by stephane...@gmail.com: UI Enhancements http://code.google.com/p/pharo/issues/detail?id=3697 Shift-click for PluggableListMorphOfMany. Not Perfect but better than nothing. Have a play (e.g. Select Classes from

[Pharo-project] Issue 3698 in pharo: removing caseOf:

Status: Fixed Owner: stephane...@gmail.com CC: marcus.d...@gmail.com Labels: Milestone-1.3 New issue 3698 by stephane...@gmail.com: removing caseOf: http://code.google.com/p/pharo/issues/detail?id=3698 Hi guys let us do another pass at cleaning and realigning the system. Could we agree to depre

[Pharo-project] ConfigurationOfGlorpDBX

Hi, While switching to Pharo 1.2 (starting from the Seaside CI build), I loaded ConfigurationOfGlorpDBX. This worked fine (after also loading PostgresV2 in my case and setting some defaults). So thanks a lot to whoever maintained the configs and packages. However, the Compiler package in now d

Re: [Pharo-project] List weekly digest

On 12 Feb 2011, at 10:08, Stéphane Ducasse wrote: > excellent > Francois if we could have this summary weekly it would be a **huge** > contribution to the community. > I know that adrian, geert, sean and dmitri were talking about a blog on > pharo-project so I imgaine that you could join effort

Re: [Pharo-project] ConfigurationOfGlorpDBX

Hi sven A message to people :) If you extend a core package with a method that you think should be in core please say it, open a bug entry, and tell us. Stef On Feb 12, 2011, at 10:15 AM, Sven Van Caekenberghe wrote: > Hi, > > While switching to Pharo 1.2 (starting from the Seaside CI build

[Pharo-project] Fwd: [squeak-dev] Object>>is:

I can understand your position. I do not have strong opinion on that and indeed I would like to avoid that this is becoming handy to do isKindOf: so may be we should remove is: Stef On Feb 11, 2011, at 9:56 PM, Colin Putney wrote: > On Thu, Feb 10, 2011 at 5:41 PM, Igor Stasenko wrote: > >>

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

Updates: Status: Fixed Comment #53 on issue 3583 by stephane...@gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Apparently in 1.3 there are places where texMorph is nil and it DNU when sent beStyled Fix attached now we sh

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

Comment #54 on issue 3583 by stephane...@gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Apparently in 1.3 there are places where texMorph is nil and it DNU when sent beStyled Fix attached now we shoudl defined two method in the

Re: [Pharo-project] Issue 3696 in pharo: Default style loading problem

Comment #1 on issue 3696 by stephane...@gmail.com: Default style loading problem http://code.google.com/p/pharo/issues/detail?id=3696 Tx. I will integrate them.

Re: [Pharo-project] External Browser

Waht I meant is External Web Browser does not seem to work with Pharo1.2/Ubuntu 10.4. Or could it be related to the VM ? Hilaire Le 11/02/2011 16:41, Hilaire Fernandes a écrit : > I am just testing this package (installed with the metacello > configuration) under Ubuntu 10.04, so far this method

Re: [Pharo-project] List weekly digest

I'll try to keep up with this weekly summary. Is there a public discussion about a blog somewhere ? On 12/02/11 10:08, Stéphane Ducasse wrote: excellent Francois if we could have this summary weekly it would be a **huge** contribution to the community. I know that adrian, geert, sean and dmitri

Re: [Pharo-project] A new GUI visual designer

Feel free to ask if some phrasing of a feature is not as clear as it should be. Maybe I should add more elaborate descriptions. :) Marcel -- View this message in context: http://forum.world.st/A-new-GUI-visual-designer-tp3067111p3302561.html Sent from the Pharo Smalltalk mailing list archive at

Re: [Pharo-project] External Browser

I will have a look at it 2011/2/12 Hilaire Fernandes > Waht I meant is External Web Browser does not seem to work with > Pharo1.2/Ubuntu 10.4. Or could it be related to the VM ? > > Hilaire > > > Le 11/02/2011 16:41, Hilaire Fernandes a écrit : > > I am just testing this package (installed with

Re: [Pharo-project] List weekly digest

On Sat, Feb 12, 2011 at 10:29 AM, Francois Stephany < tulipe.mouta...@gmail.com> wrote: > I'll try to keep up with this weekly summary. > Is there a public discussion about a blog somewhere ? In the ML archives. The blog exists: http://pharo-project.org/news Laurent. > > > On 12/02/11 10:08,

Re: [Pharo-project] A new GUI visual designer

My knowledge of Smalltalk/Squeak/Pharo is limited, but I believe somethings. 1- I believe Pharo/Squeak needs a different way for "render" the morphs. I suppose Rome go to that direction. 2- A language, human readable, for define the UI. I believe than XAML or XUL, based on XML, be good examples.

Re: [Pharo-project] Understanding regular expression matching

Hi Laurent, '(\d+)' asRegex > search: 'value: 6474 mm'; > subexpression: 1. > answers 6474. > > See > - > http://www.pharocasts.com/2010/05/dynamic-finder-with-doesnotunderstand.html > - https://gforge.inria.fr/frs/download.php/26818/Regex.pdf > > Perfect somehow I'd missed #search: The link to t

Re: [Pharo-project] Hudson and Squeaksource statistics

On Fri, 11 Feb 2011, Stéphane Ducasse wrote: I do not think so. Squeaksource was always instable. Then soon we will have a cool server (in about two or three months). Now hudson automatic builds are **really** important to us (they are the basis for software engineering practices with a stress

Re: [Pharo-project] Issue 3699 in pharo: Beeper beep raises MNU

Updates: Status: New Comment #1 on issue 3699 by abarreau...@gmail.com: Beeper beep raises MNU http://code.google.com/p/pharo/issues/detail?id=3699 (No comment was entered for this change.)

[Pharo-project] Issue 3699 in pharo: Beeper beep raises MNU

Status: New Owner: abarreau...@gmail.com New issue 3699 by abarreau...@gmail.com: Beeper beep raises MNU http://code.google.com/p/pharo/issues/detail?id=3699 If you fill an issue for the first time, please read "How to report bugs" at http://www.pharo-project.org/community/issue-tracking Pharo

Re: [Pharo-project] Issue 3699 in pharo: Beeper beep raises MNU

Comment #2 on issue 3699 by abarreau...@gmail.com: Beeper beep raises MNU http://code.google.com/p/pharo/issues/detail?id=3699 Little mistake: AbstractSoundSystem class>>beep self new beep

Re: [Pharo-project] A new GUI visual designer

I'm sorry but I disagree. XML as a meta-language is old, bad and shit. readable=good xml=really bad (and not-readable either, most of the times... unless you are some kind of cyborg) El 12/02/2011, a las 7:35a.m., nullPointer escribió: > > My knowledge of Smalltalk/Squeak/Pharo is limited,

Re: [Pharo-project] [ANN] Aida/Web 6.2 Spring edition is out

Great stuff Janko! -- View this message in context: http://forum.world.st/ANN-Aida-Web-6-2-Spring-edition-is-out-tp3301723p3302657.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Re: [Pharo-project] A new GUI visual designer

On 12.02.2011, at 13:57, Esteban Lorenzano wrote: > I'm sorry but I disagree. > XML as a meta-language is old, bad and shit. > If you say XML is no-go shouldn't you present an alternative at the same time? Norbert > readable=good > xml=really bad (and not-readable either, most of the times..

Re: [Pharo-project] A new GUI visual designer

Le 12/02/2011 14:14, Norbert Hartl a écrit : > > On 12.02.2011, at 13:57, Esteban Lorenzano wrote: > >> I'm sorry but I disagree. >> XML as a meta-language is old, bad and shit. >> > If you say XML is no-go shouldn't you present an alternative at the same time? Lisp, Scheme or even Smalltalk

Re: [Pharo-project] Issue 3696 in pharo: Default style loading problem

Comment #2 on issue 3696 by stephane...@gmail.com: Default style loading problem http://code.google.com/p/pharo/issues/detail?id=3696 in 13052

Re: [Pharo-project] A new GUI visual designer

On 12.02.2011, at 14:20, Hilaire Fernandes wrote: > Le 12/02/2011 14:14, Norbert Hartl a écrit : >> >> On 12.02.2011, at 13:57, Esteban Lorenzano wrote: >> >>> I'm sorry but I disagree. >>> XML as a meta-language is old, bad and shit. >>> >> If you say XML is no-go shouldn't you present an

Re: [Pharo-project] A new GUI visual designer

Yes, Smalltalk :) You can do exactly the same in a much better way. Last 10 years the world tried to use XML to... well, pretty much everything: as a meta-language to many DSLs, like XUL, XAML, but also for configurations, state-machines, etc. And it was a big failure... and the best example i

[Pharo-project] [update 1.3] #13052

13052 - - Issue 3583: beStyled and unStyled. - Issue 3696: Default style loading problem. Thanks Alain Plantec. Stef

Re: [Pharo-project] A new GUI visual designer

On 12.02.2011, at 14:32, Esteban Lorenzano wrote: > Yes, Smalltalk :) > You can do exactly the same in a much better way. > > Last 10 years the world tried to use XML to... well, pretty much everything: > as a meta-language to many DSLs, like XUL, XAML, but also for configurations, > state-ma

Re: [Pharo-project] Issue 3696 in pharo: Default style loading problem

Updates: Status: Closed Comment #3 on issue 3696 by stephane...@gmail.com: Default style loading problem http://code.google.com/p/pharo/issues/detail?id=3696 in 12334

[Pharo-project] [update 1.2] #12334

12334 - Issue 3696:Default style loading problem. Thanks Alain Plantec. Stef

Re: [Pharo-project] Issue 3699 in pharo: Beeper beep raises MNU

Updates: Status: Accepted Labels: 1.2 1.3 Comment #3 on issue 3699 by stephane...@gmail.com: Beeper beep raises MNU http://code.google.com/p/pharo/issues/detail?id=3699 confirmed!

Re: [Pharo-project] Issue 3699 in pharo: Beeper beep raises MNU

Updates: Status: Fixed Comment #4 on issue 3699 by stephane...@gmail.com: Beeper beep raises MNU http://code.google.com/p/pharo/issues/detail?id=3699 (No comment was entered for this change.) Attachments: Beeper.StephaneDucasse.1.cs 365 bytes

Re: [Pharo-project] Issue 3699 in pharo: Beeper beep raises MNU

Comment #5 on issue 3699 by stephane...@gmail.com: Beeper beep raises MNU http://code.google.com/p/pharo/issues/detail?id=3699 in 13053

Re: [Pharo-project] Issue 3689 in pharo: Transcript preference for #characterLimit

Updates: Status: Closed Comment #5 on issue 3689 by stephane...@gmail.com: Transcript preference for #characterLimit http://code.google.com/p/pharo/issues/detail?id=3689 in 13051

Re: [Pharo-project] Issue 1057 in pharo: SerialPlugin doesn't handle arbitrary nodes names

Comment #12 on issue 1057 by stephane...@gmail.com: SerialPlugin doesn't handle arbitrary nodes names http://code.google.com/p/pharo/issues/detail?id=1057 in 13053

Re: [Pharo-project] Issue 1057 in pharo: SerialPlugin doesn't handle arbitrary nodes names

Updates: Status: closed Comment #13 on issue 1057 by stephane...@gmail.com: SerialPlugin doesn't handle arbitrary nodes names http://code.google.com/p/pharo/issues/detail?id=1057 (No comment was entered for this change.)

Re: [Pharo-project] Issue 3546 in pharo: Have a look at SystemReporter

Comment #4 on issue 3546 by stephane...@gmail.com: Have a look at SystemReporter http://code.google.com/p/pharo/issues/detail?id=3546 first let us make it work in 1.3 because 1.2 is in release candidate and we should avoid to change it. Now if the systemreporter can be made loadable in 1.2

Re: [Pharo-project] Issue 2004 in pharo: Object>>windowActiveOnFirstClick looks strange

Comment #3 on issue 2004 by stephane...@gmail.com: Object>>windowActiveOnFirstClick looks strange http://code.google.com/p/pharo/issues/detail?id=2004 I would really like to have a distinction between an object and a model. I think that having everything in Object is not good.

Re: [Pharo-project] List weekly digest

woow, excellente, and I imagine, very hard to maintain. Thanks. 2011/2/11 Francois Stephany : > Hi, > > I've posted a small digest of past week activity in the Pharo-Project ML. I > find it difficult to follow the pace of this list so I hope it will be > useful to some of you. I will try to post

[Pharo-project] DrGeo in success stories

Hi, I was impressed by DrGeo at PharoConf. It's used by several schools. Is it OK to add it to the success stories page on pharo-project.org ? Laurent Laffont - @lolgzs Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Re: [Pharo-project] DrGeo in success stories

sure! Stef On Feb 12, 2011, at 5:17 PM, laurent laffont wrote: > Hi, > > I was impressed by DrGeo at PharoConf. It's used by several schools. Is it OK > to add it to the success stories page on pharo-project.org ? > > > Laurent Laffont - @lolgzs > > Pharo Smalltalk Screencasts: http://www.p

[Pharo-project] New success story online

We've added a new success story about a large Argentinian application based on Pharo: http://pharo-project.org/about/success-stories If you know about other interesting projects, please let me know. Cheers, Adrian __ www.adrian-lienhard.ch twitter.com/adrianlien

[Pharo-project] [COTDC] 9 - HTTPDownloadRequest

Today: HTTPDownloadRequest 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/Com

Re: [Pharo-project] A new GUI visual designer

Am 2011-02-12 um 09:54 schrieb Stéphane Ducasse: > tobias > > if you want to think that I'm an asshole and I do not want to have a better > UI, you are free to think that. Please rest assured that this is _not_ the case. I just was astonished that you denied the usability of the Gui builder wit

Re: [Pharo-project] A new GUI visual designer

> > > >>> In the case of the UIBuilder of void, > >> > >> Void? > > The nikname of the personn > > He is called Marcel and posted elsewhere in the thread. I think that Stef is refering to nullPointer that also worked on a GUI Builder Cheers -- Miguel Cobá http://twitter.com/MiguelCobaMtz ht

Re: [Pharo-project] A new GUI visual designer

Am 2011-02-12 um 18:31 schrieb Miguel Cobá: > In the case of the UIBuilder of void, Void? >>> The nikname of the personn >> >> He is called Marcel and posted elsewhere in the thread. > > I think that Stef is refering to nullPointer that also worked on a GUI > Builder Ok, thanks f

[Pharo-project] [Hudson] Cog Unix build

Hudson news -- Cog Unix https://pharo-ic.lille.inria.fr/hudson/job/Cog%20Unix%201.3/ This is using Igor's non-interactive build. Hudson does the following: git clone git://gitorious.org/~abrabapupa/cogvm/sig-cog.git cd sig-cog/codegen-scripts sh ./buildImage.sh

Re: [Pharo-project] DrGeo in success stories

I take the description on http://community.ofset.org/index.php/DrGeo ? Do you how many schools / teachers use it approximatively ? Laurent On Sat, Feb 12, 2011 at 5:59 PM, Hilaire Fernandes < hilaire.fernan...@gmail.com> wrote: > Sure! > > Hilaire > > Le 12/02/2011 17:17, laurent laffont a écri

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On Fri, 11 Feb 2011, stephane ducasse wrote: Hi guys let us do another pass at cleaning and realigning the system. Could we agree to deprecate caseOf: and caseOf:otherwise:? it will simply the compiler, decompiler and also we do not need that at all. | z | z := {[#a]->[1+1]. ['b' asSymbol]->[2

Re: [Pharo-project] [Hudson] Cog Unix build

really cool! Next week I will prepare scripts for doing same with cocoa cog and cocoa stack vms, if you agree :) Cheers, Esteban El 12/02/2011, a las 2:38p.m., Marcus Denker escribió: > Hudson news > -- > > Cog Unix > > https://pharo-ic.lille.inria.fr/hudson/job/C

Re: [Pharo-project] [Hudson] Cog Unix build

On Feb 12, 2011, at 9:43 AM, Esteban Lorenzano wrote: > really cool! > Next week I will prepare scripts for doing same with cocoa cog and cocoa > stack vms, if you agree :) > Yes! We will get a mac mini from INRIA for the mac build and tests. Marcus -- Marcus Denker -- http://www.m

Re: [Pharo-project] A new GUI visual designer

Create the UI with plain Smalltalk code have problems... my UIBuilder use that system and have limitations for limit of lityerals in a spec method, and other problems. Another alternative is the VW or Smalltalk/X mechanism, no readable, no updatable; only could be modified for the same designer r

Re: [Pharo-project] A new GUI visual designer

No, I don't believe anything except smalltalk is bad. Just XML. I worked with Java, C# and a lot of XML to know that. Don't be confused... I'm not talking against XML alternatives because of microsoft or anything, I have serious technical complains against it. Also, XUL is not microsoft's and I

Re: [Pharo-project] A new GUI visual designer

On Feb 12, 2011, at 6:22 PM, Tobias Pape wrote: > Am 2011-02-12 um 09:54 schrieb Stéphane Ducasse: >> tobias >> >> if you want to think that I'm an asshole and I do not want to have a better >> UI, you are free to think that. > > Please rest assured that this is _not_ the case. ok good > I j

Re: [Pharo-project] A new GUI visual designer

On Feb 12, 2011, at 6:59 PM, nullPointer wrote: > > Create the UI with plain Smalltalk code have problems... my UIBuilder use > that system and have limitations for limit of lityerals in a spec method, > and other problems. No because one single array can contain all the specs. They do that in

Re: [Pharo-project] A new GUI visual designer

xml is good a simple interexchange format. Now when you have you xml stream you have to map your nodes (different to objects) so for UISPec you can just get a parser and object builder for free. NO need to load XMLSupport. read my VW examples to understand. In VW you can click on a button and

Re: [Pharo-project] A new GUI visual designer

>> no >> updatable; >??? >> only could be modified for the same designer routine. >??? Can you modify manually the code generated for the UI Painter of VW? I´m not; I´m not mutant :) The use of XAML or XUL is for portability. Exists many tools for design a GUI in XAML or XUL. The perfect GU

Re: [Pharo-project] [Hudson] Cog Unix build

On 12 February 2011 18:50, Marcus Denker wrote: > > On Feb 12, 2011, at 9:43 AM, Esteban Lorenzano wrote: > >> really cool! >> Next week I will prepare scripts for doing same with cocoa cog and cocoa >> stack vms, if you agree :) >> > Yes! We will get a mac mini from INRIA for the mac build and t

[Pharo-project] saving a monticello working copy

Hi, Does anyone know a simple way to save a Monticello working copy into the package-cache? Cheers, Doru -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."

Re: [Pharo-project] A new GUI visual designer

2011/2/12 nullPointer : > > >>> no >>> updatable; > >>??? > >>> only could be modified for the same designer routine. > >>??? > > Can you modify manually the code generated for the UI Painter of VW? I´m > not; I´m not mutant :) > > The use of XAML or XUL is for portability. Exists many tools for de

Re: [Pharo-project] [Hudson] Cog Unix build

On 12 February 2011 18:38, Marcus Denker wrote: > Hudson news > -- > > Cog Unix > >        https://pharo-ic.lille.inria.fr/hudson/job/Cog%20Unix%201.3/ > > This is using Igor's non-interactive build. Hudson does the following: > > git clone git://gitorious.org/~abrabapupa/cogvm/sig

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On 12 February 2011 18:41, Levente Uzonyi wrote: > On Fri, 11 Feb 2011, stephane ducasse wrote: > >> Hi guys >> >> let us do another pass at cleaning and realigning the system. >> Could we agree to deprecate caseOf: and caseOf:otherwise:? >> it will simply the compiler, decompiler and also we do n

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On Sat, 12 Feb 2011, Igor Stasenko wrote: oh come on. Switch statement should live where it belongs to: C code. It's nothing like C's switch statement, and I'm sure you know that. Why we should support this ridiculous syntax constructs in smalltalk? What's so ridiculous about it? IMO: A

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On 13 February 2011 00:17, Levente Uzonyi wrote: > On Sat, 12 Feb 2011, Igor Stasenko wrote: > >> oh come on. Switch statement should live where it belongs to: C code. > > It's nothing like C's switch statement, and I'm sure you know that. > >> >> Why we should support this ridiculous syntax const

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On Sun, 13 Feb 2011, Igor Stasenko wrote: Don't try to convince me that there are sort of problems which can be solved only by using case statement :) We all know that it can be solved, but the solution won't be nicer at all, instead it will be a lot slower. First, get rid of these integer

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On 13 February 2011 00:59, Levente Uzonyi wrote: > On Sun, 13 Feb 2011, Igor Stasenko wrote: > >> Don't try to convince me that there are sort of problems which can be >> solved only by using case statement :) > > We all know that it can be solved, but the solution won't be nicer at all, > instead

Re: [Pharo-project] [Hudson] Cog Unix build

Markus, Igor, everyone, this is *excellent work*. It is really a tremendous leap forward. It is amazing how the different efforts (hudson, configuration, modern handling of VM sources, Cog VM, Pharo Core) of the community can converge to something as useful as we see here. Thanks to everyone invo

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On Sun, 13 Feb 2011, Igor Stasenko wrote: On 13 February 2011 00:59, Levente Uzonyi wrote: On Sun, 13 Feb 2011, Igor Stasenko wrote: Don't try to convince me that there are sort of problems which can be solved only by using case statement :) We all know that it can be solved, but the solut

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

El dom, 13-02-2011 a las 02:26 +0100, Levente Uzonyi escribió: > I know what's premature optimization. It appear that you know but doesn't understand. See below. > What I do differently than other > people (including you) is: > - if I can choose from different solutions for some problem, then

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On 13 February 2011 02:26, Levente Uzonyi wrote: > On Sun, 13 Feb 2011, Igor Stasenko wrote: > >> On 13 February 2011 00:59, Levente Uzonyi wrote: >>> >>> On Sun, 13 Feb 2011, Igor Stasenko wrote: >>> Don't try to convince me that there are sort of problems which can be solved only by u

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On Sat, 12 Feb 2011, Miguel Cobá wrote: El dom, 13-02-2011 a las 02:26 +0100, Levente Uzonyi escribió: I know what's premature optimization. It appear that you know but doesn't understand. See below. What I do differently than other people (including you) is: - if I can choose from differ

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On Sun, 13 Feb 2011, Igor Stasenko wrote: Please read the Ian's paper about switch statement vs message sends.. You will discover something surprising for you. Link please? Levente Levente Levente -- Best regards, Igor Stasenko AKA sig. -- Best regards, Igor Stasenk

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

El dom, 13-02-2011 a las 02:58 +0100, Levente Uzonyi escribió: > On Sat, 12 Feb 2011, Miguel Cobá wrote: > > > El dom, 13-02-2011 a las 02:26 +0100, Levente Uzonyi escribió: > > > >> I know what's premature optimization. > > > > It appear that you know but doesn't understand. See below. > > > >>

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On Sat, 12 Feb 2011, Miguel Cobá wrote: El dom, 13-02-2011 a las 02:58 +0100, Levente Uzonyi escribió: On Sat, 12 Feb 2011, Miguel Cobá wrote: El dom, 13-02-2011 a las 02:26 +0100, Levente Uzonyi escribió: I know what's premature optimization. It appear that you know but doesn't understan

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On 13 February 2011 02:58, Levente Uzonyi wrote: > On Sun, 13 Feb 2011, Igor Stasenko wrote: > >> Please read the Ian's paper about switch statement vs message sends.. >> You will discover something surprising for you. > > Link please? > > Here: www.piumarta.com/pepsi/objmodel.pdf- -

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

Ok, guys... I'm sorry to interrupt this polite discussion, but this is taking nowhere. Having such strong arguments (for or against) is not helpful for anybody. We all know using #caseOf:otherwise: it's not exactly good style, but sometimes you need to compromise between design and efficiency, and

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

On 13 February 2011 04:05, Ricardo Moran wrote: > But please don't ban people who are willing to sacrifice a little > readability for performance reasons. Thanks. Then C language is your choice! It is full of such sacrifices :) But can i ask you to not turn smalltalk into C , please? > Best reg

Re: [Pharo-project] A new GUI visual designer

my 0.002 cents: - XML suxx - we need better UI - we need good graphics engine - we need good event system - we need to evaluate all alternatives :) -- Best regards, Igor Stasenko AKA sig.

Re: [Pharo-project] A new GUI visual designer

WindowBuilder is impressive. I'm not sure how to clean room it though. If the concern is over the serialization of objects, has anyone considered SIXX for that? Doing that could give us something similar to the Dolphin ViewComposer but clearly of distinct origin. To the result, we could add

Re: [Pharo-project] A new GUI visual designer

XML suxxx XAML or XUL suxxxs too? regards. -- View this message in context: http://forum.world.st/A-new-GUI-visual-designer-tp3067111p3303424.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Re: [Pharo-project] [Hudson] Cog Unix build

EXCELLENT NEWS > Yes. i found the issue. Now it runs!!! :) > > And i were able to run all tests in pharo 1.3 core image on StackVM: > > 7864 run, 7787 passes, 51 expected failures, 8 failures, 17 errors, 1 > unexpected passes > > no more crashes! :) really really great. >> Ideally, bu

Re: [Pharo-project] could we agree to remove caseOf: and caseOf:otherwise:

Hi ricardo, igor and levente I really want to remove caseOf: since years. Why: - conceptually wrong (even if this may be nice to have for $A and numbers) - to me it looks like coming from another age - never needs to use it: of course other people may of course -