I was doing some reading on the weekend and came across some really good thoughts on how to make decisions in code – but not by using conventional if or select branching mechanisms or others that masquerade as flow control statements under other guises.
There’s a whole movement for “if-less programming”.
And it fits very well with using OOP and the capabilities of polymorphism in ways that make your code clearer and easier to maintain and extend.… Read the rest
IfNotNil has some new tutorials.
I’ve posted one, in a series, on data structures and how to implement them in Xojo.
More to come.
I’ve now had use of a Pro+ license for nearly a year.
When this license type was introduced Xojo told us that the Pro+ included
… Read the restTop Priority Support is just as defined on that page, we’ll bump your support questions to the top of the queue and we’ll review your Feedback cases first. And of course you can set up a call with us anytime too.
Some companies like to pose certain programming questions as part of their interview process.
I’ve run into a variety of these. They’ve been SQL related questions, code writing, and algorithm descriptions. Some were fairly straight forward. Some less so.
One of the best I heard was a series of “How would you write this code if you had to write it …” with varying restrictions put on things.… Read the rest
MacOS has been fully 64 bit since the release of 10.7 (Lion) in 2011.
Yet is has continued to support running 32 bit apps up until the release of 10.15 (Catalina) which removes support for 32 bit apps entirely.
There are ways to work around this like running an old version of macOS in a VM.… Read the rest
Xojo includes the ability for you to supplement the plist a macOS build creates.
You can’t overwrite the items the IDE will generate for you but you can add things like heys for App Transport security, Crash on Exceptions and even your own custom items if you want them.
The entire of creating and adding a plist is fairly simple.… Read the rest
Lots of times we might like to clean up our code by making sure we fix all the errors AND all the warnings as well.
And one of those you might find you get warned about is unused parameters. These might come about from implementing some interface for a nice consistent API but some implementors of the methods on the interface dont use all the parameters.… Read the rest
I’ve seen lots of discussions that talk about how certain bugs have been copied over from API 1.0 to API 2.0.
This is unlikely and mostly not correct. From what I can tell nothing was “copied” from one API to another.
Let me detail why I think this is the case with an analogy.
Suppose you had source code that you could compile into a dynamic library for macOS (a dylib), Windows (a DLL), or Linux (a .so).… Read the rest
In 2019r3 Xojo added something that a lot of people have been asking for for a very long time. A way for a class that exposes events to know IF an instance implements the event.
Its literally called IsEventImplemented (see http://feedback.xojo.com/case/58342)
But it remains undocumented
Previously if you wrote a class that could have some default behaviour IF an instance did not implemnent the event to alter the behaviour you had no way to know if you should operate in whatever way was the default or not.… Read the rest
And by that no I don’t mean that YOU personally should fail. I’m of the same mind as my dad on that front. You should work your ass off to do the best job you know how to do. That doesn’t mean you’re perfect or that you expect perfection. There are lots of things in this world that I do not know how to do very well – but when given the opportunity I try to do the very best job I know how to and I try to learn how to do it better next time.… Read the rest