Re: [Pharo-dev] Release Mode

great mail :) On 28 Mar 2014, at 23:03, Nicolai Hess wrote: > 2014-03-28 16:58 GMT+01:00 Marcus Denker : > > On 28 Mar 2014, at 16:53, p...@highoctane.be wrote: > > > The look of nautilus button isn't "ok to integrate" since there is much > > more work needed to get this working properly. > >

Re: [Pharo-dev] DateAndTime>>#= slow?

On Fri, Mar 28, 2014 at 8:17 PM, Ben Coman wrote: > p...@highoctane.be wrote: > > Looks like a lot of people are going to be running patched versions if the > release goes without some enhancements. > > What about a > ConfigurationOfPharo30EnhancementsPackThatWereNotIntegratedForSomeSurelyVeryV

Re: [Pharo-dev] New Nautilus side bar buttons

On 28 Mar 2014, at 17:57, Benjamin wrote: > Hello guys, > > since I do not really like the new buttons introduced in Nautilus, > and since the previous one were broken, I propose this new set > of buttons based on the eclipse theme. > > > > > Tell me what you think about it :) much nicer!

Re: [Pharo-dev] New Nautilus side bar buttons

On 28 Mar 2014, at 23:16, Nicolai Hess wrote: > Really? > > What was wrong with the old one? They look 70’ :) And the B button misses a butt :) Ben

Re: [Pharo-dev] Release Mode

2014-03-28 16:58 GMT+01:00 Marcus Denker : > > On 28 Mar 2014, at 16:53, p...@highoctane.be wrote: > > > The look of nautilus button isn't "ok to integrate" since there is much > more work needed to get this working properly. > > > > Now, the scrollbars in 2.0 really suck if you ask me. So, I'd vo

[Pharo-dev] Font problem identified

Hi guys I found the problem now I will think about the solution. https://pharo.fogbugz.com/default.asp?13149 Stef

Re: [Pharo-dev] funny TIOBE

Stephan Eggermont wrote > Well, I don’t know. We keep on fixing bugs and don’t get any closer to > release :) Feel like this guy?! http://upload.wikimedia.org/wikipedia/commons/4/43/Punishment_sisyph.jpg - Cheers, Sean -- View this message in context: http://forum.world.st/funny-TIOBE-tp47

Re: [Pharo-dev] Capturing stdout

Maybe… Since Pharo now has a command line handler, you could redirect stdout to the vm process? Will probably not work while the image is running I guess. But maybe it will (see for example http://serverfault.com/questions/178457/can-i-send-some-text-to-the-stdin-of-an-active-process-running-in-

Re: [Pharo-dev] funny TIOBE

> Von: Pharo4Stef > > On 28 Mar 2014, at 22:00, Sean P. DeNigris wrote: > > > Pavel Krivanek-3 wrote > >> after a very long time I checked the TIOBE index and Smalltalk is not > >> listed there at all... :-) > > > > Maybe we died and don't know it... must be heaven, not hot enough for the > >

Re: [Pharo-dev] VistaCursors are killing my LinuxVM (beCursor primitive failing)

Yes we have this issue: 12960 Primitive 101 (Cursor beCursor) fails on Ubuntu we just need someone who can edit the pharo vm build config. 2014-03-28 18:52 GMT+01:00 p...@highoctane.be : > I moved a windows image with VistaCursors to Linux and t

Re: [Pharo-dev] funny TIOBE

Sean wrote: >Maybe we died and don't know it... must be heaven, not hot enough for the >other place ;) Well, I don’t know. We keep on fixing bugs and don’t get any closer to release :) Stephan

Re: [Pharo-dev] Every class should redefine printOn:

On 28 Mar 2014, at 22:08, Sven Van Caekenberghe wrote: > I am all for that, but I don't think you can make it that strict, what if > there are no instance variables ? ok :) a smart rule > I like custom #printOn:'s especially for debugging. > > On 28 Mar 2014, at 21:45, Pharo4Stef wrote: >

Re: [Pharo-dev] Every class should redefine printOn:

