This was part of the reason that I only sold source code. That way the person who bought it could modify to suit their needs and if I left the community they could (if they wanted) maintain the code. Tried encrypted source for a while and all it did was generate support emails because no matter how good the documentation was there were questions that could easily be answered by looking at the source.
End result is that there are not enough developers in the community that need an advanced control like FTC to make it a feasible revenue stream. Same with ActiveRecord and any number of other controls/libraries. MBS pretty much has the only feasible model for libraries and Einhugur is really the only successful Controls vendor. Well, I suppose Graffiti Suite might be the other but I never bought into their controls so I donāt have much of an opinion either way.
Yes but what are you waiting for. The amount of Xojo Developers is not climbing up abiove Java. Exactly that is the point. it is an extremely small community with too less people so niche controls are not needed often enough to find supporters. And many stuffs passed away with the developers.
Iāve looked at FTC, but since Iāve managed to build an htmlviewer containing the summernote editor inside. works fine and I have all I need in a text editor with that. (plus I managed to add some table editor inside that works fine too !)
This issue is a PERFECT example of how not having a suitable testing mentality screws over users & forces them to have to do thorough testing every damned time
Someone dinks with the compiler and DOESNT have a regression test suite, or doesnt use it or ā¦ I dunno ā¦ and something breaks which breaks other dependent code
Iāve been told that this was reported and will be fixed in the next version. And yes, itās a shame that there is no unit tests or regression testing (to be fair there might be some but it didnāt catch this bug). In my 25 years of using the product this happens with such regularity that its reputation of being buggy is well deserved.
Unit tests and code reviews seem like it slows things down. And it does at first, but itās a cumulative effect in the future. I recently did some work on a Windows file type that had embedded data of another file type. Made a change to the first that caused the unit tests to fail for the embedded data type. It saved mucho time because QA never saw it and certainly no customer ever saw it. Win-win-win all around. Itās really a shame that Xojo does not see the advantages.
They behave so cause they have no people behind which could do that job. A really small company which serves a product which is not a good idea to use. So they have their QA. Didnāt you see the developers in their Developer section. Only Pro developer having entrance. And there the QA is done. For all the Bugs , no.. for the most of the bugs .. no ā¦ for one of hundret BUGS. Simply that is their system. And thatās why it is so dangerous to rely on them.
Even with Swift you can have āClose encounters of the THIRD KINDā. But at least you will come out of it. Same with other languages. But with Xojo you have nearly the guarantee that your Bug will not be fixed. If you are lucky it is - after a year or two. If you are on Android: huuu thatās long time development. Wait a decade.
Hey, sorry everyone. I created the Github repo that hosts the FTC. Unfortunately, I havenāt maintained my Xojo license and have stopped using it over the years. I only stopped by this forum again recently to see what was going on.
Iāll work with someone who is interested in either transferring the repo or at least putting a link to a new repo in the README. I donāt have Xojo to even be able to test the software as it is now. Once again, sorry.
Itās been a while, but I think when you open a project without a license, you cannot save changes back to the original text-based project. I think the IDE will force you to save to binary format.
I could be wrong, so someone please correct me if I amā¦
Or save as text which can also be surmounted its just a pain in the rear
what you end up doing is
get the project as text
open it
any changes have to be made in the TEXT items in the local copy of the repo using BBEdit, TextEdit, etc
make a trivial change in the project open in the IDE and REVERT TO SAVED to reload the now project from
You can at least edit code this way & test it
Project level changes (adding items etc) are WAY more complicated and well beyond the scope of the hacky workaround I mentioned above
That shows how a code-lock really can work: they made their own way of it. XoJo isnāt a good Idea. It looks soo nice but if you want to use it it comes to dead code at the end.
