![]() ![]() I am on the other hand sad that Xojo has gone in the direction it has, and to be honest I think the departure of Norman was probably the nail in the coffin for both Xojo and its reputation. I don’t regret moving away from Xojo in the least, I have a business to run and making money for both myself and my family is priority No. Luckily I only have one legacy Xojo web 1 app that is still in use by one of my customers but it only has a limited lifespan now of a couple more years so the 2015 version of Xojo that I used to write it is ample to maintain it and make any changes required in the short term. I can safely say I’m in a much happier place now than I was when I was struggling with some of the errors I was encountering in Xojo. There is a very active and friendly forum with people always willing to help (very much like here).īy continuing to use the Chilkat plugins (modules) which are useable in so many languages, I have so far not come up against any show stoppers. Since moving over to Purebasic I have had very few problems porting my software and the speed improvements in some cases have been amazing. The next version of Purebasic will actually output straight C code and enable inline C, it will still need the IDE to be run on the required platform but will open up almost every possible architecture bringing the mobile platforms into play as well. For cross platform you do need to run the IDE and compile on each individual platform but for me that is not a problem as all my customers are on Windows. Purebasic is cross platform and currently produces ASM output which is then compiled using fasm. Out of the 14 products / tools I had written over the last 8 years for a couple of my customers I have rewritten 8 of them in Purebasic. ![]() I found the feedback system as about much use as a chocolate teapot with the majority of problems either being marked as unreproducible or that were just being plainly ignored altogether. I was blown away by the lack of functionality in the released version of Web 2 and the amount of bugs that were consistantly not getting fixed release after release. ![]() I dropped Xojo as a product over 18 months ago and didn’t renew my license nor did I renew any of my third party product licenses except for the Chilkat plugins I was using (this was because I used them in the language I switched to). I’ve been following most of the threads on this forum for quite a while now and I can only but agree with a lot of the criticism regarding the running of Xojo as a company rather than the functionality of the product. When we must drop into platform-specific code, even though it’s rare, we still need to know both AppKit and UIKit. This might reduce the learning curve for both types of devices, but it is limited to those two types of devices only. The advantages and disadvantages of approach 2Ĭode can target both mobile and desktop systems at the same time mostly using one framework. The only shared code for all platforms is for the GUI (although it may still require device-specific tweaks). The reader must figure out how to add mobile coding with UIKit later and add it with platform-specific code. Only AppKit must be covered, but the reader learns more about macOS-specific coding, which is covered less than UIKit in most tutorials. The advantages and disadvantages of approach 1: For Catalyst, most of the calls outside of SwiftUI are via Catalyst, which is more iOS-like.īefore I start, I need to know which approach readers would be more interested in: (1) directly working on macOS only (outside of SwiftUI) with AppKit, or (2’ writing all of their apps for both the iPad and Mac with more iOS-like code, which reduces the learning curve a bit but prevents is limited to those two types of devices only. For macOS apps using SwiftUI, any need to add platform-specific code beyond SwiftUI would require AppCode calls. I could concentrate on the desktop, but the approach would be much different depending upon whether I use SwiftUI vs. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |