So what is on the plate for the plugin ? Well, it still need to be decided, So instead of waiting for feedback or try to invent the wheel, I was thinking "why can't I just share the plugin with others".
Now that is a thought.
I was always afraid that group work will be to demanding, but I think that if others can come up with ideas and make the plugin better than why not !
So what now?
I believe that the plugin can have two main source codes, one will be closed and manage by me, and one will be open and shared with others.
The main idea is to be able to control what will put into the closed source, while the open source can play a role of test platform for new ideas (this does not mean that it is unstable).
As I said, I'm sharing my thoughts here, so I have no time line or dead line, but at least there is the seed of the idea, and I hope I'll realize it in the near future.
Well, I was working on other staff in the background, but nothing was published.
One of the things I'm testing is a plugin that will send UDP messages from x-plane to external port.
If you ask yourselves why do you that, x-plane already implement that, my answer would be:
* I was not able to parse XP native UDP, so I'm trying my own solution (which was done by others too).
My aim is to allow others to fill in what Dataref they would like to send, and the plugin will do it for them, so no extra code is needed.
So, after much time of silence, I wrote quite a bit, but done nothing so far...
I hope to update this blog soon with more news and progress.