Re: [Pharo-dev] cannot use shortcut in text pane of MC

fix in since 50597 > On 22 Feb 2016, at 08:41, Marcus Denker wrote: > > https://pharo.fogbugz.com/f/cases/17570/Shortcuts-to-browse-code-are-not-available-any-more-in-some-tools > > There are *lots* of fixes in the queue to be integrated… progress is slow > sometimes

Re: [Pharo-dev] in 50596 protocol icons are lost

fix in 50604 > On 22 Feb 2016, at 08:42, Marcus Denker wrote: > > https://pharo.fogbugz.com/f/cases/17524/Invisible-protocol-icons > > no fix yet > >> On 21 Feb 2016, at 19:00, stepharo wrote: >> >> Hi guys >> >> I noticed that when I look at the

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50604 Home: https://github.com/pharo-project/pharo-core

[Pharo-dev] [pharo-project/pharo-core] d0ecf7: 50604

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d0ecf7f23af140c408e8371809b9b13ad0989488 https://github.com/pharo-project/pharo-core/commit/d0ecf7f23af140c408e8371809b9b13ad0989488 Author: Jenkins Build Server Date:

Re: [Pharo-dev] 50603 highlighting broken

I addd this as an issue: https://pharo.fogbugz.com/f/cases/17684/highlighting-broken-in-message-list-senders-off-implementors-of > On 23 Feb 2016, at 15:15, Nicolai Hess wrote: > > > > 2016-02-23 14:48 GMT+01:00 Marcus Denker

Re: [Pharo-dev] Differences Compiler vs. OpalCompiler (or parser)

On Tue, Feb 23, 2016 at 2:26 PM, Nicolai Hess wrote: > > > 2016-02-23 18:58 GMT+01:00 Eliot Miranda : > >> Hi Nicolai, >> >> On Tue, Feb 23, 2016 at 7:37 AM, Nicolai Hess >> wrote: >> >>> >>> >>> 2015-11-20 22:57 GMT+01:00

Re: [Pharo-dev] Hackathon IoT. I used Pharo.

Very cool. I am downloading the OPC test software. Yeah MODBUS is in the picture (as are a ton of other data source). Thx for the info! Depending on serendipitous conditions, I'll be able to land a prototyping contract and Pharo would be a good thing to use, even if it has to do some OSProcess

Re: [Pharo-dev] Hackathon IoT. I used Pharo.

On Tue, Feb 23, 2016 at 7:32 PM, philippe.b...@highoctane.be wrote: > FWIW I'll be looking at an industrial bigdata project starting next week. > This is solid stuff and I'll be a recommender for some things. And btw, there is always the old warhorse "Modbus" that

Re: [Pharo-dev] Problem loading new class comments

2016-02-20 9:54 GMT+01:00 Marcus Denker : > > On 19 Feb 2016, at 22:19, Sven Van Caekenberghe wrote: > > > On 19 Feb 2016, at 22:06, Nicolai Hess wrote: > > > > 2016-02-19 15:37 GMT+01:00 Sven Van Caekenberghe : > I am

Re: [Pharo-dev] Differences Compiler vs. OpalCompiler (or parser)

2016-02-23 18:58 GMT+01:00 Eliot Miranda : > Hi Nicolai, > > On Tue, Feb 23, 2016 at 7:37 AM, Nicolai Hess > wrote: > >> >> >> 2015-11-20 22:57 GMT+01:00 Eliot Miranda : >> >>> Hi Nicolai, >>> >>> On Fri, Nov 20, 2015 at

[Pharo-dev] nautilus does not refresh method changed

Hi may be this is already fixed but in Latest update: #50596 I found myself forced to reopen a class to see its correct method. Stef

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

On February 23, 2016 1:35:48 PM GMT+01:00, "Peter Uhnák" wrote: >Hi, > >is it possible to have fully self-contained Linux VM? > >Right now if you want to use Pharo on Linux you have to install some >libraries directly in the system, which isn't particularly >user-friendly. On

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] fully self-contained Linux VM

On Tue, Feb 23, 2016 at 4:42 AM, Nicolai Hess wrote: > > > 2016-02-23 13:35 GMT+01:00 Peter Uhnák : > >> Hi, >> >> is it possible to have fully self-contained Linux VM? >> >> Right now if you want to use Pharo on Linux you have to install some >>

Re: [Pharo-dev] Differences Compiler vs. OpalCompiler (or parser)

Hi Nicolai, On Tue, Feb 23, 2016 at 7:37 AM, Nicolai Hess wrote: > > > 2015-11-20 22:57 GMT+01:00 Eliot Miranda : > >> Hi Nicolai, >> >> On Fri, Nov 20, 2015 at 1:37 PM, Nicolai Hess >> wrote: >> >>> GTDummyExamples class

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

