[TYPO3-doc] Reference of Typo Script
Peter
legine at gmx.de
Mon Mar 13 11:59:47 CET 2006
Hehe :)
Tyler Kraft wrote:
> I'm sorry - you've been "working with" typoscript for 4 days and you
> want to re-write one of the core/fundamental reference documents to the
> whole CMS!?!?
No. I want to have a discussion with the threat I do something.
I want something that goes beyond a a list of things that someone thinks Important.
I want something that tells me what I do not know what options you have at one
point. The current reference does not show this.
I want to be able to look at a code snipplet like:
# First level menu-object, textual
page.10.marks.MENU_GOES_HERE.1 = TMENU
page.10.marks.MENU_GOES_HERE.1 {
# Level 1: Normal state properties
NO.allWrap = <div class="menu1-level1-no"> | </div>
NO.stdWrap.htmlSpecialChars = 1
# Level 1: Enable active state and set properties:
ACT = 1
ACT.stdWrap.htmlSpecialChars = 1
ACT.allWrap = <div class="menu1-level1-act"> | </div>
# Level 1: Enable Spacer Menu Item (no link)
SPC = 1
SPC.doNotShowLink = 0
SPC.doNotLinkIt = 1
SPC.allWrap = <div class="spacer"> | </div>
}
And learn by looking into the Reference.
With the currently system this is simply impossible. At least I do not know
where I would like to understand what a active state is. (Yea I can thing of
something, but thats simply my idea, not that what typo3 thinks it is. I may be
right I maybe wrong.
>
> Not to smash your enthusiasm for wanting to contribute, and I'm sure
> there are updates and possible improvements to TSref needed, but perhaps
> you should just build a site first and then go back and re-evaluate this
> idea of yours. Being a newbie and having a hard time undersatnding some
> of the things in TSref does not qualify you - nor warrent you - to
> re-write a referrence manual that the whole community uses.
I try to contribute something in order to build my first side.
Of course I could fill me in by asking on the Lists. But when I read the
questions asked there I was frustrated right away because they were I had.
So I think that maybe I solve on step on the way and stuck with the next Problem
I have to ask. That cant be!
So I simpli need something I can work with without knowing how it is build.
I already worked through the tutorials. They are nice, they gave me a general
feeling how the Typo3 works and thinks. But I cant catch every graps I read in
there. And a transformation is hard since you get only told whats interesting in
that currently worked on problem. Not whats possible in general.
>
> Thats like training to become a pilot and on day 4 of instruction of
> basic theory you want to re-write the cockpit manual for a Boeing 757
> just because you don't yet understand it!
If I want to fly a B 747 I get a nice tutorial that explains me every button,
and instrument. I can get a simulator and train on it by actually fly a b 747.
I mean the terrorist on the 11th Sept done it exactly that way.
I know already a bit about CMS systems and PHP and stuff. So I can build on
little, as did these terrorist. But basicly you need something you can reference
to. I had my troubles and so had elmer and others on the list. And I think it is
because the reference is not as good as it should be.
I do not want to offend anyone the stuff is workable. If it would not be that
way it would not have a community this big. But I think that it could be better
and easier to get a grasp on. And I think I did not read a single post from
Elmer, Mathew or you that did not state this.
thanks for diskussing with me :)
Peter
>
>
> Peter wrote:
>
>> Hello,
>>
>> I do not like the reference offered in the typo3 documentation section.
>> http://typo3.org/documentation/document-library/references/doc_core_tsref/current/view/toc/0/
>>
>> I would like to start an alternate on the wiki similar to the html
>> Refernce of selfhtml.org.
>>
>> I am asking because I do not want to start f there is a exelent
>> reference around. And I would like to know if I there is anyone that
>> is willing to help since I only have 4 days of experience with
>> typoscript :D
>>
>> Thanks
>> Peter
More information about the TYPO3-project-documentation
mailing list