Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
Topic closed
This should be a challenge for any experienced programmers willing to participate.
With this complete, it will be possible to port PlayerIOClient to multiple languages. (Woo, cross-platform bots without dependencies!)
I've managed to call the API from PHP, and Python, and create a working bot without PlayerIOClient in C#.
Years ago, I've went through the ugly decompiled PlayerIOClient Message class code and somehow made it work.
This was accomplished years ago, with the release of EEDecode.
However, considering it uses goto heavily, it's messy and not very fun to implement at all.
Which is why I'm issuing this as a fun and potentially productive challenge: creating a working Message serializer and/or deserializer without goto statements.
Feel free to participate and leave replies in here with code snippets.
*u stinky*
Offline
I'd really like to have the Python API in hand, because I can handle the language to the perfection. I've been just too lazy to do these kind of projects. I could just learn C# anyways, so whatever.
Offline
I'd really like to have the Python API in hand, because I can handle the language to the perfection. I could just learn C# anyways, so whatever.
Here you go. Python source.
It's not a full implementation, as noted above, it still needs a working Message serializer/deserializer.
Best of luck.
*u stinky*
Offline
^^ Because C# is too mainstream.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
We could just write it in C and bind it to all the different languages, rather than doing all that work to do a full port to every language.
Offline
We could just write it in C and bind it to all the different languages, rather than doing all that work to do a full port to every language.
Definitely. At this point, it would be very good to have a working implementation in any language.
*u stinky*
Offline
If you're just interested in using PlayerIO in a different language, and aren't worried about the dependencies, could you just run a C# playerio "server" and just have a thin python interface to interact with the local server?
Offline
If you're just interested in using PlayerIO in a different language, and aren't worried about the dependencies, could you just run a C# playerio "server" and just have a thin python interface to interact with the local server?
Mixing two languages just to add support to one for a server would be a complete mess up. The important thing is the client and a multi-language API instead, would not be a mess up.
Offline
If you're just interested in using PlayerIO in a different language, and aren't worried about the dependencies, could you just run a C# playerio "server" and just have a thin python interface to interact with the local server?
That's how my first midi bot worked and it was a horrible mess. From the end user's standpoint, it's a lot more headache than it's really worth.
Offline
Pages: 1
Topic closed
[ Started around 1732437006.2312 - Generated in 0.057 seconds, 13 queries executed - Memory usage: 1.5 MiB (Peak: 1.64 MiB) ]