On Tue, Feb 23, 2016 at 12:47 AM, stepharo wrote: > Hi > > I saw that something or > I do not know why but I have the impression that is > better. > Because we may have code not present and still want to load the code. > Given the current semantics of pragmas only is

[Pharo-dev] curiousity, ensure unwind block priority inheritance

Just thought I'd share something enlightening I learnt today, a curious surprise... When a process is terminated, the #ensure: unwind block effectively inherits the priority of the terminator process. Thus the following... log := OrderedCollection new. s := Semaphore new. p := [

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

On Tue, Feb 23, 2016 at 8:17 PM, stepharo wrote: > I do not think that Pharo will become a static language :) > For the moment we can let it as a documentation. > Now I would prefer to have tests because such annotations may be obsolete. Maybe not if those pragmas become

Re: [Pharo-dev] Differences Compiler vs. OpalCompiler (or parser)

2015-11-20 22:57 GMT+01:00 Eliot Miranda : > Hi Nicolai, > > On Fri, Nov 20, 2015 at 1:37 PM, Nicolai Hess > wrote: > >> GTDummyExamples class >> d: anInteger >> >> >> > anInteger'> >> >> MessageNotUnderstood> >> >> ^ 1

Re: [Pharo-dev] 50603 highlighting broken

2016-02-23 14:48 GMT+01:00 Marcus Denker : > > > On 23 Feb 2016, at 14:41, Nicolai Hess wrote: > > > > in pharo 50603, if you open a sendersOf MessageBrowser, the first > selected > > methods code is not or wrongly highlightey (all red). > > You

Re: [Pharo-dev] fork during debugging to auto spawn new debugger

Hi Ben 2016-02-23 14:08 GMT+01:00 Ben Coman : > Maybe if somehow a Process new it was > being debugged and the new process inherited that state. > I plan to introduce inheriting state for spawn processes. Idea is to add InheritedProcessSpecificVariable. Particularly I want

Re: [Pharo-dev] 50603 highlighting broken

Caused by: Build 50601 16020 Syntax Highlighting Rubric: First shows non-highlighted text, then color. Looks slow https://pharo.fogbugz.com/f/cases/16020 From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of Nicolai Hess Sent: Tuesday, February 23, 2016 2:41

Re: [Pharo-dev] 50603 highlighting broken

> On 23 Feb 2016, at 14:41, Nicolai Hess wrote: > > in pharo 50603, if you open a sendersOf MessageBrowser, the first selected > methods code is not or wrongly highlightey (all red). > You have to change the selected item to get the right result! Yes, this is a side

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

On Tue, Feb 23, 2016 at 2:00 PM, Stephan Eggermont wrote: > On 23-02-16 13:35, Peter Uhnák wrote: > >> Could something like that be done also for the remaining lib32 libraries >> required to run the VM? >> > > Sure. And then you need to release updates whenever one of the

[Pharo-dev] 50603 highlighting broken

in pharo 50603, if you open a sendersOf MessageBrowser, the first selected methods code is not or wrongly highlightey (all red). You have to change the selected item to get the right result!

[Pharo-dev] [pharo-project/pharo-core] a8609c: 50603

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: a8609c784255b249c46006004e78a224022e4e8d https://github.com/pharo-project/pharo-core/commit/a8609c784255b249c46006004e78a224022e4e8d Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50603 Home: https://github.com/pharo-project/pharo-core

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

> On 23 Feb 2016, at 13:57, Sven Van Caekenberghe wrote: > >> >> On 23 Feb 2016, at 13:43, Tudor Girba wrote: >> >> Hi, >> >>> On Feb 23, 2016, at 1:24 PM, Esteban Lorenzano wrote: >>> >>> On 23 Feb 2016, at 13:20, Alain

[Pharo-dev] fork during debugging to auto spawn new debugger

Just a quick random thought before it gets away... It would be *nice* if when debugging and I step over a fork, the new process automatically halts at the start and spawns a new debugger. If its it was spawned at a higher priority, I could immediately move to the new debugger and step through

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

On 23-02-16 13:35, Peter Uhnák wrote: Could something like that be done also for the remaining lib32 libraries required to run the VM? Sure. And then you need to release updates whenever one of the underlying lib32 libraries changes. OpenSSL comes to mind. Stephan

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/50602 Home: https://github.com/pharo-project/pharo-core

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

