Quote:
Originally Posted by markoroots
|
Markoroots - Thank you for sharing those suggestions at vBulletin.com. Much appreciated. The Panjo plugin continues to improve thanks to the input of forum owners like you and thousands of others. The best place to follow
Panjo improvements and updates is on Panjo's blog under the 'software update' label.
Panjo does not have 25 installations. Panjo has nearly 1,000 installations. Due to the fact that Panjo comes preinstalled in vB 4.2.2 and due to the fact you can download Panjo from Panjo.com, the total count is ~1,000, not the 25 listed on this vB.org mod page. Panjo works lots of big boards that to are too busy running their businesses to come back to this page to flag Panjo as 'installed.'
As for the iFrame - why does Panjo leverage an iFrame? Panjo balances contemporary software development best practices with a world where vB 3.8 dominates. Panjo's use of an iFrame enables Panjo to be agile and quickly ship new features, benefits, and bug fixes. If Panjo relied on or burdened our partners with a task every time we wanted to deploy a new benefit or fix a bug, Panjo would have an install base running many different versions of Panjo. Through the iFrame, Panjo is able to rapidly improve the marketplace tools. Additionally, Panjo is able to provide security best practices to its partners through a use of SSL in a world where most vB forum operators are not using SSL. We don't disagree that a native vB php mod would be more ideal in some senses, but in many other senses it would be a loser. For four years, Panjo has continued to grow and improve. That can't be said for many vBulletin plugins because they took the route you are suggesting. We too wish were didn't have to use an iFrame, but it maximizes benefits and minimizes costs. PS - Take a VERY close look at the way Panjo integrates with the "post new thread" button and thread posts. Panjo's deep integration into vBulletin leverages the work flows and work flows familiar to your members.