Re: [CAD_CAM_EDM_DRO] Re: Rhino, Was:vector's learning curve
Posted by
Tim Goldstein
on 2002-11-06 14:58:49 UTC
----- Original Message -----
word processor and a spread sheet. I am refering to programs that are used
by huge numbe of users.
not software engineering. In the real world (that is the world where
companies make billions selling software) the command line is dead except
for the geeks and Unix contingent.
command line is not the way to go. If you are there is no doubt about the
speed.
program when they can fit it in which is far from often enough to become
accomplished at remembering all the command line commands.
user hat and clicking and dragging is the prefered method so that when I
bring up a program I have not used in 2 months I can get something done
immediately.
are a HOBBY user and this is the first time you have gotten to use the
program in a month.
Again the point I am making is that the requirements for a day in day out
user are vastly different from a casual user. In my mind Vector gives the
casual user the power of many big $$ programs in a format that is better
suited to their usage.
Tim
[Denver, CO]
> Productivity programs by their very essence aren't for the casualGuess I should clarify. Outside of the CNC world a productivity program is a
> user, they are heavyweight full time programs.
word processor and a spread sheet. I am refering to programs that are used
by huge numbe of users.
> The command line hasn't been dropped but it's alive and well.Again you are looking at this from the perspective of the machine shop and
not software engineering. In the real world (that is the world where
companies make billions selling software) the command line is dead except
for the geeks and Unix contingent.
> Have aExactly what I am saying. If you are not a daily user of the program the
> look at any serious Cad programs like Autocad, Microstation etc and
> the people who use these 10 hours a day are all on command line
> inputs.
command line is not the way to go. If you are there is no doubt about the
speed.
> True there are mouse / menu moves to duplicate these movesRemember this is a hobby list and the majority of the members use a CAD/CAM
> but the speed is still in the command line.
program when they can fit it in which is far from often enough to become
accomplished at remembering all the command line commands.
> One of the biggest failings I hear against Turbocad is that it's veryOrganizations vs hobby again. You need to put on your casual, occasional
> powerfull but the endless clicking dragging and tabing makes it a
> pain to use. I know of quite a few organisations that have evalulated
> it only to drop it because of the slow input.
user hat and clicking and dragging is the prefered method so that when I
bring up a program I have not used in 2 months I can get something done
immediately.
> What can be more productive when needing to draw a keyway or slot 8mmNothing unless it takes you 10 minutes to figure out the command because you
> wide and 30mm long in the vertical plane than to enter the following
> on the command line:-
> SL,8,30,90 <enter>
are a HOBBY user and this is the first time you have gotten to use the
program in a month.
Again the point I am making is that the requirements for a day in day out
user are vastly different from a casual user. In my mind Vector gives the
casual user the power of many big $$ programs in a format that is better
suited to their usage.
Tim
[Denver, CO]
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