style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"pquenzi" <pquenzi@up.net>I
wrote in message
href="news:f123eb8.1@WebX.maYIadrTaRb">news:f123eb8.1@WebX.maYIadrTaRb...
know your frustration. Your letter struck a nerve.
Kent, I take exception
to your answer. When I started to use Inventor, I did just as you suggested,
read all I could on "Projects". Every time I did, I came away feeling like a
complete idiot. It is described in such a generalized manner using such
convoluted terms as to be almost meaningless to a new user. I'm sure what they
say is accurate and would make perfect sense once you figured out how to
actually use "Projects", but to go in the other direction and use the
insturctions to learn how to use "Projects" is another matter enitrely.
Realizing I needed help, I called my Autodesk retailer. They told me to take
their course on Inventor. I told them I felt I was doing okay with Inventor
and just needed help on "Projects". They essentially said. Can't help, take
the course. I did and spent an awful lot of money on the course. After the
first morning I realized I knew as much if not more than the instrutor and
asked for the rest of my money back. He said they hadn't gotten to the good
stuff yet and they would make it well worthwhile for me to finish the course.
Turns out I learned very little from them and when it came time for
"Projects", they ran out of time and spent 3 minutes on the subject. With that
off my chest, everything I learned about "Projects" has been by trial and
error.
Wogz, if you want to email me direct, I KNOW I can describe how to
use projuects in PLAIN ENGLISH better than what is done in Point A etc. I,m no
expert, but what I'm doing is working.
Kent, this is an invitation to you
guys too. Maybe with my attempts at explaining it in English and your
corrections on procedure, we could come up with a simple one page insturction
you could post on a web site to handle such questions.
Best regards,
Phil Quenzi
pquenzi@up.net
Kent,
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
"pquenzi" <pquenzi@up.net>Kent,
wrote in message
href="news:f123eb8.3@WebX.maYIadrTaRb">news:f123eb8.3@WebX.maYIadrTaRb...
I have no argument with what you say, but some of the basic stuff like
what exactly do you include in a project is not at all clear, or what do you
put in "local" versus "workgoup" versus "workspace" etc.
I think I can explain that nicely by using a real world example and walking
through it.
When the tutorials use examples they might talk about a "widget" or
something. By definition you don't know what a "widget" is or what it is
composed of, so how can you get a feel for how to set up a project for it?
If you use a real world example such as a building, bridge, telephone,
automobile, tractor, etc. it is something that people can relate to. I design
specialized mobile equipment, and would describe how I'd set up the project
for a new machine and some of the mistakes I've made along the way. You, or
others in your group could make improvements to what I suggest.
I know there are all sorts of working enivronments out there and wouldn't
pretend to have answers for those individual needs, but I think a simple,
brief explanation of the basics using a real world example would be ueful for
new users.
I'll try to write something up and send it to you. It may take a day or
two.
Phil