Re: [Pharo-dev] [pharo-project/pharo-core] dbba45: 50646

> On 16 Mar 2016, at 13:28, GitHub wrote: > > 17797 random crash while trying to dispose a NULL handle > https://pharo.fogbugz.com/f/cases/17797 > again, this is an attempt against the "Font crashing VM” bug… please I need

Re: [Pharo-dev] Changes Browser is broken

yes, Epicea will be integrated “first week of Pharo 6”, so we can iterate and fix :) > On 18 Mar 2016, at 08:52, Serge Stinckwich wrote: > > On Fri, Mar 18, 2016 at 7:45 AM, stepharo wrote: >> Yes because we have epicea to replace it but epicea

Re: [Pharo-dev] problems with the default font

t; I checked the issue tracker and I did not find a bug. Is there such a report > or should I create one? well… I closed last one (I submitted a fix), but I think I need to open a new one :) Esteban > > Cheers, > Doru > > >> On Mar 12, 2016, at 2:59 PM, Esteban Lorenz

Re: [Pharo-dev] problems with the default font

bah… “fix it” in the sense that correct fonts will be restored :) > On 12 Mar 2016, at 14:19, Tudor Girba wrote: > > Hi, > > It looks to me as if in the latest Pharo, the default font is rendered with > the DejaVu bitmap font instead of Source Sans Pro. > > Here is

Re: [Pharo-dev] problems with the default font

no, I do not confirm (that the defaults are DejaVu): it is a bug. what actually happens is an effect of the infamous “font bug” that is around. in fact, if you have that effect with a latest image you should not need to reload fonts, just saving image will fix it. > On 12 Mar 2016, at 14:19,

Re: [Pharo-dev] Starting to add class comment and test on BlElements

+1 > On 06 Mar 2016, at 09:09, stepharo wrote: > > +1 > > Stef > > Le 5/3/16 18:59, Aliaksei Syrel a écrit : >> Documentation != checking of contract. >> All assertions can be removed from code easily with simple script when bloc >> will be released (or another solution

Re: [Pharo-dev] Call about Numerical Methods in Pharo :)

> On 06 Mar 2016, at 10:50, Benoit St-Jean via Pharo-dev > wrote: > > Instead of spending a sh*tload of bytes arguing about this nonsense, let's > move on to do some coding... Sorry, but this is the only reasonable thing I can rescue from this whole thread. The

Re: [Pharo-dev] Call about Numerical Methods in Pharo :)

