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

[Falk Kühnel]

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.

Mainly i would let all changed elements have the correct pid, which would allow to traverse through the workspace tree alot easier.

But thats just the tip of the iceberg. I personally think that workspaces are an absolute must have for a serious use in a larger setup, and even in smaller ones. And at the time being, workspaces are broken in 6.0 since drag and drop does not work.

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.

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

Best regards
Falk

Am 05.12.2012 um 00:10 schrieb Tolleiv Nietsch <tolleiv.nietsch at typo3.org>:

> Hi,
> 
> the only person to answer this is Kasper - "we" just inherited this code
> and structure and maintained it. But still you should answer how you'd
> provide the same feature set with the same base technique.
> 
> Btw. I turned you member request to the team down for now - you don't
> need to be part of the team (and have commit rights) to contribute. If
> you want to cleanup, feel free to send patches to Gerrit. Make sure your
> changes come with a migration wizard to make sure that old instances can
> be upgraded.
> 
> Cheers,
> Tolleiv
> 
> Falk Kühnel schrieb:
>> Hi!
>> 
>> I am still wondering, why the workspace records are handled soooo complicated.
>> 
>> First of all, why does a moved or created record not sit right in the correct position of the tree, where it belongs?
>> I still dont understand, why these placeholders are necessary. Could someone please explain?
>> 
>> A moved page gets a copy of itself with a new pid and the pid set to -1 and a state of 4.
>> This one holds the page info.
>> Then there is a placeholder, with another uid and pid of the new parent page and a move_id of the original uid.
>> 
>> Whats the reason not to let the page have a proper pid with its actual parent id, but use -1 instead???
>> Makes it way too complicated to get the parent page, or try to build a rootline.
>> 
>> Please help me out here.
>> 
>> Best regards
>> Falk Kühnel
>> 
> 
> -- 
> Tolleiv Nietsch
> TYPO3 Core Developer
> 
> 
> TYPO3 .... inspiring people to share!
> Get involved: typo3.org
> 
> 
> _______________________________________________
> TYPO3-team-workspace mailing list
> TYPO3-team-workspace at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-workspace

Liebe Grüße
Falk Kühnel

-- 
cogitatio - Ihr kompetenter Medienpartner

Am Lappenweiher 3
53127 Bonn

fk at cogitatio.de
Tel: 0228 - 3693699
www.cogitatio.de