OS dev Tree

[Toaster]

thanks for the replies,

when I said there are just a handful potential companies [if], I didn't meant Microsoft, Sun oder Apple
I know a few little companies I have done work and earned some money with system development
I have experience with "these" companies and can say they are surely using Windows

the documents I have written are not part of the site, they are just tutorials for german people
and of course I always write technical documents [as always the source code] in english - just to clarify

for the website I know the problem that the pictures are not displayed in full screen or nearly full screen, this is a bug with the cms module that the max. width value can't be changed from 800

I'm currently thinking how I can improve the design and user interface, I'll upload a new edition with some improvements then.

Toaster

[Toaster]

I've "updated" the program (only little minor changes because I've slept the whole afternoon and I've got since that no ideas for improvement), but anyway it has now a little bit more elegance, and I'll working on it further.

Now where you know how it looks like, there comes the big simple question, would you use the program if the information there would be complete (all devices, all listings, further information to all resources)?
And if not, why not? do you like a html webpage more than a standalone program?

Toaster

[neon]

I personally like the idea at what you are wanting to do. It creates a single point of information about the chipset, and programming the controllers.

It would be great if the community around this software added much more information to it--how they work, etc. A comprehensive and very extensive set of documentations - all in one place. (Now that I think of it, thats what a Wiki is for )

Unfortunately, there is the problem of appealing to each controller and device.

Who knows--mabey it will find appeal to the world, mabey not. It is always worth a shot though. Perhaps asking one of the OS development firms you are referring to to determin what they think of the idea.

In any case, good luck

Why don't you do an HTML page for each document and references at the bottom.

I agree with the use of HTML pages, as HTML is a very standard format. The references are great as well, provided what they link to stay static and do not become invalid.

Because it's tried and tested, and unlike you (a hobbyist) their aim is to make money and to do that they want an OS up and ready quickly. Having so many tools around conforming to an open standard is an easy, cost effective way of achieving that. Plus the unix architecture is good.

I see what you mean.

[Alboin]

After reading your posts, it sounds to me as if you are simply creating a virtual version of the Indispensable PC Hardware Book. (It's quite a nice book, being essentially what you are describing, but with everything written by the author.)

IMO, the IPCHB is lacking is several areas, so I guess if you were to create a full book of the type, virtual or not, it would be useful. The only part that I'm dubious about is your osdev theory related material. I'm not sure that this would blend well with pure technical documentation. (ie. Theory being more of a reading exercise and tech doc's being more of search and check.)

A suggestion, (?) maybe? I think that if you made each tech doc really structured, it would be more fitting in the design of a program like you are describing. For example, when accessing a floppy controller document, a pdf just wouldn't pop up on the screen, but a structured view would appear, and would sub-divide each category, and almost outline the entire document with all relevant information. (eg. ports, values, etc.)

Another small idea might possibly be a bit setter-like tool, so if one needed to, say, create a byte to initialize the PIC, one could simply click on the PIC initialization byte structure diagram, set one's required bits, and it would spit out a hex, octal, etc. value. Occasionally useful, I guess.

To abstract the previous, a plugin system would be interesting....

As for your market, I really don't know.
Good Luck!

[Toaster]

Another small idea might possibly be a bit setter-like tool, so if one needed to, say, create a byte to initialize the PIC, one could simply click on the PIC initialization byte structure diagram, set one's required bits, and it would spit out a hex, octal, etc. value. Occasionally useful, I guess.

Hey thanks! that'ts a really good idea! I'll include it definitely in the program, this gives more interactivity and usefulness

yesterday (btw. today after midnight) I have developed a "history-list" feature, and the dependence view which was until now empty
I'll publish a new version and screenshots today evening. And I'll go then from program development to enter more information.

Toaster

[AndrewAPrice]

How about exporting selected documents to PDF?

[Toaster]

How about exporting selected documents to PDF?

you mean exporting the text/information from one Controller/peripheral device?

[madeofstaples]

Maybe it's just me 'cuz no one has mentioned it yet, but something really bothers me about the look.

It's like, when someone first plays around with VB, or, delphi in this case I guess, and they use all sorts of controls not how they were intended and end up deviating greatly from the look & feel of a normal application. This wouldn't be so bad if they did it right (programs like winamp did it right), but most of the time, changing the Appearance settings in windows will royally screw up how your application looks. Not to mention it's ugly in the first place (those pseudo-tabs?).

As for would I use this? Yeah sure because it's information.

Would I pay for it? You must be joking

[Toaster]

thanks for your feedback,

I have added so far following features:
- [history]
- Dependence View
- Export into File
- Print

I will change the Floppy and HD drives in the Dependence View and make them more elegant.
Your reviews are furthermore welcome and asked for.

Like always I have uploaded an updated version of the program.

Toaster