Hi Stef. I was reading your link.
I found it very interesting . I think i will working in that direction having
in mind your advise.
Tia
Ing. Pablo Digonzelli
Software Solutions
IP-Solutiones SRL
Dividato SA
25 de Mayo 521
San Miguel de Tucumán
Email: pdigonze...@softsargentina.com
pdi
> On 5 Mar 2017, at 19:53, Martin McClure wrote:
>
> On 03/05/2017 03:01 AM, Sven Van Caekenberghe wrote:
>> I also think that allowing concatenation on Symbols does not violate their
>> immutability contract.
>>
>> As a thought experiment, what could be the problem with adding
>>
>> Symbol >
On 03/05/2017 03:01 AM, Sven Van Caekenberghe wrote:
I also think that allowing concatenation on Symbols does not violate their
immutability contract.
As a thought experiment, what could be the problem with adding
Symbol >> , arg
^ (self , arg) asSymbol
?
Aside from the infinite rec
On 5 March 2017 at 11:03, Esteban Lorenzano wrote:
>
> On 5 Mar 2017, at 05:00, Alexander Samoylovich
> wrote:
>
> Hi Ronie, Esteban.
>
> Ronie's suggestion in the form Esteban presented it helped.
> After implementing the fix I failed to crash my application any more.
>
> Will anybody be so kin
Understood.
My use/understanding of hash and =, true in DrGeo, was more like unique
identifier regarding its ontological characteristics (what distinguish
it from other). So an exact same Point in DrGeo will have different hash
value depending on its position on the plane, or it being free on a
lin
Dear all,
we have 10 mentors + 4 admin at the moment. We are looking for me !
Please join the #gsoc-planning Slack channel.
Thank you.
On Wed, Mar 1, 2017 at 1:45 PM, Serge Stinckwich
wrote:
> Heartiest Congratulations !
>
> Pharo Consortium has been selected as a mentor organisation for Google
Hilaire
Sounds like this has nothing to do with voyage. If you modify part of on
object's unique identifier, it's another object. The best you can do is to use
a synthetic id that has no business meaning and use that for object identity.
Joachim
> Am 05.03.2017 um 12:02 schrieb Hilaire :
>
>
Situation looks a bit clearer.
The duplicated object entries issue arises with two concomitant situations:
- the object reimplements hash and = methods
- one of the attributes participating in the comparing protocol is modified.
In that scenario, Voyage guess it is dealing with a new element, eve
I also think that allowing concatenation on Symbols does not violate their
immutability contract.
As a thought experiment, what could be the problem with adding
Symbol >> , arg
^ (self , arg) asSymbol
?
(I have found the original issue raised annoying as well)
> On 5 Mar 2017, at 11:3
I don't need (or want) to mutate the receiver. Actually I thought that String
is also immutable.
$, could just return a new symbol instance instead. Concating symbols is quite
practical for metaprogramming, as most things are named with symbols and
compare by identity...
Peter
On Sun, Mar 05,
On Sun, 05 Mar 2017 00:42:44 +0100, Paul DeBruicker
wrote:
This may be overkill for your use but would love to have an MIT licensed
set
of classes that allow for/enable something like this:
https://medium.com/assist/theres-a-dozen-ways-to-order-a-coffee-why-do-dumb-bots-only-allow-one-272
Looks awesome.
Now, how hard would it be to reuse a WATask from Seaside from normal,
non web code?
A lot of WAxxx concepts could be brought back into nornal "Spec/Morphic"
apps, like WASession, WATask, filters etc.
Indeed and we can accept them and cocoon them :)
Looks awesome.
Now, how hard would it be to reuse a WATask from Seaside from normal, non
web code?
A lot of WAxxx concepts could be brought back into nornal "Spec/Morphic"
apps, like WASession, WATask, filters etc.
Phil
On Sun, Mar 5, 2017 at 12:42 AM, Paul DeBruicker wrote:
> This may be ove
Voyage cannot guess user intentions.
But yes we could add a helper to do the transformation easier (like a special
description for dates), but you will always need to configure that by hand.
Esteban
> On 5 Mar 2017, at 10:22, Hilaire wrote:
>
> Hi Esteban,
>
> This is a recurring problem. Ma
Hi Esteban,
This is a recurring problem. May be Voyage should come with the
necessary adaptor to have the Date right. It is likely *every* Voyage
user faces the problem, and it does not fell good about the framework to
have issue on such elementary feature.
Hilaire
Le 05/03/2017 à 10:06, Esteban
Hi Sabine, Norbert,
It is nice to have feedbacks from other Voyagers ;)
Thanks about the notice regarding reset on the repository.
It may have implication I should be careful about, but not in my
scenario because:
- I start with empty collections in the repository, for the model part,
- I import
yes, this is a good solution.
the base of the problem is that mongo does not actually has a Date type, just
DateAndTime (even if is called Date).
So if you want a Date, you need to do some conversion.
Esteban
> On 4 Mar 2017, at 11:25, Hilaire wrote:
>
> Concerning this problem, one option
> On 5 Mar 2017, at 05:00, Alexander Samoylovich wrote:
>
> Hi Ronie, Esteban.
>
> Ronie's suggestion in the form Esteban presented it helped.
> After implementing the fix I failed to crash my application any more.
>
> Will anybody be so kind to explain me what actually happens and why the fi
Esteban, not Stephen. Me.
Send me a private mail with the username/email you used to register.
cheers,
Esteban
> On 5 Mar 2017, at 02:36, Juan Manuel Vallejos
> wrote:
>
>
> Thank you. What is Stephen's mail?
>
> Juan Manuel Vallejos
>
> 2017-03-04 4:17 GMT-03:00 Stephane Ducasse
Hi Stephan,
I am maintaining such a digest, with links to the discussion on the
list. I will post it once I am done with Voyage.
Hilaire
Le 04/03/2017 à 21:34, stepharong a écrit :
> I would love to have a digest of the problems you encountered and the
> solution.
> Because like that we could wr
20 matches
Mail list logo