Leslie,

<< Any news on the public beta? >>

Nothing yet.  2.01 B2 has to be released, and then I'll see about updating
the build system for some test builds for FPC.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

"Nothing yet.  2.01 B2 has to be released, and then I'll see about updating
the build system for some test builds for FPC."


As you see it at the moment can you estimate a  probable timeframe? (Supposed nothing none
foreseeable comes up.)

Shouldn't it be 2.02 B2? :O
Where can I find list of the changes for the next build?

Leslie

"Shouldn't it be 2.02 B2?" - please ignore. I thought "B" stood for beta, just realised it
is  "Build".

Leslie

Leslie,

<< As you see it at the moment can you estimate a  probable timeframe?
(Supposed nothing none foreseeable comes up.) >>

As I said already when you first asked this - early August.  So, in the
first couple weeks of August.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Originally we were talking about a beta some time in July, that is why I had to ask again.
I am patiently waiting as always, but need to adjust my plans and my communication to our
clients to the availability of the WinCE port. It is no problem if it takes longer then
you have expected, but as I said when we first talked about this, it is very important for
me to know if there is any change in plans. Hope you understand.

Leslie

Leslie,

<< Originally we were talking about a beta some time in July, that is why I
had to ask again. >>

I didn't give any timeframe on a beta, nor actually commit to a public beta.
What I said was that I would try to get you a copy to play with once I got
the builds completed (mainly because you're the only one interested in this
at the moment .  We don't normally do public betas for minor releases.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

There was obviously no promise. I told you our timeframe and - as I understood - you
were willing to try according that. Could not have expected anything more. The only thing
I asked for was to be notified if there would be any change in the initial timeframe.
Naturally you can change your plans concerning the WinCE port any time as it fits you, my
only request is to know about it.  I thought these were clear from the beginning … maybe
it is just my English.  

I am taking a risk here by trying to build our projects on a db engine I am not familiar
with … is just being ported … but it is my decision, would not blame on anyone else if it
does not work out as hoped.  In the previous post I tried to explain a bit why I am
bringing the timeframe question up again, but it was probably unnecessary. Had no
intention to drag you into my problems, which may have been the taste of it. From now I
will cut it short.

Leslie

Leslie,

<< There was obviously no promise. I told you our timeframe and - as I
understood - you were willing to try according that. Could not have expected
anything more. The only thing I asked for was to be notified if there would
be any change in the initial timeframe. Naturally you can change your plans
concerning the WinCE port any time as it fits you, my only request is to
know about it.  I thought these were clear from the beginning … maybe it is
just my English.  >>

Everything you say is exactly as I understand it, so I don't think there's
any difference of expectations.  Our plans are to ship 2.02 by the second
week of August with the FP port in place.

<< I am taking a risk here by trying to build our projects on a db engine I
am not familiar with … is just being ported … but it is my decision, would
not blame on anyone else if it does not work out as hoped. >>

Well, the engine itself did not change at all.  The only thing that changed
for the FP port was the "edges" of the engine - I/O, and API calls.  Plus,
we already ported the engine to CF, so much of the API issues were already
resolved.  The only difficulties that were encountered were with a bug in
the TWideStringField in FP.  Apart from that, the rest was fairly simple,
including the alignment requirements.

<< In the previous post I tried to explain a bit why I am bringing the
timeframe question up again, but it was probably unnecessary. Had no
intention to drag you into my problems, which may have been the taste of it.
From now I will cut it short. >>

I understand your concerns, and sorry if I'm seeming a little "prickly".
I'm under the gun to get 2.01 B2 out and get back to work on 2.02, and
things like the email and newsgroups are just not cooperating.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

It is all clear then.

Leslie

Tim,

FPC 2.2.2 has been released. It may have solved the issue you mentioned.

http://wiki.freepascal.org/User_Changes_2.2.2

Leslie