I am all for that, but I don't think you can make it that strict, what if there are no instance variables ? I like custom #printOn:'s especially for debugging. On 28 Mar 2014, at 21:45, Pharo4Stef wrote: > Hi guys > > I’m trying to understand freeType and when I debug I get aBlah aFoo and this

Re: [Pharo-dev] funny TIOBE

On 28 Mar 2014, at 22:00, Sean P. DeNigris wrote: > Pavel Krivanek-3 wrote >> after a very long time I checked the TIOBE index and Smalltalk is not >> listed there at all... :-) > > Maybe we died and don't know it... must be heaven, not hot enough for the > other place ;) :) > > > > -

Re: [Pharo-dev] funny TIOBE

Pavel Krivanek-3 wrote > after a very long time I checked the TIOBE index and Smalltalk is not > listed there at all... :-) Maybe we died and don't know it... must be heaven, not hot enough for the other place ;) - Cheers, Sean -- View this message in context: http://forum.world.st/funny-T

Re: [Pharo-dev] Capturing stdout

Emilio Oca-3 wrote > I managed to do that in Windows using... ProcessWrapper... As it's for a core test, I need to find a way to do it without loading additional libraries. I could pipe the output to a tmp file if there's nothing... - Cheers, Sean -- View this message in context: http://fo

[Pharo-dev] Every class should redefine printOn:

Hi guys I’m trying to understand freeType and when I debug I get aBlah aFoo and this is frankly annoying because I’m trying to learn the implementation and it does not help me at all. I hate the classes that only their implementors understand. In Pharo 4.0 I will put a strict rule: - no

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

thanks Igor. I’m trying to look at the font reloading bug. On 28 Mar 2014, at 17:19, Igor Stasenko wrote: > https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-different-platforms > > > On 28 March 2014 16:42, Igor Stasenko wrote: > so, the quick and dirty fix is to put: >

Re: [Pharo-dev] DateAndTime>>#= slow?

> It is easy. It is called pharo 3.1 or pharo 4.0. The rule is: Don’t change > the current release being in freeze. Release it, change then everything you > wanted in the next step and make sure you can release the next version pretty > soon. IMHO the best solution to this kind of problems is t

Re: [Pharo-dev] Release Mode

> > > On 28 Mar 2014, at 16:17, Sven Van Caekenberghe wrote: > > > On 28 Mar 2014, at 16:00, Marcus Denker wrote: > > > On 28 Mar 2014, at 15:52, Sean P. DeNigris wrote: > > While I was on holiday, it seems my dear friends have gone feature crazy... > almost as bad as me in the run up to the 2.

[Pharo-dev] funny TIOBE

Hi, after a very long time I checked the TIOBE index and Smalltalk is not listed there at all... :-) Cheers, -- Pavel

Re: [Pharo-dev] New Nautilus side bar buttons

Benjamin wrote >since I do not really like the new buttons introduced in Nautilus, >and since the previous one were broken, I propose this new set >of buttons based on the eclipse theme. Would you be so kind to explain what you do not like about them, and compare to both the earlier ones and this

Re: [Pharo-dev] DateAndTime>>#= slow?

p...@highoctane.be wrote: Looks like a lot of people are going to be running patched versions if the release goes without some enhancements. What about a ConfigurationOfPharo30EnhancementsPackThatWereNotIntegratedForSomeSurelyVeryValidReason ? (Let's make the name shorter but

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

Hi, On Fri, Mar 28, 2014 at 4:01 PM, Igor Stasenko wrote: > > Ookkayy.. > First of all, thanks a lot for offering a fix for the font problem! This was a critical issue for Moose. > so, current status: > > - finally we got an agreement that big red square because of font loading > issues and

Re: [Pharo-dev] [Pharo-users] [ANN] Application Security for your domains

Thank you for reporting. I have added links to Pharo and Fuel websites. Cheers, Hernán 2014-03-28 4:53 GMT-03:00 Pharo4Stef : > the linke o your blog leads to > > http://www.smalltalkhub.com/#%21/%7Ehernan/ApplicationSecurity > > > On 28 Mar 2014, at 00:58, Hernán Morales Durand > wrote: > > Hel

Re: [Pharo-dev] [Moose-dev] Re: Fwd: Font problem is still there

On 28 March 2014 15:01, Tudor Girba wrote: > I added the code in the mail precisely to leave out any ambiguities :). > > The first part of the snippet (as also listed by Vincent) loads the very > latest development version of Athens configuration. So, yes, I think I > loaded the latest code. > >

