fluidcontent vs. gridelements

fluidcontent gridelements + Spalte hinzufügen
Fluid Content Engine Grid Elements (Typo3 Extension)
Kategorie
Weitere
Beschreibung Flexible templating and logic engine for TYPO3 enterprise CMS ?
Tag Enterprise CMS, development framework based on FLUID and EXTBASE for TYPO3 ?
Mehrbenutzersystem Ja Ja
Pingback Bedingt ?
Extension/Plug-in Bedingt ?
Betriebssystem
Programmiersprache
Datenbank
Webseite fedext.​net typo3.​org/​extensions/​repo…gridelements
Trackback Bedingt ?
Mehrsprachiger Inhalt Ja Ja
Datenbankmodell
Unicode Ja Ja
WYSIWYG-Editor Ja Ja
Multiple Projekten Ja Ja
Standardkonform Ja Ja
Externe Seiten Ja ?
Benutzer-Statistiken Ja ?
Versionierung Ja Ja
Software-Distribution
Template Language
Zielgruppe
Volltextsuche Ja Ja
Design Pattern
Anforderungsgrad
PSR-0 kompatibel Ja Nein
Object-Relational Mapping (ORM) Ja Nein
Documentation level ★★★☆☆ ★★★★☆
Codezeilen 1,05 k ?
Comments Nein ?
Multiple categories Ja ?
Hierarchical menus Bedingt ?
Kostenlos nutzbar Ja Ja
Supported VCS
Versionierung Gut Gut
Input Widgets Ja Nein
Datei Assets Ja Ja
Data storage
Implementation flexibility 50% Votes 50% Votes
Free for commercial use Ja Ja
Sexiness 100 100
Full workspace support Ja Ja
FAL support Ja Ja
drag'n drop Ja Ja
Dynamic Fields Ja Ja
Native Drag-n-Drop Ja Nein
Extension Base
Value-to-Object Transformation Ja Ja
Inline Assets Ja Ja
Drag In Ja Ja
Unused elements Ja Ja
Reference content records Ja Ja
Reference pages Nein Ja
Reuse TV DS Nein Ja
Copy from another page Nein Ja
Paste copy into columns Ja Ja
Paste reference into or after Ja Ja
Drop copies Ja Ja
Flexforms Ja Ja
Content Preview Ja Ja
T3D Export Nein Ja
List Module Support Nein Ja
T3X Export/Import Ja Nein
Native layout wizard Nein Ja
Allowed content elements Nein Ja
Collapsible containers Ja Ja
Test Coverage 92 80
Overrides core functions Nein Ja
Overrides core modules Nein Ja
Normalized relations Ja Ja
Template Mapping GUI Nein Nein
TYPO3 CMS Version 6,2 6,2
+ Zeile hinzufügen ++
fluidcontent gridelements
  • vsChart ist wie ein Wiki

    Mach mit und teile dein Wissen mit der Welt.
    Zum Bearbeiten einfach in eine Datenzelle klicken.

  • blau
    = gut
    dunkler
    = besser
    Legende
  • Auf eigener Seite einbetten
  • Copy & Share
  • Creative Commons License Lizenz
  • EnglischDeutsch (German)

