IDEA:
1. glossify links nodes to nodes
so

we need ways to choose node-terms(NT) and node-articles-to-parse (natp)

What if instead we used views to build the lists of terms and we used the current parsed page as an arg to that view?

The admin UI as it is now is a subset of this general concept - it is the case when the argument does not change the term-nodes array...

This will open the doors for the usage of non-title cck fields for terms (am I crazy?)

I am considering parsing of cck fields too - thus the name of the view arg should be the name of the cck field...

So thus glossify will become a field 2 field thing...

And the glossifying process would consist of 1. build a view to select terms based on the parsed field's name - only the fields and filter sections of views are used (and arguments too)
2. for each view you can select a glossify display style... actually we can use the view's display concpt (i am talking about the page, block,feed displays...)

Quite weird meta-use of views , eh?

Did someone understand sth?

Comments

Ivo.Radulovski’s picture

Issue tags: +views integration

Hello!

This is something we considered and its a good idea! But first we have to concentrate on basic features.

If someone can help on this with the views part it would speed things up. For any information contact rsvelko

Ivo.Radulovski’s picture

Version: 6.x-2.0-alpha1 » 6.x-3.x-dev

we have rewritten the module - i think soon we could think about this

WorldFallz’s picture

Status: Active » Closed (won't fix)

imo this is out of scope and definitely stretching views.