A full control that uses all the features of the WebSDK and heavelly commented on why that feature is used.
Another tool that I use, is making their controls open source in their own SDK, maybe Xojo could port one or more of the internal controls to be written on the SDK and made it open source, this way you have a good example, and you can inprove the SDK
Maybe another Feature Request to improve the documentation also
Great unraveled the mystery! Well if they don’t contain sensitive data I’d say you can make them public if you’d like so we can vote/ test them etc.
If you mean working as in “run” then yes sure it runs.
But Web control example that has no UI and does nothing at all is not even close to useful. Web 1 at least had example how to do control displaying its UI, talking to its Java script etc etc.
Example that does nothing is just wasting everyone’s time.
The Gravatar example is a visual control. We’ll add more though.
It would be great having a sample application that gives beginners a ride across the gamut of Web 2 capabilities. Code snippets can be hard to understand for beginners.
Björn is one of the oldest and most experienced Xojo users. He has been designing powerful Xojo/Realbasic plugins for a very long time.
If he finds the webSdk documentation and examples unconvincing, you really have to take his feelings into account I think, because 99.99% of Xojo users are less experienced and competent, and will therefore have a much harder time than he did.
The Gravatar example works here:
Another example can be downloaded from:
this is an updated ChartJS library (ver 3.x, Xojo uses 2.x)
Anybody willing to help to improve the examples is invited to comment in this Feature Request:
Add more WebSDK examples
Just adding my two cents here: I’m building a bigger Xojo Web app and find it generelly joyful to do so with Xojo. It helps me to get from Idea to Production in hours, not days or weeks.
However, there is a major downside to Xojo Web: most of the important components are buggy. I filed 8 bug reports over the course of only a few weeks, all of them confirmed (for a moment it felt like I was the only one using Xojo Web). Most of them are concerned with the WebListBox. It is the most important component for me but barely useable beyond the most simple use cases. So I purchased Graffitisuite, which adds another $399/year to my bill - just for a working Grid.
Then there are the WebPanel, WebPagination and WebCharts. All of them are buggy, as soon as I want to use them seriously. Sometimes there are workarounds, sometimes there aren’t, which is very bad when you are in the middle of a serious project and have no way to fix:
While I am still generally happy, these issues throw a shadow over Xojo Web, a product that is costly for exactly one reason: to provide a smooth experience for developers who don’t want to struggle with HTML, CSS, JavaScript, React, Webpack, Node.js, Webservices etc. and so on.
I hope that @Ricardo_Cruz will speed things up at Xojo Web and will fix not only the low-hanging fruits but all those dealbreakers which drive people away from Xojo Web.
I guess this is case #66052
Can you try: this WebSDK ChartJS
Amazing! I just tried that project and noticed it already uses Chart.js 3.x, which is great. You probably saved my day @AlbertoD . Is this your project?
@Ricardo_Cruz created the project, I just added a couple of things.
I want to learn WebSDK to do things like that but I haven’t looked into it (no time).
Well then, thank you @Ricardo_Cruz !
Yup. We need to clone @Ricardo_Cruz. He is an exterminator extraordinaire in a target rich environment.