The Homebrew section is almost here! I went through this topic and came up with a rough draft of the form, guidelines, and subpage. The preview button will work, but the submission button will not. Submissions will not be allowed until all the fields and what not are finalized and properly hooked up to the queue.http://www.romhacking.net/?page=homebrew&action=addentrypage
Most ideas were incorporated, but I am still not sold on several of them and wish to discuss them further.1. Source Code Language
I don't think we want to get involved in keeping/maintaining a table of programming languages. We might want to axe this field. Perhaps for homebrew, we may only be talking about Assembly, C, and C++ and need no more. I don't personally know of any written in anything else. However, I am also giving consideration that this field may be ported to other sections like Utilities which would use any language conceivable and require maintenance.2. Source Utility:
This was done as Neil suggested linking to our Utilities 'Assembly Tools' category. If we go with this field, we may want to rename that category so it is clear to accept C/C++ compilers (or have a separate compilers category and link both to the drop down here). My issue with this field as mentioned earlier in the topic is version mismatches. Say homebrew X assembles only with older assembler version Y and not the current version Z carried by our site. Secondly, I expect lazy people will, rather than submitting the tool they used when not found to our database, simply chose 'None'. Then, we'll have a bunch of 'Nones' and the field isn't all that useful.3.Source License
Here's another field we may choose to axe. I don't think we want to get involved with maintaining a list of available software licenses (and there are always custom ones) for a proper dropdown. So, we're left with a write-in field. Write-ins are only partially useful as it becomes just a text tag and not easily searchable for any other purpose. Also, as mentioned, the majority of content on this site has no license whatsoever. So, I certainly question how useful this is as-is? I also shudder with the educational consequences of people having no clue what a license is.4.Modifications:
While I understand the general idea behind this one from what Neil suggested
, I'm not sure how useful it is in its current iteration. What do you guys think about this? I'm not sure I understand the choices well. Everything would be 'processor' wouldn't it? Nearly everything with any screen output would also be 'Graphics' by default. I'm not sure how useful those would be for starters.5.Category:
My initial thoughts were homebrew basically fits into three categories and I have tried to provide explanation of the difference between the three. Although, a case could be made that Tech Demos and Hardware Tests are basically the same. My thoughts were mainly to separate them due to the potential for archiving emulator accuracy test type ROMs. Perhaps they should be ruled out of scope here, but I don't think accuracy test ROMs are actually centrally archived anywhere else and thought maybe we should do so. Thoughts on the categories?
Lastly on all the source code fields, I am also giving consideration that these fields may be ported to other sections like Utilities. So, if we want to keep them, consideration should be made on their usefulness and application to other areas of the site.