Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
103 user(s) are online (59 user(s) are browsing Forums)

Members: 1
Guests: 102

salass00, more...

Headlines

 
  Register To Post  

« 1 (2)
Re: Where is the SDK?
Just popping in
Just popping in


See User information
@glames

Quote:

When I launch SDK/C/sh, if I enter a "dir" then I have a DSI error.

IIRC that was a .rodata write bug which is fixed in the meantime,
search for an update of "abc-shell".

Go to top
Re: Where is the SDK?
Just popping in
Just popping in


See User information
@TetiSoft

Ok. Thanks.

Go to top
Re: Where is the SDK?
Amigans Defender
Amigans Defender


See User information
@glames
Quote:
When I launch SDK/C/sh, if I enter a "dir" then I have a DSI error. PErhaps, it will be good to check it in newer version.

That was a problem with .rodata as already said and was fixed a long time ago in an update to sh which you can find on OS4Depot.

There is also the problem that dir and C:Dir are both in your path. We should probably change "dir" to "gdir" to avoid that conflict.

ExecSG Team Lead
Go to top
Re: Where is the SDK?
Amigans Defender
Amigans Defender


See User information
@glames
Quote:
My system hangs up if I try to trace with gdb a lowlevel.library opening.

That one I don't know anything about but gdb probably needs some rework. We'll need to retest gdb with all the updated components of course.

ExecSG Team Lead
Go to top
Re: Where is the SDK?
Just popping in
Just popping in


See User information
@ssolie,

Thanks for info.

Go to top
Re: Where is the SDK?
Quite a regular
Quite a regular


See User information
@ssolie

