Where is the problem in the first place, and then what is the solution? Let’s dive in.
I am on a spree today. The number of topics I wanted to blog about has accumulated, and I just decided to dump the stuff over here while I both feel the motivation and have time for blogging. However, in this hurry, I forgot to add some important content to my previous post.
First, I forgot to mention that the example of my preserve-jquery script trick can be found in this github repo:
That’s the demo I blogged about earlier today, except this time it has two more branches:
- Branch “problem”: showcases how a problematic script can break your code.
- Branch “solution”: showcases how this problem can be fixed by applying the trick from my previous post
Also, there are two JSFiddles I created to follow screenshot-base examples from the post:
In my previous post, I’ve written about the situation when you (or somebody you trust) redeclares the $ variable, thus inadvertently breaking all your jQuery code. I’ve also explained how to remedy for it inside the code you write by applying the Immediately Invoked Function Expression (IIFE) or Self-Executing Anonymous Function pattern.
However, is there anything you can do to prevent anyone from trampling over $ or jQuery variables in the first place?
As I said in my last post, yes, and no.
Let’s take a closer look at it.
Continue reading Preventing trampling over $
Now let’s jump into the point. A friend asked me for help with a control add-in in which “jQuery doesn’t work, I can do jQuery() but I cannot do $()”
Continue reading Why doesn’t my jQuery work?
One of major limitations of control add-ins is not being able to define HTML. It seems so unbelievably unbelievable, that anyone looking at it from the outside of the NAV/BC playground may say “obviously, you must be missing something!”. But I am not. The one thing that you would expect to find first when defining a control add-in (and control add-ins in NAV/BC are nothing more than pieces of HTML that live within the allocated area of your browser real estate) is to be able to define the HTML. And yet, you can’t define it. The only way to show any UI from your control add-in is to procedurally create any of your control add-in HTML.
This makes no sense. No. Sense.
Continue reading Abusing Images property to load HTML in control add-ins