frankly all this zealot mails do not have any sense. first, SciSmalltalk is a project made fundamentally by Serge, and is Serge who has pointed he wants a change of name for something sexier… what is the problem? second, by discussing a nonsense (because is subjective and everybody has a

Re: [Pharo-dev] [FFI] DNU ByteArray>>#rollAsDoubleToArity: arity

Ah yes. I fixed that but is not in the image... Just load bleeding edge of UFFI > On 3 Mar 2016, at 18:30, Aliaksei Syrel wrote: > > (In the latest FFI) > > Assume we have a native call declaration (we want to get values from x and y > later): > >> primGetCurrentPointX:

Re: [Pharo-dev] [pharo-project/pharo-core] 22898d: 50626

> On 03 Mar 2016, at 14:35, GitHub wrote: > > 17392 FreeType numCharMaps nil causes Array>>basicNew: to fail > https://pharo.fogbugz.com/f/cases/17392 > I’m not sure this will actually fix the problem… but I’m getting closer,

Re: [Pharo-dev] A question about the Dark Theme main background color

people would like to change it… that’s why we need to revive the settings for themes! Esteban > > On Thu, Mar 3, 2016 at 1:43 PM, Sven Van Caekenberghe <s...@stfx.eu > <mailto:s...@stfx.eu>> wrote: > OK, thanks, I got it. > > > On 03 Mar 2016, at 13:33, Esteban

Re: [Pharo-dev] A question about the Dark Theme main background color

Hi, > On 03 Mar 2016, at 12:04, Sven Van Caekenberghe wrote: > > I know that colours are a matter of taste, but I have a question about the > Dark Theme main background color. > > Here is a screenshot of my 4.0 image: > > > Versus the same in 5.0 > > > Note how the

Re: [Pharo-dev] error: cannot find OpenSSL or Libgcrypt when creating the VM on OSX

you have a dependency conflict. but most probably you do not need those plugins. Why do you want to build VM by your own? In any case, you can just remove those dependencies for you build… after if you need it you can check what conflicts: buildMacOSX32 "Build with freetype, cairo,

Re: [Pharo-dev] New Cog VMs available

> On 01 Mar 2016, at 13:43, Alexandre Bergel wrote: > > I am a bit lost. Do we have a 64bits support? If yes, then why do we still > have some 32 bits images? we don't > > Alexandre > >> On Mar 1, 2016, at 1:19 PM, Stephan Eggermont wrote: >> >>

Re: [Pharo-dev] [bloc] when saving bloc and relaunching I get

not spur… UFFI (or Athens)… that means ExternalAddresses are not correctly freed before quitting :( Esteban > On 26 Feb 2016, at 21:14, Aliaksei Syrel wrote: > > The same for me... Looks like something spur related. I could not find what > causes an issue :( > > On Feb

Re: [Pharo-dev] "error: 'math.h' file not found" when building the new VM

> On 26 Feb 2016, at 12:52, Alexandre Bergel wrote: > >> read the instructions :) >> >> https://github.com/pharo-project/pharo-vm/blob/spur64/README-Win32.md >> > > I use OS X, why should I read

Re: [Pharo-dev] "error: 'math.h' file not found" when building the new VM

read the instructions :) https://github.com/pharo-project/pharo-vm/blob/spur64/README-Win32.md > On 26 Feb 2016, at 11:24, Alexandre Bergel wrote: > > Hi! > > I am trying to build the VM,

Re: [Pharo-dev] [pharo-project/pharo-core] 93fd3c: 50612

not clear in the message, but this issue also makes SDL2 work (a first iteration, there will be problems probably) > On 25 Feb 2016, at 14:45, GitHub wrote: > > 17236 unload NativeBoost (spur migration) > https://pharo.fogbugz.com/f/cases/17236 >

Re: [Pharo-dev] [bloc] why redefining new is not enough?

ailto:alain.plan...@yahoo.com>> > To: Pharo Development List <pharo-dev@lists.pharo.org > <mailto:pharo-dev@lists.pharo.org>> > Cc: > Date: Thu, 25 Feb 2016 12:37:59 +0100 > Subject: Re: [Pharo-dev] [bloc] why redefining new is not enough? > > > On 25

Re: [Pharo-dev] [bloc] why redefining new is not enough?

t; To: Pharo Development List <pharo-dev@lists.pharo.org> > > > >> On 25 févr. 2016, at 11:49, Esteban Lorenzano <esteba...@gmail.com> wrote: >> >> this is bad… redefining basicNew should not be done, never, never, never. > why ? well… is not forbidde

Re: [Pharo-dev] [bloc] why redefining new is not enough?

this is bad… redefining basicNew should not be done, never, never, never. that’s why we have new and basicNew :) Esteban > On 25 Feb 2016, at 09:52, stepharo wrote: > > BlElement class>>basicNew >"Redefined to set the space of the element" > >^ super basicNew

Re: [Pharo-dev] [Pharo-users] help needed for testing the order in spotter

right now feels a lot better than before. also the explicit (visible) keybingins to filter are a great addition :) Esteban > On 24 Feb 2016, at 19:34, Tudor Girba wrote: > > Hi, > > Thanks. Indeed, I agree with you. In fact, this is what we did, and then I > was told

Re: [Pharo-dev] fully self-contained Linux VM

> On 23 Feb 2016, at 19:05, Eliot Miranda wrote: > > > > On Tue, Feb 23, 2016 at 4:42 AM, Nicolai Hess > wrote: > > > 2016-02-23 13:35 GMT+01:00 Peter Uhnák >: >

Re: [Pharo-dev] [Bloc] Do we want or

> On 23 Feb 2016, at 13:57, Sven Van Caekenberghe <s...@stfx.eu> wrote: > >> >> On 23 Feb 2016, at 13:43, Tudor Girba <tu...@tudorgirba.com> wrote: >> >> Hi, >> >>> On Feb 23, 2016, at 1:24 PM, Esteban Lorenzano <esteba...@gmai

Re: [Pharo-dev] [Bloc] Do we want or

