[TYPO3] how to actually work with typo3?

[dave typo]

I'm pretty sure that everything typo3 is frustrating. TV or not.

The interface is pretty much terrible, and the hidden instances where one
must write code, or perform analyses, or grant permissions are convoluted
and illogical. And the dichotomy between what is possible/impossible in the
backend/frontend is frustrating as well.

I really think typo3 is a difficult product to use. Especially for the
audience of my site.

Ah well, I've managed to cope thus far, so it can't be all bad.

I really think gifbuilder is brilliant :)

and I think without TV typo3's learning curve would be much, much too
difficult.

just my two cents.


-dave

On 6/28/07, Tyler Kraft <headhunterxiii at yahoo.ca> wrote:
>
> Good morning all,
>
> Fair enough, everyone is entitled to there opinion, and I'm not saying
> your wrong, I'm only going on my own experience.
>
> I don't have time right now to write (or more so give lots of examples)
> what I dislike about it and I must admit that I've not looked at it for
> some time. So I'll be the first to say that I'm sure its probably
> improved greatly since I last used it, and that perhaps I should give it
> another go - but in the real world I have deadlines to meet and need to
> just do what works best and get on with it. For me and my employer it
> was not TV. ;-)
>
> About 2 years ago I used it for about 8 months and then left it again,
> and I've never gone back. Why did I leave it - Because I found it the
> most frustrating thing to use. I understood it and I got it to work but
> at the same time I found it very inflexible to use for most things I was
> trying to do. In theory I thought it was great as a concept,  then when
> I tried to make it work on anything that had what appeared to be any
> complexity - it just became a pain in the ass to use. The one great
> thing about it was that it allowed to have very odd or eccentric content
> elements, and that they were easy to create. But after stopping using
> it, it became just as easy to create the odd new content item if I
> needed it. I do admit it does allow the break up of pages into multiple
> columns or even single/multiple/single columns very easy, which is a
> very nice feature.
>
> Regarding it being more friendly, well again I didn't find it that way
> to use as a developer, and my users (some new to typo3 some used to the
> older method of using typo3) all found it very difficult and frustrating
> to use.
>
> Just my 2p, and if I have a chance this summer I'll go back and give it
> a go again and I'll come back to this if I still find it inflexible,
> frustrating and non-userfriedly.
>
> Ty
>
>
>
>
>
> Georg Rehfeld wrote:
> > Hi Tyler, all,
> >
> > Tyler Kraft wrote:
> >> ... at the same time - i find TV to be the most restrictive, least
> >> flexible, and most annoying way of doing ;- )
> >
> > TV actually was made to overcome _limitations_ of the older ways of
> > doing things, so I can't second your opinion, that TV is less flexible
> > than older methods (but I notice, you seem to not like it :-) , as
> > Dmitry already said).
> >
> > To start with: TV has a perfect isolation between designer and TYPO3
> > coder/admin, the designer just can prepare nice HTML/CSS with sample
> > content without any need to know TYPO3/TypoScript with the tool, he
> > prefers. The TV mapping done by the admin on that prepared HTML/CSS is
> > usually easy as a snap.
> >
> > And about flexibility: as the designer can prepare _more_ than one HTML/
> > CSS template and TV can handle that, the flexibility for different
> > designs is unlimited.
> >
> > And finally, when combined with FCEs (Flexible Content Elements) which
> > might be just containers (say for a 2 column layout in the #content
> > area) or elements for a special purpose (say a receipe with image, list
> > of ingredients and desciption) editors can compose their content very
> > flexible and intutive.
> >
> > So, IMHO, TV is _most_ flexible way of doing things.
> >
> > regards, Georg
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>