Idiosyncratic patterns

+status

+needs

Sometimes you want to structure things in a more complicated way than inclusions in text (structure) or a simple list of cards (Pointers, Search).

For example, the menu of cardtypes when you add a card can get crowded, and even in a Wagn without custom cardtypes could be chunked and/or ordered.

And when you want to have Settings portrayed in a set of logical chunks, it would be nice to be able to specify that structure in Wagn in one card and use it many places.

There's also some interest in specifying two-dimensional layouts (e.g. tables or columns in HTML), but that may be beyond the scope of this blueprint.

is there a unifying theme? Almost seems by the idiosyncracity that this isn't unified enough for a blueprint -- what makes it more than a collection of ideas?

It is 'just' a collection, coming together with the organizing tag.

I'll just delete this next time I see it.

--John Abbe.....Wed Feb 16 12:25:45 -0800 2011

I'm going to add a status to blueprints so that we can close them. I also just tried to get a bit more specific here about what qualifies as a blueprint.

In this case, I think what we want is just an idiosyncracy tag. However, we may want to organize tags a bit more ;)

--Ethan McCutchen.....2013-02-25 16:20:56 +0000

Also see:

sharks

monkeys

platypuses

everyone

Idiosyncratic patterns

+needs

sharks

monkeys

platypuses

everyone

Idiosyncratic patterns

+needs

+discussion

+tickets for item