Protection - show protected children elements

[arescope]

If the conference is public but has protected contributions, these should be properly indicated (by means of a qtip, for instance).

[pferreir]

The amount of code in the last commit is just overwhelming. I think it's clear we need a change of strategy here, otherwise we'll end up having 5 or 6 methods per type of object that basically do the same thing in different ways.

In my public repo, you can find everything up to the one but last commit, with some changes. I've made it look (I think) a bit nicer, but it's still lacking the display of public elements inside private events, as implemented by the last commit.

Me and Jose had a short discussion on the strategy to follow and the best idea we could get to was an O(1) structure (BTree, TreeSet?, dictionary, etc..) containing all the elements inside the event that do not follow the standard inheritance rule (they're "exceptions"). This could be then used to directly retrieve the elements that don't have a "predictable" protection status. This would have to be updated whenever setProtection() is called.

[jbenito]

commit: 8037867b7a1bdbe688912a5e282b1d91f7c3bc3b