TheSwamp
CAD Forums => CAD General => Topic started by: Big Boi on October 08, 2009, 02:54:42 PM
-
Where in the menus can you change your ACAD2010 to the classic setting, which basically gets rid of the ribbon?
Thanks in advance.
I think I figured it out......you type in "menubar" and turn it on. Then you turn the ribbon off......
-
Where in the menus can you change your ACAD2010 to the classic setting, which basically gets rid of the ribbon?
Thanks in advance.
I think I figured it out......you type in "menubar" and turn it on. Then you turn the ribbon off......
That works in regular ACAD but not in the Architectural vertical. Unverified Rumor (keyword folks) is that eventually menu bars will go away in all types sometime in future.
-
I think I figured it out......you type in "menubar" and turn it on. Then you turn the ribbon off......
That is how you turn it off, but type WSSAVE to save the current workspace so they don't pop back up again.
Unverified Rumor (keyword folks) is that eventually menu bars will go away in all types sometime in future.
Ugh... I think I'm going to cry....
-
Unverified Rumor (keyword folks) is that eventually menu bars will go away in all types sometime in future.
Is this something they have done based on consumer testing or just because we can?
-
Unverified Rumor (keyword folks) is that eventually menu bars will go away in all types sometime in future.
Is this something they have done based on consumer testing or just because we can?
From what I gathered and assumed from said Unverified Rumor is that they are going to mimic MS then the latter applies because they can.
-
Sounds like Wizards First Rule.
http://www.theswamp.org/index.php?topic=14073.msg367966#msg367966
-
Sounds like Wizards First Rule.
http://www.theswamp.org/index.php?topic=14073.msg367966#msg367966
Yep becuase we as a society constantly need a State of Fear.
-
For the record.. I wouldn't bet on those ribbons going anywhere.. it would invalidate any training done this year or next (because it's in 2011 too).
If there's one thing I've learned about software version updates of any kind.. you're better off adapting to use the new stuff, because eventually the old stuff goes bye-bye. Not to mention competitors copying each other to stay competitive, so there's nowhere to run.
Where did you think windows came from? You think MSDOS had any real limitations? Or that windows 3.1 had any real reason to be there? It "made things easier" without adding much at first, but gradually, it became more useful.
That kinda bacteria just keeps on growing, and the more you learn to adapt to it, the longer you'll survive without a new release slapping you in the face with discontinuation of your favorite things, and you'll start seeing how it CAN improve, and then you'll start seeing how it DOES improve.
:mrgreen: <-- just ask him where disco went :-D
-
Why is the Ribbon a so sucky?
Resource demands on systems cause hitches and stutters
Icons are always changing while a menu is written words
(lets face it, the symbols are nearly the same size as the words are anymore)
Why it is likely to change to Ribbons anyway?
To finally drive the AutoCAD community nuts and drive us away for good :lmao:
This similar philosophy was held by those who prefered command line programs over gui's :ugly:
-
From the old DOS days, it has always seemed to 'dumb down' the software. Concentrating on NEW customers rather than the existing and 'experienced' customers. - Just like the rest of the businesses out there.
craigr
-
Sounds like Wizards First Rule.
http://www.theswamp.org/index.php?topic=14073.msg367966#msg367966
Great books, even if he does get long winded at times.
-
From the old DOS days, it has always seemed to 'dumb down' the software. Concentrating on NEW customers rather than the existing and 'experienced' customers.
I tend to think it's only that way if that's what you want to see.
For example, take command line vs. GUI. A lot of people complain about that. But if you had to go back to using nothing but a GUI, I'm positive you'd be very upset. We've gotten too used to WYSIWYG, drag-n-drop, multiple app windows, and more. Even people who still use a command line or text interface (such as vim) will often do THAT inside a window, and have multiple windows open simultaneously.
Now it's true that, sometimes, people design a GUI that's crap, and much harder to use than whatever it replaced. But that's usually because of the GUI design. A good example is some of the stuff inside of Civil 3D, where we have to setup these big tables of values, and the GUI is terrible, forcing us to click on cells one at a time, right-click and select "Create New Item" and then have to hunt through the entire table for the new item, and very terrible GUI design elements like that. But just because SOME people abuse GUIs, that doesn't mean that GUIs are bad.
And even for experienced users, it's nice when things get simpler. When the easy tasks get simpler, so do the more complex tasks, which might involve combining simple tasks in convoluted ways. As it becomes easier and faster to do more in a given application, the experienced users can use that better platform to do even fancier things. Sometimes it gets frustrating, because when they make a change, they sometimes break one of our fancy processes. But it's always a growing process, and while sometimes it seems we take two steps back for every step forward, we eventually are much further along than when we started.
At least, I feel that's another way of looking at all the same stuff.
-
They (ACAD and MS) seem to try to give us the opportunity to set up program customizations (cui), why can't they include a way to customize the gui also? Remember how, before windows, you could buy a seperate "shell" program that sort of "wrapped around" dos and let you make our own windows type interface?
Why can't we, as the user, have more control over all user control interface operations? Or should I just shut up and learn VBA?
-
I understand your point and don't neccesarily disagree. - I just don't like having to learn the new interface(s). I tend to prefer to follow the same path most of the time. When I HAVE to take a totally different path it throws me some.
In the end, it isn't like I / we have a choice in the matter. In our Industry we HAVE to keep up with the changing technology & software. If we don't, their is always someone waiting in the wings that HAS kept up with it and just waiting for our jobs. I was just venting a little frustration I feel every time it changes.
craigr
-
They (ACAD and MS) seem to try to give us the opportunity to set up program customizations (cui), why can't they include a way to customize the gui also? Remember how, before windows, you could buy a seperate "shell" program that sort of "wrapped around" dos and let you make our own windows type interface?
Why can't we, as the user, have more control over all user control interface operations? Or should I just shut up and learn VBA?
Don't learn VBA - it's almost dead.
But as for the rest of what you're saying, I can't really follow... The CUI lets you create menus and toolbars and Ribbon panels, which you can then arrange however you wish, and you can save your favorite layouts as Workspaces. What would you rather see?
-
Those "old timers" who have been using (geez, sounds like a drug...) since R12 will likely not be working much with the software in ten years, either due to retirement/semi-retirement, promotion to managerial position, etc. I feel like they are focusing on the future front-line users rather than those who are using it today.
There's also a few future-of-the-software type questions, like whether the ribbon is better when using the touch screens which seem to be popping up everywhere. You think the ribbon takes up screen room, how about an entire virtual keyboard on the screen for devices without a hardware keyboard? Also, is it easier to interface the ribbon with a cloud-based application than it is with something that is command-line driven?
-
Yes, I too have thought of the 'on screen' keyboard. Because of the 'real estate' taken by having the Keyboard on screen, I don't see a physical keyboard going aways anytime soon, even if our screens get really big. There will always be the practicality issue.
I believe we will have more and more of our tasks taken over for us in future releases. Software that actually 'learns' how one uses the software. As an example, will learn that to trim 2 intersecting 90° lines, I like to fillet at 0 radius, my coworker likes the trim command. I believe the software will learn the differences and automatically cue up the command or just do it on its own. Kind of like the voice recognition software learns our voice.
If us 'old timers' (am I an old timer at 50?), don't learn to adapt and stay up to date, we may be useless for this type of work.
It will continue to be mind boggeling what is to come in the realm of software, just hold on tight and ride along.
craigr
-
If us 'old timers' (am I an old timer at 50?), don't learn to adapt and stay up to date, we may be useless for this type of work.
Yep. But how come the ones with check book never seem to understand this logic?
-
If us 'old timers' (am I an old timer at 50?), don't learn to adapt and stay up to date, we may be useless for this type of work.
Yep. But how come the ones with check book never seem to understand this logic?
Mostly it is because they have purchased training from the local vendor at some point in the past...and the cost benefit ratio was such that they never recovered their 'investment' in the training. And from that point forward any mention of training is seen as an expense with no benefit, so they continue to skip on training. This is my perception after 9 years as independent consultant, and echoed by nearly every client I have served, and all of the ones I did not. They just cant get over that experience; and I can't blame them too much either.
-
Bear in mind that the ribbon, as a concept, was created for office applications and they have far, far fewer commands and variables than any CAD programme.
But the acad ribbon is getting better and will continue to get better - I just hope it doesn't become the only available interface whilst I'm stilll active.
btw, the PELLIPSE variable was going to be dropped around the 2000 release - it still exists in the 2011 release.