> On 23 Feb 2016, at 13:20, Alain Plantec via Pharo-dev > wrote: > > > From: Alain Plantec > Subject: Re: [Pharo-dev] [Bloc] Do we want or > Date: 23 February 2016 at 13:19:34 GMT+1 > To: Pharo Development List

Re: [Pharo-dev] [pharo-project/pharo-core] a1da99: 50599

> On 23 Feb 2016, at 11:42, Ben Coman wrote: > > but these log messages *should* include all the linked issues. > cheers -ben this is a bug in the integrator build of log message :P Esteban > > On Tue, Feb 23, 2016 at 4:17 PM, stepharo wrote: >> The

Re: [Pharo-dev] double selection in the debugger is confusing

> On 23 Feb 2016, at 08:49, Nicolai Hess wrote: > > > > 2016-02-23 8:46 GMT+01:00 stepharo >: > > > Le 22/2/16 09:50, Nicolai Hess a écrit : >> >> >> 2016-02-21 19:19 GMT+01:00 stepharo >

Re: [Pharo-dev] [pharo-project/pharo-core] d6c5cd: 50593

how it happens, #loadSymbols fail and then fonts became invalid… so at least now I know where to put the halt :) hopefully next week I can finish this… Esteban > > 2016-02-19 15:53 GMT+01:00 Esteban Lorenzano <esteba...@gmail.com > <mailto:esteba...@gmail.com>>: > >>

Re: [Pharo-dev] [pharo-project/pharo-core] d6c5cd: 50593

> On 19 Feb 2016, at 15:40, Esteban Lorenzano <esteba...@gmail.com> wrote: > > >> On 19 Feb 2016, at 15:17, GitHub <nore...@github.com >> <mailto:nore...@github.com>> wrote: >> >> >> 17392 FreeType numCharMaps nil causes Array>

Re: [Pharo-dev] [pharo-project/pharo-core] d6c5cd: 50593

> On 19 Feb 2016, at 15:17, GitHub wrote: > > > 17392 FreeType numCharMaps nil causes Array>>basicNew: to fail > https://pharo.fogbugz.com/f/cases/17392 > I’m not sure my fix will solve the problem completely… but there was a

Re: [Pharo-dev] FFI BoxedFloat64 bug?

explain why by default you reduce the precision of float to 32 bits ? > Is it because the library used expects a single precision float to be passed ? > > > > 2016-02-18 11:57 GMT+01:00 Esteban Lorenzano <esteba...@gmail.com > <mailto:esteba...@gmail.com>>: > bu

Re: [Pharo-dev] build 50588 strange font failure?

> In case its useful, I uploaded a fuel dump of the stack here... > http://wikisend.com/download/365684/fuel.zip > <http://wikisend.com/download/365684/fuel.zip> > expires in 7 days, zip password = pharo > > /home/ben/.local/share/Pharo/VMs/spur/pharo-vm/pharo > CoInterp

Re: [Pharo-dev] FFI BoxedFloat64 bug?

de that involve FFI and floats that was working before Spur. > I got the error mentioned by Alex. > Defining this pointer method gives a weird behavior. > > It would be great to have this fixed. probably because of what I just described… I will commit a fix. > > Alexandre > >>

Re: [Pharo-dev] FFI BoxedFloat64 bug?

a.clem...@gmail.com> wrote: > > I don't understand. All BoxedFloat have 8 bytes, that's why they are called > BoxedFloat64. There are no 4-bytes floats in Pharo. Even in 32 bits. > > 2016-02-12 18:06 GMT+01:00 Esteban Lorenzano <esteba...@gmail.com > <mailto:esteba...@gmail.c

Re: [Pharo-dev] Object>>rollToArity:?

I’m not happy with the method name, but I think is well explained in method comments: ExternalAddress>>rollToArity: arity "This will 'roll' a pointer to a certain arity. What does this means? Let's say I have a method who will be called with a ** arity:

Re: [Pharo-dev] Improving Ghost proxies

> On 15 Feb 2016, at 18:15, Mariano Martinez Peck wrote: > > > > On Mon, Feb 15, 2016 at 1:22 PM, stepharo > wrote: > our policy is > Any package used in the core of Pharo should be saved under Pharo. > > > >

Re: [Pharo-dev] FFI BoxedFloat64 bug?

