During the initial development of XenApp Mobile Pack, certain choices were made for the status/error codes. This all made sense during that time but certain topics have come up since then which requires attention. Nothing serious, but rather more of an indication that things need to be better explained.
When something new is created, it is often difficult to capture its essence in words. If not that, then it is hard to know where to start. Sometimes it is much easier to create with the hope that the explanation will happen later.
Later is now. In the coming weeks we will be providing new documentation and samples. We are also providing our first videos for the SDK. This is a new business model for us and we are working hard to make sure that the SDK is accepted and used in businesses.
Today I am going to cover the SDK functional groups. The hope is that describing the functionality in groups will make it easier to understand what the API can do overall. The first stop is the documentation on the web. Please take a moment to look at the functional groups. This documentation page was only meant for C/C++ but the ideas could be mapped to COM and C# as well.
XAMA SDK documentation is now available online at http://www.citrixcloud.net/mobilesdk/index.html. The documentation was generated from the source code using doxygen. Because of this, the information is more up to date than typical SDK documents. Three interfaces are covered. Continue reading
Since we just announced XAMP and XAMA just a few days ago, and it also very close to the holidays, it is not expected that many people will get a chance to try these solutions before January.
However, to anticipate potential questions, there is a solution regardless of when the questions are asked.
First of all, there is a Citrix forum dedicated to the XAMA SDK. There has not yet been much traffic here yet but we have had a few questions. The forum is the place to go when you have an issue with getting the SDK to work. So far we have covered some of the issues that happen when you first start and also how to debug. Thanks go out to Jason Conger for being an early adopter. Just remember that we are instantly notified of any new request and do our best to answer the question within a day.
Another path is to use our direct email account. The group that worked on the Mobility Pack has a group email alias. This address is mobilitysdk (at) citrix.com. As usual, substitute “(at)” with @. I wrote it this way in the vain attempt to hide the email address from automated programs.
The email address is direct and instant and is directed to several people in Citrix. It probably comes down to preference whether you want to use the forum or email. Either way, you will get the help you need with the XAMA SDK.
When a developer first experiments with mobile phones and tablets, one of the first questions is how it can be debugged. With PCs it is fairly easy to start a debugger for a program since the environment is well established and there is plenty of screen space. With a phone, the space is very limited. On top of this, there is very limited input control. Using touch is very effective for mobile devices but not always that effective for debugging the applications than run on these devices. There has to be some kind of outside control to make this more effective.
There are some general strategies:
- Using tracing to log files
- Using tracing to remote consoles
- Interactive Debugging inside session
- Interactive Debugging in another session
The first version of the Citrix XenApp 6.5 Mobile Application (XAMA) SDK has been published on the Citrix web site as of December 17, 2011. In order to use the SDK, the XenApp server must have the Citrix XenApp 6.5 Mobility Pack (XAMP) installed first. The team has worked for around a year bringing this together. The overall goal is to make it easy for enterprise Windows developers write software that works well on mobile devices (phones and tablets).