Hi,
Pavel Janík a écrit :
BTW, this is not the first personal attack against me. Last was when
I asked for money for the WWDC, where you wrote bad things about me.
You take everything too personally...
Just the facts : when I read " (because I feel that Eric just wants to
announce something...)! ". This is personal attack.
Sending people who signed NDA and
thus (at least you systematically tells so) can't share the contents of
sessions at WWDC is nonsense for the project.
No : what we will see during conferences (exepted public confs) is under
NDA.
What we will do with Apple engineers will be public, and blogged /
reported. Big difference, no ?
And I'm confident, the infos we will obtain are more important than the
4500 euros the travel will cost : optimize time and quantity of
information is one of the objectives of WWDC attending.
I won't pay someone to go
somewhere and NOT tell me about the visit!!!
This is wrong. See above.
What is the difference, for the end user, between two assembled cws,
and the same in a milestone ?
He gets something predictable?
If cws is correct, both are predictable at the same level : what we do
mixing aquavcl01 and aquafilepicker01 is exactly the same we will do
integrating them.
I disagree again : my patches are only what will be soon added, and
they are public : http://eric.bachard.free.fr/mac/aquavcl/patches/
salframe/may07/aquavcl01_ericb.diff
Good - prepare them for aquavcl01 cws please and it will be in the next
dev. snapshot of aquavcl01...
Ok, I'll commit the patch, and no problem with anymore. Of course, I
fully agree the background must me drawn differently : I'm the first to
search how proceed cleanely.
*We have* aquavcl01 + aquafilepicker01 and for the ui, we have that too.
Yes, we have two separate child workspaces. There is no defined way to
get a build of two cwses in one build. And if they conflict, it is
impossible to do -> it doesn't make sense to mix them together.
Then there is a problem with the process.
Technical point: they are IMHO compatible. Just reverse changes in
aquavcl01 fpicker, and do not use vcl changes in aquafilepicker 01
solves everything.
>> What you propose will add at least two weeks. OpenOffice.org is an
adminsitrative monster.
And why two weeks matter when we were working on it for three years?
I disagree with "three years", for several reasons : the real work
started before, with Stephan Schaefer and Dan Williams contributions,
and other.
The correct order was : complete X11 version, complete Intel port, and
start Aqua port.
The real Aqua work started lat year , just after Intel port. I'd prefer
say since 1 1/2 year instead of three.
This is funny. Two weeks or month more.
The discussion is open.
My personal opinion : things are open. I was sure you (and other) will
have a reaction, and I had in mind to discuss after the meeting what we
will exactly do. No need to add personal attacks.
Of course we will. We all agree with that, and that's the main reason
why I asked to prepare things before to anounce anything.
Do you think we will have them all prepared sooner than in two weeks? ;-)
The point is : do something, because continue to hide what we do is
negative.
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
