Welcome back to the Year of Code 2025 series! For August, I built a minimalist and fun Console Task App that allows users to add,…
1 CommentXojo Programming Blog Posts
Deploying Xojo web applications offers developers flexible pathways to production. For devs prioritizing minimal infrastructure management, Xojo Cloud provides a fully-managed solution with automatic scaling, SSL, and…
Comments closedToday’s software landscape is constantly evolving and so are the costs associated with building and maintaining great products. We’ve worked hard to absorb rising costs…
Comments closedJuly’s Year of Code theme is charting. Charting uses the DesktopChart, WebChart or MobileChart controls to make your data stand out with visualizations like Bar, Bubble, Pie, Scatter charts and more.
For this project, I created a small iPhone app to track my expenses – something I personally needed. While it’s designed for tracking holiday and travel spending, it works just as well for managing general monthly expenses.
Comments closed
Xojo 2025r2 has just been released—time for an update to the Android Design Extensions 4.0, which are compatible with all Xojo 2025r2+ versions. With the…
Comments closedUsually, you only need to manage one Apple Developer Account when publishing your macOS or iOS apps. However, as many Xojo users have pointed out, there are situations where you need to work with multiple Apple Developer Accounts – perhaps you are publishing macOS apps for different companies (with different Team IDs). So, how do you handle this using the App Specific Password setup introduced in Xojo 2025r1?
Comments closedIf you’re building rich, maintainable and scalable user interfaces on Windows, XAML is a great choice. Its clean, declarative syntax and solid separation between design…
Comments closedFeaturing WebStyle state support for creating more polished user interfaces, enhanced event handling capabilities, and a collection of bug fixes and utility improvements, 2025r2 continues…
Comments closedUntil now, the only way to work with named iOSLayoutConstraint instances was by assigning a name in the Inspector Panel. This allowed you to reference them later in code, for example, to deactivate, reactivate, or remove them from a MobileScreen or MobileUIControl. Very handy!
But what about iOSLayoutConstraint instances created in code? Starting with Xojo 2025r2, that’s been improved! Keep reading to learn how.