Beta Builds of the Xion Plugin SDK. These are builds that are not quite ready for Release, but need feedback and bug submissions in order to move it to Release Status
WARNING: This is a Beta Build of the SDK. That means that Interfaces may changes, variables may get renamed, etc. It is also possible it has bugs that are NEW! If you are looking for stability, please don't expect this build of the SDK to be perfectly stable. It may have issues. If on the other hand you are happy to try this SDK build out and post any bugs back in this thread, then please do!
Xion Version Compatibility This version of the SDK requires Xion version 1.0.83 and above in order to run.
Changelist:
First Release!
This is the First Release of the SDK. Due to some cleanup changes, Components built with the SDK, WILL NOT WORK ON Xion 1.0.82. You need to download and install the latest Beta version 1.0.83 for this to work. If you don't, Xion 1.0.82 will crash when trying to perform certain operations. This crash has been fixed in 1.0.83 so that if further core updates cause a version change, Xion won't crash, but instead show which Component is causing problems.
I'm not looking for new feature requests at this stage. Use this Thread to ask questions if you have problems compiling the SDK. The SDK was written using Microsoft Visual Studio 2003, in C++, using pure Win32 API calls. I'm fairly confident that it will work on Visual Studio 2005. It may work on Visual Studio 6.0, but I'm yet to test it. It's also possible that it will compile with other IDEs and Compilers/Linkers such as the GNU toolchain.
I've included a single Example at this stage. The Example is basically a code complete copy of the SimpleVis component that is included with Xion.
Each Component can talk to other Components and the Xion Core using the XionCompRecvMsg() and XionCompSendMsg() functions. For a list of pre-defined Messages, Identifiers, etc See MessageDefines.h
Feel free to ask any questions about how things work and I'll do my best to explain them.
I'm also happy to post example source code if you want to know how to do something that another of the built in Components does (to an extent!).
Don't expect to receive answers on basic programming questions. You should try Google first as there is a plethora of information out there! This isn't a 'Learn how to Program' thread!
This is cool that there is an sdk, lets say i make something really useful, does it get tracked and maybe added as a xion feature? or basically, is it possible to get into developing stuff for xion(seeing as it kicks so much ass)
I am new, i didnt search but this post is not about the above question.
FuzzYspo0N Wrote:This is cool that there is an sdk, lets say i make something really useful, does it get tracked and maybe added as a xion feature? or basically, is it possible to get into developing stuff for xion(seeing as it kicks so much ass)
I am new, i didnt search but this post is not about the above question.
Great to see an sdk, lol
As explained the SDK uses C++/win32. So if you know how to program you can make things
Components are separate pieces of code that are compiled. If you have a simple feature, its probably best to request it in the feature request thread.
Hi Cliff,
just ran through my first look at the vis example code last night.Being stubborn, I ran it through 2008 first. (having reformatted recently also, it was what I had installed) It's very exciting to me and I'll reinstall 2005 over the weekend. I'm going through my c++ tutorials now, (from 1st to last) and will leave you alone about that part, just want to thank you for such a kick ass program as it has provided the impetus to crack the books and do it right, from the start, and worry 'bout making a vis in good time, not tommorrow.I am exploring the available libraries and resources also tho, hehe.
xonenine
In fact, that's the only real pertinent question that just popped into my head just now.Is there a favorite site or link you have offhand for libraries, source code examples, etc.I've used similar places for html, java, applets and such, and figure you might know a good one.
thanks again
actually i was just about to look what apis are avaliable and what can be done. toy around andso... ultimately i thought about making a "better library" plugin of some sort