In fact after the latest SDK update, gdb tends to be really unreliable on my system whereas I was pretty solid before.
It seems that almost every time I try to attach a crashed process to gdb via GrimReaper either my whole machine hangs, either gdb prints strange error messages asking to contact GNU authors... Really annoying, so now when a program crashes I reboot, launch a shell, then relaucnh the soft inside gdb and try to reproduce the crash (most of the time I'm unable to

@TetiSoft

Was just reading the CatComp documentation and found a (very) small problem in it but I guess this comes from CVS :
Quote:

## rcsid $Date: 2005/12/08 19:01:33 $ $Revision: 1.10 $
## name myprogram.catalog

The above will embed "$VER: myprogram.catalog 39.1 (31.7.92)" inside of the
message catalog.

See the incoherence in the date ? Also two lines above where the format is presented CVS seems to have expanded it so one won't see the format but two times an example...

Back to a quiet home... At last
Go to top
Re: Where is the SDK?
Just popping in
Just popping in


See User information
@abalaban

This was already fixed in V52.2 of CatComp.doc some days before,
now it looks like

Quote:

- "rcsid" lets you specify a version string using the standard RCS method.
That way, versions of catalogs can get updated automatically by RCS.

- "name" can be used in conjunction with the "rcsid" command to specify
the name component of a 2.0 version string. For example:

## rcsid $Date: 2007/02/05 15:52:21 $ $Revision: 1.13 $
## name myprogram.catalog

The above will embed "$VER: myprogram.catalog 1.13 (5.2.2007)" inside of the
message catalog.


The problem is that CVS modifies the rcsid part od the file
each time an update is checked in, so dont wonder when minor
glitches (wrong revision or date) will appear again in future

Go to top
Re: Where is the SDK?
Just popping in
Just popping in


See User information
Years ago there were promises of updated ROM Kernel Manuals. They haven't been updated since 2.04 (over 15 years ago), it is now 4.0, they are in dire need of updating.

They don't need to be released in hardcopy of course, softcopy versions would do.

In particular some detailed ReAction coverage would be welcome.

Go to top
Re: Where is the SDK?
Just can't stay away
Just can't stay away


See User information
@ALL

Note that doing a SDK is a huge task. If anybody can help writing docs, writing example codes, it will be appreciated by everyone.
Please send your work to os4-sdk on hyperion-entertainment dot biz

Thanks.

Philippe 'Elwood' FERRUCCI
Sam460ex 1.10 Ghz
http://elwoodb.free.fr
Go to top
Re: Where is the SDK?
Quite a regular
Quite a regular


See User information
@Tetisoft

I have another one, reading Exec.library/FindPort, I can read :
Quote:

From V50 onwards, the method of protecting the access through
ObtainSysList/ReleaseSysList is prefered to Forbid/Permit locking.


but I did not found any of those ObtainSysList()/ReleaseSysList() methods, so what one should do ?Still use Forbid/Permit or anything else ?

Back to a quiet home... At last
Go to top
Re: Where is the SDK?
Just popping in
Just popping in


See User information
@abalaban

It seems those SysList functions dont exist and adding
such a description to the autodoc was a mistake, the current
autodoc doesnt mention such functions anymore, the example
uses Forbid().

Go to top
Re: Where is the SDK?
Quite a regular
Quite a regular


See User information
@TetiSoft

Ok thank you for the information.
Altough that was IMHO a good idea to have such functions, because as I understood it (and my version of autodocs is stating) the Forbid/Permit couple is something to avoid and can also cause problem parallel computing environment.

Back to a quiet home... At last
Go to top
Re: Where is the SDK?
Home away from home
Home away from home


See User information
@TetiSoft & ssolie

I've found another item that could use a big update. The datatypes documentation. For example, the animation_dtc autodoc lists the methods that an animation datatype has, but not what arguements they take, etc. That documentation seems to be embedded in the datatype source-code for datatypes released with source. Even then, there are tricks such as alf->alf_UserData possibly pointing to a previous frame that should be unloaded.

For the benefit of both datatype users and implementors, these details really should be moved out of example source-code and into the docs. Also the base datatype class has no autodoc, and hence no documentation on its methods.

Hans

Go to top
Re: Where is the SDK?
Just can't stay away
Just can't stay away


See User information
@Hans

Quote:
animation_dtc autodoc lists the methods that an animation datatype has, but not what arguements they take

Aren't tags enough? Or I misunderstood you.

Philippe 'Elwood' FERRUCCI
Sam460ex 1.10 Ghz
http://elwoodb.free.fr
Go to top
Re: Where is the SDK?
Home away from home
Home away from home


See User information
@Elwood

Quote:

Elwood wrote:
@Hans

Quote:
animation_dtc autodoc lists the methods that an animation datatype has, but not what arguements they take

Aren't tags enough? Or I misunderstood you.


No, they're not enough. Take ADTM_LOADFRAME for example. The msg parameter (arguement) is supposed to be a pointer to a variable of type struct adtFrame and alf_TimeStamp within the passed struct is supposed to be set to the desired timestamp. Without this information, you can't use ADTM_LOADFRAME, or write a datatype that has an ADTM_LOADFRAME method. The autodoc simply lists the valid MethodIDs, not what the parameters and return data are for the methods.

Difficulty in finding this information is probably one of the biggest reasons why we have so few datatypes.

Hans

Go to top
Re: Where is the SDK?
Just popping in
Just popping in


See User information
@Hans

Quote:

Take ADTM_LOADFRAME for example. The msg parameter (arguement)
is supposed to be a pointer to a variable of type
struct adtFrame and alf_TimeStamp within the passed struct
is supposed to be set to the desired timestamp.
Without this information, you can't use ADTM_LOADFRAME,
or write a datatype that has an ADTM_LOADFRAME method.
The autodoc simply lists the valid MethodIDs, not what
the parameters and return data are for the methods.

The autodoc is only a part of the SDK. The include files
also contain comments for human readers. <datatypes/animationclass.h>
contains
Quote:

/* ADTM_LOADFRAME, ADTM_UNLOADFRAME */
struct adtFrame
{

which clearly eplains that this structure has to be used
with this methods, and the structure itself starts with
Quote:

ULONG MethodID;
ULONG alf_TimeStamp; /* Timestamp of frame to load */

/* The following fields are filled in by the ADTM_LOADFRAME method, */
/* and are read-only for any other methods. */

which IMHO clearly explains that besides the MethodID
alf_TimeStamp is the only field to be filled out by the
caller, and what else than the desired frame could be specified
by this field?

Quote:

Difficulty in finding this information is probably one of
the biggest reasons why we have so few datatypes.

IMHO the current datatypes system is too limited and too slow
for modern animation formats, thats the reason why everybody
writes custom animation players instead of a datatype which
would allow to use MultiView for viewing DVDs etc.

Go to top
Re: Where is the SDK?
Home away from home
Home away from home


See User information
@TetiSoft

Quote:
The autodoc is only a part of the SDK. The include files
also contain comments for human readers. <datatypes/animationclass.h>


I've been using the headers as well, but the information is not as clear as you think. There is no definite, "here are the input parameters, this is what is output" documentation there, although it's all implied. Moreover, people starting out don't think to look in header files. A lot of people put their documentation in their .c files instead of the header where it should be.

Quote:

TetiSoft wrote:

IMHO the current datatypes system is too limited and too slow
for modern animation formats, thats the reason why everybody
writes custom animation players instead of a datatype which
would allow to use MultiView for viewing DVDs etc.


While experimenting with the gif anim format, performance in Hollywood increased dramatically the moment I enabled 24-bit bitmaps. Unfortunately, the animation datatype can't handle those. The performance issue seems to be because the datatype converts from chunky to planar and then to display it, you have to convert back to chunky again.

Regarding the limitations, I agree that adding support for truecolour bitmaps, streaming, encoder prefs menu popup, etc. would make the datatypes much more useful. Looking at the animation datatype itself, I think that it could easily be improved and extended. There was a group several years ago that were going to attempt this, but it died. It's all a matter of a group getting together and officially extending it.

Even if you use custom viewers for watching, datatypes would still be useful for reading manipulating and saving datatypes. I'd be interested in helping out with advancing the datatypes, the animation datatype in particular.

EDIT: Or should I create a video.datatype class?

Hans


Edited by Hans on 2007/3/11 16:00:53
Go to top
Re: Where is the SDK?
Just can't stay away
Just can't stay away


See User information
@Hans

I don't know if you have time but if you consider writing some documentation (even a small one), I'll be happy to include it in the SDK.
Thanks.

Philippe 'Elwood' FERRUCCI
Sam460ex 1.10 Ghz
http://elwoodb.free.fr
Go to top
Re: Where is the SDK?
Home away from home
Home away from home


See User information
@Elwood

Ok, if I have time. I'm still figuring out how things are structured though.

Hans

Go to top

  Register To Post
« 1 (2)

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project