Special:Badtitle/NS90:Talk:Kdenlive/UI Review/Thoughts on "For newbies: common habits of any software"/reply

As for (4) I don't see where the workflow to add transitions would be similar to adding effects? Or do you refer to being able to drop transitions on clips in the same way the user can drop effects on clips?

Copying transitions is already possible, while the workflow for effects differs: effects need to be pasted specially, as this would otherwise conflict with copying clips.

Most importantly, transitions differ considerably from effects: effects work on a single clip. Transitions work on tracks! They combine tracks. No, they don't combine clips. Did you ever needed to use the same transition across multiple clips on the same source tracks? Changing the workflow as you intend would break the existing workflow if done exclusively.

Agreed, there is a of understanding when it comes to transitions. But then, tracks are not layers ... albeit there's some experiment going on with respect to a new UI element tracks. But I'm not sure at this point that will improve the UI instead adding complexity.

2. Adding features is often not making software better. Take Microsoft Word. Take OpenOffice. Bloatware is a well-known term for feature-ridden applications. Also, Google has no upload UI but wants users to go through their pages instead of uncontrolled third party upload software. Why renventing the wheel?