I’m reminded of the WWDC where attendees complained about Copland’s lack of symmetric multiprocessing. Gil Amelio retook the stage to announce that they would add that. Given Copland’s state at the time (when supposedly mere months from shipping), this was taken as a bad joke. I wonder whether Geoff is engaging in similar buzzword- compliance. Anyway, I’m not holding my breath.
1 Like
Kind of disapointing that after many years listening to geof most people cant understand the “Im technically not lying” languaje…
+
=
It is a huge undertaking that will take many years. We havent started yet but as we have plans to do it we can say that xojo almost has preemptive threading for marketing.
Looks like this is the next “Buy now, we almost have android ready.”
3 Likes
I expect it would largely be things supported in Xojo Script.
- Karen
Christians comments on the thread on TOF are probably close to the truth
1 Like
Did. Wasn’t.
IOS still isn’t, but I was making do, patching up all much missing functionality with the iOSLib
I have a huge beef about the pricing compared to other single target licences (4 times the price of a Lite) , the lack of any upgrade discount (newbies pay the same as anyone who has had multiple previous licences, including Pro) , and the blackmail that happens due to Apple demanding newer SDK this month. The fact that we cant just say ‘use SDK version X’ as a preference is a disgrace.
This what I DO NOT understand about people wanting to build iOS… .we all know Xojo isn’t up to the task and probably never will be, and its what $300 for “Xojo for iOS”?
Swift is FREE, no hoops to jump thru when macOS is updated, no worries about “newest SDK” as it happens automatically… Sure the langague is different, but NOT THAT different… I made a full transition from Xojo to Swift years ago, and have never looked back.
So when I hear complaints about “Xojo for iOS”, I have to just laugh and shake my head
2 Likes
It is though. Tried it, hate it. Life is too short to start again.
2 Likes
Well I am 68 years old (and I bet that is alot older than you)… and I found the learning curve to be really short, and while there were/are frustrations, they pale in comparision the the hacks and workarounds and 3rd party add-ons required to make Xojo even semi-viable these days.
So, if you wish to spent $300 a year to “support” Xojo, and deal with the issues inherent in that decision, thats on you…
so no framework classes like graphics, folder item, etc
just the primitives
unfortunately that makes it not quite so useful
1 Like
I use B4i, WAY more out of the box than xojo and it is only $119 for 2 years and it is BASIC like.
2 Likes
Well I am 68 years old
I’m 65. You old codger! I imagine that if I did nothing but try for it, I could get there in a few months.
But I’m constantly supporting commercial apps in Xojo among lots of other things that eat time. I’d need to get off the hamster wheel first. Not sure I can do that.
I use B4i,
Now that (B4A) I did make quick headway with a few years back. Could still be an option.
It is not basic like. It is basic. And that’s the nice part. And you have also B4A and B4J with options for Android, Desktop and the Web. Desktop on all platforms by the way.
The Idea behind is beautiful and the maker was doing a real good job with a low level of bugs inside of the code. And with Chuzpa to dix bugs when ever somebody finds a bug. This he sees as his policy and makes an everyday job.
And yes, the best is: it’s all sharable code. Even UI code can be shared. B4x helps. And even for firmware you can still use b4r.
I would be happy to see Xojo bringing such system. For example on base of kotlin. They could. But not like they try now. That will not work.
1 Like