That's great if you want to read through it, but meaning no offense whatsoever to the contributors, a proper database with nice front-end in which you can enter desired price range, desired switch, desired plug type etc. and get back a list of matching products is probably best.
It's not even that hard to do. I just don't know the actual SQL to do it, but I know it's not hard to do.
but what would be the purpose of the DB?
Rid us of half page sigs?
The DB as I'd envision it would be every keyboard ever known to any geekhack member. It would not be used to show off what we own but rather to document them. Same type of deal as current keyboard reference wiki but would allow easy cross-referencing by switch type, plug type, original computer it was shipped with, price range and so forth.
No, no member names. There could never be two entries for the same keyboard, it would completely destroy the idea of what this is.
well, i didnt mean actual names. But it could be a way for people to see who else owns it (or wants to try it, or is willing to let others try it, or is selling it, etc).
ie, so long as there is a database, why not put it to multiple uses, and eventually fold in the 'keyboard owner locator' and etc?
Then you go to the most awesome Wiki entry EVER!
Link. (http://geekhack.org/showwiki.php?title=Mechanical+Switch+Keyboards+Sorted+By+Switch)
Addesso Blue Cherries now shipping for $70. See the last post in the link.
The current way we do things around here is about as counter-intuitive as Windows.
I took an entry level course in college. I could make a very basic database but we never did learn how to incorporate online elements since the databases mostly were one user models that stayed on each student's computer.
Really it comes down to who has the skills to pay the bills. Parsing the sentences into the database would not be a huge problem with some basic string handling functions but again it might take somebody with more experience. If nobody here has the skills then it is not possible without some study. I was hoping we had a database programmer in our midst. I'm just a hobbyist game programmer at most. As a programmer, my mind is always thinking "optimize organize" ect. The database just seems like a natural fit for this because you have a series of similar entities (keyboards) that share the same attributes with unique configurations (field data).
this past semester I had an introductory PHP class
Show Image(http://jasdemi.com/wp-content/uploads/drinking_bird.jpg)
It's a good thing they don't teach symbolic logic anymore in college. Gives me the edge.
Well, that got my head spinning in circles.
Mental Hobbit, owner field would be bad, unless it were a field containing a list of every person who does own it. The idea is documenting the existence of the keyboard, not documenting who owns them.
The idea is documenting the existence of the keyboard, not documenting who owns them.
I don't think we've agreed on that part yet. I'd like to have owners included.
IF Manufacturer = "IBM"
THEN Owner := "webwit"
ELSE Owner := "Who cares"
END IF
Technically my algorithm is wrong because it fails to consider the Industrial Model F...
What good does it do to identify who owns keyboards?
I'm getting too many PMs already. Leave the owner part out. That's what sigs are for.