Don't really vote but speak of...
Users can be listened if they continuously list their problems to the
The aim is only to be able to do physical or mechanical analysis as simpler
as possible and to avoid complicate import-export functions.
"Mark Mossberg" a écrit dans le message de
news: %Ndme.2961$ firstname.lastname@example.org...
We need bicycle, cars, trucks...
We use Notepad, Framemaker, Word and we can copy and paste, perhaps we could
have such middle and high level softwares... with copy and paste!
"Cliff" a écrit dans le message de news:
Well, Abaqus does pretty well at interoperating using Python. SW knows
Python via Cosmic Blobs. SRAC could have had Cosmos/M working in a
similar manner. Don't get your hopes up that Abaqus will run inside SW
however. Abaqus needs a preprocesser to create the mesh. And it
typically needs a pretty decent system to run the solver. Given that
most SW users are going to try to analyze everything but the kitchen
sink putting Abaqus into SW would leave a lot of people underimpressed.
Microsoft and Dassault Systèmes to Align XML formats
3D XML to support and extend Microsoft?s XAML format
Redmond, Wash., USA, and Paris, France - April 14, 2005 - Microsoft
Corp. and Dassault Systèmes (DS) (Nasdaq: DASTY; Euronext Paris: #13065,
DSY.PA) today announced that, as part of their strategic alliance and
commitment to jointly delivering value to their customers, they will
collaborate to support Microsoft?s Extensible Application Markup Language
(XAML) format in Dassault Systèmes? 3D Extensible Markup Language (XML)
format. XAML is the format for "Avalon," the code name of the next
presentation subsystem for the Microsoft® Windows® operating system.
"Avalon" provides the foundation for building applications and
high-fidelity experiences, blending together user interfaces, documents and
media content while exploiting the full power of users? computers. "Avalon"
provides native support for declarative, markup-based programming with XAML,
making it simpler to build, customize and enrich Windows-based applications.
3D XML is a universal, lightweight XML-based format that enables users
to capture and share live, accurate 3D data quickly and easily. Dassault
Systèmes will use the 3D XML format in its entire line of products: CATIA,
DELMIA, ENOVIA, SMARTEAM, SolidWorks, and Spatial.
Compatibility between 3D XML and XAML will enable users of 3D
solutions to view, modify and customize 3D objects in an environment of
unmatched openness and take advantage of this 3D experience in any
"3D XML is a universal, lightweight XML-based format that enables users to
capture and share live, accurate 3D data quickly and easily" Material data
also exist under xml (matxml). So xml Geometry, xml material behavior, xml
boundary conditions, xml loads ... = xml FE
Not a stretch for the imagination really as ABAQUS uses text "input
decks" to run analyses. Input decks contain the option cards that
describe the mesh, BC's, loads, materials etc. Converting this to some
form of XML would IMHO be of questionable value. I'd rather see what
Dassault do in terms of pre- and post-processing.
ABAQUS is a VERY different beast if all you've ever done is linear
statics analysis. There are s**tloads of options, tweaks and analysis
types (they don't send you 14 manuals for nothing...).
Long as I can have a pre-processor as good as I-DEAS (or Hypermesh)
inside SW, I'll be a happy man (as well as 1xseat of I-DEAS maintenance
better off) :-o