Compatibility with old projects?
Edit: missed Christian’s post above, good news.
Looks like bootstrap was used for styling
HTTP/2 ?
Moving on to Xojo API’s.
- Designed in 1997.
- Started with just MacOS in mind.
- Got crufty over the years leading to inconsistencies.
- Changes could break existing projects.
- So created the new framework.
…
No comments yet. Greg has a whole session later.
The new framework:
- Namespaced.
- Consistent behavior.
- Changed what needed to be changed.
- But more complex.
…
Their guidelines for the new framework:
(Actually, there is more here than I can keep up with. Short version: put a lot of thought into making it consistent and discoverable.)
But the guidelines created inconsistencies with the existing API’s, so they are looking for Best of Both Worlds.
- Keep the current API’s for compatibility.
- Add new API’s for consistency.
- Replaced API’s will be deprecated.
- But these will be attached to the old framework so transition at your own pace.
- SO NO NAMESPACES! (mostly)
To summarize: squint
(someone copying these bullets?)
So does String make it into the “new” framework now? Stay tuned…
This will be called API 2.0.
We will have a blog post up very soon after the keynote is over with all of these details.
So… what does this mean with respect to those of us who have adopted the (now apparently old) new framework?
How do they handle the zero- vs. one-based index inconsistencies? Stay tuned…
That better be part of the the consistency thing!
It’s hard not to have a sense of “I told you so” right now. This design has my support so far.
XDC 2019 will be in Miami at the Marriott Biscane Bay, May 1 - 3. $149 per night.
This makes it super easy for UK people (and Europeans, I assume) to get to.
I might actually be able to make it next year.
The new IDE interface is considered a Priority and the word from Geoff is that they are putting a lot of effort into it.
@Travis Hill is starting his session on API 2.0.