Template Structures -- Rethinking and Request

[GoogleCodeExporter]

For gems and some other's like buyouts would it not be more clean to use a 
structure like so:

{Gems.Quality} <-- pull all gems matching .Quality as a filter
Take that further with: 
{Gems.Quality:20} <-- pull gems only with 20 quality

Other examples that could be handy for gems: 
Gems.Red (or Str) Gems.Green (or Dex) Gems.Blue (or Int)..

Similarly for Everything, would help with buyouts specifically with that being 
new and sort of limited..

{Rare.Weapon.Buyouts} <-- pull all rare weapons with a buyout 
{Rare.Weapon.Buyouts:"1 Chaos"} <-- pull all rare weapons with a 1 chaos buyout?

Also a filter to not include buyouts to help prevent showing item / objects set 
of items multiple times: 
{Rare.Weapons.HideBuyOuts} < -- to filter out anything with a set buyout?

And possibly in reverse if a Buyout is set for an item // object item set:
{Rare.Weapons.ShowBuyouts} <-- Display buyouts with reference to the parent 
object set, if no parent object set show all buyouts via just {ShowBuyouts}.

More or less break everything up into objects that can be tied to one another 
in meaningful ways

Original issue reported on code.google.com by jlmos...@gmail.com on 29 Dec 2013 at 8:30

[GoogleCodeExporter]

This is a good suggestion, but it would still come down to parsing the tags as 
text and would require a rewrite of the tag code.

The real problem is that everyone has a different way they want the shop code 
generation to work. Some people want to be really granular and have separate 
sections for everything, other people set a buyout for everything and just have 
{Buyouts} in their template as they don't care about the way the shop works, 
only that it's indexed.

With the current tag system and the new buyout system in 1.1.1, I've tried to 
make the most generic system that will cater for everyone's preference.

Original comment by stickymaddness on 2 Jan 2014 at 3:53

• Changed state: Done