Here's a thought. Someone mentioned in the OGA 2.0 design forum that one problem we have here is a lack of consistent art. Maybe we could have a challenge where we place certain constraints on it in order to maintain consistency, so we end up with a set of things that can (theoretically) be used together. Say, have a particular color palette specified in advance where you have to use those colors for your textures and pixels, and also a particular setting. We could ask that the musical entries fit the "flavor" of that setting.
The problem, of course, is that 2D and 3D aren't generally used together in the same kind of game.
@shirish: When you're logged in, the login and password boxes will be replaced with a link to your user profile and a way to log out.
@Redshrike: Good question. I like the two-color thing, but the issue there is that in order to have two colors, I have to split the page at some fixed distance from the left edge. A lot of pages have content that's a fixed with (960 pixels is common) and that content is centered on the screen so that the margins on both sides are equal, and that's most likely what you're used to seeing. The other possibility is I could have a semi-fluid layout, where the right column expands to the width of the screen. The problem with those is that they're more of a pain to implement.
I could probably accomplish a fluid layout with javascript, but my instict is to avoid having a page style that depends on javascript. Maybe I should re-evaluate that. I'll give it some thought.
I can't make any promises about OpenID. Unfortunately it's another one of those areas that I don't have time to do myself, so I'm using a canned Drupal add-on. It's not something that I use myself, so I'm not really even sure how it works -- I added it at someone else's request. I'll see what I can do, but other features will have to take priority. At this point in time, does your openID work the way you described for other websites?
I'll keep people posted on the progress, but I'm not going to be posting a timeline, because ultimately I'll just end up missing the deadline anyway. :)
I've had two suggestions on the menu bar: Either make the whole thing one color, or separate it so that the color separation is meaningful. I'll be doing one of those things, but I haven't yet. :)
...and paste that boilerplate into your code (say 'Copyright 2010 DougX.net'). It does exactly what you're trying to do, and people will be more comfortable making use of the code because it's a license they recognize.
I know it sounds kind of silly (and believe me, the last thing I want to do is be off-putting), but you'd be amazed at how much of a difference licensing can make.
The mockup renders correctly on the latest versions of Chrome (5), Safari, and Opera! Perhaps unsurprisingly, it doesn't render correctly on IE 8, which doesn't support rgba(...) colors or @font-face.
I'm pretty sure the current version of OGA works relatively well on IE6, although it's likely that this will no longer be the case when 2.0 goes live. I can't promise I'll support IE7 either. As for IE8, I'll make sure everything is functional, but I'm not going to spend extra time to make certain that the theming matches exactly. At ay rate, compatibility hacks have to come last, and the design is still in a very early stage.
Here's a thought. Someone mentioned in the OGA 2.0 design forum that one problem we have here is a lack of consistent art. Maybe we could have a challenge where we place certain constraints on it in order to maintain consistency, so we end up with a set of things that can (theoretically) be used together. Say, have a particular color palette specified in advance where you have to use those colors for your textures and pixels, and also a particular setting. We could ask that the musical entries fit the "flavor" of that setting.
The problem, of course, is that 2D and 3D aren't generally used together in the same kind of game.
@shirish: When you're logged in, the login and password boxes will be replaced with a link to your user profile and a way to log out.
@Redshrike: Good question. I like the two-color thing, but the issue there is that in order to have two colors, I have to split the page at some fixed distance from the left edge. A lot of pages have content that's a fixed with (960 pixels is common) and that content is centered on the screen so that the margins on both sides are equal, and that's most likely what you're used to seeing. The other possibility is I could have a semi-fluid layout, where the right column expands to the width of the screen. The problem with those is that they're more of a pain to implement.
I could probably accomplish a fluid layout with javascript, but my instict is to avoid having a page style that depends on javascript. Maybe I should re-evaluate that. I'll give it some thought.
Bart
I can't make any promises about OpenID. Unfortunately it's another one of those areas that I don't have time to do myself, so I'm using a canned Drupal add-on. It's not something that I use myself, so I'm not really even sure how it works -- I added it at someone else's request. I'll see what I can do, but other features will have to take priority. At this point in time, does your openID work the way you described for other websites?
I'll keep people posted on the progress, but I'm not going to be posting a timeline, because ultimately I'll just end up missing the deadline anyway. :)
I've had two suggestions on the menu bar: Either make the whole thing one color, or separate it so that the color separation is meaningful. I'll be doing one of those things, but I haven't yet. :)
The button font will probably need to be changed.
For anyone finding this link through here, please note that the code is MIT-licensed. Thanks again to DougX. :)
Bart
WIP version 2 of the mockup is here. I'll post a message when I've finalized it.
http://oga2.opengameart.org/mockup2/
Awesome, thanks!
For clarity, you may want to go here:
http://en.wikipedia.org/wiki/MIT_License
...and paste that boilerplate into your code (say 'Copyright 2010 DougX.net'). It does exactly what you're trying to do, and people will be more comfortable making use of the code because it's a license they recognize.
I know it sounds kind of silly (and believe me, the last thing I want to do is be off-putting), but you'd be amazed at how much of a difference licensing can make.
Peace!
Bart
Good news everyone!
The mockup renders correctly on the latest versions of Chrome (5), Safari, and Opera! Perhaps unsurprisingly, it doesn't render correctly on IE 8, which doesn't support rgba(...) colors or @font-face.
I'm pretty sure the current version of OGA works relatively well on IE6, although it's likely that this will no longer be the case when 2.0 goes live. I can't promise I'll support IE7 either. As for IE8, I'll make sure everything is functional, but I'm not going to spend extra time to make certain that the theming matches exactly. At ay rate, compatibility hacks have to come last, and the design is still in a very early stage.
Robin: Featured collections, for instance? I hadn't considered that, but it's a very good idea. Tentatively, yes.
Addendum: It's been suggested to me that "forl this work" may not make sense to our users who aren't FOSS coders, and also sounds vaguely obscene. :)
How do people like "remix this work" instead?
Pages