Oops… I didn’t implemented #pointer for floats… it should be something like this: Float>>#pointer ^ (ByteArray new: FFIExternalType pointerSize) floatAt: 1 put: self; yourself can you test it? (and you can commit it to Pharo/NB-FFI repo… I’m taking a

Re: [Pharo-dev] FFI BoxedFloat64 bug?

> On 12 Feb 2016, at 17:50, Aliaksei Syrel <alex.sy...@gmail.com> wrote: > > On Fri, Feb 12, 2016 at 5:45 PM, Esteban Lorenzano <esteba...@gmail.com > <mailto:esteba...@gmail.com>> wrote: > Float>>#pointer > ^ (ByteArray new: FFIExternalType p

[Pharo-dev] Esteban's log now also in Slack!

Hi, Just to tell you that I improved a bit the WorkLog: I configured slack to receive (by rss) my updates. You can find it under #worklog channel. So, happy stalking :) Esteban

Re: [Pharo-dev] Bloc Documentation

> On 09 Feb 2016, at 09:15, Aliaksei Syrel wrote: > > Bloc does not have examples yet. > What classes/methods do you need to be commented first to understand the > system? > mmm… that’s a bad question because I would answer “all of them”, but I understand you want to do

Re: [Pharo-dev] Some questions

> On 09 Feb 2016, at 13:38, Stéphane Ducasse wrote: > >> >> p.s. To all who see this email: Bloc needs more complains >> >> :) >> >> Some random thoughts: >> BlWorldElement and BlSpaceElement sounds like this is for elements *in* >> space or *in* world, not like

Re: [Pharo-dev] Best way to access icons?

> On 07 Feb 2016, at 22:08, stepharo <steph...@free.fr> wrote: > > > > Le 5/2/16 09:21, Esteban Lorenzano a écrit : >> of course, but since we have not implemented such mechanism, we need to go >> one step at a time… > > yes but this is good to thi

Re: [Pharo-dev] [ANN] We are in "code freeze" for Pharo 5

> On 05 Feb 2016, at 08:34, Nicolai Hess <nicolaih...@gmail.com> wrote: > > > > 2016-02-04 12:21 GMT+01:00 Esteban Lorenzano <esteba...@gmail.com > <mailto:esteba...@gmail.com>>: > Hi, > > We are on “just bugfixes” since some time now… I delayed t

Re: [Pharo-dev] [pharo-project/pharo-core] 3e343d: 50571

ok, now it got in… no idea why now worked and before it didn’t… but is like that… is there now :) > On 08 Feb 2016, at 16:08, GitHub wrote: > > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 3e343d0298d3b2111bb18db4e1366d3cb7d2b2c4

Re: [Pharo-dev] [pharo-project/pharo-core] 3d6dce: 50569

again, that didn’t worked… there is something bad with that configuration > On 08 Feb 2016, at 14:51, GitHub wrote: > > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 3d6dce043ce1c1e48b9027eb2d0f82648117a26c > >

Re: [Pharo-dev] [pharo-project/pharo-core] 3d6dce: 50569