Re: [Pharo-dev] [Moose-dev] Re: Re: Fwd: Font problem is still there

Yes, I can confirm. But, this is a known issue that in practice has little impact, and it was not related to the issue of rendering in Athens. So, from my point of you, the critical issue is now solved. Thanks! :) Doru On Fri, Mar 28, 2014 at 3:33 PM, Pharo4Stef wrote: > yes but if you unchec

Re: [Pharo-dev] New website about Spec - http://spec.st

Super nice, very professional, congratulations to everybody who working on this! On 28 Mar 2014, at 14:18, Benjamin wrote: > Hi guys :) > > I am glad to announce (even if Philippe already let the cat out :P) a website > dedicated to Spec: http://spec.st. > You can find a quick introduction, do

Re: [Pharo-dev] Capturing stdout

Hi I managed to do that in Windows using ProcessWrapper new useStdout; startWithShellCommand: aCommand ; upToEnd. where aCommand is something like: "someApp.exe -p params moreParams > G:\other\place\stdou.log" This is what Hernan Morales offered > Gofer it >

Re: [Pharo-dev] someone using Magritte-Morph?

EstebanLM wrote > should instead be... Without an image handy, your change looks like good. IIRC I did the display string stuff after I implemented the relation morphs and probably forgot to change it there. - Cheers, Sean -- View this message in context: http://forum.world.st/someone-usin

Re: [Pharo-dev] New Nautilus side bar buttons

On 28 Mar 2014, at 19:35, Benjamin wrote: >> But how dare you propose a change, please stop contributing, I hate people >> who actually do stuff ;-) > > The question is not about people doing things, it’s about introducing things > that are not fixes or critical. > Of it is decided to not int

Re: [Pharo-dev] Release Mode

Marcus Denker wrote: On 28 Mar 2014, at 16:17, Sven Van Caekenberghe wrote: On 28 Mar 2014, at 16:00, Marcus Denker wrote: On 28 Mar 2014, at 15:52, Sean P. DeNigris wrote: While I was

Re: [Pharo-dev] New Nautilus side bar buttons

On 28 Mar 2014, at 19:31, Sven Van Caekenberghe wrote: > Beautiful. Thank you ! Thanks :) > But how dare you propose a change, please stop contributing, I hate people > who actually do stuff ;-) The question is not about people doing things, it’s about introducing things that are not fixes o

Re: [Pharo-dev] New Nautilus side bar buttons

Beautiful. Thank you ! But how dare you propose a change, please stop contributing, I hate people who actually do stuff ;-) On 28 Mar 2014, at 17:57, Benjamin wrote: > Hello guys, > > since I do not really like the new buttons introduced in Nautilus, > and since the previous one were broken,

[Pharo-dev] Release Mode

While I was on holiday, it seems my dear friends have gone feature crazy... almost as bad as me in the run up to the 2.0 release, ha ha. As cool as they are, are: - changing the look of Nautilus buttons - evaluate arbitrary expressions in Spotlight - etc, etc showstopping bugs?! This beta time is

Re: [Pharo-dev] Release Mode

On 28 Mar 2014, at 16:53, p...@highoctane.be wrote: > The look of nautilus button isn't "ok to integrate" since there is much more > work needed to get this working properly. > > Now, the scrollbars in 2.0 really suck if you ask me. So, I'd vote for that > one. > > Welcome back to the fray. >

Re: [Pharo-dev] New website about Spec - http://spec.st

Sorry about that. It wasn't intentional. Superb work. And I want that dark theme :-) Phil On Fri, Mar 28, 2014 at 4:03 PM, Sven Van Caekenberghe wrote: > Super nice, very professional, congratulations to everybody who working on > this! > > On 28 Mar 2014, at 14:18, Benjamin > wrote: > >

Re: [Pharo-dev] Release Mode

