[TYPO3-english] License of the introduction package

Tue Jul 13 18:49:51 CEST 2010

Exactly Ron

yeah wec_contentelements are great and this is what fascinates people in
TYPO3. It is the multitude of possibilities this CMS gives to you. More than
any other CMS. The system itself isn't actually so difficult to explain as
90% of the clients don't need to know all the PHP or TS background. With the
wec_contentelements, combined with your framework for templavoila we have
IMHO the best starter approach at all BECAUSE it combines both worlds and
because it is already very well documented and ONLY a link from typo3.org to
those packages is missing!

Datastructure forth and back, we had this discussion already so often and
still mayor - or biggest - TYPO3 companies like AOE Media - to name only one
are promoting TemplaVoila others do the opposite well that is diversity and
this is good.

Ron's System is a "Twitter" inbetween. Here we can setup a site in no time
and we can teach people which come to us for TYPO3 Trainings and Workshops
how TypoScript and the traditional way of templating is working. After those
trainings they are able to maintain and program actually both systems even
they might got separated. Each system has got drawbacks and plus. Which
flavor everyone is using should be simply up to them. The TV and framework
for templavoila way is very well documented as already mentioned, so is the
way of standard templating when using the packages from mediatech. Both is
existing and its good and well documented, and lots of stuff you can
actually use in both systems or from both systems independently of what kind
of templating approach you have chosen.

Andi

On Tue, Jul 13, 2010 at 8:55 PM, Ron Hall <ronslists at busynoggin.com> wrote:

> Hello Again,
>
> This discussion has illustrated what is both the beauty of TYPO3 and the
> challenge of expanding its developer base.
>
> It is a beautiful thing that TYPO3 is so flexible. Not only flexible in its
> front end output, but also flexible in the different ways a developer can
> achieve that output. It is truly a content management framework not simply a
> content management system.
>
> But a highly flexible system is more difficult to explain to a new person.
> It is always good to make it as easy to explain as possible, but it will
> never be as easy to explain as a simpler, more rigid system. But I will take
> TYPO3 over a simpler, more rigid system any day.
>
> Templating is a prime example of this flexibility. Each of the TYPO3
> templating methods has its strengths and its warts. Personally, I have used
> pure TypoScript, auto-parser and TV. I like them all but find challenges at
> times with each.
>
> In fact, I really consider my current approach as a hybrid.
> 1) TV as the backbone to tie everything together
> 2) TypoScript to handle the majority of layout changes site-to-site
> 3) FCEs to handle content elements that contain other content elements
> (like columns and modules)
> 4) Create extensions for custom content elements using the API provided by
> the WEC content element  (this has taken over 90% of what I used to do with
> FCEs and these extensions are created without PHP knowledge)
>
> Now this is what works best for me (at the moment), but does not mean that
> it works best for everyone.
>
> For those not familiar with the API provided by the WEC content extension
> -- which is probably everybody :) -- you can check these two links.
>
> http://lists.typo3.org/pipermail/typo3-project-v4/2010-March/000051.html
> http://bugs.typo3.org/view.php?id=14015
>
> Thanks,
> Ron
>
> Twitter: busynoggin (general web tweets)
> Twitter: typo3ron (for TYPO3 specific tweets)
>
>
>
>
>
>
>
>
>
> On Jul 13, 2010, at 6:37 AM, JoH asenau wrote:
>
> >> As I have only ever used TV, I'm not clear on whether things like
> >> flexible backend layout and FCE's are available to
> >> Automaketemplate/Jetts. EG it's easy in TV to create a 2-col FCE
> >> which can be easily populated by editors and, in the backend,
> >> displays appropriately as two content columns. Similarly with more
> >> complex FCE's you can augment how the content containing areas appear
> >> in the backend to make life easy for the editors. Are such things
> >> possible / going to be possible with Jetts, or is it only really a
> >> solution for simpler sites? I've looked at IceBox/IcePack, but it
> >> doesn't seem to be quite on a par with TV.
> >
> > ICE Pack was never meant to be a replacement for FCE, since it is
> following a completely different principle. So of course it's not quite on
> par with TV ;-)
> >
> > FCE will create fixed structures for different content elements that then
> can be used by editors only in the way they have been defined. So actually
> they are not flexible but restrictive when used.
> >
> > ICE will give the editors the option to freely combine default and
> special ICE elements based on IRRE features of the core to create individual
> elements on their own. Additionally ICE will give you a user interface to
> easily create GIFBUILDER based graphical headers without knowing TypoScript
> at all. Last but not least it contains ICE flavors, which is the successor
> of fancy corners and will let you create fancy styled content boxes that you
> can assign to any kind of content element.
> >
> > The major difference is that ICE will work for both TV and non TV based
> sites, while FCE aren't available outside the TV world.
> >
> > If it's just about having a matching backend layout you should take a
> look at this one:
> > http://www.youtube.com/watch?v=SsxfNd4TYbk
> >
> > It's already in use as a prototype here:
> > http://www.charles-voegele.com
> >
> > Current plans are to have this ready for 4.5 and there is a forge project
> for it called "modernbe".
> > Could be interesting to combine it with Jetts to get a real TV successor.
> >
> > Have fun wiht it
> >
> > Joey
> >
> > --
> > Wenn man keine Ahnung hat: Einfach mal Fresse halten!
> > (If you have no clues: simply shut your gob sometimes!)
> > Dieter Nuhr, German comedian
> > Xing: http://contact.cybercraft.de
> > Twitter: http://twitter.com/bunnyfield
> > TYPO3 cookbook (2nd edition): http://www.typo3experts.com
> > _______________________________________________
> > TYPO3-english mailing list
> > TYPO3-english at lists.typo3.org
> > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
> >
>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
>