2021r3 Announced?

65

Good job MVPs! Muahaha

66

Yes, a few hours before each release they start to switch parts of the website.

So it may come later today.

67

Yes, the page last changes is said to be in last September.

And… the applications takes more time to download than the documentation “switch” (set the visible bit to “Yes“)

68

There is now a banner on TOF with a link to download 2021r3.

69

The reaction to the release over the next few weeks will be interesting…

2 Likes
70

I don’t think that it will take that long.

2 Likes
71

New Desktop Control aren’t really new if they are just renamed.

72

Once decided against Namespaces you may need to react so if you want to get one Codebase somewhen which isn’t one Codebase at all. Somehow.

73

They are new because lots of old code needs to be reworked. There is a menu item called “Update controls to API 2”. In my main project this makes 1218 errors because some stuff isn’t available any more. And you have to do everything at once because DesktopWindows need DesktopMenus.

74

No matter what Xojo do some people are never happy.

1 Like
75

Just fix bugs and slow down on making new ones. Easy peasy. But instead they rename things to look busy. Muahaha

1 Like
76

Please don’t convert projects.

Maybe next year after another Xojo release or two, but not now.

1 Like
77

I know I can’t convert my project. But everyone will try and everyone will be ecstatic.

1 Like
78

They literally just had a huge bug fix release. Like I said some people are never happy.

1 Like
79

There is no need whatsoever in a modern cross platform programming environment to have this kind of nameing structure. a “BUTTON” is a “BUTTON” is a “BUTTON”
not a “DesktopButton” and “MobileButton” and “WebButton”
The compiler KNOWS what platform it is compiling for and could/would/shout treat a BUTTON object in the manner suited for the current platform

Now that being said… Apple is somewhat doing the same thing, with UIButton and NSButton but adding these lines, the compiler once again takes over

#if !os(macOS)
import UIKit
public typealias aliasBUTTON         = UIButton
#else
import Cocoa
public typealias aliasBUTTON         = NSButton
#endif

Xojo could have internally taken a similar approach and gained GOOD WILL from their remaining clients, instead of what we expect to see over the next several days/weeks

80

What I dont get:

DesktopWindow
DesktopListbox

etc

surely to be ‘cross platform’ code reuse, the goal would be
Window
Listbox
etc and have the compiler/IDE handle the difference transparently?

This change means all code for desktop needs to be converted from a format that doesn’t compile on mobile, into another format that also cant be used in mobile.
I know not everything CAN be, obviously, but what we are ending up with is not
'one Xojo that can be used to write once/ compile many ’
so much as
‘several apps , all called Xojo, that do different stuff’ ?

81

Hahahaha. Yeah one release with some bug fixes solved the problem.

Desktop is the only ‘complete’ target. Web is FUBARd. But keep being happy with Xojo’s lack of progress. :laughing:

And now Desktop us FUBARd…

1 Like
82

You see. There is nothing Xojo could ever do that would make you feel positively about the product again. You are wasting your time wrapped up in negativity- it’s not good for you.

2 Likes
83

Well this community allows those users to vent. If you have a problem with that you don’t have to be here.

1 Like
84

Reverse that. What could Xojo do to earn trust back?

3 Likes