Some exciting changes for iOS… will be interested to see how declares interact with the new Mobile classes, and if any of iOSKit is usable with API2.0. Some sort of conversion tool for projects will go a long way since converting it will take forever manually.
All great news! Thanks for the update and the features look like really nice additions!
I’m curious what kind of interaction might be available for workers. Will they have an optional persistent lifecycle that we can interact with?
we’ll find out a lot of this once we can actually test things out and poke around for ourselves
Excellent presentation. Lots of really exciting new things to play with. Well done!
Whilst I am very happy about iOS plugins, are interops no longer a thing?
[quote=480628:@Garry Pettet]Excellent presentation. Lots of really exciting new things to play with. Well done!
Whilst I am very happy about iOS plugins, are interops no longer a thing?[/quote]
Its dropped down the list but its still on the roadmap. https://documentation.xojo.com/resources/roadmap.html
Wow, looks like the roadmap has changed significantly since I last looked at it a few weeks ago. And the multicore support – which I assume is the Workers class? – at priority 5 will certainly not be in 2020 R1. So I’ll continue to develope my own console apps and communication in the interim.
But still the long term vision of many things is very promising!
Blown away. Great news across the board.
Wow…can’t wait. 
Web-based Feedback!!!
Nice video! Thanks a lot! Fun to watch!
@Geoff
You were laughing telling users use some graphics code to draw things at runtime.
Not so quick here: they build reports, they build up data queries and they will have to learn how to program (maybe for little things).
The problem at least at our site: too few software developers available and it does not get better.
Btw., look at NetBeans: it’s also a framework for application building (use the NetBeans infrastructure itself for Your application).
So, Xojo as adjustable framework with then (lower) runtime license costs per user (as each one is using Xojo as app).
I mean what is more user friendly being an IDE than Xojo?
2020 promises to be a good year after all!
Can’t wait to start testing the fantastic new goodies! Web 2.0, PDF, Worker classes! Wow! I am like a kid just before Christmas! (Yes I know… Not all for R1… But just the same!)
edit: fixed typo: it is know
Will be missing on Android?
and today we can see the android video…?
Already up.
Edit: I meant, they just made it public.
Well, to be fair, it came out after they’d asked
Link! https://youtu.be/rQBe-Cp-0x8
Thread! https://forum.xojo.com/59141-android-update-video-with-paul-lefebvre/
When does API 2get other methods from the “new” framework such as Xojo.Core.TextEncoding.ConvertDataToText()? It is things like this that are lacking which mean I can’t eliminate the use of Text in my app. Xojo.Core.TextEncoding.FromIANAName() is another.
Did I misunderstanding what I read yesterday about Strings ?
What did you read yesterday about Strings? I may have missed that.