[TYPO3-dam-devel] RFC #9552: Clean Up Click Menu

[Dan Osipov]

Attached is the modified patch. The only thing that has changed, is that 
the "Edit File" command available on text files has been moved to the 
file operations section, before the "Rename File"

Please approve!

Dan Osipov
Calkins Media
http://danosipov.com/blog/

Uschi Renziehausen wrote:
> Hi dan,
> 
> Dan Osipov wrote:
>> Ah - I didn't test it with text files... I will rearrange the icons.
>>
> 
> k, what is your prefered version, edit file under file operations or 
> simply the last one in the first section.
> 
>> As for the name - the right click menu is supposed to be easy to use, 
>> and if we start putting long descriptions into them, it would defeat 
>> the point. All the options are available elsewhere in the module, so a 
>> description can be found there. Here the icons are more critical. If 
>> you find a better label, that doesn't blow out the menu, let me know.
>>
> 
> Having the icons described elsewhere is not what I do count as 
> intuitive. The info has to be short but precise and consistent. As I see 
> your point in labels being too long and have no brilliant idea at the 
> moment I'd say that we leave the wording (and icon) stuff to another 
> round of patches. To find satisfactory and consistent wording solutions 
> is a task quite often underrated ...
> 
>> Side note: I'm re-doing way too many patches.
> I do feel with you. And they are getting into trunk far too slowly. It 
> gives me a hard time to merge the stuff pending in this list to get a 
> working installation.
> 
> 
>> As I read in one of my first CS books, "Weeks of coding can save you 
>> hours of planning".
> 
> *LOL* I love this one! Do you have the full bibliographial data for me, 
> please?
> 
>> So I would really appreciate having a concrete list of things to be 
>> done by a patch prior to sitting down to code it. Unfortunately, right 
>> now the discussion starts only after the patch is submitted for review.
> 
> I am sorry and I do feel with you. Apart from the usual reasons (not 
> enough time to dig into a problem really carefully) I think one of the 
> reasons is that DAM is (at least in parts) kind of terra incognita to 
> *ALL* of those who are working on it, with the following effect:looking 
> at the surface of problem A you do not know what might be the impact on 
> problem B, at least this is my personal experience. Also the people who 
> are in the team are quite heterogenous in terms of t3 abilities in 
> general and dam in detail.
> Perhaps we should try to develop a culture to describe problems on every 
> level in more detail (screenshots, for the uschis and the bens, for the 
> bennis and the dans and the stans) to come to decent specs?
> 
> I am sure we will all learn and succeed in the end, but it is a process.
> 
> 
>  I have
>> no problem correcting my own mistakes, but I don't want to adjust it 
>> to individual tastes, especially if it could have been decided prior 
>> to coding. Don't know how to approach this problem, but its an issue 
>> that takes a lot of my time.
>>
> 
> Individual tastes in a project like this one should never play an 
> (important) role! Please believe me that I at least try to have in mind 
> different people with different needs when I make complaints about this 
> that and the other.
> 
> My five cents, Uschi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 9552_v3.patch
Type: text/x-diff
Size: 6365 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-dam/attachments/20081128/b814efb4/attachment.patch