|
Authored by: jesse on Sunday, April 22 2012 @ 06:40 AM EDT |
The term "blueprints" are used for basic designs with technical detail
that are printed on paper used for creating an object.
It is not restricted to just the method of creating copies.[ Reply to This | Parent | # ]
|
|
Authored by: Ian Al on Sunday, April 22 2012 @ 09:48 AM EDT |
Oracle: When you launch the API design process, what do you
do?
Mark Reinhold: Collect use cases, define the problem/solution
space, general requirements. Important to get quick to a high-level summary [ of
the design ] to share with others. Sketching, writing code snippets. Then you
start writing code for the methods. It's important to work on the implementation
at the same time as the API specification to find bugs in the
specification.
So, he starts with a sketch of the set of interface
specifications and some code fragments and builds from there. That early sketch
is not a 'blueprint' for the completed API implementation.
What he
never says is that nothing in the range from early API sketches to the final
Java API Specification is a blueprint of what to make. The whole is iteratively
designed until it is ready as production code and the Java API Specification.
That Specification is not, now or ever, a 'blueprint' because it is
not a guide to making something, it is a record of the details of how something
is made. Or rather, it is the operating instructions for something that has been
made. --- Regards
Ian Al
Software Patents: It's the disclosed functions in the patent, stupid! [ Reply to This | Parent | # ]
|
- Not blueprints - Authored by: Anonymous on Sunday, April 22 2012 @ 04:00 PM EDT
|
Authored by: betajet on Sunday, April 22 2012 @ 10:40 AM EDT |
Obscure reference to the "Why a duck?" scene in the Marx Brothers' play and 1929
film The Cocoanuts, where Groucho asks Chico: "Do you know what
blueprints are?" and he replies "Yes, oysters" referring to Blue Point oysters.
[ Reply to This | Parent | # ]
|
|
Authored by: complex_number on Sunday, April 22 2012 @ 01:16 PM EDT |
Back when I were a young lad, I did a 4yr Apprenticeship in Mech Engineering.
Part of that was working in the Drawing Office. One of my jobs was to take the
Engineering Master Drawings and copy them.
The semi-transparent masters were fed into what I think we called a 'dyeline'
machine. The result was basically a revered print with White where there were
lettters or lines etc. The remainter of the paper was 'blue'.
That is what I think of as a 'blueprint'.
Then there were the 'blue' prints you got everywhere when you used 'Engineers
Blue' but that is another subject.
---
Ubuntu & 'apt-get' are not the answer to Life, The Universe & Everything which
is of course, "42" or is it 1.618?
[ Reply to This | Parent | # ]
|
|
Authored by: artp on Sunday, April 22 2012 @ 01:47 PM EDT |
The printing process that I am familiar with is the diazo
process. I'll let you look it up on Wikipedia. The normal
process produced blue lines, and a cheaper (?) process came
out in sepia. I have seen some truly big honking blueprint
machines, some bigger than a car.
I would be surprised if blueprints were obsolete. When I
think about the number of obsolete IT projects still
running, and compare that to the 1921 linen drawing that I
pulled out of a drawer back in 1981, it seems very unlikely
that someone actually spent the money to redraw all those
ancient drawings that produce such low volume.
One final nit: If blueprinting went out of use before CAD
became common, then how did companies reproduce their
drawings? Plotters are nice, but they can't reproduce a
linen or mylar drawing.
Final note: I am a terrible drafter. Besides having no hand-
eye coordination or manual dexterity, I lost a full grade in
Drafting class (1974) for always having a dull drawing
pencil. No jokes, please, Groklaw does have standards. ;-)
---
Userfriendly on WGA server outage:
When you're chained to an oar you don't think you should go down when the galley
sinks ?[ Reply to This | Parent | # ]
|
|
|
|
|