Hello,
I am all listening, learning and happy Norbert helps to fix this issue.
Best wishes of success.
Hilaire
Le 05/01/2017 à 12:43, Sabine Manaa a écrit :
> Norbert, its crazy - THAT WAS IT
> Thank you very much!
>
> I can't wait with the beer till esug, send me your a
about usability and discoverable
features (include not only method comment but clearly written tooltips).
Pharo 5 was released with really poorly documented UI code, although the
tools set is all there (settings browser).
Hilaire
Le 05/01/2017 à 20:24, Siemen Baader a écrit :
> that helps, and
Once you are an expert the mind map is in your mind, but it does not
mean the mind map is useless for newbie. So every thing helping the
newbie to build their own mind map is important to catch them and more
importantly to make them stay with Pharo
Le 06/01/2017 à 21:39, Dimitris Chloupis a écrit
Le 08/01/2017 à 10:44, Stephane Ducasse a écrit :
> We think about it since long time ago. This is why we rewrote and
> produce Nautilus (but the design was not good) - remember in nautilus we
> could edit mutliple methods but it was not good and why that because we
> needed also panes and .
Hello,
When I download a fresh DrGeo16.10 (Pharo3 based), run it, open all
window, I can see it eat almost 25% of cpu, when lucky it get down to 8%
What can I do?
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
I know this path of understanding code while it is running (inspector or
debugger), but it is still a tedious path, and I feel Pharo is a bit
under featured on that specific department, therefore my question on Moose.
Hilaire
Le 09/01/2017 à 15:09, Tudor Girba a écrit :
> That is why my adv
Le 09/01/2017 à 16:09, Tudor Girba a écrit :
> Hi,
>
> In my opinion, Pharo provides the strongest infrastructure for understanding
> a system from all technologies I have seen. So, if you say that Pharo is a
> bit "under featured in, then I think we are not referring to the same thing
> :).
W
tem.
hilaire@pchome $ ./pharo --version
3.9-7 #1 Sat Jun 14 17:26:13 CEST 2014 gcc 4.6.3 [Production ITHB VM]
NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.20 uuid:
cf2a-897d-48fd-8251-6789dd21d958 Jun 14 2014
NBCogit NativeBoost-CogPlugin-EstebanLorenzano.20 uuid:
cf2a-897d-48fd-8
I should add I am stick with Pharo3 for DrGeo, however the new inspector
in Pharo 4 and 5 reduces a lot the cascade of inspector windows, thanks
to its horizontal slider.
Le 09/01/2017 à 16:37, Hilaire a écrit :
> We are refering to the same things. I express a feeling from a user
> expe
Great! IMHO there is a lot to learn from newbies or naive users
experience to improve the Pharo IDE tools.
The Calypso multiple tab panels of edited methods is nice.
By the way, when asking for the reference of a Trait it always returns
an empty list, but I guess you already know it.
Le 09/01/201
Ok, nice to hear that. I will have to change the VM sooner or later for
DrGeo then.
Le 13/01/2017 à 16:44, Esteban Lorenzano a écrit :
> yes they do.
> you just have to download the vm for Pharo4
>
> (vry old versions of Pharo maybe will not work, but who knows :P)
>
> Esteban
--
Dr. Geo
h
I don't know yet Jeff. I don't have either a macos sierra at hand. Once
a Mac OS Sierra user reported me the problem your are mentioning[1], but
I did not get very far investigating the problem.
For me it is not clear at all from[2] if there is any Mac VM 4.0. May be
Esteban can enlighten us.
[1]
Will it work with Pharo 3 image?
Le 14/01/2017 à 20:38, Esteban Lorenzano a écrit :
> oops… I forget to update that one.
> I will do it next week, thanks for reporting!
>
> Esteban
--
Dr. Geo
http://drgeo.eu
I like interacting with the news group too, including with this mailing
list. I found it very efficient.
Hilaire
Le 15/01/2017 à 09:46, jtuc...@objektfabrik.de a
écrit :
> And that's exactly why I still like the usenet: I can read/answer
> whenever I want, using my mail cl
Hi,
Is there a way from an instance to access a method situated 2 layers up
in the class hierarchy?
A kind of super super.
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
Thanks Henrik
Le 15/01/2017 à 22:33, Henrik Nergaard a écrit :
> menu perform: #isMorph withArguments: #() inSuperclass: ProtoObject. "Error
> #isMorph not implemented"
--
Dr. Geo
http://drgeo.eu
Playing with Pharo5 with Phratch, I just noted two usability problems:
- Short cut for class ref does not work (CTRL+SHIFT+B)
- selecting a word by double clicking in text editor is not as good as
before, you need to be fast on your double click. It worked as a charm
with Pharo 3.
- when right cli
...another one
In an implementor view, when selecting a method in the top list, then
clicking somewhere in the text view, the carret does not follow, you
have to clic again! Another regression compare to Pharo3.
--
Dr. Geo
http://drgeo.eu
Agree on the hook. However the super class are not mine. Not an ideal
situation
Le 21/01/2017 à 11:19, stepharong a écrit :
> No and I'm happy that this is like that.
> I think that it means that you need to create special hooks in the super
> superclass.
--
Dr. Geo
http://drgeo.eu
Yep, it is the first situation I face where I need it in 10 years of
Smalltalk/Pharo. Otherwise I will refactor super class package, may be I
should
Le 21/01/2017 à 11:19, stepharong a écrit :
> pay attention and to not use it. It is evil to use that in plain domain
> code.
--
Dr. Geo
http://drg
yes, something like factoring out in its own method a chunk of code in
super super method I want to access from my subclass.
Le 21/01/2017 à 19:32, Sebastian Heidbrink via Pharo-users a écrit :
> Now I am wondering what you guys are meaning by "hooks"?
--
Dr. Geo
http://drgeo.eu
Worst than that :) In theory I can refactor the super code and commit,
but SmalltalkHub does not let me commit even I have RW access... So I
have to knock at the Philippe's or Masashi's door so they can commit it
for me. It's annoying to bother busy people. Anyway enough small talk ;)
Le 21/01/201
seem to be taken in consideration.
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
jects.
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
Thanks for the update, we will check.
Hilaire
Le 30/01/2017 à 14:28, Sven Van Caekenberghe a écrit :
> STON can do that.
>
> It handles shared, circular references, and thus graphs.
>
> It short circuits classes by using their global name.
>
> But it is meant for doma
xulrunner is abandonware? The new way to build UI in Firefox is
totally different I guess so then?.
Beside Phobos, there is no reliable and feature complete alternative to
build desktop application, is it that?
Thanks
Hilaire
Le 30/01/2017 à 11:36, Pavel Krivanek a écrit :
> Hi Hilaire,
>
Hi,
So in Pharo5 we have these 'beautiful' unreadable tooltips: tiny black
font on light gray (ie. take a look to its squeak counter part, it looks
so much more pro)
Is there a way to programmatically change the backround color?
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
think something is not working properly in the
Pharo process release.
Another complain, why do we have now for Morph #setBallonText: and
#helpText: to set tooltips?
With my little resource, I am just itching the surface, I wonder how it
is deep underneath.
Thanks
Hilaire
Le 30/01/2017 à 15:56
Thanks for the udpate.
GTK binding? Thanks but no thanks, it does not fit for pro desktop
application.
Hilaire
Le 30/01/2017 à 16:34, Pavel Krivanek a écrit :
> The XULRunner was stopped to be supported in 2015. It can still run now
> but without security patches, support of the new OS ve
I don't buy this argument at all: tooltips were modified to become
unreadable, there are responsibility behind to be taken by someone.
FOSS is not an excuse for mere quality.
In the past I have to fix the WaterTheme because a merge was poorly done
at some point without obviously no visual testing
Does it make a difference? I guess you are wearing your glass when at
computer.
Le 30/01/2017 à 17:15, Dimitris Chloupis a écrit :
> I am able to read the Pharo tooltips and I have a 6 degree myopia.
>
--
Dr. Geo
http://drgeo.eu
Indeed font is different, but this one can be changed programmatically,
so can be fixed.
I am not sure the same can be done for the background, it is more
important to improve the contrast (for example yellow or even blue as it
was some release ago).
The Squeak tooltip is nice.
Hilaire
Le 30/01
Well it can't.
So here is the fix for pharo6
https://pharo.fogbugz.com/f/cases/edit/19627/
Le 30/01/2017 à 18:53, Hilaire a écrit :
> I am not sure the same can be done for the background, it is more
> important to improve the contrast (for example yellow or even blue as it
> was so
Thanks Ben.
Le 30/01/2017 à 19:22, Ben Coman a écrit :
> BalloonMorph setBalloonColorTo: Color yellow.
I did not know this one. Btw this method name is awful, #ballonColor:
would have made it just fine
>
> Or...
>
> Pharo3Theme subclass: #Pharo3aTheme
I know this one, and I want to avoid it.
its
was feedbacks, as the tooltips in the GUI provide it ;)
Hilaire
--
Dr. Geo
http://drgeo.eu
I would like to help in both accessibility and implementation detail of
the theme. In the other hand I fell we are in such flux with the future
UI in Pharo. What are the grounds we can stand on regarding UI?
Hilaire
Le 31/01/2017 à 11:21, p...@highoctane.be a
écrit :
> Well there is no subcl
Hi Ken,
Did you have former experience using Phobos for real desktop application?
Hilaire
Le 30/01/2017 à 20:03, kmo a écrit :
> I think Phobos is really good. It would be great to have Pharo 6 version.
> It's a pity about XULRunner being abandoned but all is not lost. There is
I mean no offense to Esteban, I appreciate him well (he slept a couple
of days at my place :) but GTK looks so odd on Mac and OSX desktop, then
it is not that much well featured. There are richer alternative like
wxWidget or Qt.
Le 30/01/2017 à 16:45, Hilaire a écrit :
> GTK binding? Thanks
Blue is fine too. It was so before.
Le 31/01/2017 à 14:14, Ben Coman a écrit :
> Any opinions from the rest of the community on making one of those two
> default?
--
Dr. Geo
http://drgeo.eu
ideas?
Hilaire
--
Dr. Geo
http://drgeo.eu
Ok, found it, I was looking in the wrong place. Related to
#wantsRoundedCordner and #handlesDropShadowInHand.
Hilaire
Le 02/02/2017 à 17:57, Hilaire a écrit :
> Hi,
>
> In Phratch, between Pharo4 and Pharo5, we have this difference when
> grabbing/dragging a costume, it gots now wit
uess there are a lot of idiots out there, and these are the ones
we want to come and *to stay* with Pharo!
So any wish to *really* improve the UI quality, or just words?
Hilaire
Le 02/02/2017 à 19:38, stepharong a écrit :
> On Tue, 31 Jan 2017 13:52:54 +0100, Hilaire
> wrote:
>
>&g
, but my plates are already mostly
full. But if Pharo thinks quality is good enough then ok, I will shut up.
Hilaire
Le 03/02/2017 à 09:54, denker a écrit :
> Yes, words is the problem: it is *so* easy to know what others have to do.
> Trivial. *Doing* is hard… maybe you should be in charg
e annoying bugs regarding usability
- the team should be able to fix itself most of these issues.
How does it sound?
Hilaire
Le 03/02/2017 à 12:25, Serge Stinckwich a écrit :
> I like the idea of a UI quality team and more dedicated teams should
> be built maybe on documentation, CI, etc .
;through' buttons in the
debugger.
Then I may be able to word tooltips for these two buttons, but you will
have already word it in your explanation I guess.
Ok we are just making round circle here ;)
I guess a UI quality team could see that sort of tiny itches and ask to
the community, then fix it.
Hilaire
--
Dr. Geo
http://drgeo.eu
Damned you are inferring a lot on my writing, but I understand now.
In my previous post I had no argument against the *new* debugger, nor I
wrote its interface degraded. I just made an absolute remark regarding
lack of information on non obvious function, in the debugger in my
example, which apply
Will Serge, Dimitris willing to join in with me?
Hilaire
Le 04/02/2017 à 18:26, stepharong a écrit :
>> How does it sound?
>
> good but will we find these people?
--
Dr. Geo
http://drgeo.eu
May be more naive eyes will more likely see glitches
Le 04/02/2017 à 22:45,
serge.stinckw...@gmail.com a écrit :
> I guess we can find better qualified people about UI quality than me ;-)
> Doru or Johan are examples.
--
Dr. Geo
http://drgeo.eu
Seaside is needed by Voyage.
Is there a way to get a recent Voyage installed without altering an
existing Seaside set up?
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
Some more info.
Installing the configuration of Voyage from Pharo4 itself also breaks
the installed Seaside, which was previously installed from the Pharo4
configuration too.
Now when installing the Voyage configuration, it warns about installing
Seaside-Core and the conflict with installed versi
Trying to understand this problem:
>From my development image, I uninstalled all seaside, then I installed
Voyage. This time it went fine AND Seaside-core *was not* installed
during the process.
What the heck is going on?
When Seaside was present in my dev. image, installing Voyage make
Seaside-
s constant over time. This approach is not
really possible with Pharo.
Best wishes
Hilaire
Le 15/02/2017 à 23:43, horrido a écrit :
> In file-based word, the answer is tests and CI. What is the smalltalk way?
> And please do not say "It's in the conceptual nature of programming&quo
tp://smalltalkhub.com/mc/Magritte/Magritte3/main/ ---
http://smalltalkhub.com/mc/Magritte/Magritte3/main/
Loaded -> ConfigurationOfMagritte3-TudorGirba.122 ---
http://smalltalkhub.com/mc/Magritte/Magritte3/main/ ---
/home/hilaire/Travaux/Developpement/Cofilair/Code4.0/sources
Fetched -> Configu
7;Voyage';
load: 'mongo tests'.
It still have the same error, do an upgrade of Seaside.
Enclosed is the transcript for both Metacello and Voyage install.
Seaside installed was 3.1.x. I don't know the x digit, it is not
documented in an obvious way :(
Hope it helps
Tha
The configuration of seaside is the same before and after the
'Monticello new' loads. #278
It match the fact you don't see a ConfigurationOfSeaside3 download in
the transcript.
As I wrote in a previous email, if Seaside is not installed, the install
of Voyage doesn't trigger a Seaside install. Don
Building the image from the shell is what I do for DrGeo release.
For development environment it is more in flux but likely should be
done. Any recommended reading on that specific point?
Hilaire
Le 18/02/2017 à 12:54, Pierce Ng a écrit :
> Nowadays we are encouraging building images f
aside installed from the configuration browser, fix the seaside broken
installation, then install Voyage which went fine. Did not test Voyage
is working though.
Hilaire
[1]The Pharo4 configuration browser's Magritte3 is installing Seaside
update, this should NOT happen.
Now image comes with a Con
d and less-used stuff.
As long as you don't mix old and new it is fine, and it is how is
designed Debian. In the contrarty, I had the felling that Pharo4
configurations were mixing old and new, and of course it brings problem.
Hilaire
--
Dr. Geo
http://drgeo.eu
I will try to get a look at your lock feature, and report.
Thanks
Hilaire
Le 19/02/2017 à 18:50, Dale Henrichs a écrit :
> I mentioned last night that I thought that there was a better solution
> to your problem and I think that if you load the latest Metacello and
> then lock Seaside3
e in the first place, I think it
was from the configuration browser.
Hilaire
Le 19/02/2017 à 18:50, Dale Henrichs a écrit :
> I mentioned last night that I thought that there was a better solution
> to your problem and I think that if you load the latest Metacello and
> then lock Seaside3:
ok to have instances saved in A with
attributes saved in B?
When fetching instances from A, will these instances get their
attributes saved in B right?
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
Hi Dale,
Le 21/02/2017 à 18:30, Dale Henrichs a écrit :
> Metacello image
> project: 'Seaside';
> list
It returns an empty list in this image.
Can you send me privately your email at hilaire [AT] drgeo.eu so I can
send you a link? (I am reading through gmane news foru
CGOrganisation new name: 'Pharo'; id: 0; yourself.
repo1 save: orga.
repo2 save: (CGUser new id: 0; name: 'Hilaire'; organisation: orga;
yourself).
repo1 reset.
repo2 reset.
repo1 := repo2 := nil.
repo1 := VOMongoRepository host: 'localhost' database: 'test1'.
y host: 'localhost' database: 'MaBase'.
repo enableSingleton.
orga := String fromString: 'Pharo'.
orga save.
Then I can press atl+., I got the attached Pharo debug log.
At some point I used wrongly Voyage, from there I got problem.
Thanks
Hilaire
--
Dr. Geo
http:/
Yes, I marked the class String as voyage root. Should it be ByteArray?
Hilaire
Le 22/02/2017 à 14:30, Esteban Lorenzano a écrit :
> did you marked the class as “voyage root”?
--
Dr. Geo
http://drgeo.eu
I though String may be problematic, so I try with Association.
The problem still occurs at,
self collectionAt: anObject class inDatabase: db
There I can see at least a command failed error.
The collection can't be added.
In addCollection: aString capped: aCapped size: aSize max: aMax, the
e the problem before:
CGOrganisation voyageCollectionName. => 'Organisations'
Not sure it is the exact cause of the problem.
Hilaire
--
Dr. Geo
http://drgeo.eu
So far, I edited this method, adding a final string conversion:
voyageCollectionName
"This method can be overridden with a more meaningful collection name"
^ (((self persistentClass name first: 3) allSatisfy: #isUppercase)
ifTrue: [ (self persistentClass name allButFirst: 2) ]
ifFa
Here is the version I have, not sure it is the right way to get the
version number:
ConfigurationOfVoyageMongo project currentVersion >=1.3.3
[ConfigurationOfVoyageMongo]
Le 22/02/2017 à 15:02, Esteban Lorenzano a écrit :
> and probably the version for Pharo 4 does not have the fix… I do not reme
Got it!
Hilaire
Le 22/02/2017 à 15:22, Esteban Lorenzano a écrit :
> I know, but I don’t know what it has or has not that version.
--
Dr. Geo
http://drgeo.eu
se: 'test1'.
repo2 := VOMongoRepository host: 'localhost' database: 'test2'.
orga := 'Pharo' -> 13.
repo1 save: orga.
repo2 save: ('Hilaire' -> orga).
repo2 selectAll: Association.
=> an OrderedCollection('Hilaire'->'Pharo&
and then one repository for each organisation, you can still apply
> same pattern as before, but instead enums you persist a reference to your
> organisation and then on materialisation you can repoint to it.
Indeed, I was thinking about storing reference.
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
ration/MacOperation
depending on the host running the VM.
That way you could add up more operation when needed.
But likely there is already something like that in the system but I
can't see.
Hilaire
Le 24/02/2017 à 02:11, Offray Vladimir Luna Cárdenas a écrit :
>
> I'm trying to open some
Oh, you can add your extension to the OSPlateform hierarchy.
So one your extensions added in the hierarchy, your code will use it
with an uniform:
OSPlateforme current openPdf: 'grafoscopio.pdf'
Le 24/02/2017 à 18:55, Hilaire a écrit :
> But likely there is already something lik
rld menu using the pragma name:
WorldState desktopMenuPragmaKeyword: 'drgeoMenu'.
Hilaire
Le 24/02/2017 à 02:24, Pablo R. Digonzelli a écrit :
> Hi, I want to know how to do in order a desktop application start with
> its custom menu without pharo panel.
> I read something ab
The best of the two worlds ;)
Le 25/02/2017 à 12:37, Norbert Hartl a écrit :
> To me it is important to have a working image that collects side effects as
> well as having a process that builds an image from scratch.
--
Dr. Geo
http://drgeo.eu
y, no access to the DB takes place.
As understood, cache can be flushed, but it is overkill, no?
Is it safe to just do:
VOMongoRepostiry current cache removeObject: objectA
to only flush objectA from cache?
Hilaire
--
Dr. Geo
http://drgeo.eu
Well done!
Le 27/02/2017 à 18:07, Serge Stinckwich a écrit :
> Great news !
>
> Thank you Jigyasa, Uko, Peter and Alex for your great work this year !
>
--
Dr. Geo
http://drgeo.eu
be at some time I will use float for efficiency, but in the mean
time I would like to postpone optimisation and persist exact numeric
value when possible.
Hilaire
--
Dr. Geo
http://drgeo.eu
Hi Raffaello,
You can annotate your methods with a pragma, for example
, then from the Finder tool (WorldMenu>Tools>Finder),
you search for pragma:
In the left text field, input workInProgress, then in the drop down list
at the right, select Pragmas.
Hilaire
Le 01/03/2017 à 18:53, Raf
eCode, but I suspect I will have trouble too
with the key, as I see from Voyage code it is persisted as a String.
An idea how to overcome this (without modifying my model)?
Fuel was persisting it fine.
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
It will, thanks
Le 01/03/2017 à 20:42, Esteban Lorenzano a écrit :
> hope this helps,
--
Dr. Geo
http://drgeo.eu
be an acceptable option. Is
there a global way to do this? I see the per attribute beEager but it
will be needed for a lot of attributes making not practical.
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
someObjects includes: each anAttribute "the one Voyage should fetch"]
I guess implementing = and hash in the anAttribute class will resolve
the issue, but it will be slower, and an uneeded feature.
Any alternative idea?
Hilaire
--
Dr. Geo
http://drgeo.eu
includes: each anAttribute "the one Voyage should fetch"]
Hilaire
Le 02/03/2017 à 21:58, Esteban Lorenzano a écrit :
> Hi Hilaire,
>
> I do not understand well your problem. Which query do you want to implement?
>
> cheers!
> Esteban
--
Dr. Geo
http://drgeo.eu
sDate]);
yourself
However, the tutorial on Entreprise Pharo book only mention the later one.
So what the differences?
Thanks
Hilaire
--
Dr. Geo
http://drgeo.eu
jects includes: each anAttribute "the one Voyage should fetch"]
There is some lazyness in resolving the object.
I implemented = to bypass the == and primivite but it does not help.
For efficiency and special aspect of the model, I prefer to stick to the
Smalltalk iterators when possible.
H
I don't understand why I should use a query!
I already have an instance of the object fetched from the repo but its
attributes are not resolved when read from an iterator block: I can't
pick up the one I want.
These attributes are not root, to the contrary to what I wrote initially.
H
Some more clues: in my application if I go in other part where these
attributes are used for some simulation, the attributes are resolved as
expected. Then when I go back the other part the select is working.
On more hints: the attribute collection seems to resolve fine, so proxy
is working, howev
ies intToDate: (GratuitousIncompatibilities
dateToMilliseconds: '1966-2-17' asDate)) asDate
=> 15 Février 1966
Hilaire
--
Dr. Geo
http://drgeo.eu
leAccessor
read: [:person | person birthday ifNotNil: [person birthday
mmdd]]
write: [:person :string |string ifNotNil: [person birthday:
string
asDate]]);
yourself
Le 03/03/2017 à 21:12, Hilaire a écrit :
> Not sure it is related to this:
> http:
pointer?
Hilaire
--
Dr. Geo
http://drgeo.eu
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
when I inspect an
instance, edit one attribute from the inspector, then save it from the
inspector with "self save" command.
Hilaire
Le 04/03/2017 à 12:21, Sabine Manaa a écrit :
> did you do VORepository current reset in the meantime?
>
> If yes, this could be the reason.
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
, even if
it is not the case.
In some scenario, user really needs to override the comparing protocol,
how to deal with the duplicated entries issue in that case?
Hilaire
Le 05/03/2017 à 10:19, Hilaire a écrit :
> I must stress the same instance duplication occurs when I inspect an
> instance
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
The more I think the more it seems wrong to me. Whenever you ask an
instance to save itself, if already in repo it should not duplicate
itself whenever hash/= is overrided in this object. It does not sound as
an expected behaviour.
Hilaire
Le 05/03/2017 à 14:51, Hilaire a écrit :
> Underst
Le 03/03/2017 à 18:09, Hilaire a écrit :
> I will try to dig for more clues.
Now that I clarified the issues regarding duplicated entries and Date. I
took another look to this problem.
After reset of the repo, to test for sure Voyage correctly retrieves the
attributes, I face the same is
Ah, sorry I was not clear enough in my introduction. Obviously, I
removed all =/hash overrides on the involved objects and it is therefore
an orthogonal issue (that's why I first resolved the other issues
first). Or did you mean something I did not understand in your previous
message?
Hilair
1 - 100 of 1072 matches
Mail list logo
