Too late to submit Negative feedback for R2012b !
3 views (last 30 days)
The Jan Simon's question Experiences with release 2012b shows that a lot of experienced users find the new MATLAB interface horrible .
However , there were 2 opportunities this year to submit your feedback to MathWorks to say them that you do not like the ribbons.
- February 2012 (before R2012a was shipped): the MATLAB Desktop Beta . Let me quote an email of the MathWorks which reminds us the aim of testing : _We appreciate your help in testing prereleased software. This gives you the opportunity to contribute feedback directly to MathWorks Development staff and get early access to software that is not yet commercially available._This was the first opportunity for MATLAB users to discover the new interface.
- June 2012 : *R2012b_Prerelease*Another opportunity to discover the new MATLAB interface and to submit his feedack
So I have 2 questions :
Question for MATLAB users : Did you test one of these beta and SUBMIT your feedback to MathWorks?
Question for TMW : Did you receive negative feedback about the ribbons?
Oleg Komarov on 18 Sep 2012
Edited: Oleg Komarov on 18 Sep 2012
I did test the R2012b_prerelease and I submitted my feedback as mentioned in the other post Aurelien linked.
However, I am not likely to send a negative feedback unless is truly disrupting my workflow (like it did for the run configurations), and the ribbon wasn't really that bad (you can minimize it and use the QAT).
I also think that the "horrible" ribbon is a result of an escalation of negative feelings and betrayed expectations auto-alimented by community feedback. What I want to say is that we could all feel a bit disappointed on our own, but when we gather together then we become outraged (herding). However, we cannot talk on the forum about the pre_release in its testing phase, thus the reaction of the herd can only be assessed ex-post.
BTW, not to late to submit feedback on R2012b but for R2013a!
Jan on 18 Sep 2012
Edited: Jan on 18 Sep 2012
I did not test 2012b-pre because I do not have an active maintenance licence currently.
There is no overlap between the wished features (started in Feb 2011) and the implemented features.
[EDITED] Not concerning ribbons, but the new help style:
Look at the help text about the figure properties. This is much harder to read than the corresponding page, which is found in 2011a locally. Search for the ButtonDownFcn for instance:
- The important header "ButtonDownFcn" is written in normal weight and typewrite font with an empty line before the paragraph. Then a lot of paragraphs is following which contain one or two sentences only, but the separating vertical spaces are very large.
- The header for the section, which describes the usage starts with a +2 fontsize bold Using the ButtonDownFcn. This looks more important than the main section about teh ButtonDownFcn.
- Headers and text start at the same horizontal position, although there is a huge space on the left and the right.
- The giantic margins on the left and the right, additional margins in medium grey and the generous usage of empty lines almost around any sentence, less than 30% of a full-screen window on a 4:3 19'' monitor contains information. On wide-screens this will be less, I'm afraid.
I did not see the online help before the release date.
I also suspect this was a decision taken some time ago -> a strategic management decision....
It would of taken a lot of time to develop and hence - there wouldn't of been enough time to revert back to the previous menu based system based on any negative feedback recieved. Also if they did revert back - what would the difference of been between 2012a and b?
Just my humble opinion...
I've only just migrated to 2010b so it will be a while before we upgrade and I hope its either seen to work or we can skip a release or two and the menu will have come back.... (hopeful thinking I imagine...)
Michelle Hirsch on 19 Sep 2012
Answering Aurelien's second question:
We received lots of feedback throughout the process of developing the Toolstrip and documentation center, literally hundreds and hundreds of individual points of feedback. While it might not be obvious from the communication online, the majority of feedback was positive.
We analyzed everything that we heard, both quantitatively and qualitatively, working particularly hard to pull out the constructive elements from the critical feedback. One significant result of this was quite a bit of refinement of the design and integration of features specifically intended to support our most experienced users. Those of you who provided specific workflow-related feedback on the Desktop beta can likely see features in 12b that were direct responses to your input.
I had no access to the beta version for testing - so no opportunity to provide feedback.