For Swift version I do not know.
For XCode, I have v 14.3.1; I downloaded it some weeks ago and no new version is available (no update is flaggingā¦).
You may talk about the version for a not yet released MacOSā¦
ummmmā¦ we are only at Swift 5.8.1 and Xcode 14.3.1
|
Correct, the linked video and code is for a future version of Swift/Xcode not yet released.
Also from the linked doc, macOS 14.0+ is needed and so on:
2 Likes
You have learned by now: The Xojo community is allergic to features that have not yet been released. We have learned over decades that these promises are never fulfilled, and if they are, then in a very different way. And with Xojo being the de factor leader in innovation, itās safe to assume Apple will be too. 
Thanks for sharing, interesting content.
1 Like
Yes, works with Xcode and Swift delivered with Sonoma, now in beta.
1 Like
Babylonian confusion grips the Xojo community:
https://forum.xojo.com/t/xaml-controls-on-mac-or-linux/76865
Lets just say I think they pooched this one based on whats been posted
Havenāt tried it myself
OLEControl ALREADY existed and its platform specific
Yet if I add it to a layout on macOS it does NOTHING
And the project compiles !
the XAML controls SHOULD behave the same
IF they dont then ick and Iād report the bug
EDITED : to add clarification I havenāt TRIED the DesktopXAMLControls at all
And that they should behave like OLEControl
2 Likes
A x-plat IDE that supposedly abstracts the developer form platform-specific details should handle this in a transparent way - Xojo fails, again.
1 Like
Some kind of auto immun disease?
https://forum.xojo.com/t/about-me-self/76933
Let me please ask a question. Why the hell somebody should need a XAML control? That sināt native at the end as far as I know. I mean I thought always that Xojos major goal isnāt to be a dotnet dude but a complete native clean solution or am I totally wrong?
And as a second aspect: when and if I am starting to use for windows apps xlml controls why I should not directly start to use instead of Xojo directly c# and dotnet for Windows? I canāt really understand that especially while this not native argument was always the major argument against all kinds of Java Solutions in the Xojo community and now the community starts to love the Xaml Control? I am not able to get that.
I never met anyone understanding Xojoās goal, including myself. Even Xojoās supreme NI seems to be confused.
2 Likes
Xojos GOAL is to take the most cool and bleeding edge technology of today and deliver a half baked crappy version of it seven years from nowā¦ by which time what was cool is now luke warm
6 Likes
According to wikipedia, XAML is 15 years oldā¦
Yeah thatās about right; I think it was originally concocted for the now-apparently-deprecated Windows Presentation Framework (WPF). Never really cared for it; it seemed inelegant / unwieldy to me, so now that the Green Ones are touting it as a feature Iām not impressed. Iām kind of irritated to see it being used in .NET MAUI.
2 Likes
Xojo on sale again:
https://forum.xojo.com/t/xojo-sale-save-25-on-licenses-and-extras/76989
Pro Plus comes, lo and behold, with an extra level of support!
Who could resistā¦
Twice nothing is still nothing
1 Like
I can resistā¦ and donāt even have to exert any effort to do so
3 Likes
If Xojo Pro was $200, it might be worth it, knowing that a vast majority of it NOT going to be used and youāll need to write a bunch of declares to get anything resembling a modern UI, heck, even modern functionality.
Exactly, that is BASIC marketing. The customer feels scammed when is charged for something that it is not going to use.
I was tempted, the xaml control could solve a problem in windows and web 2 is almost usable. But, they have incresed the prices, while the value offered has not really increaced, bugs still there, new features half baked, mobile is a joke.
Maybe if they create a new cheaper Tier, Desktop + Web, could be more attractive to some users. $200 sure, even $300 could be a good option, beyond that it is hard to find some value in xojo worth the money.
They worked hard on change, not progress.
3 Likes