1  |   Order by index

Nov 10, 2002, 3:00pm

Is there an updated one... I don't see much about many of the new features. Maybe I
missed something.

--Bowen--

Nov 10, 2002, 3:50pm

Don't rely on the SDK web-site for the documentation. Some of it is sorely
out of date, especially the attributes. Because most of the changes in 3.4
appear to be browser changes, the major impact is on the attributes list
rather than the calls themselves. Us poor developers are left to either
guess what is updated or wait for the officially updated version. Hopefully
the attributes list will be brought up to date at the same time as it
appears to be very you of sync with aw.h.


[View Quote]

Nov 10, 2002, 4:00pm

I'm not sure if build 27 of the sdk is the most up to date version though. :\

--Bowen--

[View Quote]

Nov 10, 2002, 4:07pm

[View Quote] Yeah it looks like it's not the most up to date with the newest browser and server
settings.

--Bowen--

Nov 10, 2002, 4:12pm

Either way, the documentation is nowhere close to the latest version that
*is* available for download. There's a lot of updating to be done.

More changes once the correct "latest" version is released I guess.

Grims

[View Quote]

Nov 10, 2002, 4:14pm

[View Quote] It's horrible, now I have to wait. :P

--Bowen--

Nov 10, 2002, 4:29pm

Sadly we all do. Impatience is a virtue heh

[View Quote]

Nov 10, 2002, 11:29pm

I must have missed it too.. where is the updated SDK I wonder, drowned
in 3D waters? I hope at least this post gets answered, there has been
more than one about this without ANY answer from devteam... or maybe
the answer got purged? :(

Alex G = XelaG

On 10 Nov 2002 12:00:05 -0500, "bowen"
[View Quote] >Is there an updated one... I don't see much about many of the new features. Maybe I
>missed something.
>
>--Bowen--
>

Nov 11, 2002, 12:38am

I must have missed it too.. where is the updated SDK I wonder, drowned
in 3D waters? I hope at least this post gets answered, there has been
more than one about this without ANY answer from devteam... or maybe
the answer got purged? :(

Alex G = XelaG

On 10 Nov 2002 12:00:05 -0500, "bowen"
[View Quote] >Is there an updated one... I don't see much about many of the new features. Maybe I
>missed something.
>
>--Bowen--
>

Nov 11, 2002, 10:31am

There goes my next thought then. I was going to ask you if you had some
simple event handling code form X1 I could purloin so I wouldn't need to
make an educated guess at the new attributes in the events.

As you mentioned in another post somewhere ... realease notes for each build
of the the SDK (rather than just updated documentation which we all need
compare against previous versions) would be a massive help to developers.

Grims


[View Quote]

Nov 11, 2002, 11:32am

Well, keep in mind that 3.4 is far from completion because the help files
for 3.4 haven't even been posted yet. If it were released now, nobody would
know how to control, say, the water, because there's nowhere to go for help.

Or maybe the documentation is already almost finished and just not uploaded
yet?

[View Quote]

Nov 11, 2002, 2:28pm

This is just my opinion of course but as far as I am concerned the interface
is the first thing that should have been frozen and documented, and done so
a long time ago. The SDK doesn't hold much in the way of functionality, if
anything, so the only true dependencies for the SDK is the finalisation of
"what is supported", the implementation of the necessary changes to the
interface itself and the changes to the server components to support the new
features. To some (well, ok, me anyway), the features available through bot
development are as AT LEAST as important as those features in the browser
itself - where the look of the world in the browser is just client
functionality (why would I need wavey water to slow down the world when the
3D environment is intended to be primarily functional rather than
"pretty"?).

If the documentation for the SDK isn't complete, then its just the same old
story of a bad development lifecycle. Completion of documentation should NOT
be an afterthought, its an important (and early) part in a successful
development. Its supposed to be available for use as a reference for the
construction and testing phases, but all too often its considered just too
damned boring for techies to bother with at the right time, and the
documentation is created after the fact (and is often left incorrect and/or
incomplete). There's no *valid* reason for the technical documentation not
to be available so far into a project (including pressing deadlines).

If the SDK documentation IS complete, then there's no reason not to publish
it as pre-release documentation. And if, once again, it turns up as a "state
of the union" piece, where the new interface is described in full with
remarks on release changes dotted around the pages rather than having the
changes to the interface documented as a separate deliverable, then I'm just
going to be frikkin livid. So much time is spent by so many people making
changes to generic code for handling the AW interface that its inconceivable
that there are no decent release notes produced.

I'm getting myself annoyed now, so I'll leave it there. I can just imagine
the internal project documents that AW produce and work with. Reading
through the Beta newsgroup, some of the types of bugs posted make me think
that the project starts by changing the code and relying on individual
knowledge to pick up any "quirks" that the changes may cause. I doesn't
exactly fill me with confidence - I've seen it far too often.

Grims


[View Quote]

1  |   Order by index