Palmpons is a budget friendly online discount marketplace with discounts and offers having proven their worth for business owners, generating tons of interest from consumers.

From a business perspective, finding new customers and keeping them can be expensive, time consuming and at times downright frustrating. Many companies struggle to market their goods and services without breaking their budget.

PalmPons addresses this issue. This online marketplace that directs visitors to businesses enabling them to create and showcase their products and services in the form of what PalmPons call snippets.

What are snippets? Snippets are the various bite sized promotional offers found on their site. Businesses can create their own snippets to attract customers, whether it is a discount on gold watches, burgers and fries for half the price or any kind of offer of the seller’s choosing.

So if a user stumbles upon your snippet and purchases it, a small percentage of the earnings goes to Palmpons while you get both the sale and a potential returning customer. No more worries on human resource use no more direct mailings, expensive flyers or hiring social media experts to help you draw in customers.

PalmPons is one hassle free way to let the customers come to you.

Seems like an applet that is inside a DOM container and getting hidden by calling JQuery’s hide() method messes up the applet’s state.

In my case, I got an IllegalStateException and in some cases forced it to restart the applet which in turned messed up the operation that my code is doing.

I used the deployJava.js script to deploy the applet and enable me to call applet methods from Javascript.

So rather than using hide, user Danny Coulombe of StackOverflow gave a very workable solution. Using CSS, you can use JQuery to add the class attribute to hide or show the applet. See code.

To hide, call $(‘myapplet’).addClass(‘hide’).

To show, call $(‘myapplet’).removeClass(‘hide’).

A very useful solution to preserve your applet state in case you wish to hide it from the user’s view and show it later on using the same instance.

This … was … a … pain. Sure, most forum commenters said that to make this work, you will have to have the attribute Trusted-Library: true in the manifest of your jars and third party jars that your applet uses.

However, that is only half of what needs to be done. Even though all my third party libraries had that attribute in the manifest and signed them I never figured it out until so many days later.

When the Javascript call was made, the annoying warning sign pops up.

So what is the solution?

  1. Make sure all your jars have Trusted-Library: true in the manifest.
  2. Inside your main jar, add another attribute Codebase: *
  3. Sign all your jars using the same certificate

That is it! Problem solved!

Related Posts Plugin for WordPress, Blogger...