Custom Navits Mod suggestion

[pegasus]

Okay, I got it. Needed to run another query instead, then build_options();

[pegasus]

The new version of CES Navbits Designer has finally been released.

This version uses no queries on runtime thanks to ElfMage's suggestion to use the datastore!

[ElfMage]

That's very cool. It will be interesting to see the feedback from the vb.org community.

[pegasus]

Well, it's not a very popular mod, since it doesn't have very many practical uses unless you have vbWiki Pro installed.

[ElfMage]

I was referring also to the generic one, the one that doesn't need vbWiki Pro...

[pegasus]

Yes, I know. But the only place I have used this outside of vbWiki Pro was in Search Results (to specify between Post or Thread results). If you know of any other places it would ideally be used, I'd be interested to hear about them .

[pegasus]

Okay, I added some new features for the next version which I think will let it be used in more scenarios.

Added *Advanced* presets NAVKEYS and NAVBITS.

NAVKEYS contains all the URLs to the page's default navbits, while NAVBITS contains the corresponding text.

Using NAVKEYS as a bit other than first or last elements will output all default navbits at that position. Using NAVKEYS N-n to specify N to start from and n to end on. NAVBITS will automatically adjust to output to correct text.

NAVKEYS (N-n) can technically be used on its own as a URL entry (this would have the effect of multiplying the corresponding text with each URL contained in the NAVKEYS range), although in most cases the effect would be undesirable. NAVBITS can likewise be used on its own, but because it is dependent on NAVKEYS for a range, a corresponding URL would be multiplied with every default entry contained in NAVBITS, making the effect slightly less desirable than using NAVKEYS on its own.

A potential use of NAVKEYS / NAVBITS could be removing categories and forums from in between default navbits, forumwide. In order to remove categories within a specific forum, a user would need the right Conditions of course, and a user-created plugin may then be required to split up the parentlist. Before this was only possible by creating a new set for every subforum and thread within that forum.

In addition, pre-parsing has been limited to presets FORUM_HOME, THIS_PAGE, and WIKI_NAME in order to allow for the use of script-specific variables in navbit URLs and text, which must be also listed under Global Variables. In previous versions of CES Navbits Designer, script-specific variables could only be used in the Conditions field.

The Navbits Designer is also more lenient: only the first element navbits are required in order to save a set (previous versions required both first and last). This allows users to edit the board element on index.php where there was previously no $navbits array.

[ElfMage]

That's very cool. You really have put a lot of effort into this new release.

[pegasus]

Thanks. Haha, I remembered today that back at Version 1.0.0, I didn't think there were any improvements that could be made.