This is not good. Somehow this disables NEC.
And resets many other NEC settings, for example
if you just enables code complation again, you still don't have
the smart characters (- inserting matchin or ) or } ...)
Are you interested in some feedback for brick, or is it in a too early
stage?
2015-08-10 12:36 GMT+02:00 Aliaksei Syrel alex.sy...@gmail.com:
Hi Nicolai,
Thanks for looking into this :) Hierarchy will be optimised. Basically
EnclosedView will gone - ProtoView will be a composition, this will
Excellent initiative.
In Moose we get
propertyNamed: propertyName
propertyNamed: name ifAbsentPut: value
propertyNamed: propertyName ifNil: aBlock
propertyNamed: name put: value
So which one do we take?
Stef
Le 15/8/15 10:24, Marcus Denker a écrit :
Hi,
I am now adding a
This is exciting. Thanks a lot for this effort!
Doru
On Sat, Aug 15, 2015 at 10:50 AM, stepharo steph...@free.fr wrote:
Hi guys
just to let you know that we run a dependencies breaking sprint yesterday
and it was great.
We will redo one or two.
Our goal is to minimise the dependencies of
Hi,
I also vote for the xyzAt:put: pattern, even though propertyAt: sounds less
English than propertyNamed:.
Cheers,
Doru
On Sat, Aug 15, 2015 at 11:03 AM, Marcus Denker marcus.den...@inria.fr
wrote:
On 15 Aug 2015, at 10:46, stepharo steph...@free.fr wrote:
Excellent initiative.
+1. This aligns with Dictionary protocol which these collection of
key-value properties essentially are.
cheers -ben
On Sat, Aug 15, 2015 at 5:08 PM, Tudor Girba tu...@tudorgirba.com wrote:
Hi,
I also vote for the xyzAt:put: pattern, even though propertyAt: sounds less
English than
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 434e84ebb6c409b4bf97712d838602747ec51ce0
https://github.com/pharo-project/pharo-core/commit/434e84ebb6c409b4bf97712d838602747ec51ce0
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Hi,
I am now adding a property API to Global/Class Variables and Instance Variables
(aka Slots).
When looking at the other property APIs, we have 4 different conventions:
1) CompiledMethod and Behavior:
propertyValueAt:
2) RB AST Nodes:
propertyAt:
3) Ring:
On 15 Aug 2015, at 10:46, stepharo steph...@free.fr wrote:
Excellent initiative.
In Moose we get
propertyNamed: propertyName
propertyNamed: name ifAbsentPut: value
propertyNamed: propertyName ifNil: aBlock
propertyNamed: name put: value
Ah, no, this is version (5). I
Branch: refs/tags/50232
Home: https://github.com/pharo-project/pharo-core
Ok, what I will do first is to add the API to Variables + Packages using the
propertyAt: format.
On 15 Aug 2015, at 11:40, Ben Coman b...@openinworld.com wrote:
+1. This aligns with Dictionary protocol which these collection of
key-value properties essentially are.
cheers -ben
On Sat,
Hi guys
just to let you know that we run a dependencies breaking sprint
yesterday and it was great.
We will redo one or two.
Our goal is to minimise the dependencies of adding Monticello to the
pharo bootstrap.
What I can tell you is that having a bootstrap is bringing an
***AMAZING*** level
Branch: refs/tags/50233
Home: https://github.com/pharo-project/pharo-core
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: 3192f5a49da5913bb016f82732c4275ec82b8a02
https://github.com/pharo-project/pharo-core/commit/3192f5a49da5913bb016f82732c4275ec82b8a02
Author: Jenkins Build Server bo...@pharo-project.org
Date:
Doru's suggestion of PP + islands is good and makes building complex parsers
easy, but his toy example gives wrong results:
script
function end() {
document.writeln('/script');
}
function start() {
document.writeln('script');
}
/script
or:
script
alert('hello');
// script
Branch: refs/tags/50231
Home: https://github.com/pharo-project/pharo-core
On 15 Aug 2015, at 18:38, Marcus Denker marcus.den...@inria.fr wrote:
On 15 Aug 2015, at 16:48, Marcus Denker marcus.den...@inria.fr
mailto:marcus.den...@inria.fr wrote:
On 15 Aug 2015, at 12:56, Marcus Denker marcus.den...@inria.fr
mailto:marcus.den...@inria.fr wrote:
Ok, what
Can you give a little example of usecase to illustrate how this will be
useful please? :)
--
Cyril
Le samedi 15 août 2015, Marcus Denker marcus.den...@inria.fr a écrit :
On 15 Aug 2015, at 18:38, Marcus Denker marcus.den...@inria.fr
javascript:_e(%7B%7D,'cvml','marcus.den...@inria.fr');
Now I moved all (known?) shortcut definitions from
TextEditor/SmalltalkEditor action-/cmdmap to Keymappings
keymappragma definitions
slice in inbox for issue 15619
Postscript: KMRepository reset.
need some testers.
please report back, what editor (TextEditor/SmalltalkEditor) and your
platform
On 15 Aug 2015, at 19:44, Cyril Ferlicot cyril.ferli...@gmail.com wrote:
Can you give a little example of usecase to illustrate how this will be
useful please? :)
The reason why I do that now is that I want to be able to put Meta Links on
these variables.
This means, to “hook” into all
Hi,
is it possible to load FastTable in Pharo 4?
Uko
Hoi Tudor--
I also vote for the xyzAt:put: pattern, even though propertyAt: sounds
less English than propertyNamed:.
(Obligatory native-English-speaker comment...)
I think it maintains continuity with English just as much as at:
does, which is very much.
-C
--
Craig Latta
I forgot to mention that people can help since we added a tahe
pharo-bootstrap.
Stef
Le 15/8/15 10:53, Tudor Girba a écrit :
This is exciting. Thanks a lot for this effort!
Doru
On Sat, Aug 15, 2015 at 10:50 AM, stepharo steph...@free.fr
mailto:steph...@free.fr wrote:
Hi guys
On 15 Aug 2015, at 12:56, Marcus Denker marcus.den...@inria.fr wrote:
Ok, what I will do first is to add the API to Variables + Packages using the
propertyAt: format.
Done for Globals and ClassVariables:
https://pharo.fogbugz.com/f/cases/16223/Property-API-for-Globals
Le 15/08/2015 16:47, p...@highoctane.be a écrit :
what's a tahe?
I think he wanted to say tag. On Fogbugz you have a category Pharo
Bootstrap.
Le 15 août 2015 15:49, stepharo steph...@free.fr
mailto:steph...@free.fr a écrit :
I forgot to mention that people can help since we added a
+1 for the propertyAt: / propertyAt:put: /
propertyAt:ifPresent:ifAbsent: etc...
This is a easiest way, in my opinion, for a relation key/value.
We should not touch Morph, but what about bloc ? Bloc seems to use the
same names as Morph.
Then we should fix Bloc.
Marcus
Yes! Thanks!
This is valuable
Alexandre
Le 15 août 2015 à 05:53, Tudor Girba tu...@tudorgirba.com a écrit :
This is exciting. Thanks a lot for this effort!
Doru
On Sat, Aug 15, 2015 at 10:50 AM, stepharo steph...@free.fr wrote:
Hi guys
just to let you know that we run a
Le 15/08/2015 10:24, Marcus Denker a écrit :
Hi,
I am now adding a property API to Global/Class Variables and Instance
Variables (aka Slots).
When looking at the other property APIs, we have 4 different conventions:
1) CompiledMethod and Behavior:
propertyValueAt:
2) RB AST
A how to help with Pharo Bootstrap article could help us help you ;)
On Sat, Aug 15, 2015 at 4:49 PM stepharo steph...@free.fr wrote:
I forgot to mention that people can help since we added a tahe
pharo-bootstrap.
Stef
Le 15/8/15 10:53, Tudor Girba a écrit :
This is exciting. Thanks a
what's a tahe?
Le 15 août 2015 15:49, stepharo steph...@free.fr a écrit :
I forgot to mention that people can help since we added a tahe
pharo-bootstrap.
Stef
Le 15/8/15 10:53, Tudor Girba a écrit :
This is exciting. Thanks a lot for this effort!
Doru
On Sat, Aug 15, 2015 at 10:50 AM,
On Sat, Aug 15, 2015 at 4:50 PM, stepharo steph...@free.fr wrote:
Hi guys
just to let you know that we run a dependencies breaking sprint yesterday
and it was great. We will redo one or two.
Our goal is to minimise the dependencies of adding Monticello to the pharo
bootstrap. What I can tell
Boostrapping is removing a ton of black magic indeed.
There will be not one Pharo but the Pharo one needs for a given purpose.
That's awesome.
Phil
Le 15 août 2015 10:50, stepharo steph...@free.fr a écrit :
Hi guys
just to let you know that we run a dependencies breaking sprint yesterday
Le 15/08/2015 10:50, stepharo a écrit :
Hi guys
just to let you know that we run a dependencies breaking sprint
yesterday and it was great.
We will redo one or two.
Our goal is to minimise the dependencies of adding Monticello to the
pharo bootstrap.
What I can tell you is that having a
yeap this is extremely important in making pharo far more flexible. It
would be great if one day making custom images is just a few clicks away.
Image fitting to the exact needs of its users instead of trying to cram
everything into a single image.
On Sat, Aug 15, 2015 at 11:50 AM stepharo
Branch: refs/tags/50234
Home: https://github.com/pharo-project/pharo-core
On 15 Aug 2015, at 16:48, Marcus Denker marcus.den...@inria.fr wrote:
On 15 Aug 2015, at 12:56, Marcus Denker marcus.den...@inria.fr
mailto:marcus.den...@inria.fr wrote:
Ok, what I will do first is to add the API to Variables + Packages using the
propertyAt: format.
Done for
Branch: refs/heads/5.0
Home: https://github.com/pharo-project/pharo-core
Commit: da7ab474476dbeb01d1443c2213ed89746750f0b
https://github.com/pharo-project/pharo-core/commit/da7ab474476dbeb01d1443c2213ed89746750f0b
Author: Jenkins Build Server bo...@pharo-project.org
Date:
yes
just take the configuration from estebanlm/FastTable and load it :)
Esteban
On 15 Aug 2015, at 21:05, Yuriy Tymchuk yuriy.tymc...@me.com wrote:
Hi,
is it possible to load FastTable in Pharo 4?
Uko
This is easy we are looking at dependencies using the dependency
analyzer (available in the catalog)
and looking at how to reduce dependencies. Often it is creating a
separate package, providing an extension hook...
Guille and Christophe started to add fogbugz entries for a first set of
Since we did not port yet spec to use Rubric all the text pane of tools
made with spec should use the textEditor.
Le 15/8/15 19:58, Nicolai Hess a écrit :
Now I moved all (known?) shortcut definitions from
TextEditor/SmalltalkEditor action-/cmdmap to Keymappings
keymappragma definitions
slice
ah ok thats much more clear thanks Stef will take a look at fogbugz :)
On Sat, Aug 15, 2015 at 11:19 PM stepharo steph...@free.fr wrote:
This is easy we are looking at dependencies using the dependency analyzer
(available in the catalog)
and looking at how to reduce dependencies. Often it is
Am 15.08.2015 10:19 nachm. schrieb stepharo steph...@free.fr:
Since we did not port yet spec to use Rubric all the text pane of tools
made with spec should use the textEditor.
Yes,but they only use SmalltalkEditor and not TextEditor.
(Regardless whether you use beForCode or beForText)
Le
42 matches
Mail list logo
