simply speed optimisation

Hi @docteurfitness,

A great many thanks for pointing this out and for posting this issue report! Indeed I even deceived myself by noting (in class/init.php:156 (2.5.4)) about scripts that “These are only enqueued if the jQuery tooltips are enabled”, while the next “if” statement (around the script loading tags) is only making sure that there is no use of alternative tooltips, those working without JavaScript libraries (and not adapting to the window).

Also I did only half of the job by completing the minification of the jQuery Tools file only (where deprecated functions needed to be replaced or redacted), not noticing that the same approach must benefit the style sheets too, where the exact same issue of wasteful layout and comment blocks designed for human readers needs to be addressed.

Thanks to implementing your recommendations, there shall be about 12 minified style sheets tailored to the needs of every combination of tooltip usage and of help (or not) with basic responsive page layout for some themes.

And indeed the tooltip-related internal CSS needs to be skipped when tooltips are not used, like the JS (inline for jQuery tooltips, internal for plain JavaScript tooltips) currently is inserted only if needed.

As a user initially offering just to fix a small heap of bugs identified after I started really using WordPress less than 1 year ago, I’m inexperienced and welcome every suggestion helping fix the plugin. You offered us a great deal of them, and I’m currently scrambling to properly and comprehensively acknowledge all users and developers who kindly contributed code, feature requests, bug reports and provided us with usage examples alongside. We are grateful for your contributions to the plugin, and you were among the first three new contributors added when the Contributors field in readme.txt was edited again after 2.0.0, for v2.5.1. Only so late because by then, maintaining the metadata was my responsibility. If it was plugin author @markcheret for sure he would have added you on the spot when you enabled AJAX autoload for v2.0.6!

(Also I would prefer the contributor label, only the fear of misinterpreted disruption on Footnotes’ forum retains me from using another account for the uploads to SVN before removing my author label.)

Thanks a lot again for your recommendations that go to be fast-tracked for instant implementation and shall be available in our very next release! We must target energy efficiency along with food sustainability everywhere it’s possible.

• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.

Sorry please, didn’t see your feedback as I was busy correcting and posting again. You are welcome!

While implementing your recommendations I remembered also Plugin author Patrizia Lutz (Pea) @misfist optimized internal processes by streamlining template load, correcting wasteful code that caused utter process garbage:

/**
* Template process optimization
*
* – Bugfix: Templates: optimize template load and processing based on settings, thanks to @misfist code contribution.
*
* @since 2.4.0
* @date 2021-01-04T1355+0100
*
* @author Patrizia Lutz @misfist
*
* @link https://ww.wp.xz.cn/support/topic/template-override-filter/#post-13864301
* @link https://github.com/misfist/footnotes/releases/tag/2.4.0d3 repository
* @link https://github.com/misfist/footnotes/compare/2.4.0%E2%80%A62.4.0d3 diff
*
* @var bool
*
* Streamline process depending on tooltip enabled status.
* Load tooltip inline script only if jQuery tooltips are enabled.
* Actual value depends on settings.
*/

Also, Plugin Contibutor @martinneumannat paved the way to making Footnotes AMP compatible, while Plugin User @psykonevro’s bug report reminded us of the urgency:

* – Adding: Referrers and backlinks: optional hard links for AMP compatibility, thanks to @psykonevro bug report, thanks to @martinneumannat code contribution.
*
* @since 2.3.0
* @var bool|str|int
*
* @contributor @martinneumannat
* @link https://ww.wp.xz.cn/support/topic/making-it-amp-compatible/
*
* @reporter @psykonevro
* @link https://ww.wp.xz.cn/support/topic/footnotes-is-not-amp-compatible/
*
* The official AMP plugin strips off JavaScript, breaking Footnotes’
* animated scrolling.

The template stack from Plugin Author @misfist enables you to meet special requirements, and if we can help you address any issue, be sure to keep in touch.

Stay safe!

Best regards.

• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.
• This reply was modified 5 years, 3 months ago by pewgeuges.

Hello,

An implementation of the design you contributed is up and running and would be released as v2.5.5 on the spot if there weren’t concerns about consistency; I’m afraid that so close a release—4 days after v2.5.4—could contradict the energy efficiency argument that v2.5.5 is placed under.

We’d also like to make sure it actually is what you had in mind. The stylesheet is split up in 3 parts depending on tooltips enabled and alternative tooltips enabled status, and the 3 optional basic responsive page layout stylesheets enter also in the concatenation of 12 unified tailored stylesheets, deleted after minification to streamline the codebase given their formatted constituents are shipped alongside. The documentation is in dev-common.css, and the bash script csscat.sh is in development/ together with a note on the stack for customized template parts from @misfist, and another one about the customized documentation schema used.

You are welcome to look into now-current development v2.5.5d0 at https://downloads.wp.xz.cn/plugin/footnotes.zip

Please feel free (but not urged) to report anything not meeting your expectations.

Thank you again very much for this improvement!

Hello @docteurfitness,

We’re glad it’s okay, thanks a lot for your feedback!

It will be in the very next update, to be rolled out soon.

Many thanks again for helping get Footnotes state-of-the-art!

Best regards,
@pewgeuges