Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
(A collapsible tree structure would be nice, like the way XML is displayed in web browsers.)
There's a kewl idea. Have the IDs be nice little XML files that can be easily phrased by a PHP/ASP/Perl/etc script, as XML files could easily be changed/edited by a script when needed. I have quite a bit of experience making PHP scripts to do that kinda thing so if someone wants to mess with it for OSIDs, I'd be happy to help ya.
Therx seems to have a good idea to simplify the form to generate one, put the options in drop down menus instead of using lots of checkboxes.
I think that with a little bit of javascript, you could enable a text box for when someone selects/ticks "Other". I'm not sure though as I don't do much of anything with Javascript anymore.
Ok,I really like the suggestions. I'm gonna use XML,Php, and javascript to do this. I am deving it with K.J. Does anyone else want to help? (Therx, u seem to have started too
---
What exactly should we do with this? Here's what i have interpreted the idea as:
1:tracks OS progress
2:tracks OS build info
3:tracks how to communicate with the developer
4:they will be included with the source downloads(*.zip)
what else?
---
Here's a list of stuff to be filled out on the form:
[osid card]
[os name]
[os web-site]
[os lang(s)]
[os build tools]
[hardware platform]
[os start date]
[os progress>]
bootloader
printf()
IDT
PIC
keyboard
floppy
hard drive
Memory mang
multitasking
console
mouse
sound
can run apps
file system
user rights
gui
cdrom drive
dvdrom drive
keep the informations grouped. For instance, knowing wether floppy is supported or not, cdrom, mouse, etc. could be collected in 2 lists : supported CHAR devices and supported BLOCK devices.
i think the "known bugs" and "developer list" is more something that belongs to the os' website ... However, knowing the memory mapping informations will help for megatokyo forums (as we often have to make assumptions when a small code fragment is posted -- which leads to "if you didn't set up paging 1:1 ... Of course i did ... then perhaps ..." ; see what i mean ?)
also, keep a place for unformatted response, to keep the card open to exotic designs (for instance, someone who had selected the "DWARF" or "A.OUT" binary format just pick up "others" in Therx's form, but he has no place to say what he actually used).
in the same kind of suggestion, it would be fine if things like "ELF" or "GRUB" or "BOOTf02" would have an hyperlink to a homepage, so that people can see what you used come from (DjGpp, etc) or what the format is about ...
I think I will put such kind of info-page upon my web-site as soon as this os i work on has some capabilities of multitasking at least. No, with that struggle, I have with memory management at the moment, I 'd rather keep it behind,as it is not even mature enough to be mentioned. *gg* And I do not want to jump from memory management to job management just because I do not get paging to work properly. I gonna get it working.
But this OSID-Idea is fine. XML-Parsing with php is fine, as php has one or two xml parsers, i think.
Although you could create a script to create the XML file, how about an option to upload an XML file with information that the developer didn't have the option to enter, which could then be embedded into the script created xml file. This could be displayed in an 'additional' section, as to not confuse the 'standard' fields. We could then review the fields people have uploaded in additional information, and update the standard to include them.
This is way, we can improve a 'standard' by evolving the kind of information which is useful for giving help and advice.
Except for the Modify Feature my attempt at an OSID db is complete. This includes:-
[0] Most fields mentioned in this thread
[0] Search, Compare and View facilities.
just a note to all those follwning these posts:
This is a community project. Let's nt monopolise it. As far as
where this project will be hosted, right here at mege tokyo
is fine. We need to work on this together(speaking of
Therx). The system Therx has is coming well, but the
interface isn't to pretty and needs to be more detailed.
---
thanks for all the suggestions, i will start editing it soon. Therx, email me at [faultylogicscs at netscape.net] so we can do this together. Or come to irc.wyldryde.net #osdev where u,me,and kj can chat about it. Everyone else is welcomed to come there, too.
keep a place for unformatted response, to keep the card open to exotic designs
Although you could create a script to create the XML file, how about an option to upload an XML file with information that the developer didn't have the option to enter, which could then be embedded into the script created xml file. This could be displayed in an 'additional' section, as to not confuse the 'standard' fields. We could then review the fields people have uploaded in additional information, and update the standard to include them.
This is way, we can improve a 'standard' by evolving the kind of information which is useful for giving help and advice.
Good idea. And as this would be stored in XML, the phraser to display the XML on a site or something would be able to understand the additional fields even if they weren't part of the "standard".
As far as where this project will be hosted, right here at mege tokyo is fine.
Here or another large OS dev site. As if this is hosted just on someone's personal site, it won't get very far.
DF: let me know if u wanna host it or not. If not, I'd be happy to host it.
Think also about something that could give posted ID cards a valid url like http://www.anywhere.net/osid/idcard.php ... ystem_name so that all the people that enter their infos can put a quicklink to it (i suggest it shows "::OSID::" or something alike) in his/her signature / profile / whatever...
A link to an external CSS stylesheet would also be fine, so that we can customize the look to the colors of our projects (but i might be asking too much ;-p )
And please consider adding "debugging useful infos" fields such as how the memory mapping is done (1:1, kernel starts at 0xC00000 ...). The OSID should provide informations to help people external from the project to track bugz in the project (so that we can help each other)
Just an "add info" field in the ID card with a "info.keyword" and "info.datas" is enough ... but it is very important, imho...
I agree with Pype on all 3 accounts, and i don't think it's too much to ask
As long as the data is all presented in the same way, using a style sheet to change fonts / colours is ok.
I think whoever implements this should remember that this isn't about showcasing our Operating Systems and their features, but Providing I useful set of information to help people help you When you post that help message, we will no longer need to proceed with the 'Lets find out what you've done' preliminaries.
Note that if you don't have a place where you can have your OSID hosted, you still can make it plain text and POST it on the board as an attachement
What is important is not to have a PHP database of it (though it could be smart , but to provide this information.
So why not just write your own OSID, post it here as an attachement, and then edit your profile with an [ url = <path to OSID> ] ::OSID:: [ / url ] in your signature or whatever ...
