Quote from: dinocorn at Feb 08, 2014, 02:48 PMMark,
I think I understand what you are implying. That this contest is a waste of time and should have been done differently and isn't about the default theme. What I don't understand is why you see it that way.
You're simply wrong there. I do NOT think this contest is a waste of time.
If I thought it was a waste of time, I would not have offered modmore licenses, or spend the time trying to get my point across about a slightly different way the contest could be shaped in order to, in my belief, maximise the outcome.
What I think is this and nothing more or less: designers trying to figure out ExtJS in order to submit working themes can be better spent by those people to create great mock-ups and iterate upon that, leaving the implementation to developers.
In that sense, the part of the contest that needs people to build a full working theme that may or may not end up being used in the core or as package, yes I think
that part of the contest and that part alone could be wasted time
for the people building out entire themes. While it does get people to look at what's possible and how to do it, I, as developer that will gladly help doing the developing, would rather have designers focusing on what they do best: design. Most people are either really good at design or development, and not both like you JP.
This whole thread started because of the default theme, and I simply made the edit to clarify that we aren't going to guarantee that the winner of this contest, whatever it be, is automatically the default theme. What if none of the submissions even work?
Fair enough, the most important thing should indeed be that it is an improvement and works properly. That's exactly what I want too.
Now, maybe I caused confusion by making that clarification and emphasising the importance of non-default themes as options, but I'd be disappointed to see you succeed in steering the direction of this thread away from how it started, our desire to see the default theme evolve.
If you think I'm trying to steer this thread away from evolving the default theme, there is definitely a lot of miscommunication going on. All I want is for designers to focus on what they do best, so the end result is a default theme that is as best as it can be with the talent we have in the community.
The primary reasons my interpretation of this contest is that it's focused on alternative manager interfaces instead of the default are:
- themes need to be fully built out (if it's just about getting the right design, that shouldn't be asked from designers - a group of developers could build out the winner)
- the edit in the first post that I interpreted differently than it was intended, which you just clarified.
- indeed your clarifications about non-default themes, moving away from the one manager interface and shipping multiple themes with 2.3. Again, something you just clarified.
Either way it isn't possible to release 2.3 right after a theme is chosen as it needs testing, so I don't see the problem in delaying a release an extra week for building the best theme.
If we agree that we want the same thing, an improved design for 2.3, then we are somewhat on the same page and I propose we drop all misinterpretations and assumptions and just work on making 2.3 as great as it can be.
If by now you still don't agree that it might be a bit unnecessary to build out a full theme in order for the team to review a submission and consider it for 2.3, then nothing I can say will sway your mind and you wont hear from me about that again. That doesn't mean I agree it's the best way to run this, but hey, this is a contest set out by MODX and if MODX wants to do it that way, then I'll just have to suck it up. I just thought the fact the first post wasn't finalised yet that the exact details were still open for discussion.
☆ A M B ☆
