Re: Visual Scripting component (maybe flowcharting)
From: Wagner R. Landgraf (wagner_at_automa.com.br)
Date: 06/04/04
- Next message: Nils Haeck: "Re: Visual Scripting component (maybe flowcharting)"
- Previous message: Nils Haeck: "Re: Visual Scripting component (maybe flowcharting)"
- In reply to: Jacob Thurman: "Re: Visual Scripting component (maybe flowcharting)"
- Next in thread: John Jacobson: "Re: Visual Scripting component (maybe flowcharting)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 4 Jun 2004 16:49:18 -0300
You approach is different for the one described by John (the newsgroup +
clock example). That was my fear: very wide of applications, specially when
you talk about diagramming scripts. Your idea seems to me more like a
sequence of actions, while his idea is more like designing a state chart
where properties go from one block to another.
I'm going to think about it, I'm very interested in building this kind of
tool since we have both worlds here (scripting and diagramming), all we need
to do is join them. I still don't know if there are many users interested in
it, and also if there are different ideas from the ones exposed here. Will
continue thinking, and I appreciate any extra comments and suggestions
anyone might have.
-- Kind regards, Wagner R. Landgraf Automa Consultoria & Informática Ltda. TMS Technology Partner wagner@automa.com.br "Jacob Thurman" <jacob@delphi-expert.com> escreveu na mensagem news:40c0b062$1@newsgroups.borland.com... > > TMS Software has also Diagram Studio, which is a tool to build diagrams > and, > > of course, flowcharts. > > > > We've been thinking about building an integration between both Scripter > > Studio and Diagram Studio, in order to provide a powerful tool for visual > > scripting. We would be very glad to hear from you about this tool, what do > > you expect and what would be the features in this new tool. > > The TMS diagramming components are actually very high on the list of > components to use if I have to build this myself. If you already had that > capability, I would probably already have bought it. The question at this > point is how long it would take you to have it ready. :) > > What I would like to see is the ability for an end user to design a script > visually, and have the resulting script be serializable. > > From a technical standpoint, it would seem like the developer would have to > supply actions to the script as things that user can actually do. These > could be TAction descendants, or just any class implementing IScriptAction > (I perfer the interface approach, personally). There would also be > decisions that would have to be made, perhaps the same pattern could work. > Basically, the trick here is how the script interacts with the host > application, aka how the host application is exposed through the script. > > Another issue would be how the diagram component would interact with the > script. Going from a script to a diagram should be a piece of cake: > MyDiagram.LoadScript(MyScript). It would also be ideal if you could do > MyDiagram.GetScriptObject: TScriptObject as well, although I can see a lot > of potential difficulty in that. > > Just some random thoughts.... > -- > Jacob Thurman > Creator of Castalia - The ultimate Delphi Productivity Suite. > http://www.delphi-expert.com/ > Super-Smart Syntax Highlighting > Fast, powerful code templates > Code Navigation Facilities you've only dreamed of > Automated Refactoring > Inline variable declaration > On-the fly syntax checking > >
- Next message: Nils Haeck: "Re: Visual Scripting component (maybe flowcharting)"
- Previous message: Nils Haeck: "Re: Visual Scripting component (maybe flowcharting)"
- In reply to: Jacob Thurman: "Re: Visual Scripting component (maybe flowcharting)"
- Next in thread: John Jacobson: "Re: Visual Scripting component (maybe flowcharting)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|