Yesterday I talked about Xojo Desktop 2.0 and how GraffitiSuite fits in to that picture. At the time I was really frustrated and didn’t know how I was going to proceed. Thanks to that post, however, some of my users reached out to offer their support and discuss. At the end of these discussions, I had a path forward.
Continue reading →We’ve all known this was coming for a while. Today, with the release of Xojo 2021R3, it became a reality. Xojo has created a new set of controls for Desktop to replace the legacy controls which will modernize the API for the user interface as well as bring the APIs for Desktop, Web, and Mobile closer together.
Continue reading →One of the most commonly asked questions we’re getting right now is
Continue reading →What will GraffitiSuite for Xojo Web 2.0 look like?
They did it! Xojo reverted the event renaming in API 2.0 for Release 2019R2.1!
Continue reading →In Part 1 we covered the history of animating UI effects in Xojo. Part 2 we dug in to linear interpolation. Part 3 saw the addition of support for concurrent animations and color changes. In Part 4 we’ll cover easing, which can make the most drab User Interface interactions beautiful.
Continue reading →In Part 1 we covered the basic history of animating in Xojo using pre-calculated chunks to modify the width of our component. In Part 2 we went a bit further by using linear interpolation(lerp) to calculate our current width at each step of the animation process, and setup for concurrent animation.
In this part we’ll be covering a few different things, chiefly concurrent animations. But that’s not all, as I’ve added a lerpColor function to show you how to animate color changes.
Continue reading →Continuing with what we previously learned, this version introduces the use of linear interpolation to calculate the current stage of the animation at each step, plus switching to a Dictionary object for variable storage to setup for future parts in this series.
Continue reading →Background
Today I had the need to develop a method by which GraffitiSuite users could determine what version of GraffitiSuite a particular product was taken from. Normally I go through the rigmarole of telling them to follow these steps:
- Open the demo project
- Expand the App object
- Expand the Notes section
- Select “ChangeLog”
- The top line is the version
But a customer pointed out that this can be a fairly big ask when GraffitiSuite is so expansive. Coupled with that, as I thought more about it, once you take a product from the demo and add it to your project you really have no way of discerning what version that particular product is! So I needed something better. Something that stayed with each product, regardless of what project it was in. Enter IDE Scripting.
My plan was to add a Constant or Note for each part of GraffitiSuite that can be easily updated. Browsing through the documentation I saw a lot of listed caveats.