[TYPO3-hci] Less ways to do it...

[Peter Niederlag]

Hi,

Ernesto Baschny [cron IT] schrieb:
> Michael Scharkow schrieb am 22.05.2006 17:53:
> 
>> just a few thoughts about making common tasks easier to solve by
>> *removing* stuff from the BE:
> 
> Yeah, I like the concept.
> 
>> 1. Remove page types completely (except for sysfolders, see #2), only
>> keep page properties. See the various questions about not-in-menu
>> pagetype *and* the property hidden-in-menu, or the question whether
>> shortcuts can have subtitles, etc. Basically, we should only have pages
>> that have certain properties, and those should be nicely arranged in a
>> tabbed interface.
> 
> This seem to be already proposed several times now. See your own thread
> "Less features, more future" in typo3-dev from oct-2005. :) I agree this
> fits nicely in this newly created group.

Woaw, pls no ;(

>> 2. Make a stricter distinction between pages and sysfolders. It has been
>> a best-practice ever since, but it should be enforced strictly: Pages
>> contain *only* content records and sysfolders contain all other records
>> but no content records. Any ambiguity as to where store stuff should be
>> removed.
> 
> Would be nice, but would break a lot of sites that rely on that (news
> related to a specific sub-part of a site stored in the "start-page" of
> that sub-part). A solution to migrate those sites would be to
> "auto-create" SysFolders under each page that has non-content elements.
> But this would also require template changes (uid's) and maybe even
> extension changes.

Waow II, I don't think I'd like that. I am even rather against this.
Trees and Content are Nodes, and yes ther are node:properties but
there's also a NodeType. And we already have that in various places (as
well as subtypes). I am very fine with that and rather like to extend
this. For example by a node-registry.


Well, alright some folks might know this is mainly driven by the JSR170
(java content repository) specifications. But anyway, I don't really
like this idea (removale /to drop) to much I must admit. :-<

>> 3. If we follow #2, we can remove the distinction between list and page
>> view: Pages default to page view and sysfolders to list view. no need
>> for any other options if the functionality (=clipboard and sorting
>> mostly) is there.

Some mechnismen to change the default-view component would really be nice!

> True, clipboard/copy&paste are some things that are not very reachable
> in the Page-Module. But you would always need to keep functionality in
> sync between TemplaVoila and "Modern" template building.

We need a clipboard in the FE btw!

[...]

Greets,
Peter
-- 
Peter Niederlag
http://www.niekom.de * TYPO3 & EDV Dienstleistungen *
http://www.typo3partner.net * professional services network *