Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How am I protected form a possible demise of “Jenny Does Maps”?

0
Posted

How am I protected form a possible demise of “Jenny Does Maps”?

0

You always remove Jenny code and leave the generated map code, as if “Jenny Does Maps” was never used. Jenny Does Maps” works by preprocessing. After reading the user provided parameters and the “Jenny Does Maps” definition file, the Jenagin processor generates the map code. After the map code is generated, the processed code passively remains on the page where it can be changed and reprocessed to maintain the map. But neither the user provided parameter code nor the definition code have any effect on map operations. Users can easily remove all traces of Jenny and functionally keep the same maps. The maps stripped of Jenny would less maintainable, but no less so than non Jenny generated map code. “Jenny Does Maps” does not obfuscate the code it generates. Even if the Jenny/Jenagin project itself should not survive, a usable working processor is freely available and well documented. This alone should suffice protect user coding for the expected life of the Google Maps API. And should th

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123