> I would be interested in the opinion of other developers. I would keep the
names they were because I like the idea of speaking names instead of prefixed
method names.
IMHO if you're adding lots of prefixed methods it's to keep a conceptual
separation, which is fine if there's only a few methods in the object
overall but when there's lots of other methods it's often better to use a
separate object, e.g. myWidget.getAnimation().fadeIn(). This has the
advantage that the API can grow without naming conflicts and that API docs
are collected together for example, all properties and methods and events
related to animation would be in one place (which is what I think Franck
wanted to achieve) rather than mixed in with everything else just with added
prefixes.
Personally I prefer the speaking names style and I prefer to not change the
API names unless there's a really good argument for it (or the API is hardly
ever used), so I'd leave it as it is unless the methods were to be
abstracted into a separate object
John
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
