[TYPO3] Content condition

[Tyler Kraft]

Hi

> Yeah, figured it out myself a view minutes ago.
> and i think thats a great example which shows what the difference 
> between a "complete" and a "good" documentation is.

Ace! :-)


> You and i as plugin developers know that plugins treat the [] in urls 
> like arrays, but there are a lot of people who havent a clue how piVars 
> are treated by TYPO3.

I'm not a developer. I do think, even thought it is plainly written 
there, that this is one place they should add another example - similar 
to the one in question.


> Another point is the structure of the documents:
> if i want to know something about "globalVar" conditions, i dont want to 
> read through the "globalString" section (i probably even dont know what 
> a "globalString" is...)

But thats what  reference is! When you go to wikipedia (or any other 
reference like a dictionary or an encyclopaedia) and you're reading 
about "cars" it doesn't have a discussion there about the internal 
workings of a diesel engine - you'd have to go look that up else where ;-)

Just my 0.02

> Its completely clear to me that a big complex system like TYPO3 is hard 
> to document in a way everybody can use it, but its not hard to find 
> issues on bad usabillity here.

I don't know, I think it could be improved but I also think it's pretty 
good in the grand scheme of things. Much better than a lot of open 
source and non-open source software.

Ty