Hi Peter, Peter Klein wrote: > "Jigal van Hemert" <ji...@xs4all.nl> wrote in message > news:mailman.1.1249587591.27405.typo3-engl...@lists.netfielders.de... >> Peter Klein wrote: > >>> The manuals haven't been updated in several years. (I guess it's more >>> profitable to write books), so you'l have to dig into the core source if >>> you really want to understand TYPO3. >> I don't think it's a matter of books being profitable. If there is only >> electronic documentation available people start asking "isn't there a >> good book?", if there are mailing lists and newsgroup people start asking >> about a forum, ... > > A search on www.amazon.de, gives me a result of 65 TYPO3 books!, so there > must be some reason why people write books rater than opdating the official > documentation!
This doesn't tell me a lot, except that there are enough people who want to buy a book. > If you look at the official TYPO3 documentation, then you'll see that some > of the major docs, haven't ben updated in 5-6 years! > > Backend Programming - last update: 29.11.2002 23:29 > Frontend Programming - last update: 29.11.2002 23:29 > TypoScript Templates - last update: 30.11.2002 03:36 > doc_tut_quickstart - last update: 22.07.2004 17:55 > Basic Extension Tutorial - last update: 26.07.2004 20:09 Oh come on, you are very selective: Typo3 Installation and Upgrading - last update: 04.01.2009 13:17 TSref - last update: 13.05.2009 18:12 TSconfig - last update: 01.12.2008 01:59 TYPO3 Coding Guidelines - last update: 03.07.2009 11:57 Inside TYPO3 - last update: 01.12.2008 01:49 TYPO3 Core API - last update: 01.12.2008 01:40 > Reporting issues on bugtracker doesn't have much effect. Bugs I (and others) > have reported several years ago, still exist in present TYPO3 versions. Just > try sorting the bugs by date, and you'll get the picture. > It looks like there's more interest in adding new features to TYPO3, rather > than fixing old bugs. :( Many of the old bugs are already fixed or for other reasons (code has been replaced by something different) not relevant anymore. Other things have never been tested. Most people can help out testing bugs, confirming them, maybe finding out where the problem exactly is, writing a patch, etc. There were two old bugs (with a patch) in automaketemplate; my employer got the key transferred to him and I updated the extension in TER. Not too much work, but somebody just has to do it... > How do you expect someone (except the core team) to write better/updated > documentation, if they don't know of the new features? As you can see earlier, core documentation (TSref, core api, etc.) is pretty recent. It's the documentation for beginners which can use rewrites. This can be done by people who are not core team members. Other documents like Modern Template Building or Futuristic Template Building could do with new screen shots and descriptions which correspondent with the latest interface, but you can still follow the turorials without major problems. -- Jigal van Hemert. _______________________________________________ TYPO3-english mailing list TYPO3-english@lists.netfielders.de http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