The look of nautilus button isn't "ok to integrate" since there is much more work needed to get this working properly. Now, the scrollbars in 2.0 really suck if you ask me. So, I'd vote for that one. Welcome back to the fray. Phil On Fri, Mar 28, 2014 at 3:52 PM, Sean P. DeNigris wrote: >

Re: [Pharo-dev] DateAndTime>>#= slow?

Looks like a lot of people are going to be running patched versions if the release goes without some enhancements. What about a ConfigurationOfPharo30EnhancementsPackThatWereNotIntegratedForSomeSurelyVeryValidReason ? (Let's make the name shorter but you get the idea). Phil On Fri, Mar 28,

Re: [Pharo-dev] [Moose-dev] Re: Fwd: Font problem is still there

On 28 March 2014 14:42, Tudor Girba wrote: > I also tried based on a Moose 5.0 image on OS X 10.9.2: > > Gofer new > smalltalkhubUser: 'Pharo' project: 'Athens'; > configuration; > loadDevelopment. > > AthensSceneView new scene: [ :canvas | |s| > canvas setFont: (Logi

[Pharo-dev] VistaCursors are killing my LinuxVM (beCursor primitive failing)

I moved a windows image with VistaCursors to Linux and the beCursor primitive failed, leading to a white screen opening. Maybe this is because the cursors are bigger than the 16x16 form. I saw discussions of this being fixed in Squeak. Are we having this issue in Pharo? Phil

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

so, the quick and dirty fix is to put: CairoGlyph class>>byteAlignment NativeBoost platformId = NativeBoostConstants win32PlatformId ifTrue: [ ^ 8 ]. ^ super byteAlignment and then: CairoGlyph rebuildFieldAccessors CairoGlyphsArray initialize (note you must run this snippet each time

Re: [Pharo-dev] DateAndTime>>#= slow?

Hi all, With Sven's fixes loaded, our model unit tests are all running fine. The benchmarks indicate the same speed as in 1.4. This is really great! I'm still running the entire suite of tests but that will take a while to complete. But essential datetime bugs should have been spotted already.

Re: [Pharo-dev] [Moose-dev] Re: Re: Fwd: Font problem is still there

De : moose-dev-boun...@iam.unibe.ch [mailto:moose-dev-boun...@iam.unibe.ch] De la part de Stéphane Ducasse Envoyé : vendredi 28 mars 2014 15:39 À : Pharo Development List Cc : Moose-related development Objet : [Moose-dev] Re: [Pharo-dev] Re: Fwd: Font problem is still there In Pharo 3.0 this is

Re: [Pharo-dev] New website about Spec - http://spec.st

On 28 Mar 2014, at 14:43, Pharo4Stef wrote: > What is the best github repo to edit the chapter? https://github.com/spec-framework/documentation, since I would like to gather as much as possible all the things related to spec at only one place :) Ben

Re: [Pharo-dev] Release Mode

On Fri, Mar 28, 2014 at 6:39 PM, Sergi Reyner wrote: > 2014-03-28 16:32 GMT+00:00 Benjamin > : > >> On 28 Mar 2014, at 17:30, Stephan Eggermont wrote: >> >> > Philippe wrote >> >> The look of nautilus button isn't "ok to integrate" since there is >> much more work needed to get this working prop

Re: [Pharo-dev] New Nautilus side bar buttons

Just out of curiosity (this is not a rhetoric question, i just don't know it) - when should i look at the bytecode? And are there enough use cases to justify such a very prominent place in the UI? Or would a place in the context menu be enough? Or a plugin, if there are people - like compiler devel

Re: [Pharo-dev] Release Mode

2014-03-28 16:32 GMT+00:00 Benjamin : > On 28 Mar 2014, at 17:30, Stephan Eggermont wrote: > > > Philippe wrote > >> The look of nautilus button isn't "ok to integrate" since there is much > more work needed to get this working properly. > > > > That's two different issues. One is integrated, the

[Pharo-dev] Contribution process: broken links / missing page

https://code.google.com/p/pharo/wiki/HowToContribute but then https://pharo.fogbugz.com/default.asp?W39 --> doesn't exist Then http://www.pharo-project.org/community/how-to-contribute which leads to "this page explains... --- Philippe Back Visible Performance Improvements Mob: +32(0) 478 650

Re: [Pharo-dev] New Nautilus side bar buttons

I am not a compiler developer but I am interested in bytecodes. The whole set of buttons on that location should be a plugin area IMHO. So that we can easily extend it. NautilusPlugins enhancements would make for a great Pharo4 theme indeed. Phil On Fri, Mar 28, 2014 at 6:24 PM, MartinW wrote

Re: [Pharo-dev] New Nautilus side bar buttons

On 28 Mar 2014, at 18:24, p...@highoctane.be wrote: > Too bad, we'll have to wait for 4.0 (or 3.1 to get them…) As it is actually fixing something, maybe it will make it :) > Jokes aside, they are very nice. And I want them. > Where is the slice? https://pharo.fogbugz.com/default.asp?13151 B

Re: [Pharo-dev] Release Mode

On 28 Mar 2014, at 17:30, Stephan Eggermont wrote: > Philippe wrote >> The look of nautilus button isn't "ok to integrate" since there is much more >> work needed to get this working properly. > > That’s two different issues. One is integrated, the other not. > 13137 The SBIC buttons change is

Re: [Pharo-dev] DateAndTime>>#= slow?

Am 28.03.2014 um 16:56 schrieb p...@highoctane.be: > Looks like a lot of people are going to be running patched versions if the > release goes without some enhancements. > That is the road to never have a release. > What about a > ConfigurationOfPharo30EnhancementsPackThatWereNotIntegratedFor

Re: [Pharo-dev] New website about Spec - http://spec.st

On 28 Mar 2014, at 16:57, p...@highoctane.be wrote: > Sorry about that. It wasn't intentional. No problem :P It motivated me to finish fast :P > Superb work. And I want that dark theme :-) Me too :P Ben

Re: [Pharo-dev] New Nautilus side bar buttons

hi Benjamin,   I really like them better than the current UI mess regarding the right toolbar in Nautilus and would like to see them changed before for the release. But the "I" icon means (Java) interface in Eclipse and the button in Pharo is for instance variables.  The "C" icon means (Java) cl

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

On 28 March 2014 16:01, Igor Stasenko wrote: > > Ookkayy.. > so, current status: > > - finally we got an agreement that big red square because of font loading > issues and font rendering artifacts is two separate issues. > Thanks! > - i am not going to address font-loading issue here and now.. (

Re: [Pharo-dev] New Nautilus side bar buttons

Nice. To make them perfect - The I and C are too dominant. Perhaps have the c use the green from ’tricky asserting’ and the I a bit more pastel? Something that looks a bit more washed out like the theme? Stephan

Re: [Pharo-dev] New Nautilus side bar buttons

On 28 Mar 2014, at 18:24, MartinW wrote: > Just out of curiosity (this is not a rhetoric question, i just don't know it) > - when should i look at the byte code? That’s a good question :) I usually look at byte code when I have strange compilation errors. > And are there enough use cases to jus

Re: [Pharo-dev] Release Mode

Sean wrote: >As cool as they are, are: >- changing the look of Nautilus buttons >showstopping bugs?! Yes. Or at least they should be. Releases are for new users. There the first impression is crucial. We are all used to these ugly buttons and know that the functionality is the same. New users

Re: [Pharo-dev] Capturing stdout

Max Leske wrote > Forget what I said… Just rambling… Ha ha, I was doing the confused-puppy-head-tilt (see http://da0cb6511396a92928c7-488d28a6573db6ac4a247063b638fcb9.r77.cf2.rackcdn.com/files/o-DOG-COCKED-HEAD-facebook.jpg) - Cheers, Sean -- View this message in context: http://forum.worl

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

https://pharo.fogbugz.com/f/cases/13150/Different-memory-alignment-on-different-platforms On 28 March 2014 16:42, Igor Stasenko wrote: > so, the quick and dirty fix is to put: > > CairoGlyph class>>byteAlignment > > NativeBoost platformId = NativeBoostConstants win32PlatformId ifTrue: > [

Re: [Pharo-dev] Release Mode

Philippe wrote >The look of nautilus button isn't "ok to integrate" since there is much more >work needed to get this working properly. That’s two different issues. One is integrated, the other not. 13137 The SBIC buttons change is ok, afaik. 13135 exposes lot’s of issues in the tools. All kinds

Re: [Pharo-dev] [Moose-dev] Re: Re: Fwd: Font problem is still there

On 28 Mar 2014, at 15:01, Tudor Girba wrote: > I added the code in the mail precisely to leave out any ambiguities :). > > The first part of the snippet (as also listed by Vincent) loads the very > latest development version of Athens configuration. So, yes, I think I loaded > the latest code

Re: [Pharo-dev] Release Mode

Am 28.03.2014 um 16:17 schrieb Sven Van Caekenberghe : > > On 28 Mar 2014, at 16:00, Marcus Denker wrote: > >> >> On 28 Mar 2014, at 15:52, Sean P. DeNigris wrote: >> >>> While I was on holiday, it seems my dear friends have gone feature crazy... >>> almost as bad as me in the run up to the

Re: [Pharo-dev] Release Mode

On 28 Mar 2014, at 16:17, Sven Van Caekenberghe wrote: > > On 28 Mar 2014, at 16:00, Marcus Denker wrote: > >> >> On 28 Mar 2014, at 15:52, Sean P. DeNigris wrote: >> >>> While I was on holiday, it seems my dear friends have gone feature crazy... >>> almost as bad as me in the run up to th

Re: [Pharo-dev] [Moose-dev] Re: Re: Re: Fwd: Font problem is still there

Ookkayy.. so, current status: - finally we got an agreement that big red square because of font loading issues and font rendering artifacts is two separate issues. Thanks! - i am not going to address font-loading issue here and now.. (because we spent time on it earlier today with Stef already an

Re: [Pharo-dev] Release Mode

On 28 Mar 2014, at 15:52, Sean P. DeNigris wrote: > While I was on holiday, it seems my dear friends have gone feature crazy... > almost as bad as me in the run up to the 2.0 release, ha ha. > > As cool as they are, are: > - changing the look of Nautilus buttons > - evaluate arbitrary expressio

Re: [Pharo-dev] Capturing stdout

On 28.03.2014, at 15:55, Sean P. DeNigris wrote: > Max Leske wrote >> Forget what I said… Just rambling… > > Ha ha, I was doing the confused-puppy-head-tilt (see > http://da0cb6511396a92928c7-488d28a6573db6ac4a247063b638fcb9.r77.cf2.rackcdn.com/files/o-DOG-COCKED-HEAD-facebook.jpg) :p > > >

Re: [Pharo-dev] [Moose-dev] Re: Re: Fwd: Font problem is still there

yes but if you uncheck and recheck freetype the embedded fonts are lost -> substition -> substitution failed. -> get a strike font and boum. Can you confirm? On 28 Mar 2014, at 15:26, Tudor Girba wrote: > Excellent. > > I confirm the same result in the latest Moose image (which no longer load

Re: [Pharo-dev] [Moose-dev] Re: Fwd: Font problem is still there

I added the code in the mail precisely to leave out any ambiguities :). The first part of the snippet (as also listed by Vincent) loads the very latest development version of Athens configuration. So, yes, I think I loaded the latest code. Doru On Fri, Mar 28, 2014 at 2:57 PM, Igor Stasenko wr

Re: [Pharo-dev] New website about Spec - http://spec.st

Thanks ben This is really to see my ideas coming to live ;D > > I am glad to announce (even if Philippe already let the cat out :P) a website > dedicated to Spec: http://spec.st. > You can find a quick introduction, documentation (mainly what is now in the > Pharo For The Enterprise book), and

[Pharo-dev] New website about Spec - http://spec.st

Hi guys :) I am glad to announce (even if Philippe already let the cat out :P) a website dedicated to Spec: http://spec.st. You can find a quick introduction, documentation (mainly what is now in the Pharo For The Enterprise book), and a news feed where I will explain the API changes, the news w

[Pharo-dev] Regex groups

I find myself often writing code like: matcher := RxMatcher forString: 'SHA-1\: (\w+)'. matcher search: shaLine trimBoth. ^ matcher subexpression: 2. Is there an easier way, or could a convenience method be useful to write e.g.: 'SHA-1\: (\w+)' asRegex subexpression

Re: [Pharo-dev] Capturing stdout

Forget what I said… Just rambling… On 28.03.2014, at 13:48, Max Leske wrote: > start pharo from the console? > > On 28.03.2014, at 12:57, Sean P. DeNigris wrote: > >> I want to write a test for an NB Mac system call example (Issue 13147). I can >> check the exit code easily, the output goes

Re: [Pharo-dev] Capturing stdout

start pharo from the console? On 28.03.2014, at 12:57, Sean P. DeNigris wrote: > I want to write a test for an NB Mac system call example (Issue 13147). I can > check the exit code easily, the output goes to stdout of the image. Can I > capture it somehow? thx :) > > > > - > Cheers, > Sea

Re: [Pharo-dev] [Moose-dev] Problem with fonts

And a last one :). You can find the actual code here: GTImageSetupCommandLineHandler>>installFonts Cheers, Doru On Fri, Mar 28, 2014 at 1:42 PM, Tudor Girba wrote: > And the installation of the font happens like this: > > install > FreeTypeFontProvider current > addFromFileContents: self fo

Re: [Pharo-dev] [Moose-dev] Problem with fonts

And the installation of the font happens like this: install FreeTypeFontProvider current addFromFileContents: self fontContents baseName: self originalFileName Cheers, Doru On Fri, Mar 28, 2014 at 1:41 PM, Tudor Girba wrote: > I am not quite sure this is where the problem comes from given t

Re: [Pharo-dev] [Moose-dev] Problem with fonts

I am not quite sure this is where the problem comes from given that we see half of the letters being well drawn and half not well. Here is how the font is loaded: #('SourceCodeProRegular' 'SourceCodeProBold' 'SourceSansProRegular' 'SourceSansProBold') do: [ :each | each asSymbol asClassIfAbsent: [

Re: [Pharo-dev] DateAndTime>>#= slow?

Hi johan Please let us know because I would be in favor of integrating such speed up if your system fully work. stef On 28 Mar 2014, at 09:17, Johan Brichau wrote: > > On 28 Mar 2014, at 06:24, Esteban Lorenzano wrote: > >> Bugs are errors that prevents the system to run. > > > Some pe

[Pharo-dev] Capturing stdout

I want to write a test for an NB Mac system call example (Issue 13147). I can check the exit code easily, the output goes to stdout of the image. Can I capture it somehow? thx :) - Cheers, Sean -- View this message in context: http://forum.world.st/Capturing-stdout-tp4751320.html Sent from

Re: [Pharo-dev] [Moose-dev] Problem with fonts

On 28 Mar 2014, at 12:38, Stéphane Ducasse wrote: Hi We found with igor the problems that produced red cross in Moose. The problem is that the system is looking Source Sans Pro and does not find it. The logic in findBestFont: does not find it because there is no such font registered in font

Re: [Pharo-dev] [Moose-dev] Problem with fonts

Hi, well.. source sans pro should be loaded (along with source code pro), but: 1) I loaded the wrong font. 2) for some reason, the build fails to use it by default (you need to update “use freetype” in settings, then re-choose). I did not spend too much time on trying to fix that bug (other

Re: [Pharo-dev] Smalltalkhub & API

I just wanted to have my projects repos added to my preferences file. Without an API, it requires scraping the UI and writing code. So, yes, an API would be nice (or some helper to help with the repos registration for a given user/team in Monticello). But the REST thing is good enough at this poi

Re: [Pharo-dev] Smalltalkhub & API

Would it be useful if SmalltalkHub provided an API (I mean, something documented)? Nico p...@highoctane.be writes: > Ah, nice! > > Thx > > > > On Fri, Mar 28, 2014 at 10:44 AM, Nicolas Petton > wrote: > >> Hi! >> >> You can do: >> >> GET http://smalltalkhub.com/hub/projects/{user,team} >> >> C

Re: [Pharo-dev] Smalltalkhub & API

Stephan Eggermont writes: > 0.9.2-baseline might load in 2 by removing the 3.x, > but I haven’t tried. I can’t commit in > NicolasPetton/SmalltalkHub Hi, Do you want write access to the repo? Cheers, Nico

Re: [Pharo-dev] DateAndTime>>#= slow?

2014-03-28 5:24 GMT+00:00 Esteban Lorenzano : > Bugs are errors that prevents the system to run. > If a system runs, even if slow, then is not an error. One could argue that bugs are defects that cause unintended behaviour (including not operating at all). Given that definition, and assuming tha

Re: [Pharo-dev] Smalltalkhub & API

Ah, nice! Thx On Fri, Mar 28, 2014 at 10:44 AM, Nicolas Petton wrote: > Hi! > > You can do: > > GET http://smalltalkhub.com/hub/projects/{user,team} > > Cheers, > Nico > > p...@highoctane.be writes: > > > Is there a way to ask for a set of project names under a given Team/User? > > > > I don't

Re: [Pharo-dev] SmalltalkHub update

No, I don't have Safari but colleagues do. I'll test it this afternoon. Cheers, Nico Stephan Eggermont writes: > Do you test with Safari? I get lots of restarts.10.9.2 > > Stephan -- Nicolas Petton http://nicolas-petton.fr

Re: [Pharo-dev] Smalltalkhub & API

Hi! You can do: GET http://smalltalkhub.com/hub/projects/{user,team} Cheers, Nico p...@highoctane.be writes: > Is there a way to ask for a set of project names under a given Team/User? > > I don't like maintaining lists like this one: > > #( > 'BitmapCharacterSet' > 'CollectionArithmetic' > '

Re: [Pharo-dev] Font problem is still there

De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de Igor Stasenko Envoyé : jeudi 27 mars 2014 16:45 À : Pharo Development List Objet : Re: [Pharo-dev] Font problem is still there Btw, guys i need some details: - what platform you using The problem appears on both Linux Ubun

Re: [Pharo-dev] DateAndTime>>#= slow?

Am 28.03.2014 um 09:17 schrieb Johan Brichau : > > On 28 Mar 2014, at 06:24, Esteban Lorenzano wrote: > >> Bugs are errors that prevents the system to run. > > > Some performance problems make the system impossible to work with > > There are always use cases that make a system painful slo

Re: [Pharo-dev] Fwd: Feedback for Pharo 3

Hello, About #valueWithInterval: and co, I added that in Pharo because they are present in javascript with the same name and I think they were very convenient to easily implement UI animation. According to the number of discussion about these 2 methods, I think they are useful, but we should ret

Re: [Pharo-dev] DateAndTime>>#= slow?

On 28 Mar 2014, at 06:24, Esteban Lorenzano wrote: > Bugs are errors that prevents the system to run. Some performance problems make the system impossible to work with Anyway, going to check in Sven's changes today. cheers Johan

Re: [Pharo-dev] DateAndTime>>#= slow?

Excellent! Thanks for all this good and proactive energy. Stef > Umbrella issue: > > https://pharo.fogbugz.com/f/cases/13139/Speed-Regressions-in-DateAndTime > > I rewrote (and simplified) DateAndTime>>#+ #- #= > I added caching for #epoch > I switched the localTimeZone to an #asFixedTimeZon

Re: [Pharo-dev] [Pharo-users] [ANN] Application Security for your domains

the linke o your blog leads to http://www.smalltalkhub.com/#%21/%7Ehernan/ApplicationSecurity On 28 Mar 2014, at 00:58, Hernán Morales Durand wrote: > Hello guys, > I'm doing a double announcement here. > > First, a new blog about development with Pharo, and Smalltalk: > > http://807381632

[Pharo-dev] Fwd: Feedback for Pharo 3

Begin forwarded message: > From: Richard Sargent > Subject: Feedback for Pharo 3 > Date: 27 Mar 2014 18:46:11 GMT+1 > To: Stéphane Ducasse > > Hi Stéphane, > > Benjamin Pollack @bitquabit just tweeted the features list for 3.0. I have to > say that you folks have some really exciting things