There are many plans to enhance VPL with things we had to leave out due to time constraints. One of the most important ones is addressing cross node deployment (distributed diagrams, which the underlying diagram can support today).
What specific features/fixes/enhancements are you looking for?
thanx
g
It seems that the MSRS is a very powerful and attractive messaging system. I think that boiler plate code for things like timers, ports, messages, and handlers could perhaps be done in a graphical environmet that also allowed one to drill down to the code level. As I write this it sounds like I'm asking for a graphical MSRS environment to be part of Visual Studio.
Of course, i also have some ideas for improvements, so i'm posting it in this topic..
- Possiblity to draw Symbols,blocks,lines, rectangles, arrows in the diagram for comments (see below)
- editable connection lines, like splines in Vector-Graphics or like links in electrical-CAD.
- support of Standart Shortcuts like Ctrl+Scrollwheel for zooming; Alt+Scrollwheel,...
- Categories in the Service-Window, to get a better orientation
- Autoscrolling console - resizeable width for long messages!
- a "For loop" (althoug you can do it with recursion)
- a "Foreach-Loop" ("")
- Create Service-Objects, like "GenericMotor" dependently, like Data-Objects (->input "create")
- Bug: VPL always crashes if you want to edit Data-Connections of a Service which
was altered, especially if a Message-Body was altered in VisualStudio.
- And of course the possibility to reload/refresh Services..
In my opinion, the most interesting part in vpl is not to make it easy for beginners to program their robots, but to make
it easier understanding data-connections and -flows in big projects with a lot of people working on it!
I think it would be great if you'll develop VPL further in this direction.
One step would be to provide a better navigation between you main-diagram and created activities. For example with MSRS VPL1.5
you can't create a custom activity, and import it to a different project (unless you compile it as a service) - or did i miss st.h
?
So i would suggest to provide a Manager to import/export created activites, with the possiblity to edit them directly.
A further step would be to focus a little bit more on tutorials for writing Code in c# an embedding this code in
VPL as a service. Because you'll never be able to write all behaviours in VPL so we'll alwas depend on c#..
Also it would be great if there would be some additional tools, like i've mentioned s.th to draw boxes and underlay them in you
VPL diagram (like those in MS Visio). I mean, you've created a possibility to program by drawing boxes and lines, why relie
on that old fashiond way of text-comments, why shouldn't we take this progress to improve comments? ![]()
Also i would love it to be able to replace the standard-Service Symbol(this little gear-wheel)
by custom symbols.
Thanks for everything ![]()
regards, Andi
schedule.
- And of course the possibility to reload/refresh Services..
Please check out View --> Reload Services
Andreas