Why people should not use directly the kotlind toolchain? One question I got never an answer for. Apple UI and Android UI generated and the Logic shared. kotlind Multiplanform Mobile with native UI. That’s it.
Why do you insist on using java instead of using assembler directly? 
Yup, the xojo debugger sucks compared with other tools. But on android, they reach a new low. 
While Assembler is hardware dependent. Java is not. What kind of question this shall be Ivan? And why you speak about Java when I spoke about Kolin Multiplatform Mobile? has nothing to do with Java Ivan. Has to do with Kolin, the main Language for Android Development. The Language Xojo tries to implement with their Android Implementation. So what you want to ask me? You can speak about Java when I do it. But lay in my mouth Java now and totally ignoring what I wrote? Hey I thought there is more behind that what you write. Sorry, that is a LOW.
Didn’t you tell me the other day that you hate Kotlin? 
1 Like
I do. But other people may not. What shall I say? Every other toolchain is better than the Xojo one which is not really working and needs for every puh a declare. That was why I was speaking about Kolin and not about Java. Was not helping reading the total worthless comparison between Java and Assembler.
This one helped me as it is structured, like all of his courses.But I took it 2 years ago. Many resources are as well avaiable on youtube or udemy etc. But I prefer spending money and getting a focused course and not people repeating themselves endlessly just to make the next 100h course. Netninja is a trusted source.
Another trusted source IMHO is https://fireship.io/
Problem with this gentleman, he is very focused and you need to add some own research, but I like that approach, best way to learn new things.
1 Like
This thread is about using XOJO’s ANDROID tools
IF you have experience with Xojo for Android then feel free to contribute
If this is just another avenue to push something else and bemoan Xojo (which I fully understand) please dont
keeping things sort of on topic would be nice for a change
The Xojo Android Tools using the Kolin Toolchain indirectly. The question I was asking was in a direct conclusion with this while I wanted to understand that. Kolin is the Language Xojo uses with Transpirier what results in a toolchain not for tablets for example. That was why I was asking that.
But to ask more Xojo related: why they are not coming to the conclusion that the extremely nice technology they have for UI Design with their Designer could be used for directly using Kolin Language for this kind of projects while they would bring out then a toolchain which makes Mobile projects much more powerful. It fouls be implemented in the Xojo IDE and I would think that this would be also an Idea how that toolchain could grow in a completely new wise.
Because they’d have to rewrite everything else they have that is already IN xojo
That could be a lot of code, or very little
In my case I’d love to be able to “port” code to Xojo for Android
But it starts in Xojo for iOS and “porting” means rewriting most of it anyway since the Xojo framework is deprecated
So I have started trying to rewrite it directly in Android Studio
The biggest impediment is just figuring out the entire architecture that it follows to start the app, load an activity, and get “the same” layout on screen
Or “learning the ropes” all over again
Other than that AS is pretty quick - although it has some weirdness to the IDE too
Now IF I had Xojo’s layout editor in AS that would be nice
I’m sure someone will point out how I can achieve that
And then I’ll be done with Xojo on Android
That’s exactly what I meant. Thanks.
Yes
there’s who have API 2 code already may find that they can reuse more of their code than I can
But there’s still a long way to go before I’d say Xojo for Android is on par with Xojo for iOS even
And thats saying something
And even Xojo for IOS has leaky functionality with the need of tons of declares. That is let me say: a pain in the a… I am not allowed to say so let me say back side .
Yeah iOS remains largely incomplete
Even when I worked there it didnt move much
That was, in part, due to relentless pushback from certain users and their complaints about the Xojo framework
It was, if you go read comments from that time (if they are available), meant to grow fast & spread to all the project types much quicker
Best laid plans & such
And it had certain advantages in what could be stripped out making for smaller faster builds
And a LACK of mish based type for TEXT and BINARY data - some folk decreed that separation
And yes it required the use of namespaces
There was a plan to reduce the need for those OVER TIME; but those who complained did so loud & long & that got attention
So that plans got shelved and iOS remained largely “as is” for many years
But Android is even less capable than iOS in many ways
debugging is … well … shit
the debugger just doesnt work
rarely if ever stops at break points in the emulators
so I’ve resorted to debugging in 1985 style - printf
1985 was nice. I was young and felt much better than today. The debugging wasn’t my problem. Everything was nice. And many, many girls around. Nice time.
It was the exact same kind of question you ask.
It is called an analogy, Glad you see the problem through it 
Sorry that you have no talent for analogies. It wasn’t one in no kind of analogy. And it was not the same question.
The question behind was asked while Xojo uses exactly that technology for Android. It is Kotlin behind it. And they could do with their technology much more.But that you did not understood at all. Sorry for you.
Who do you address? I replied to a question, so don’t shoot the messenger please.
If this is just another avenue to push something else and bemoan Xojo (which I fully understand) please dont
I’m used to Xojo-esque attitudes and don’t take them personal. Your wish comes true, I’ll mute this rat race now, Xojo doesn’t get any better by monologizing the nonsense over and over again.
1 Like