n (except some cyclic dependences, but they should not interfere). And in my machine it loads fine :( Anyway… I will comeback with news when I have them. Esteban > > I tried the script in a fresh Pharo 5.0 image and it worked just fine. > > Cheers, > Doru > > >> On Fe

Re: [Pharo-dev] Best way to access icons?

>> new version of the icon. >> >>ic broadcastNewIcon: #button >> >> This way >> >>t does not have to use a plain bad global variable and does not care >> about the global namespace. >>t should only use local resources held in class

[Pharo-dev] [ANN] We are in "code freeze" for Pharo 5

Hi, We are on “just bugfixes” since some time now… I delayed the announcement because Epicea still needs to enter and we didn’t manage to include it yet. But well… with the exception of Epicea, no new features will be included un Pharo 5… just bugfixes (and we have a lot of bugfixes incoming…

Re: [Pharo-dev] Best way to access icons?

> On 04 Feb 2016, at 17:38, Stephan Eggermont <step...@stack.nl> wrote: > > On 04-02-16 17:00, Esteban Lorenzano wrote: >> Smalltalk ui icons iconNamed: #protocolExtension. >> >> Still ugly, but I’m not happy with the idea of a selector-per-icon… > > W

Re: [Pharo-dev] Best way to access icons?

Smalltalk ui icons iconNamed: #protocolExtension. Still ugly, but I’m not happy with the idea of a selector-per-icon… they will never be enough and well… is like a monolithic vision. Not that what we have is much better, but you can consider it an iteration :) Esteban > On 04 Feb 2016, at

Re: [Pharo-dev] Travis CI integration added to OSSubprocess and FFICHeaderExtractor

m > <mailto:marianop...@gmail.com>> wrote: > >> BTW, Esteban Maringolo asked me if the Travis scripts were "sharable". Well, >> Esteban Lorenzano shared them with me and I improved them a bit for my >> needs, so of course they are shareable! An

Re: [Pharo-dev] Travis CI integration added to OSSubprocess and FFICHeaderExtractor

Hi Holger, As I pointed before, smalltalk-ci it is still not working. Mariano is using an alternative I explained here: http://log.smallworks.eu/web/post/84 In general, smalltalk-ci is an attempt to have a "level playing field” between different smalltalks (for now pharo and squeak, in close

Re: [Pharo-dev] Travis CI integration added to OSSubprocess and FFICHeaderExtractor

Hi, > On 03 Feb 2016, at 15:21, Holger Freyther <hol...@freyther.de> wrote: > > >> On 03 Feb 2016, at 13:36, Esteban Lorenzano <esteba...@gmail.com> wrote: >> > > > Hi, > > > >> And it is still not working correctly (even if my pu

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

but layoutProperties are not immutable so if you receive an instance of NullLayoutProperties (singleton), and you do something like this: myMorph cellInset: 5, you has to check for correct properties anyway… that’s why is implemented as this: cellInset: aNumber "Layout specific. This

Re: [Pharo-dev] Thanks nicolai and the sprinter for fixing the selectorTable

> On 01 Feb 2016, at 08:24, Nicolai Hess wrote: > > > > 2016-01-31 21:52 GMT+01:00 Cyril Ferlicot Delbecque >: > > > On 31/01/2016 15:23, stepharo wrote: > > Hi guys > > > > Thanks for this fix. > > I will

Re: [Pharo-dev] Warning in Pharo 5

probably this is the default… which it should not! Esteban > On 31 Jan 2016, at 16:51, Mariano Martinez Peck wrote: > > Did you set GTGenericStackDebugger alwaysOpenFullDebugger: true ?? > > On Sun, Jan 31, 2016 at 12:12 PM, Cyril Ferlicot D.

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

no, I don’t :) I commented there. > On 30 Jan 2016, at 21:22, Aliaksei Syrel wrote: > > Hello > > Do you agree? > https://pharo.fogbugz.com/f/cases/17502/Morph-layoutProperties-must-not-be-nil-by-default > >

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

> On 31 Jan 2016, at 13:16, Aliaksei Syrel <alex.sy...@gmail.com> wrote: > > layoutProperties := NullLayoutProperties uniqueInstance > to share only one object you would be creating “extension morphs"l anyway > > On Sun, Jan 31, 2016 at 1:06 PM, Esteban L

Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by default

lt;pharo-dev@lists.pharo.org> > Subject: Re: [Pharo-dev] 17502. Morph layoutProperties must not be nil by > default > > layoutProperties := NullLayoutProperties uniqueInstance > to share only one object > > On Sun, Jan 31, 2016 at 1:06 PM, Esteban Lorenzano <esteba...

Re: [Pharo-dev] [pharo-project/pharo-core] 6456a3: 50555

this is, again, not true… integrator is seriously broken… looking at it now. > On 29 Jan 2016, at 12:28, GitHub wrote: > > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 6456a3f5d3400e8efce6941a99ea425f7c3da45a > >

Re: [Pharo-dev] Travis CI integration added to OSSubprocess and FFICHeaderExtractor

Cobrale! Cobrale! ;) > On 29 Jan 2016, at 18:28, Mariano Martinez Peck <marianop...@gmail.com> wrote: > > BTW, Esteban Maringolo asked me if the Travis scripts were "sharable". Well, > Esteban Lorenzano shared them with me and I improved them a bit f

Re: [Pharo-dev] [pharo-project/pharo-core] a7c782: 50553

this didn’t work :( > On 28 Jan 2016, at 18:16, GitHub wrote: > > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: a7c782bf85e2fd1905cf9834fc8782040096060f > >

Re: [Pharo-dev] [pharo-project/pharo-core] 770605: 50554

this one also didn’t work :( > On 28 Jan 2016, at 18:58, GitHub wrote: > > Branch: refs/heads/5.0 > Home: https://github.com/pharo-project/pharo-core > Commit: 7706057c37f925a319931cc3c5f3ef0f3fcbab62 > >

Re: [Pharo-dev] [pharo-project/pharo-core] a7c782: 50553

no idea, but integrations are not happening (not just GTools) I will check tomorrow :) > On 28 Jan 2016, at 19:37, Tudor Girba <tu...@tudorgirba.com> wrote: > > What is the problem? > > Doru > > >> On Jan 28, 2016, at 6:25 PM, Esteban Lorenzano <esteba...@

Re: [Pharo-dev] pay attention there is a problem with rubric in latest image...

if it is that, is a known bug… just save and reopen (I will find the bug eventually, but is complicated). Esteban > On 27 Jan 2016, at 17:27, Skip Lentz wrote: > > Hi, > > Did it involve Array class>>basicNew: and FreeType? I got it while typing in > a Rubric editor. >

Re: [Pharo-dev] monkey error

no idea… I think is a sthub problem, I need to take a look at it but as always, I’m running with other stuff… but I will try to add a retry when downloading (that’s the stupid timeout). ah, then there are a couple of random glamour and other tests that fails. Just a couple. I vote to fix them

Re: [Pharo-dev] spotter: top search for senders and references

> On 19 Jan 2016, at 16:15, Esteban Lorenzano <esteba...@gmail.com> wrote: > > >> On 19 Jan 2016, at 15:23, Esteban A. Maringolo <emaring...@gmail.com >> <mailto:emaring...@gmail.com>> wrote: >> >> It turns the search field into a &

Re: [Pharo-dev] spotter: top search for senders and references

> On 19 Jan 2016, at 18:08, Esteban A. Maringolo wrote: > > 2016-01-19 13:34 GMT-03:00 stepharo : >> >> cool >> now could we have an help menu that describes the key elements. >> People cannot discover that by themselves. A menu item is cheap. > > The

Re: [Pharo-dev] spotter: top search for senders and references

It has to be the oposite: #implementors should show what people understand until now (a list of implementors) #methods should show the actual methods (as now does #implementors) why complicate things if we can do it in a way that satisfaces everybody? Esteban > On 19 Jan 2016, at 18:07,

Re: [Pharo-dev] [Vm-dev] Unable to read Utf8 ?

> On 17 Jan 2016, at 13:43, Thierry Goubier <thierry.goub...@gmail.com> wrote: > > Le 17/01/2016 13:22, Esteban Lorenzano a écrit : >> this is working in latest VM build. >> >> https://pharo.fogbugz.com/f/cases/17389/ >> >> so.. you can go ba

Re: [Pharo-dev] Seeing class method template when there is no protocol

well, I disagree :) > On 17 Jan 2016, at 17:47, Sven Van Caekenberghe wrote: > > >> On 17 Jan 2016, at 17:13, stepharo > > wrote: >> >> >> >> Le 17/1/16 16:09, Sven Van Caekenberghe a écrit : On 17 Jan 2016, at 15:52, Gabriel

Re: [Pharo-dev] [Moose-dev] roassal2 seems to work well now

> On 17 Jan 2016, at 18:02, Tudor Girba wrote: > > Hi, > > With the latest development, Roassal2 seems to work well. > > For example, the rendering of the logical view of Glamour browsers was > broken, and now it works well. This is great news. > > > > Is this just

Re: [Pharo-dev] Why there is no setting to disable QA?

> On 17 Jan 2016, at 18:12, Eliot Miranda wrote: > > >> On Jan 17, 2016, at 9:06 AM, Yuriy Tymchuk wrote: >> >> That’s the point. Someone finds this disruptive, someone instructing. But >> it’s always a true information. So here we are not

Re: [Pharo-dev] [Moose-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

problem is that *all other tools* have accept/cancel in context menu. if you change one, you need to change all… otherwise you are breaking muscular/visual memory for no gain. So… I propose to put them in same place all other tools have it: in the contextual menu. cheers, Esteban ps: in

Re: [Pharo-dev] Growl setting name

> On 16 Jan 2016, at 09:18, Dimitris Chloupis wrote: > > Personally I dont see the point of a rename, we got like 30% of people coming > from macos that will be familiar with the name Growl, 0% that will be > familiar with any other name. So you take a name that is very

Re: [Pharo-dev] [Vm-dev] Unable to read Utf8 ?

> On 16 Jan 2016, at 11:59, Thierry Goubier <thierry.goub...@gmail.com> wrote: > > Le 16/01/2016 11:39, Esteban Lorenzano a écrit : >> >>> On 16 Jan 2016, at 10:45, Eliot Miranda <eliot.mira...@gmail.com> >>> wrote: >>> >>>

Re: [Pharo-dev] Git repository and branch for spur enable pharo-vm

Hi, > On 15 Jan 2016, at 18:29, Holger Freyther wrote: > > Hi, > > what is the official pharo-vm git repository? It looks like > github.com/pharo-project/pharo-vm is not being updated right now. It looks > like esteban's fork is currently being used and the spur64 branch.

Re: [Pharo-dev] [IMPORTANT] Starting migration to Spur VM

ergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Jan 15, 2016, at 12:16 PM, Nicolai Hess <nicolaih...@gmail.com >> <mailto:nicolaih...@gmail.com>> wrote: >> >> >> >> 2015-12-14 11:24 GMT+

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

this, but I’m introducing it because is better name :P) I *think* #2 can be skipped, but #1 and #3 are a must. opinions? Esteban > On 13 Jan 2016, at 11:28, Esteban Lorenzano <esteba...@gmail.com> wrote: > >> >> On 13 Jan 2016, at 03:46, Ben Coman <b...@openinworld.com>

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

core). > Then one could change the how a class is viewed in a simple manner (see > attached example). > > > Best regards, > Henrik > > From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of > Esteban Lorenzano > Sent: Wednesday, January 13, 2

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

