With API 2.0, Xojo has taken the opportunity to transition to more consistent APIs, modernize frameworks when we can and generally prepare for the future so that you can continue to use Xojo to make great apps for a long time. We are excited about the future of Xojo and can’t wait to see the apps you create!
Comments closed39 search results for "API 2.0"
Xojo 2020 Release 2 includes API 2.0 for iOS which has many, many changes and new features. Features include MobileMoviePlayer, MobileMapViewer, iOS Notifications …
Comments closedWe realized we misnamed a few APIs in the existing frameworks. Rather than live with those forever, we decided it made sense to change them now. Being consistent across the API surface is extremely important for both learning and productivity.
Comments closedXojo has built in database classes for accessing SQLite, Postgres, MySQL, Microsoft SQL Server, Oracle & ODBC. API 2.0 sets the bind types for you and that means you can switch engines by just changing the Super of your database class and updating the connection settings.
Comments closedRecently I needed to update an old Web project that used a Microsoft SQL Server Database as its data source. This application is running as a service on a Windows machine and is for internal use only. I decided when updating the project, I would also update to API 2.0 database commands using Xojo 2019 R3.2 and I would like to share some of those code changes with you.
Comments closedYou might be assuming you absolutely must upgrade to API 2.0 right now, but that’s not the case. We have designed it so that you have tremendous flexibility in terms of what and when and even if you move to API 2.0.
Comments closed2019r2 has many changes related to API 2.0. Most of your projects should open and run without any changes. You can then switch code to API 2.0 when you want (or not at all — it’s up to you).
Comments closedAre there bumps in the road? Sure! Are they worth barreling into at full speed? Oh yeah! Bring it on Web 2.0, I’m ready!
Comments closedOne of the big changes in Web Framework 2.0 is that web styles are no longer the primary means of styling controls. Instead themes are used to provide a single, consistent look and feel across the entire application. We made this change because dealing with individual styles became more complex and unwieldy as projects grew bigger. Themes simplify this dramatically.
Comments closedWith the release of Xojo 2020r1 comes the new 2.0 version of our web framework. While the way in which you build web applications hasn’t fundamentally changed, this new version is a from-the-ground-up rewrite and utilizes API 2.0 for greatly improved consistency. This means that the conversion process is going to be time-consuming, but will be well worth the effort as web applications built upon Web Framework 2.0 will be more robust, handle more users, be more responsive and have a far more modern look and feel.
Comments closedCan't find what you're looking for? Try refining your search: