[Zope] NIST meeting: "Defining Standard, Scriptable Objects forCAD/CAE/CAM/PDM"CAD/CAE/CAM/PDM"

[Steve Waterbury]

"Defining Standard, Scriptable Objects for CAD/CAE/CAM/PDM"

Date:  December 13th 
Time:  10:00 AM - 4:00 PM
Location:  NIST, Building 225, Room A54
   -> for directions and maps to NIST, see:
http://www.nist.gov/public_affairs/maps/nistmaps.html

* If you plan to come, you MUST contact Michael McLay, so that 
we are sure that the meeting room space is adequate:

   mailto:[EMAIL PROTECTED]
   - or call 301-975-4099

Background:

Roughly, PDM ("Product  Data  Management")  does for  CAD/CAE/CAM
models and related  objects  what Zope does for the objects  that
need to be managed in a typical Web site (HTML docs, etc.).

Problem Statement

The problem is to find an open  architecture  for integrating and
managing the configuration of  computer-aided  design,  analysis,
and manufacturing (CAD/CAE/CAM) tools, models, and data.

The purpose of the meeting is to  evaluate  technologies,  try to
define an approximate  roadmap for building an open architecture,
and establish a ROM guess of (1) how much work may be required to
implement  the  architecture  components  and  (2)  the  cost  of
developing and maintaining an instance of the architecture for an
engineering organization.

Agenda:

  * Engineering Tool/Data Integration Requirements
Steve Waterbury/NASA

  * GenCAM: a Standard API for Electronic Manufacturing Data
Michael McLay/NIST

  * The MEMS Exchange: Python and ZODB for Management of Complex Objects
Andrew Kuchling/CNRI

  * The CADScript/IScript Architecture (and Demo)
Doug Cheney/International TechneGroup, Inc.

  * Python and Zope: Architectures and Directions
Barry Warsaw/Python Labs

  * Group discussion
- How to incorporate interfaces to Python and Zope components 
  such as ZODB into a standard PDM architecture
- What enhancements to ZODB, ZCatalog, ZPatterns, etc., can 
  address functionality and interfaces needed for general PDM
- Which pieces of the architecture make the most sense as open 
  source products, which ones are most logical as commercial 
  products, and what interfaces should be standardized to 
  enable open source and commercial products to interoperate.  

Cheers,
-- Steve Waterbury
   NASA/Goddard Space Flight Center.

   oo _\o
\/\ \
  /
 oo _
"Sometimes you're the windshield; sometimes you're the bug."
- Knopfler

Stephen C. Waterbury   Component Technologies
Code 562, NASA/GSFC  and Radiation Effects Branch
Greenbelt, MD 20771   Engineering Web/Database Specialist
Tel: 301-286-7557  FAX:  301-286-1695
WWW:  http://misspiggy.gsfc.nasa.gov/people/waterbug.html
_

___
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )

[Zope] Need some help with installing ZPatterns

[Steve Waterbury]

I'm a newbie.  Have successfully installed the precompiled Zope 
2.2.2 on Solaris 2.6, running with apache 1.3.14 via fastcgi.  
Now trying to install ZPatterns-0-4-3b2.  Untarred it into the 
zope dirs, so now its source is in zope/lib/python/Products/ZPatterns 

Following the instructions in README.txt, I looked for a 
Makefile.pre.in ... it wasn't included, so I looked around in 
the zope distribution and found one in /lib/python/Shared/DC/xml/pyexpat 
-- it claims to be "Universal Unix Makefile for Python extensions", 
and it says it works with Python 1.5 or newer:

# Build *and install* the basic Python 1.5 distribution.  See the
# Python README for instructions.  (This version of Makefile.pre.in
# only withs with Python 1.5, alpha 3 or newer.)
   ^ (sic -- is that a Python idiom?  :^)

... so I figured it might work, but when I try 
"make -f Makefile.pre.in boot", I get the following:

rm -f *.o *~
rm -f *.a tags TAGS config.c Makefile.pre python sedscript
rm -f *.so *.sl so_locations
VERSION=`python -c "import sys; print sys.version[:3]"`; \
installdir=`python -c "import sys; print sys.prefix"`; \
exec_installdir=`python -c "import sys; print sys.exec_prefix"`; \
make -f ./Makefile.pre.in VPATH=. srcdir=. \
VERSION=$VERSION \
installdir=$installdir \
exec_installdir=$exec_installdir \
Makefile
make: Fatal error: Don't know how to make target 
`/vol01/software/zope/lib/python1.5/config/Makefile'
Current working directory /vol01/software/zope/lib/python/Products/ZPatterns
*** Error code 1
make: Fatal error: Command failed for target `boot'

**

What blockheaded thing am I doing?  

TIA!
-- Steve.

   oo _\o
\/\ \
  /
 oo _
"Sometimes you're the windshield; sometimes you're the bug."
- Knopfler

Stephen C. Waterbury   Component Technologies
Code 562, NASA/GSFC  and Radiation Effects Branch
Greenbelt, MD 20771   Engineering Web/Database Specialist
Tel: 301-286-7557  FAX:  301-286-1695
WWW:  http://misspiggy.gsfc.nasa.gov/people/waterbug.html
_

___
Zope maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope-dev )