> On 13 Jan 2016, at 12:56, Max Leske <maxle...@gmail.com> wrote: > > >> On 13 Jan 2016, at 11:32, Esteban Lorenzano <esteba...@gmail.com >> <mailto:esteba...@gmail.com>> wrote: >> >> So, recapitulation: >> >> I want to introd

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

en whatever prefix name and the object name? (for example underscore). > Then one could change the how a class is viewed in a simple manner (see > attached example). > > > Best regards, > Henrik > > From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org &g

Re: [Pharo-dev] Pharo50 spur works on CentOS?

-Message d'origine- >> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de >> Esteban Lorenzano >> Envoyé : lundi 11 janvier 2016 19:21 >> À : Pharo Development List >> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS? >>

Re: [Pharo-dev] Pharo50 spur works on CentOS?

it should raise an error? No it can't :) And is hard to show an error, is not always possible (depends on command line handler developer) Of course it can be enhanced... But it requires time, as always :) Esteban > > Vincent > >> -Message d'origine- >> De : Ph

Re: [Pharo-dev] Pharo50 spur works on CentOS?

, > so at that point, the option is consumed already. No, it doesn't :) > >> Vincent >> >>> -Message d'origine- >>> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de >>> Esteban Lorenzano >>> Envoyé : lu

Re: [Pharo-dev] Pharo50 spur works on CentOS?

