Am 23.08.17 um 11:08 schrieb Herby Vojčík:
jtuchel wrote:
Herby,
as Esteban already said, UPSERT doesn't make any sense in an ORM. It
I don't know... I just create new object (with same "primary key") and
register it (yes, I know I get an error - maybe I should be able to
set the policy to
Meanwhile, you can check at [1], a Grafoscopio notebook where I documented Brea
and the problem is trying to solve.
[1] http://mutabit.com/repos.fossil/gig/dir?ci=tip
Cheers,
Offray
El 23 de agosto de 2017 20:15:38 GMT-05:00, Offray
escribió:
>Hi Hannes,
>
>I will improve docs and test, but
Hi Hannes,
I will improve docs and test, but for the moment I'll be away of my computer at
least until Friday. Image persistance is not implemented.
Cheers,
Offray
El 23 de agosto de 2017 13:44:46 GMT-05:00, "H. Hirzel"
escribió:
>On 8/23/17, Offray wrote:
>> Hi,
>>
>> On the Teapot + Musta
a die handle is a group of dice as in 2D20.
I'm not sure that I want to explain what is double dispatch up front.
I want to go from the requirements to the solution
How to add
die (6) + die(5)
die (6) + 2D20
2D20 + die(6)
2D20 + 2D10
Without doing a self class == Die
Stef
On Wed, Aug 23, 2017
On Wed, Aug 23, 2017 at 9:20 PM, Herby Vojčík wrote:
> Maybe in general sumWithFoo: => addSelfToFoo: to make clues clearer.
I see now it should be more
addSelfWithFoo: or sumSelfWith: because we do not modify the argument.
Stef
Tx I will read your point carefully.
On Wed, Aug 23, 2017 at 9:20 PM, Herby Vojčík wrote:
> Maybe in general sumWithFoo: => addSelfToFoo: to make clues clearer.
>
> Herby
>
>
+Handling all the cases: summing a die/die handle with a die/die
handle
.>file://figures/DieDoubleDispatchFull.pdf|width=70|label=figDieDoubleDispatchFull+
See Figure *@figDieDoubleDispatchFull* for internal ref is missing.
Two Column is missing. I do not know it works in Latex.
I will try to c
On Wed, Aug 23, 2017 at 09:11:47PM +0200, H. Hirzel wrote:
> Thanks, it is useful.
> Date is 24 June 2014.
> Not sure if it is the latest version for what I have now in Pharo 6.
>
> --Hannes
True, but it only covers the basic text mark-up and I don't think that
has changed recently. Anyway, I ha
Maybe in general sumWithFoo: => addSelfToFoo: to make clues clearer.
Herby
Stephane Ducasse wrote:
feedback is welcome
Good reading
2.4
"is to explicit type check"
- "is to explicitly type check", or
- "is to do explicit type check"
s/we will haveother/we will have other/
s/distabilizing/destabilizing/
"In fact we just to tell the receiver ,,,"
Thanks, it is useful.
Date is 24 June 2014.
Not sure if it is the latest version for what I have now in Pharo 6.
--Hannes
On 8/23/17, Alistair Grant wrote:
> How about:
>
> http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet
>
> Cheers,
> Alistair
>
>
> On 23 August 2017 at 20:22, H.
How about:
http://pillarhub.pharocloud.com/hub/pillarhub/pillarcheatsheet
Cheers,
Alistair
On 23 August 2017 at 20:22, H. Hirzel wrote:
> Found the (incomplete) list on the last slide of
>
> http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf
>
> so far.
>
> HH
>
>
>
> On 8
On 8/23/17, Offray wrote:
> Hi,
>
> On the Teapot + Mustache integration, Hannes, you may want to see my early
> prototype:
>
> http://smalltalkhub.com/#!/~Offray/Brea
>
> At some point, it will contain distributed wiki, backed by Fossil, now that
> we're thinking in empower community driven wiki
Found the (incomplete) list on the last slide of
http://esug.org/data/ESUG2015/4%20thursday/1600-1630%20Pilar/Pillar.pdf
so far.
HH
On 8/22/17, Stephane Ducasse wrote:
> Cyril
> I imagine that you refer to link ref with *@...*
> Yes we should probably produce a stylesheet.
>
> Now I'm busy f
Hi Stef,
Thank you for your explanations!
About deprecation, I found it fast because I think FFI as a key component of
a language. I imagine similar problems could happen when going from Morphic
to its successor (Bloc?). Even with a stable API, I expect some code to
explicitely depends on Morphic
Hi Marcus,
I would be happy to contribute to your experiment. Let me know.
Bruno
--
View this message in context:
http://forum.world.st/Parser-failure-on-FFI-pragmas-declaration-in-Pharo-5-tp4961737p4963662.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Hi,
On the Teapot + Mustache integration, Hannes, you may want to see my early
prototype:
http://smalltalkhub.com/#!/~Offray/Brea
At some point, it will contain distributed wiki, backed by Fossil, now that
we're thinking in empower community driven wiki like documentation.
Offray
El 21 de a
I read it once without knowing what double dispatch is, after reading it ,
I did not know what double dispatch is. It took several reads to understand
what double dispatch is.
My suggestion is starting with explaining as a summary what double dispatch
is , instead of leaving it for the conclusion,
Pharo desperately needs an image management tool. But in the end it will be
up to the code hero that will decided the bite the bullet and do it. There
are like a ton of things that can improve and a ton of potential ideas and
projects, this is just one.
It wont be easy though because code inside P
jtuchel wrote:
Herby,
as Esteban already said, UPSERT doesn't make any sense in an ORM. It
I don't know... I just create new object (with same "primary key") and
register it (yes, I know I get an error - maybe I should be able to set
the policy to "overwrite" and it would makes sense; or not
We would like to have dll like deployment too. But I'm too dull to
know how to do implement it.
Stef
On Tue, Aug 22, 2017 at 2:17 PM, Esteban A. Maringolo
wrote:
> VAST provided such image deployment tool, where you could save the
> deployment instructions, as whether to include/exclude certain
21 matches
Mail list logo
