[TYPO3-workspace] Why is it soo complicated???

[Tolleiv Nietsch]

Hi,

sorry for the late response, I actually hoped someone else would jump in.

Falk Kühnel schrieb:
> Hi Tolleiv!
> 
> Well i would gladly discuss this, as the current implementation is way too difficult for my taste. Is there anyone in particular, who feels closest to the workspaces? I would like to talk to them about what i think would be a better solution.

I assume that would be me - the workspaces team isn't really active in
these days (many reasons) and I assume there are only few people we are
willing to put their hands in the tcemain / EXT:version dirt ;)

> I would not like to reimplement the workspaces without a second opinion though, just to have it ripped to pieces because the core team doesnt agree ;) . And testing that stuff will be quite tough i think.

Whatever you'd like to do, that is possible. Just have a look at
EXT:version and EXT:workspaces. Remove these two extensions and plug
your own functionality (as an extension) into it.

> 
> And i dont have enough insight into the core at the moment to find all the places that need touching for this.

This would be the first step - read the documentations and the
wiki-pages related to it and try to understand how EXT:version works ;)
If you seriously plan to reimplement things with your ideas, that's the
only way to go.

This might sound harsh, but versioning is complex like hell and I've
rarely seen systems dealing with it properly. I've seen EXT:extbase
failing with much simpler scenarios and I failed myself to get
EXT:extbase ready for our versioning scheme.

So if you really want to jump into a new workspace implementation, I'd
suggest you bring up a standalone extension which works as a
proof-of-concept. It doesn't have to have a UI or anything, it "just"
has to show how your newly developed database-schema can be used with
the functionality you suggest.

The basic features it should cover are:

* a written down technical plan (prerequisite to enable teamwork)
* versioning of any record (including pages and tt_content)
* handling multiple versions of one record in parallel
* versioned moving of records while keeping the reference structure
consistent
* frontent or backend performance should not be influenced if workspaces
is turned off (as an example easy SQL filters like pid==-1 need to exists)
* (optional) migration path from the old to the new workspaces

Once again - don't take this as a harsh response but as a serious
advice. Once you've a prototype running, I think (re)activating the old
team and turning it into a Core module is possible.

Cheers,
Tolleiv


-- 
Tolleiv Nietsch
TYPO3 Core Developer


TYPO3 .... inspiring people to share!
Get involved: typo3.org