Tweet
I'm very dissapointed in GV for releasing this upgrade and hard coding the interface colours into it. Didn't anybody stop and think for a moment that maybe there are some users out there that don't want an even uglier interface than we already have.
I've put up with a lot of stumbles and bumbles along the way, but to stuff up something so straight forward, someone should be looking for a new vocation.
To say this is on the unapproved list, and it will be looked at in due course, makes me even more steamed. Don't they understand that I'm looking at this colouring-in colour scheme from a 3 year old, all day.
All day.
I've designed software myself, and GV is not acquitting itself with either it's development control or it's QC. The product design team need to be put in the corner and told, you either fix this goofy stuff up now, right now, or you can start taking support calls.
I mean really stuffing up the interface like this, unbelievable.
And after all this time, still not able to stop the cursor flying all over the place, and that's just the most frequent reminders of this kind of ineptitude. To say that you have to get into the mindset of the designer.... How about they get in the mindset of the user for a change? That old chestnut is always put forward when the designers are unable to make the changes.
Have the development team got themselves into such a mess that they can't fix these things? Because that's what it sounds like to me. The base code has ended up not being able to be modified. I've seen this before, a product starts out being very responsive to customer requirements, then no-one effectively polices the changes, they are done add hoc, and then the next release can't incorprate all of the add hoc changes that were previously made, and bingo we get the same problem coming back, and even new problems, because the add -hoc changes were tested, but by recoding other problems are introduced.
Classic version control stuff.
These kind of problems were sorted out 15 years ago in professional development environments. GV need to get on top of this right now or Edius is already dead.
GV I'm very disappointed in these latest changes, you've lost one of the few that have been banging away evangelising Edius.
This interface makes me so mad, I'm finishing the 3 projects I have running at the moment under 4.5, and going back to 3.61 before I start looking for something else. At least 3.61 doesn't make me want to throw up every time I look at it.
Edius 4.5 - GV your bad.
Ross Herewini
Sydney
I've put up with a lot of stumbles and bumbles along the way, but to stuff up something so straight forward, someone should be looking for a new vocation.
To say this is on the unapproved list, and it will be looked at in due course, makes me even more steamed. Don't they understand that I'm looking at this colouring-in colour scheme from a 3 year old, all day.
All day.
I've designed software myself, and GV is not acquitting itself with either it's development control or it's QC. The product design team need to be put in the corner and told, you either fix this goofy stuff up now, right now, or you can start taking support calls.
I mean really stuffing up the interface like this, unbelievable.
And after all this time, still not able to stop the cursor flying all over the place, and that's just the most frequent reminders of this kind of ineptitude. To say that you have to get into the mindset of the designer.... How about they get in the mindset of the user for a change? That old chestnut is always put forward when the designers are unable to make the changes.
Have the development team got themselves into such a mess that they can't fix these things? Because that's what it sounds like to me. The base code has ended up not being able to be modified. I've seen this before, a product starts out being very responsive to customer requirements, then no-one effectively polices the changes, they are done add hoc, and then the next release can't incorprate all of the add hoc changes that were previously made, and bingo we get the same problem coming back, and even new problems, because the add -hoc changes were tested, but by recoding other problems are introduced.
Classic version control stuff.
These kind of problems were sorted out 15 years ago in professional development environments. GV need to get on top of this right now or Edius is already dead.
GV I'm very disappointed in these latest changes, you've lost one of the few that have been banging away evangelising Edius.
This interface makes me so mad, I'm finishing the 3 projects I have running at the moment under 4.5, and going back to 3.61 before I start looking for something else. At least 3.61 doesn't make me want to throw up every time I look at it.
Edius 4.5 - GV your bad.
Ross Herewini
Sydney
Comment