This project is read-only.

Addin Studio

1st Iteration

  • Create a design surface to generate UI element shells based on selections driven by a PropertyGrid. These types would be importable into the generic addin framework using ComponentModel.Composition. In other works, the addin studio would generate a DLL that would be dropped into the same directory as the generic addin framework. When the generic addin framework loads it will create a UI host with the imported user control. User control functionality will still be manually developed.

2nd Iteration

  • Introduce a work-flow system to addin studio. The user would use the design surface to design a UI element along with Buttons, TextBoxes, etc. UI element members (Methods, Fields, Properties) would be generated from the work-flow. The work-flow would consist of dropping in functionality exposed by the SolidWorks Interop types. See PowerWF for the idea.

References:
http://msmvps.com/blogs/theproblemsolver/archive/2009/12/23/rehosting-the-workflow-designer-in-wf4.aspx
http://blogs.msdn.com/b/cathyk/archive/2009/11/05/implementing-a-custom-expression-editor.aspx
http://msdn.microsoft.com/en-us/magazine/cc163504.aspx
http://blogs.msdn.com/b/endpoint/archive/2009/05/29/a-tour-on-the-wf4-activity-palette.aspx
http://blogs.msdn.com/b/mwinkle/archive/tags/activities/
http://blogs.msdn.com/b/flow/archive/2010/01/24/lights-camera-activities-windows-workflow-foundation-s-activity-model.aspx
http://blogs.msdn.com/b/tilovell/
http://mstecharchitect.blogspot.com/2010/02/wf-40-custom-activity-designer.html

studio.jpg

Last edited Jun 24, 2010 at 1:34 PM by fixitchris, version 10

Comments

No comments yet.