> On 23 Feb 2016, at 13:43, Tudor Girba wrote: > > Hi, > >> On Feb 23, 2016, at 1:24 PM, Esteban Lorenzano wrote: >> >> >>> On 23 Feb 2016, at 13:20, Alain Plantec via Pharo-dev >>> wrote: >>> >>> >>> From: Alain

[Pharo-dev] [pharo-project/pharo-core] d37c12: 50602

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d37c124b9367ad904de724a5db0f27ca34be93fa https://github.com/pharo-project/pharo-core/commit/d37c124b9367ad904de724a5db0f27ca34be93fa Author: Jenkins Build Server Date:

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

Hi, > On Feb 23, 2016, at 1:24 PM, Esteban Lorenzano wrote: > > >> 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 >

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

2016-02-23 13:35 GMT+01:00 Peter Uhnák : > Hi, > > is it possible to have fully self-contained Linux VM? > > Right now if you want to use Pharo on Linux you have to install some > libraries directly in the system, which isn't particularly user-friendly. > > I know that for

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

> On Feb 23, 2016, at 1:17 PM, stepharo wrote: > > I do not think that Pharo will become a static language :) Certainly not a static language! :)) > For the moment we can let it as a documentation. > Now I would prefer to have tests because such annotations may be obsolete.

[Pharo-dev] fully self-contained Linux VM

Hi, is it possible to have fully self-contained Linux VM? Right now if you want to use Pharo on Linux you have to install some libraries directly in the system, which isn't particularly user-friendly. I know that for example libcairo (needed by Roassal) has hard-coded library paths, but maybe

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] [Bloc] Do we want or

I do not think that Pharo will become a static language :) For the moment we can let it as a documentation. Now I would prefer to have tests because such annotations may be obsolete. Anyway the code quality of aleksei is really good. Le 23/2/16 10:33, Tudor Girba a écrit : Hi, At the moment,

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

Ok so I will use # Stef Le 23/2/16 11:09, Nicolai Hess a écrit : Old compiler does not allowed only And I think opal should behave the same (not fixed yet) 2016-02-23 11:01 GMT+01:00 Peter Uhnák >: >Because we may have code not present

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

Pablo Tesone Phd was on type inferencing but he accepted another PhD topics with Noury and us. Le 23/2/16 10:43, Alexandre Bergel a écrit : Just emerging from holidays. Is there an effort to have type annotations? How these annotations are then used? Alexandre On Feb 23, 2016, at 5:47

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 >

[Pharo-dev] TxText architecture question

In the TxText model, a text consists of a double-linked list of spans, containing the text content and its attributes. I wonder how to efficiently map a hierarchical text model (like that of Pillar) to that. Stephan

Re: [Pharo-dev] Hackathon IoT. I used Pharo.

FWIW I'll be looking at an industrial bigdata project starting next week. This is solid stuff and I'll be a recommender for some things. Maybe should we focus on the data feeding side of things. How fast can we be? Phil On Feb 23, 2016 11:07 AM, "Ben Coman" wrote: >

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

On Tue, Feb 23, 2016 at 5:33 PM, Tudor Girba wrote: > Hi, > > At the moment, it is used for documentation purposes in Bloc. It is part of > the effort of Alex to document Bloc thoroughly. I think it is an interesting > idea, in that we would have a significant case study

Re: [Pharo-dev] Why the GTSpotter help does not explain all the categories

> On 23 Feb 2016, at 11:47, Ben Coman wrote: > > On Tue, Feb 23, 2016 at 5:30 PM, Tudor Girba wrote: >> Hi Stef, >> >> Yes, the title is what you are searching for :). I keep on trying to explain >> that, but somehow this does not come through. We

Re: [Pharo-dev] Why the GTSpotter help does not explain all the categories

On Tue, Feb 23, 2016 at 5:30 PM, Tudor Girba wrote: > Hi Stef, > > Yes, the title is what you are searching for :). I keep on trying to explain > that, but somehow this does not come through. We changed the rendering of the > category label to include # in front to make it

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

but these log messages *should* include all the linked issues. cheers -ben On Tue, Feb 23, 2016 at 4:17 PM, stepharo wrote: > The session manager is managed as a configuration? > Impressed! > > Stef > > Le 22/2/16 18:26, GitHub a écrit : > >> >>Log Message: >>

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

On Tue, Feb 23, 2016 at 11:21 AM, Henrik Johansen < henrik.s.johan...@veloxit.no> wrote: > Sounds like a recipe for creating documentation that gets out of > sync quickly/has bugs of its own, if you ask me... > For instance, in the example, it seems weird multiplicity: (1 '*') when > the method

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

Sounds like a recipe for creating documentation that gets out of sync quickly/has bugs of its own, if you ask me... For instance, in the example, it seems weird multiplicity: (1 '*') when the method returns an empty collection if contact is nil (multiplicity 0) Cheers, Henry > On 23 Feb 2016,

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

