> De: Timothée Giet <[email protected]> > So first topic, we discussed with Zelgadis at LGM about fixing the > terminology used in Synfig, as in some place we could use more specific > terms, that could fit better, be less confusing, and so enhance the synfig > experience. > So first I'd like to know if everybody would be ok for such change. > > Then we would need to agree on a list of the terms to change, and on the new > terms to use. > > So as Zelgadis told me he already have a sort of list of names to propose, > so he can start by sending it here, then if others have suggestions to > complete or modify, just say it.
Hi, Timothée! Here's my list: * Duck -> Control point * Curves Panel -> Trajectories Panel (or Graphs Panel ?) * BLine -> Curve * Groups -> Sets * Encapsulate -> Group I think those ones are already enough. Also we have "Paste Canvas" - "Inline Canvas" - "Exported Canvas" thing that is a little bit confusing for users. > Then only at the end when everyone is ok with the final list, we can start > the huge task to rename everything in the code/translations/doc. > This is another part of the problem, but we'll see then. 2012/5/11 Carlos Lopez Gonzalez <[email protected]>: > Also I would like to mention that do a global change on the code is not a > big deal with the modern edition tools and search and replace all the > occurrences of one string is not so difficult. Other thing is that there > were variations of the same word (shortened for example) and we want to > replace by other. This might be done manually. I don't know about wiki and > its complexity on changing strings. For wiki we can do global search and replace, but I'm not sure if it will work everywhere. We need to be careful with that and of course the work with proofreading all stuff is still required. > Finally I would like to know if this terminology fixing will cover the code > variable names too. It can be done but it is an internal thing that wouldn't > affect others than coders. I personally would prefer to take time > documenting the code instead of change the name of a variable or class. Also > change the code terminology implies to understand it first, which is a > requisite to have it well documented too. My suggestion is to go with the same way as we did for Zoom/Scale layer -> leave variables untouched. At least for now. Cheers! K. -- http://morevnaproject.org/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Synfig-devl mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synfig-devl