gine- >> De : Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] De la part de >> Sven Van Caekenberghe >> Envoyé : mardi 12 janvier 2016 10:57 >> À : Pharo Development List >> Objet : Re: [Pharo-dev] Pharo50 spur works on CentOS? >> >> >>>

[Pharo-dev] I will rename FFI-NB to UnifiedFFI

Hi, People has pointed (and they are right) that the name of the new FFI front-end is misleading. So yesterday I was talking with Stef and we think UnifiedFFI (or UFFI, for short) is a better name… and to keep packages prox. to regular FFI I was thinking on rename FFI-NB packages to

Re: [Pharo-dev] [Pharo-users] [ann] gtdebugger in pharo 5.0

no, I’m quite sure they are bugs :) I also believe the other tools do not have accept/cancel visible (they are in contextual menus), so maybe they should be there. Esteban > On 12 Jan 2016, at 23:24, Nicolai Hess wrote: > > > > 2016-01-08 11:24 GMT+01:00 Tudor Girba

[Pharo-dev] Pharo-spur VM builds are back to green

Hi, I restored the pharo spur vm builds. Which means latest vm (from zeroconf of directly downloaded from files.pharo.org ) is aligned with latest sources. I know there were a couple of bugs waiting to be tested… so please, go ahead! Esteban

