#define private public - Claus Brod on stuff (October 2012)

topic end
<!--
   * Set TOPICTITLE = #define private public - Claus Brod on stuff (October 2012)
-->

<style type="text/css">
pre {background-color:#ffeecc;}
</style>

%TOC%

%STARTINCLUDE%
%INCLUDE{DefinePrivatePublic20121011ResolvConf}%
%INCLUDE{DefinePrivatePublic20121011Mediathek}%
%STOPINCLUDE%

Previous month: Click [[DefinePrivatePublic201202][here]].



<!--
   * ELS 2009:
      * Web applications in Lisp (vs. Java)
      * Other presentations
      * Reini Urban
   * Intel chipset issues: http ://cocreateusers.org/forum/showthread.php?t=7291; relate to
     DefinePrivatePublic20090715NiceAndSlow
   * "This application has requested the Runtime to terminate it in an unusual way", R6034 -
     http ://twiki.ptcnet.ptc.com/Users/Claus/BlogJanuary2007#25_January_2007
   * Single selection to multiple selection "converter"
   * http ://www.dumpanalysis.org/blog/index.php/2007/05/20/custom-postmortem-debuggers-on-vista/
   * http ://support.microsoft.com/kb/931673
   * http: //www.microsoft.com/downloads/details.aspx?FamilyID=E089CA41-6A87-40C8-BF69-28AC08570B7E&displaylang=en (user-mode dumper)
   * http ://blogs.technet.com/askperf/archive/2007/06/15/capturing-application-crash-dumps.aspx

   * Common Lisp at CoCreate:
      * sd-defdialog and how it implements a DSL
      * IKIT
      * Origins of our implementation
      * Using OSMPE to play with our Lisp implementation

(defmacro with-muted-function(function &rest body)
  (let ((old-function (gensym)))
    `(let ((,old-function (symbol-function ',function)))
       (unwind-protect
         (progn
           (setf (symbol-function ',function) #'(lambda(&rest args) t))
           ,@body)
         (setf (symbol-function ',function) ,old-function)))))


Dialogs and action routines are special beasts
   * Part 4
      * ME10: Commands (= action routines), interrupt functions (interrupt ARs), arithmetic functions
      * defaction produces an state-machine interpreter
        which prompts for/checks/accepts user input
      * Terminate actions, interrupt actions, subactions
      * http ://twiki.ptcnet.ptc.com/Programming/WritingActionRoutinesAndPersonalityActionRoutines
      * When eval detects an AR property, it will trigger
        the state machine right away
      * Curiosity: =complete= is an AR!
      * Example from DefinePrivatePublic20090620CommonLispInCoCreateModeling
      * http ://www.hpl.hp.com/hpjournal/95oct/oct95a7.htm
      * Services provided by ARs
      * Qualified/unqualified usage of ARs
   * Part 5:
      * Terminology:
         * Command
         * Action routine
         * Dialog
         * Official/IKIT term for AR? Command?
      * sd-defdialog builds on defaction
      * Action routines vs. dialogs vs. Lisp functions -
        rules of thumb:
         * If it's in sd-online-reference, it's a dialog
         * If it's in the old command reference, it may (still) be an action routine
         * If the name has underscores, it's an AR or dialog (or a keyword for an AR)
         * If the name has dashes, it's a Lisp function or macro
   * Part 6
      * ARs symbols carry special flags/properties
      * http ://twiki.ptcnet.ptc.com/Users/Claus/ActionRoutineImplementationDetails
      * With this background, we can now explain why ARs behave the way they do
      * "Funny differences" between ARs and Lisp functions:
         * =print= errors out, =extrude= doesn't
         * =(print)= doesn't prompt
         * =(print extrude)=
      * TBD: Practical uses for this?
        * Know functions from ARs
        * Important for dialog programmers (sd-call-cmds required or not?)
      * Future blog posts: Dialogs and what they provide on top of ARs

Early history of <nop>SolidDesigner

ME10 spawned off ME30, which was our first 3D CAD modeling program.
Impressive as it was for its time, we knew that ME30 wouldn't scale forever, as
it was based on an older technology stack. And thus, the <nop>SolidDesigner
project was born in the late 80s. (These days, the product is known as <nop>CoCreate Modeling.)

ME10's built-in macro language was a wildly successful feature.
Users and CAD administrators counted on it to configure their local installation,
and partners wrote macro-based extensions to add new functionality - a software
ecosystem evolved.

See CoCreateHistory

Kanten abtasten und diskretisiert in Excel-Datei schreiben (siehe Email von Mario Wutte)

Excel lesen und schreiben via Lisp/COM

Ankuendigung Scheibenkleister:
   * Warum so lange gezoegert?
      * rechtliche Fragen
      * Konvertierung
      * altfraenkisch, altklug
   * Copyright klaeren
   * kapitelweise veroeffentlichen, eventuell mit Appetithappen
   * in Foren ankuendigen

-->
to top
End of topic
Skip to action links | Back to top
You are here: Blog > DefinePrivatePublic201210

r1.3 - 11 Oct 2012 - 18:09 - ClausBrod to top
Blog