CAD CAM EDM DRO - Yahoo Group Archive

Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve

Posted by Tim Goldstein
on 2002-11-06 14:22:21 UTC
What you are both doing is pointing out exactly why Vector is an easier
program to learn. I am not saying that Rhino is not worth learning as it is
VERY powerful, but it is also very complex.

Most computer users are now accustom to working in Windows with the mouse,
toolbars, and menus. For the majority of users learning command line is
about equal to cleaning out the cats litter pan. Some one may have to do it,
but they would be much happier if it is not them. Vector uses these very
familiar methods that are common in most non-CAD windows programs without
the command line entry and abstract concepts that are common in Autocad
style systems. I do agree that the command line can be very fast, but it
normally requires you to use the same program frequently to remember all the
syntax and short cuts. When you look at the majority of productivity
programs in the world today that command line paradigm was dropped long ago
as it just never was successful for the casual user.

So, I sit by my contention. Vector is an easy to learn and use CAD/CAM
program. While it is very capable even in the NURBS version it is not as
powerful as Rhino. That is the reason I am working at becoming a Rhino user.
Can I do the vast majority of what I need in Vector?Certainly. I have been
able to do all that I wanted with only Vector for a number of years.
Actually I could likely have just stayed with Vector only and still done all
that I wanted to do. The primary reason for learning Rhino is for its
ability to generate great renderings that I can save into common graphic
formats using the Flamingo plugin. I am doing some articles for another
hobby and I needed an better way to create illustrations. Some of the
concepts are difficult to illustrate in 2D so I needed to be able to do them
in 3D. Vector Nurbs has allowed me to do this wonderfully on the screen, but
at the moment is lacking a method to save the wonderful renderings other
then cut and paste which is only at the display resolution. Rhino lets me
get around this limitation. Now if I wanted to machine the part I would be
all set in Vector, but for illustrating it I am not. Once I got Rhino it was
a small step to also get Visual Mill. So, now I have 2 methods to create
tool paths and I can actually combine them. I can take a drawing in Rhino
and bring it into Vector NURBS and I can take a Vector drawing and put it
into Rhino or Visual Mill. So I have increased my capabilities greatly. All
of this to say that I am in no way expecting to replace Vector with Rhino,
but more to augment may range. I still feel Vector is a great CAD/CAM
package and will continue to recommend it very highly.

Tim
[Denver, CO]

----- Original Message -----
> HI Tim,
>
> RhinoCad is very similar to Autocad in that it uses all the same commands
> and techniques. So, any tutorial on Autocad or other 'standard' Cad system
> will be helpful. Rhino has an advantage over Autocad in that it
> 'automatically' produces rendered 3D images but, for me, it has the great
> disadvantage that all its commands need to be entered in full - like
> 'circle' (to draw a circle) rather than just the 'c' of Autocad.
>
> [In Rhino, you can issue the "Circle" command by typing "ci" and then
> hitting the Tab key. Most typed-in commands can be shortcut this way, as
> long as they are unambiguous. But Rhino has at least eight ways of
> constructing a circle: the Circle command does the centerpoint/radius
type,
> but you can also choose diameter, 3 points, around curve, tangent tangent
> radius, tangent tangent tangent, vertical center radius, and vertical
> diameter. ]
>
> I would recommend that you try to learn to use Rhino from the command
line -
> just type the commands from the keyboard - rather than using the mouse all
> the time - its very much quicker and easier when you get used to it.
>
> Best wishes,
> Ian
> --
>
> Ian W. Wright
> Sheffield, UK
>
> [Yes, that can certainly speed things up. If you use certain commands
often,
> you can also set up shortcut keys to invoke them, using the
> Tools/options/aliases dialogue.]
>
> Andrew Werby
> www.computersculpture.com
>

Discussion Thread

Tim Goldstein 2002-11-05 18:51:02 UTC Re: [CAD_CAM_EDM_DRO] vector's learning curve too big, any other suggestions Scott A. Stephens 2002-11-05 18:55:31 UTC Re: [CAD_CAM_EDM_DRO] vector's learning curve too big, any other suggestions Tim Goldstein 2002-11-05 21:11:05 UTC RE: [CAD_CAM_EDM_DRO] Rhino, Was:vector's learning curve Ian W. Wright 2002-11-06 02:02:01 UTC Re: [CAD_CAM_EDM_DRO] Rhino, Was:vector's learning curve Andrew Werby 2002-11-06 13:52:22 UTC Re: Rhino, Was:vector's learning curve Tim Goldstein 2002-11-06 14:22:21 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve stevenson_engineers 2002-11-06 14:45:32 UTC Re: Rhino, Was:vector's learning curve Tim Goldstein 2002-11-06 14:58:49 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve Carlos Guillermo 2002-11-06 16:26:14 UTC RE: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve Scott A. Stephens 2002-11-06 16:46:35 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve thomasm923@a... 2002-11-06 20:16:10 UTC Re: Rhino, Was:vector's learning curve Chris L 2002-11-06 21:49:24 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve Chris L 2002-11-06 22:02:18 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve stevenson_engineers 2002-11-07 00:50:54 UTC Re: Rhino, Was:vector's learning curve Ian W. Wright 2002-11-07 01:44:41 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve Ian W. Wright 2002-11-07 06:16:29 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve CL 2002-11-07 10:19:57 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve Keith Rumley 2002-11-07 10:39:20 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve Keith Rumley 2002-11-07 10:39:22 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve Keith Rumley 2002-11-07 10:39:24 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve Keith Rumley 2002-11-07 10:48:03 UTC Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve Fred Smith 2002-11-07 14:36:52 UTC Re: productivity in drawing, was Rhino, Was:vector's learning curve