> On 23 Feb 2016, at 10:43, Alexandre Bergel wrote: > > Just emerging from holidays. Is there an effort to have type annotations? How > these annotations are then used? Apparently just for documentation Still this is a dangerous 'precedent' as it might give the wrong

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

Old compiler does not allowed only And I think opal should behave the same (not fixed yet) 2016-02-23 11:01 GMT+01:00 Peter Uhnák : > > Because we may have code not present and still want to load the code. > > I think it's just visual, because it's still referenced as

Re: [Pharo-dev] Hackathon IoT. I used Pharo.

There is real business opportunity for "Industrial" Internet of Things. Morphic (and next Block) makes Pharo would make a fantastic platform for the HMI (Human Machine Intereface) of a factory or machine. And its good reoccurring work, as engineers are *paid* to consult on troubleshooting,

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

> Because we may have code not present and still want to load the code. I think it's just visual, because it's still referenced as string in the pragma itself. For example Person>>contact ^ contact ifNil: [ contact := OrderedCollection new ] But, (Person>>#contact) pragmas first arguments

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

Just emerging from holidays. Is there an effort to have type annotations? How these annotations are then used? Alexandre > On Feb 23, 2016, at 5:47 AM, stepharo wrote: > > Hi > > I saw that something or > I do not know why but I have the impression that is better. >

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

Hi, At the moment, it is used for documentation purposes in Bloc. It is part of the effort of Alex to document Bloc thoroughly. I think it is an interesting idea, in that we would have a significant case study for that can be used later as optional types information to improve static tool

Re: [Pharo-dev] [Bloc] MDLColor and new gradient

Hi 2016-02-23 9:13 GMT+01:00 stepharo : > May be we should have some Palette > > And we could have (brainstorming) > > (ColorBuilder from: MDLPalette) > -> aColorBuilder > aColorBuilder red > -> > What the difference between red colors from different

Re: [Pharo-dev] Why the GTSpotter help does not explain all the categories

Hi Stef, Yes, the title is what you are searching for :). I keep on trying to explain that, but somehow this does not come through. We changed the rendering of the category label to include # in front to make it more apparent. So, if you have a category named #SomeCategoryTitle, you can search

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

--- Begin Message --- I don’t like it too. Alain > Le 23 févr. 2016 à 09:50, Nicolai Hess a écrit : > > > > 2016-02-23 9:47 GMT+01:00 stepharo >: > Hi > > I saw that something or > I do not know why but I have the

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

2016-02-23 9:47 GMT+01:00 stepharo : > Hi > > I saw that something or > I do not know why but I have the impression that is > better. > Because we may have code not present and still want to load the code. > I would like to know for what this is used. I don't like it. > >

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

Hi I saw that something or I do not know why but I have the impression that is better. Because we may have code not present and still want to load the code. Stef

[Pharo-dev] [Bloc] dispatcher vs shortcutHandler

Hi what is the diff between kmDispatcher and shotcutHandler? Stef

[Pharo-dev] [Bloc] Why space is weakly referenced?

Just to understand space "Return space to which I belong. Direct reference boosts performance. Each element has weak reference to the current space which is set at creation moment. @see BlElement>>#basicSpace:" self assert: spaceReference isNotNil. ^ spaceReference

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

Hi blockers and alek in particular, the code is cool and I like that each method is commented. I'm starting to write a real class comment that we will be able to use in a documentation. But I cannot run the example so this is difficult to write tests. So Alek how do you know that you make

[Pharo-dev] [Bloc] MDLColor and new gradient

Hi Guillaume Larcheveque in Telescope added support for MDLColor http://www.materialui.co/colors and nice gradient building. I asked him if we could extract this functionality and move it into Pharo because it will be usefull for Pharo, Bloc, and Roassal. A first step could be to have

Re: [Pharo-dev] MetaclassTest>>testMetaclassAndTraitClassRespectsPolymorphismRules

it is in an extension protocol, like fuel and others > On 23 Feb 2016, at 08:39, stepharo wrote: > > May be I got wrong what you say. > > But we should not link metaclass or > > TApplyingOnClassSide on Ston. > > > Le 20/2/16 12:34, Henrik Nergaard a écrit : >> Ah, test

[Pharo-dev] [pharo-project/pharo-core] 10d1e2: 50601

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 10d1e26878c91a8e25242c83e2bf25df490b56cf https://github.com/pharo-project/pharo-core/commit/10d1e26878c91a8e25242c83e2bf25df490b56cf Author: Jenkins Build Server Date: