| |
Logiker
Registered: Mar 2011
Posts: 15 |
Compo categories insufficient
Maybe I can explain best with a current example...
When we look at the Revision party there are for example following two categories:
"C64 Graphics" and "Mixed Graphics"
Within the party these categories were called:
"ASCII/ANSI/PETSCII" and "Oldschool Graphics"
I see several problems here:
- You don't know what the real compo category was called like
- You can't see that "C64 Graphics" stand for "PETSCII" (and others)
- You believe there are several entries missing, although it's not, because the other entries were from other systems (Which you would know if there was the correct name of the compo category)
There is also other examples like:
- BASIC 10Liner Contest 2019 (BASIC 10Liner Contest 2019) -> Here it's too hard to add the given categories
- Flashback 2019 Flashback 2019 -> Currently every gfx is put into "C64 Graphics", which was PETSCII at revision, so some users get confused (see comment at Flasheep).
That's my feedback so far. I hope it can help.
A similar entry already was entered some time ago: Compo descriptions |
|
... 20 posts hidden. Click here to view all posts....
|
| |
Logiker
Registered: Mar 2011
Posts: 15 |
Well, there are still some sparkles of hope.
I believe that people many people recognize now, that a long term solution is needed and not just a minor fix.
Wouldn't it be nice to find the correct categories for each event instead of just a generic one, that sometimes does not fit at all?
Let's hope the party will just start! |
| |
hedning
Registered: Mar 2009
Posts: 4731 |
Adding custom compo types will not happen. It will be misunderstood and will mess upp the database galore.
What is missing now are:
* C64 PETSCII (for clean PETSCII compos)
* Mixed Texttype (For ANSI/ASCII/PETSCII Mixed compos)
* Mixed Intro (For intro compos for many platforms)
Those seems to make sense in most of cases, for starters. |
| |
Logiker
Registered: Mar 2011
Posts: 15 |
Quoting hedningAdding custom compo types will not happen.
A pity in my mind.
Quoting hedningIt will be misunderstood...
If you could have exactly the same name as in the compo I think that would be easier to understand, not harder (as it is the case now).
Quoting hedning...and will mess up the database galore.
Well, the database would have to be adapted in an appropriate way. Not easy, but it would be worth it.
Quoting hedningWhat is missing now are:
* C64 PETSCII (for clean PETSCII compos)
* Mixed Texttype (For ANSI/ASCII/PETSCII Mixed compos)
* Mixed Intro (For intro compos for many platforms)
Those seems to make sense in most of cases, for starters.
These adaptions would definitely help a lot! :-) |
| |
Mr.Ammo
Account closed
Registered: Oct 2002
Posts: 228 |
Quoting LogikerQuoting Mr AmmoThat's not my point.
But the topic is about Compo categories not about specific events. Not adding these historical insignificant compos for the commodore 64 scene results in not having the need for these extra compo categories you mentioned for the basic demo compo.
Here's an old posting about when events need to be added to the database: Change of rules - What kind of Events belong into the Database |
| |
Jazzcat
Registered: Feb 2002
Posts: 1044 |
+1 for C64 Petscii compo. |
| |
Oswald
Registered: Apr 2002
Posts: 5094 |
corners must be cut, or csdb will end up with thousands of categories which makes the DB unusable. |
| |
hedning
Registered: Mar 2009
Posts: 4731 |
Quote: corners must be cut, or csdb will end up with thousands of categories which makes the DB unusable.
Correct |
| |
Logiker
Registered: Mar 2011
Posts: 15 |
Quoting Mr AmmoNot adding these historical insignificant compos for the commodore 64 scene results in not having the need for these extra compo categories you mentioned for the basic demo compo.
Agreed mainly. Though there were more than these examples. Look at Revision (which is relevant I think). It has now the categories "C64 Graphics" and "Mixed Graphics". It just very hard (in fact impossible) to know what these categories were called in real. Well, you can (have to) look up at the Revision homepage or at Demozoo for accurate data. Is that what this DB is there for?
And yes, there should not be too many categories, or as I call them category types. But correct category names would be more than just nice to have to me. |
| |
Burglar
Registered: Dec 2004
Posts: 1098 |
Quote: corners must be cut, or csdb will end up with thousands of categories which makes the DB unusable.
Well that's a bit of a hyperbole ;)
No one is asking for thousands of compo categories, not even dozens. I'd suggest only 1 additional compo category: PETSCII!
Many parties have a petscii compo these days, so seems quite well established. It will not make the database unusable, it will make it a bit more correct.
Only downside is that past parties with a petscii compo will need their compo results updated in the db, but this does not sound like a huge job. I'm sure compo organizers themselves will be happy to help out. |
| |
hedning
Registered: Mar 2009
Posts: 4731 |
Quote: Well that's a bit of a hyperbole ;)
No one is asking for thousands of compo categories, not even dozens. I'd suggest only 1 additional compo category: PETSCII!
Many parties have a petscii compo these days, so seems quite well established. It will not make the database unusable, it will make it a bit more correct.
Only downside is that past parties with a petscii compo will need their compo results updated in the db, but this does not sound like a huge job. I'm sure compo organizers themselves will be happy to help out.
+1. And as we have so many registered users that are constantly helping out with the database instead of whining in the forums and comments I am sure it will take no time at all. |
| Previous - 1 | 2 | 3 - Next |