Bewertungen & Kommentare

  • 💬 Kommentar
    Comment: "Software distribution" refers to how content elements are shipped, not how the extension is shipped. In fluidcontent elements can be easily shipped as extensions downloadable from any package management source including TER. For gridelements the same is true, but requires a lot of custom setup in the shipping extension to be shippable as a "plug-and-play" style content template container extension.
    Claus Due09. Mar 2013 / 14:53
  • 💬 Kommentar
    Comment: "Data Storage" refers to how templates are stored - actual instances of content built on these templates are, as always, stored in the tt_content table.
    Claus Due09. Mar 2013 / 14:56
  • 💬 Kommentar
    Actually "Drag & Drop" should not be a Yes/No, but a link (native / custom). Actually it is a drawback to just have the native TYPO3 core drag & drop, since it can't do copies via CTRL key and it does not reload the page after dropping, which leads to a complete mess, whe more than editor is working on the same page.
    johasenau09. Mar 2013 / 15:13
  • 💬 Kommentar
    BTW: Some of the compared features are NO for 1.4 but will be YES for 2.0, since the TYPO3 6.0 core will require it, so having YES/NO is sometimes not enough for a real comparison.
    johasenau09. Mar 2013 / 15:15
  • 💬 Kommentar
    And a question: Is it possible to move rows up or down, so that they will be kind of grouped by topic?
    johasenau09. Mar 2013 / 15:16
  • 💬 Kommentar
    "Reuse TV DS" means that you will be able to use your old TV structures to compare connected children against your new grid elements IRRE listing after a migration. Of course these structures will require additional TypoScript if you want to get them into the frontend again.
    johasenau09. Mar 2013 / 15:38
  • 💬 Kommentar
    Comment: I have to select "yes" in "reference pages" and "reference content records" since yes, this is possible in FluidContent (by changing the attributes used on ViewHelpers which render content elements). However, it should be noted that this requires content to be selected in the element in a different way, using a reference field instead of actual child content. In other words, referencing a page's content from a Fluid Content element does not immediately allow that content to be edited as child content - not without a fair bit of customisation of the Widget involved in rendering the nested content Grid.
    Claus Due09. Mar 2013 / 15:42
  • 💬 Kommentar
    Comment: that "copy from another page" is supported by Fluid Content but not with the qualification "...without placing the content in the clipboard" - in this regard, Fluid Content only uses TYPO3 core functions instead of adapted versions which change the way these actions are performed.
    Claus Due09. Mar 2013 / 15:45
  • 💬 Kommentar
    Fluid Content does not replace or extend the List module nor the Page module, in actuality it replaces almost none of the native TYPO3 backend functionality :) wether this is a pro or a con is up to each integrator's requirements and wishes. One could certainly argue that replacing some of the TYPO3 functionality is desirable - but this is not the road taken by Fluid Content (which actively tries to avoid any changes to existing behaviours in the BE, quite contrary to gridelements).
    Claus Due09. Mar 2013 / 15:59
  • 💬 Kommentar
    "Paste copy into columns" is yes for FluidContent as well, had it not been for the one qualifier word "empty". Even the playing field, please, by not modifying the feature descriptions with this many highly specific qualifiers ;)
    Claus Due09. Mar 2013 / 16:09
  • 💬 Kommentar
    Another difference which doesn't really fit into a tiny evaluation-comparison:

    Fluid Content is not just about supporting child content elements. It enables highly flexible content elements of any type - child content support is merely a side feature, made easily accessible by the use of Fluid as configuration engine.
    Claus Due09. Mar 2013 / 16:22
  • 💬 Kommentar
    Actually if it's just the default core behaviour, a "yes" should not count. ;-)

    Of course anyone can fetch a copy form another page with or without gridelements and fluidcontent, but the core can't without having to leave the current page.

    And of course anyone can paste into a column, but the core still refuses to do so with empty columns.

    Some of the features of gridelements is to enhance the core behaviour by additional methods. None of the original behaviours is modified though, so actually this is the same for both.
    johasenau09. Mar 2013 / 16:30
  • 💬 Kommentar
    The original purpose of Grid Elements was to bring the native backend layouts of the TYPO3 core to the next level, namely content elements.

    Grid Elements are about structured elements and not meant as a replacement for FCE. So people looking for FCEs maybe should go for fluidcontent instead, but have to live with the drawbacks of Extbase then.

    Grid Elements are extending existing core methods within the hooks they offer (except the list module which we had to XCLASS) and are able to go for different ways of content rendering from modern template building over native TypoScript to Fluid. So if you want to be more flexible in your choice while still being very close to the core methods, Grid Elements might be the way to go.

    Still it would be interesting to find out, how we could connect the best of both approaches to get something absolutely awesome for the TYPO3 6.2 LTS version :-)
    johasenau09. Mar 2013 / 16:42

Bewertung oder Kommentar schreiben

Bitte einloggen (mit Facebook, Twitter or OpenID) um um dieses Formular zu nutzen.

Typ
Bewertung
Kommentar