That’s been a joke a for many years - not just this one.
4 Likes
as far as I remember their CEO says all time that they are perfectly staffed. So. The Bugs will be fixed within three months all I would guess.
1 Like
yes, it would but this new feature complete Android version was a tiny bit more work than expected.
1 Like
“just debugging” left to do
like
https://tracker.xojo.com/xojoinc/xojo/-/issues/?sort=created_date&state=opened&label_name[]=Android&first_page_size=20
lots of fun things in that list
some are simply because Kotlin HAS NO EQUIVALENT like method local static variables
so you cant just rewrite code from Xojo into Kotlin line by line
but its “just debugging”
in the same way its “just marketing”
2 Likes
Like the time Gil Amelio came back onstage to say that, due to popular demand, symmetric multiprocessing would get tacked onto Copland at the last minute. 
2 Likes
From Wikipedia’s ‘Copland’ page:
Internally, however, the development effort was beset with problems due to dysfunctional corporate personnel and project management. Development milestones and developer release dates were missed repeatedly.
But look where Apple is right now … that will most likely be the answer of some genius in Austin 
You could build it as an Object and remember it. So you could handle this. But it makes much headache to do it. There would be CodenameOne with Java more comfortable and also open Source. The Android will serve them tons of headache in future. Or they decide: ok, rewrite the next. Also that could be happened. Or they reduce the features so that it is not possible anymore to run in an incident like that. We will see what the corporate decision about it is.
The IDE must know what xojo lines are responsible for the error in the kotlin side…
I have being working in a mobile App the last month in B4X, after the using the debugger there; Looking at the values by hovering over the variable in code even globals, the HotSwap of code… Cant imagine to use the crapy debugger in xojo for Android 
2 Likes
Steve Jobs was never the one developed the Systems. So there is no Genius guy. It is a really good Story but the Developers where hundreds of technicians. And the Idea for an iPhone? Ha, Palm had that Idea before and started Development in that direction, also HP had that Idea. Apple was getting that and was - at least faster than the others. And yes, IOSD is nice, no question. But it is not the invention of a single genius guy. It is the summary of development teams which where leaded in a functional structure and not chaotically running between bugfixes for the old stuffs, different platforms and different codebases. There are big differences. Apples decision to build what they saw at Xerox Parc was not a genius development; it was for sure the copy of the things they have seen. And so all that stories can be reduced to: the marketing capabilities of Mr. Jobs where brilliant. And that was opening the doors. And another thing was important: apple concentrated on the market and where the money is. They did not wanted to be everybody’s darling. Still not. They want to find out which peoples darling they have to be to sell as much as possible to a price which is as high as possible. And that is in some kinds: arts.
-
The feature being implemented 13 years afther the request…
-
The request existing just because the user thought it was “just” a linux target…
-
Most of the bug reports being done by a single user…
-
Just 29 open cases for a new target shows the lack of interest in beta testing…
-
Xojo not being a RAD anymore? “Wont implement properties of controls because you can make the UI in code”: Xojo: Account Login
-
Android got messed up to be in line with iOS instead of fixing both to be more RADis and close to Desktop… Xojo: Account Login
Oh I already know what I’d do in such a case
Thing is that in order to do it you have to do more than just rewrite code from xojo to Kotlin on a line by line basis
but “it’s just debugging” 
you would assume it would
Newton and yes you could use the Newton as a phone - it was just huge
10000%
1000%
1000000% so much for RAD
do it in code !
I know that you know but I wanted to reach out to the others that there are possibilities. And yes, you need to analyze the code as it and not line by line. That will in case of kotlind be complex. You could do that with Java cause it is much more flexibel by Design than kotlind in this case. And it is much more similar to Xojo especially for example in case of the inhabitation mechanisms. So I guess it would be much more interesting to use Java instead of Kotlin. At least I would do it so. But whatever, maybe the people behind having a different thinking and genius Ideas
Yeah they need to do most of what a compiler does to turn Xojo code into Kotlin code, some how preserve line #'s in that transition so the debugger can highlight the right line of Xojo code tats causing the error and … ick !
Lots of work - more than “just debugging” I suspect
What ever we suspect: they have their own base for decisions and their own thinking what is right and what not. Possibly they will do that totally different at the end. Who can know it. I believe that they had this problems in many ways before also.
1 Like
and here again the Steve clone in Austin will tell you, we are working hard on all those topics, please note my emoji this time in words: sarcsam.
They excel on all these topics, granted they aren’t yet on track finding whose people’s darling they want to be. For me the honeymoon is canceled, I waited too long for the bride to appear.
I’m all in for “corporate decision” to become the sentence of the year 2022 for Xojo
2 Likes
TBH I dont recall ever having this sort of issue
Yes there were pissed off customers - but they dealt with them cordially, friendly and very few ever turned into “trolls”
There was https://www.reddit.com/r/xojohaters/
And I dont recall anyone getting banned forever from their old PHPbb forums - BUT I didnt use them a TON
I was a mailing list person for along time
The whole “fight the trolls” attitude seems to be relatively new - and not succeeding
INN’s readership grows all the time
Oh youmisunderstood me. I spoke about the situation of the Development. We can’t know how they will get forward with the development and how they will decide how to do it. I wrote it to cryptic.
Oh true I have no idea if they have perpetuated the practices that I knew
I suspect they have based on what we see externally
But couldn’t PROVE it if I tried
The move to issues might have helped with managing bug reports
But I cant say I’ve seen it alter the entire process and overall QA
Thats something software changes alone cant effect