crosspost: https://www.drupal.org/node/2838455

At current state, there is no reason these modules co-exist. Both use taxonomies to render title-attribute-based tooltips using an input filter. Though in de D7 version of glossify it supports an advanced filter to use node-data to build tooltips from. But I doubt this will be usefull for glossify D8.

I would propose merge of these 2 modules, using the strength of each. If possible, I would like a reaction of a taxonomy_tooltip maintainer?

Comments

keesje created an issue. See original summary.

keesje’s picture

keesje commented
Issue summary: View changes
keesje’s picture

keesje commented

After a chat with the maintainer of taxonomy_tooltip we decided to merge* these modules and make it available under the taxonomy_tooltip namespace.
decisions:

  • No support for node's as providers for tooltip data as glossify D7 has, just taxonomy terms
  • This will be a complete rewrite. We would like upgrade paths for both D7 modules, this remains uncertain.
  • No styling included for sake of flexibility.
  • Easy implementation (but no dependency) of tooltip libraries like tooltipster.

*The future of glossify is not up to me to decide :-)

mtnguru’s picture

mtnguru commented

It's a great idea to merge these modules.

I recently installed the D8 Glossify sandbox and really like the way it creates a dom document for finding terms and making them into links. Having never used this method I can't speak to it's efficiency - however it is very elegant. However glossify needs better tooltips and that's where taxonomy_tooltop helps.

I have a fair amount of D8 and JavaScript experience and would like to help out, is there active work being done? What's the status?

keesje’s picture

keesje commented

Hi James, thanks for looking into this.
The DOM based replacement is not only better, its necessary to prevent markup (eg classes) to be replaced creating faulty html.

I have had briefly contact with maintainers of both glossify and taxonomy_tooltip, but both seem to be busy atm, no offence.

The ideal situation IMO:

  1. glossify takes lead as "tooltip framework", implementing replacement code and themeing.
  2. taxonomy_tooltip depends on glossify.
  3. new node_tooltip module depends on glossify, will probably be part of glossify as submodule.
  4. nicer looking tooltips will be handled optionally by other modules/libraries/themes. There's just to many options. Ideally someone ports https://www.drupal.org/project/tips to D8, or builds something else to flexibly implements js/css tooltip libraries.

1, 2, 3 I am building right now. Will make it available on github until I have a chance to have more feedback from other users/maintainers.

please share your opinion.

mtnguru’s picture

mtnguru commented

Hello Kees,

I like the approach of having glossify be a standalone module with the simple jQuery tooltips. Then having other modules that implement more advanced tooltips. I don't have experience with the tips module, I'll give it look.

I have a need to be able to specify which glossary taxonomies to use per Organic Group. This is most likely yet another module.

Let me know if I can help code, test, whatever.

keesje’s picture

keesje commented

If you (or anyone) could review https://github.com/dripl/d8-glossify-taxonomy_tooltip? that would be great.
A hook to override the taxonomies used might open up possibilities for your per-og needs, could be a nice feature.

keesje’s picture

keesje commented
Status: Active » Closed (duplicate)

We decided to merge under the "glossify" namespace and abandon taxonomy_tooltip for D8 development. Discussion here: https://www.drupal.org/node/2838455