We're using cookies to ensure you get the best experience on our website. More info
Understood
@virtualeRegistered January 24, 2008Active 14 years, 10 months ago
3 Replies made

You are right, this architecture will bring us many possibilities, if someone wants to debug the graphics, the sound, even on real time execution, memory extraction, etc… great plugins *libraries will bring a great VIDE.

Hi,
Just to let you know I tried to figure out how to do the less work, but finally I decided to start from scratch.
I will use C# and .NET Framework to made the code as easy as possible. The VIDE will work as follows:
1. It will take a “environment” descriptor written in XML to tell the application what kind of resources it should read and which plugins will be loaded. So VIDE will be a plugin/resource manager…
2. The application will instance the plugin
3. The plugin will have its own descriptor in XML to know the messages to send or receive (read below)
4. Both App and plugin will share a common procedure called “control” that will be the communication pipeline
5. According to their descriptors, messages will be available to interact even with other plugins
6. Each plugin knows how to behave so could be resource compilers, displays, morphers, and even virtual processors, memories and IO devices to attach an emulator if desired

The following diagram explains this idea:

Finally, all plugins and application will share a common package called VIDE with a toolkit of functions to share.
Thats my idea. 😀 Let me know your comments.

Thank you guys for all your support. All ideas are welcome. This new VIDE version as Chris comments should mix the best of both worlds, the programming (meaning source code) and media resources (meaning images, music and so on). Developing TRON, I faced many problems with ViDE, starting with the gcc compiler support, the native support for many external tools and even some bugs (like the 64k restriction in text editor).
Finally, ViDE for TRON meant just a MAP, CHARSET exporter instead of a unified environment for VB development. It compiles using a BAT file instead of using ViDE, Imagine that!
The goal would be to build from scratch a new version even as open source or a VS template… Im not sure, but definitely it needs “reengineering” 😀
Hoping to read as many ideas as possible, have a great day.
Alberto