Re: [Pharo-dev] Pharo50 spur works on CentOS?

> On 11 Jan 2016, at 19:06, Sven Van Caekenberghe wrote: > > Is it not ./pharo Pharo.image eval --no-quit 'ZnServer startDefaultOn: 8080' > > ? > > I.e. the --no-quit AFTER the eval. yes, is like that :) > >

Re: [Pharo-dev] gtdebugger in pharo 5.0

that’s just an example, default debugger does not have it :) I will commit my changes as soon as I can sit and clean it… the actions need to be changed to make explicit if you want text/icon/both so we can keep all behaviours (and keep compatible). Esteban > On 09 Jan 2016, at 14:08,

Re: [Pharo-dev] Help with FFI crash in latest Spur (only in Linux)

> On 09 Jan 2016, at 05:15, Ben Coman wrote: > > On Sat, Jan 9, 2016 at 7:12 AM, Mariano Martinez Peck > > wrote: >> >> On Jan 8, 2016 4:13 PM, "Ben Coman" wrote: >>> >>> On Sat, Jan 9, 2016 at

Re: [Pharo-dev] About LayoutFrame>>fractions:offsets:

that’s important. I never understood LayoutFrame… I always finish doing random stuff until I have something that “more or less” works :) > On 09 Jan 2016, at 09:56, stepharo wrote: > > Here is the new class comments I'm trying to write. > I hope that it will help people to

Re: [Pharo-dev] Why pharo is going over squeaksource when saving code?

no, is true :( the configurations for FFI and Alien are pointing to a place there, and since Monticello is… well… not so good… it scans all available repositories to get a version number. Obviously, not good.. And I think we changed that last year, but obviously is back. in the mean time, I

Re: [Pharo-dev] gtdebugger in pharo 5.0

you have to confess that with text and icons looks a lot better than the old one :P > On 09 Jan 2016, at 11:01, Esteban Lorenzano <esteba...@gmail.com> wrote: > > again re-send because of exceed limits with the image (that’s new?) > > with a small tweak

Re: [Pharo-dev] GTDebugger (case 17341 Integrate GTools version 3.3)

> On 08 Jan 2016, at 16:43, Andrei Chis wrote: > > Hi Nicolai, > > Thanks for the feedback. > Some issues I'll manage to fix until we integrate. > For those that I do not manage please open bug reports. > > On Thu, Jan 7, 2016 at 9:13 PM, Nicolai Hess

Re: [Pharo-dev] GTDebugger (case 17341 Integrate GTools version 3.3)

> On 08 Jan 2016, at 17:04, Esteban A. Maringolo <emaring...@gmail.com> wrote: > > 2016-01-08 12:48 GMT-03:00 Esteban Lorenzano <esteba...@gmail.com > <mailto:esteba...@gmail.com>>: > > > > On 08 Jan 2016, at 16:43, Andrei Chis <chisvasileand...@gmai

Re: [Pharo-dev] ConfigurationOfXXX package is not visible in nautilus...

is in Configurations group :) that’s by design, I think > On 07 Jan 2016, at 11:14, Blondeau Vincent > wrote: > > Hi, > > Happy new year ! > > It seems that any configuration loaded by Jenkins is not visible in Nautilus > (at package level) but are

Re: [Pharo-dev] [ANN] I created a web page so you can stalk me :)

> On 07 Jan 2016, at 18:18, Esteban Lorenzano <esteba...@gmail.com> wrote: > > Hi, > > Stef told me I need to make a bit more visibility my work, and while being in > Togo I sketched an application I tested last few days and seems to be working > fina. >

[Pharo-dev] [ANN] I created a web page so you can stalk me :)

Hi, Stef told me I need to make a bit more visibility my work, and while being in Togo I sketched an application I tested last few days and seems to be working fina. Of course, easiest way would be to use twitter as a work log, but I was not satisfied with the idea. Why? well… some reasons

<    6   7   8   9   10   11   12   13   14   15   >