He is using the Dotnet framework for this work so I guess that he will be able to implement many stuffs over the time. But he will now do bug fixing. It’s a nice and feature rich work. Sadly there is again no command line compiler. But I guess this will come cause he can implement the licensing. I whish the best for it.
Wow, congrats! Will test it next weekend!
I like this one 
This is the culmination of years of work and a stubborn refusal to accept that “easy to use” and “powerful” are mutually exclusive.
check Forgejo aswell…
V1 supports the concept of shared code that can live between projects. It’s on my feature list to implement proper package support with a public repository. I need to put some thought into how to support packages for those who want them to be open and those who would like to sell them.
It’s 100% something I will add as I think one of the many reasons Xojo never gained enough traction is because of the lack of a solid ecosystem.
Thanks for the kind words.
Indeed - it’s all about bug fixing right now, that’s my priority. It’s the number one complaint about Xojo and so it will not be a complaint about Objo, that’s my commitment.
I’ve added command line compiler support to my internal feature list. Actually that’s an easy implementation as the whole pipeline is already completely built, I just don’t expose it. How would you propose I support licensing however with a command line compiler? That’s possibly one of the reasons Xojo Never added it.
That is easy.
The command line compiler only runs if it sees a license file from the IDE or is invoked by the IDE.
And Xojo may be working on a command line version, too.
site code licensing to the license server, license server sends back the license code. is a simple process: falls back in install license first
Xojo’s issue was that all licensing checks were in the IDE - not the compiler
So only the IDE could tell ID you had a license
I dont think the output requires or leans on dotnet
The system is written IN C# but the output isnt a dotnet app
At least thats how I read the first post
The output is a “Desktop Host” C# app that holds the Objobasic VM, compiled bytecode, resources and Objo’s standard library.
I use Avalonia and Skia for rendering the UI the same across all platforms. Yes it’s not a native UI library but I decided that you can’t make a cross-platform app with native controls, no matter how much Xojo prattles on that you can. The concept of a visual designer doesn’t work if the controls look different and behave differently on each platform
Btw, I should ask a little favour. If anyone knows disgruntled Xojo users who might be interested in this solution but don’t visit this forum - please feel free to share this with them.
Not sure how to get traction for this project. I can’t post on the official forums because that’s against Xojo’s terms.
For those that are tracking the work I’m doing on Objo, I’ve just launched a purpose-built bug and feature tracker so anyone can see what still needs to be addressed in Objo and what’s been fixed:
It’s backed by GitHub Issues privately but provides a read-only view into bugs and features I’m working on.
Ah OK so it is a C# app
That might then require the botnet runtimes be installed but thats not so hard to manage
Is there a report control like crystal reports.
Not yet but if it’s something you can explain, please feel free to submit it as a feature on the forum 
BKeeney Shorts is one example
Is this a business?
More than an one man show?
For 99£ it is affordable but you can’t spend much time on support for that.
Yes it’s a business that I hope to make sustainable.
I’ve spent most of my free time over the last 2-3 years on it so at this point it’s mostly all I think about!
I’ve actually reduced my hours as a doctor to focus more on this project so I plan on fully supporting it and growing it over time.
They do, according to their CEO
I was