On Thu, Apr 17, 2014 at 1:46 AM, François Stephany
tulipe.mouta...@gmail.com wrote:
Phil, can you describe your use case ?!
Network of objects persistence.
On Wed, Apr 16, 2014 at 11:20 PM, p...@highoctane.be
p...@highoctane.bewrote:
I worked with Sebastian on using Mapless for my
cool :)
but still not accurate enough :(
so, keep the names going!
Esteban
On 16 Apr 2014, at 18:54, Stephan Eggermont step...@stack.nl wrote:
These are the names in the 30inbox
(((MCHttpRepository allInstances second allFileNames collect: [ :each |
|minpos dotpos|
minpos
But how does a key/value store magically store a network of objects ?
How is each object serialised ?
On 17 Apr 2014, at 08:57, p...@highoctane.be wrote:
On Thu, Apr 17, 2014 at 1:46 AM, François Stephany
tulipe.mouta...@gmail.com wrote:
Phil, can you describe your use case ?!
Network
Not magically.
I have my own guide/visitor thing to do the save.
But as I do have a complicated domain, the fact that I do not have to
maintain all attributes in the image but directly through mapless helps me
save a ton of time.
Phil
On Thu, Apr 17, 2014 at 10:03 AM, Sven Van Caekenberghe
Am 17.04.2014 um 10:08 schrieb p...@highoctane.be:
Not magically.
I have my own guide/visitor thing to do the save.
But as I do have a complicated domain, the fact that I do not have to
maintain all attributes in the image but directly through mapless helps me
save a ton of time.
Can
While looking at the code in voyage I got to WeakValueDictionary as voyage uses
it as object cache. If I looked correctly the WeakValueDictionary is based on
equality and not identity. Is that correct? Feels wrong!
Norbert
Super awesome! Thank you.
On 17 Apr 2014, at 11:27, Torsten Bergmann asta...@gmx.de wrote:
Hi,
FontAwesome is (as you may know) an iconic font designed for the user with
Twitter Bootstrap.
I now created a FontAwesome for Seaside project - which is a small Seaside
wrapper for the
Esteban wrote:
I’m collecting the names of those who contributed code for Pharo 3.
If that includes making configurations work in Pharo 3, you definitely miss
Diego Lont.
Stephan
Hi!
Just wondering, would it not make sense to rename BlockClosure into Closure?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I would rather rename is to Block, as everyone is calling it a “block”.
Uko
On 17 Apr 2014, at 16:01, Alexandre Bergel alexandre.ber...@me.com wrote:
Hi!
Just wondering, would it not make sense to rename BlockClosure into Closure?
Cheers,
Alexandre
--
On Apr 17, 2014, at 10:08 AM, Yuriy Tymchuk yuriy.tymc...@me.com wrote:
I would rather rename is to Block, as everyone is calling it a “block”.
That might be actually a good idea
sebastian
o/
PS: thinking in that line there is also ‘Context’ as, conceptually, what these
blocks of code want
Well… the whole community of programming language call a closure a closure.
Calling a block what is actually a closure may not be a well-marketed move in
my opinion.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
I usually say “block” but I have nothing against a name change. I think
“closure” would be an intention revealing name, I like it. And I’m willing to
say “closure” from now on :)
On 17.04.2014, at 15:35, Alexandre Bergel alexandre.ber...@me.com wrote:
Well… the whole community of programming
abergel wrote
Well… the whole community of programming language call a closure a
closure. Calling a block what is actually a closure may not be a
well-marketed move in my opinion.
Given that Smalltalkers consider it a block and outsiders would understand
the closure part, maybe it is
On Apr 17, 2014, at 10:35 AM, Alexandre Bergel alexandre.ber...@me.com wrote:
the whole community of programming language call a closure a closure. Calling
a block what is actually a closure
javascript is teaching every day to thousands what a real Closure is every day,
so yeah that would
On 17 April 2014 10:26, Norbert Hartl norb...@hartl.name wrote:
While looking at the code in voyage I got to WeakValueDictionary as voyage
uses it as object cache. If I looked correctly the WeakValueDictionary is
based on equality and not identity. Is that correct? Feels wrong!
well,
Am 17.04.2014 um 15:57 schrieb Sebastian Sastre sebast...@flowingconcept.com:
On Apr 17, 2014, at 10:35 AM, Alexandre Bergel alexandre.ber...@me.com
wrote:
the whole community of programming language call a closure a closure.
Calling a block what is actually a closure
javascript is
The submission deadline has been extended to April 25, 2014.
=
Second Call for Papers
Universidad de Palermo, Buenos Aires, Argentina
part of 43 JAIIO - 43 Argentine Conference of Informatics -
http://www.43jaiio.org.ar/
1st - 5th September, 2014
+1 for BlockClosure :-)
On 17 avr. 2014, at 15:44, Sean P. DeNigris wrote:
abergel wrote
Well… the whole community of programming language call a closure a
closure. Calling a block what is actually a closure may not be a
well-marketed move in my opinion.
Given that Smalltalkers consider it
Am 17.04.2014 um 16:06 schrieb Igor Stasenko siguc...@gmail.com:
On 17 April 2014 10:26, Norbert Hartl norb...@hartl.name wrote:
While looking at the code in voyage I got to WeakValueDictionary as voyage
uses it as object cache. If I looked correctly the WeakValueDictionary is
based on
It’s like saying that we have to run Pharo on JVM because everyone is doing
that. In 80s block was invented. Why should we rename it because of some other
languages?
Uko
On 17 Apr 2014, at 16:35, Alexandre Bergel alexandre.ber...@me.com wrote:
Well… the whole community of programming
Hi,
I just wanted to mention that Apple also added 'Closures' as 'Blocks' to
Objective-C (respectively C):
https://developer.apple.com/library/ios/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/WorkingwithBlocks/WorkingwithBlocks.html
Best,
Manfred
On Thu, Apr 17, 2014 at 4:45 PM,
2014-04-17 6:57 GMT-07:00 Sebastian Sastre sebast...@flowingconcept.com:
On Apr 17, 2014, at 10:35 AM, Alexandre Bergel alexandre.ber...@me.com
wrote:
the whole community of programming language call a closure a closure.
Calling a block what is actually a closure
javascript is teaching
+1
sebastian
o/
On 17/04/2014, at 12:21, Alexandre Bergel alexandre.ber...@me.com wrote:
Because what we call a block is actually a closure. Smalltalk-80 invented
blocks, which were not closures at that time. Over the time we found out that
Blocks are not really useful, but instead the
On 17 avr. 2014, at 17:33, Camille Teruel camille.ter...@gmail.com wrote:
One thing that confuses me with these terminologies is that it's hard to know
when someone speak about the syntactic construct (that you find in source
code) or about the result of evaluating this construct (that
Hi,
On 17 Apr 2014, at 17:02, Alexandre Bergel alexandre.ber...@me.com wrote:
I have modified the following methods
HandMorphgenerateKeyboardEvent: evtBuf
ScrollPanescrollByKeyboard: event
The effect is now milder.
Esteban, would it make sense to remove the event
On 17 Apr 2014, at 18:13, Esteban Lorenzano esteba...@gmail.com wrote:
Hi,
On 17 Apr 2014, at 17:02, Alexandre Bergel alexandre.ber...@me.com wrote:
I have modified the following methods
HandMorphgenerateKeyboardEvent: evtBuf
ScrollPanescrollByKeyboard: event
The effect
Hi Alexandre,
On Thu, Apr 17, 2014 at 8:21 AM, Alexandre Bergel
alexandre.ber...@me.comwrote:
Because what we call a block is actually a closure. Smalltalk-80 invented
blocks, which were not closures at that time. Over the time we found out
that Blocks are not really useful, but instead the
On Apr 17, 2014, at 1:54 PM, Eliot Miranda eliot.mira...@gmail.com wrote:
I don't think this is right. Yesterday Clément and I had lunch with Dan
Ingalls and we talked about the origin of blocks. At first blocks were not
even real objects; instead they were just a syntactic construct for
hi all,
In a fresh image #30826, I tried:
Smalltalk image condenseChanges - ZnInvalidUTF8 error
https://pharo.fogbugz.com/default.asp?12729;
describes that but it is closed.
I tried the new version:
PharoChangesCondenser condense. - parse error
Do we open a new bug?
Is there another way
On 16/4/14 16:12, Esteban Lorenzano wrote:
everything counts, there is no such thing as a “small fix” :)
+ 1
Esteban
On 16 Apr 2014, at 16:02, Sergi Reyner sergi.rey...@gmail.com
mailto:sergi.rey...@gmail.com wrote:
I did contribute some code for Spec´s ImageModel, if that counts :D
thanks igor I was thinking about that too but I thought that it could
not be that simple :)
On 17/4/14 02:20, Igor Stasenko wrote:
On 15 April 2014 23:15, pharo4s...@free.fr mailto:pharo4s...@free.fr
pharo4s...@free.fr mailto:pharo4s...@free.fr wrote:
There a plenty of isKindOf:
yes it does
On 17/4/14 10:49, Stephan Eggermont wrote:
Esteban wrote:
I’m collecting the names of those who contributed code for Pharo 3.
If that includes making configurations work in Pharo 3, you definitely miss
Diego Lont.
Stephan
On 17 Apr 2014, at 21:13, Luc Fabresse luc.fabre...@gmail.com wrote:
I tried the new version:
PharoChangesCondenser condense. - parse error
I tried recently and it just worked.
Do we open a new bug?
Yes
Is there another way that I missed?
Do you agree that we should remove
abergel wrote
Well… the whole community of programming language call a closure a
closure. Calling a block what is actually a closure may not be a
well-marketed move in my opinion.
Given that Smalltalkers consider it a block and outsiders would understand
the closure part, maybe it is
I have modified the following methods
HandMorphgenerateKeyboardEvent: evtBuf
ScrollPanescrollByKeyboard: event
The effect is now milder.
Esteban, would it make sense to remove the event generation bu the VM? This
works only for the old-style mouse with an actual wheel. Mighty
I added a lot of people. :)
2014-04-17 13:00 GMT-07:00 pharo4s...@free.fr pharo4s...@free.fr:
On 17/4/14 18:54, Eliot Miranda wrote:
If it ain't broke don't fix it. The name BlockClosure isn't incorrect.
These are blocks implemented as closures. The name MethodContext /is/
broken. These /aren't/ just
I have been able to refactor my class names with:
RBClassRegexRefactoring new
renameClasses;
replace: '^XXX(.*)$' with: 'YY$1' ignoreCase: false;
execute
But since then, Nautilus looks like quite lost with a number of weird
behaviors.
Is there a way to reset Nautilus after such
Thanks Eliot for the historical anecdote
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Apr 17, 2014, at 1:54 PM, Eliot Miranda eliot.mira...@gmail.com wrote:
Hi Alexandre,
On
pharo4s...@free.fr wrote
Why not just a StringMorph with correct background?
That doesn't look possible with the current implementation. It just draws
the string with no background:
StringMorph#drawOn: aCanvas
...
super drawOn: aCanvas. - This line doesn't exist
aCanvas
Ben Coman wrote
However the fix I described is low impact.nbsp; Is that reasonable to do
as
a temporary measure for 3.0 release, and a case opened to clean up in
4.0?
That sounds reasonable to me. It seems simple and isolated enough not to
cause any surprises...
-
Cheers,
Sean
--
View
the historical anecdote could be nice as part of the class documentation.
On Thu, Apr 17, 2014 at 8:59 PM, Alexandre Bergel
alexandre.ber...@me.comwrote:
Thanks Eliot for the historical anecdote
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
43 matches
Mail list logo
