[News] New AmigaOS 4.0 ROM Kernal Reference Manuals in the works! | ANN.lu |
Posted on 24-Apr-2002 16:18 GMT by P Ericson | 86 comments View flat View list |
In a recent interview with Hyperion Software, we're told that Olaf "Olsen" Barthel is working on new ROM Kernal Reference Manuals for AmigaOS 4.0! [The "RKRM" books are the official and prime development documentation/tutorial for AmigaOS developers] As some readers of Amiga Network News may already know, Mr Barthel has previously compiled the Amiga Developer's CD.
|
|
List of all comments to this article |
New AmigaOS 4.0 ROM Kernal Reference Manuals in the works! : Comment 72 of 86 | ANN.lu |
Posted by [JC] on 26-Apr-2002 11:56 GMT | In reply to Comment 64 (.jon): > No, the idiot is *YOU* !
>
> It is clear, that you have no real insight about good developer documentation > formats.
Yeah of course i'm an idiot cos I'm not an Amiga purist. I'm just an idiot who happens to have worked on *3* commercial Amiga game titles for a company still releasing Amiga games. Yeah. And on more platforms than just Amiga and PC. I think I have a little insight into developer documentation.
Admit it, you're against CHTML and the idea of it just because it's a Microsoft idea. What a stupid shortsighted view to take. Notice also I didnt say CHTML, i said an OPEN VARIANT of it (which would be fairly easy to create).
You've also plainly never used it by saying it's hard to maintain, because it's no more difficult to maintain than HTML (or AmigaGuide for that matter). All you do, is make up your docs as you would HTML, with an index file, and then run it through a little tool that compiles it together. At least with HTML, you get editors and things like Doxygen.
Now to answer your points on HTML:
> a) HTML is NOT searchable
That is where CHTML expands on it, by making a search index part of it.
> b) HTML adds much too much overhead
CHTML is compressed so not much overhead there. Processor wise, i'm sure a PPC G3 can handle a little text based HTML with the odd image.
> c) HTML is cluttered up on many many files, making indexing even more
> difficult,
CHTML is a compound file. And before you whine that you can't change it, they can be decompiled back into source HTML.
> d) HTML will lead to ECMAScript and Java and whatever in the API reference,
> somthing desirable, if used with a clue, but most likely it will be used
> clueless.
I've not seen a HTML or CHTML API reference yet use anything beyond plain HTML and CSS.
> PDF is NO CHOICE AT ALL ! The only thing PDF is good for is for printing.
> Period.
I will agree with you there. Most of Apple's developer docs come as PDF, and it's a pain.
You then say in a later post:
> To use it commercially (HAHAHA for a concurrent product !!) would most likely
> mean to pay expensive licenses to deliver a little market with CHTML.
Oh, and of course, it's totally impossible to create something similar and free, isn't it. Oh yes, completely impossible... oh, wait. |
|
List of all comments to this article (continued) |
|
- User Menu
-
- About ANN archives
- The ANN archives is powered by #AmigaZeux. It was updated daily (news last: 22-Oct-2004; comments last: 18-May-2005).
ANN.lu was created, previously owned and maintained by Christian Kemp, www.ckemp.com.
- Contribute
- Not possible at this time!
- Search ANN archives
- Advanced search
- Hosting
- ANN.lu was hosted by Dreamhost. Sign up through this link, mention "ckemp" as referrer and he will get a 10% commission on any account you purchase.
Please show your appreciation for any past, present and future work on ANN.lu by making a contribution via PayPal.
|