Before it happens, I'd like someone who was involved in the naming of
Layout Customizer to weigh in on that name change. More than the
other names, that one has caught on to a certain extent. I know I use
it in conversation all the time and a good bit of our documentation
early on used reorderer and layout customizer interchangeably (though
I know that shift reflects some fundamental code changes). Is there a
reason to change it?
BTW +1 Image Reorderer
Thoughts?
Jess
~~~~~~~~~~~~~~~~~~~~~~
Jess Mitchell
Boston, MA, USA
Project Manager / Fluid Project
[EMAIL PROTECTED]
/ w / 617.326.7753 / c / 919.599.5378
jabber: [EMAIL PROTECTED]
http://www.fluidproject.org
~~~~~~~~~~~~~~~~~~~~~~
On Sep 24, 2008, at 4:13 PM, Daphne Ogle wrote:
I change my vote to Image Reorderer. It wasn't on the table when I
initially voted :)
-Daphne
On Sep 24, 2008, at 12:32 PM, erin yu wrote:
Chatted with Anastasia - she thinks renaming (at least on the wiki)
is a necessary step, but we'd have to worry about backwards
compatibility. Renaming in the code wouldn't be terribly difficult,
but we'd have to be thorough.
Here are the responses so far.
Layout Reorderer
+ 1: Erin, Anastasia, Colin, Gary, Daphne, Allison
-1: Eli
Thumbnail Reorderer
+1: Erin, Anastasia, Colin, Gary, Daphne
-1: Antranig
Image Reorderer (as opposed to Thumbnail Reorderer)
+1: Gary, Erin, Allison
Erin
On 24-Sep-08, at 2:34 PM, Anastasia Cheetham wrote:
On 24-Sep-08, at 2:19 PM, Colin Clark wrote:
An alternative approach would be to provide an optional JavaScript
file that offers backwards-compatibility for such API changes. This
is very much inspired by John Resig's approach to API change in
jQuery.
Hm. I'm not sure I understand what this file would contain - the old
APIs wrapped around calls to the new APIs? I'm looking at the jQuery
code, and I don't see anything that looks like what you're talking
about?
--
Anastasia Cheetham [EMAIL PROTECTED]
Software Designer, Fluid Project http://fluidproject.org
Adaptive Technology Resource Centre / University of Toronto
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
Daphne Ogle
Senior Interaction Designer
University of California, Berkeley
Educational Technology Services
[EMAIL PROTECTED]
cell (510)847-0308
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________
fluid-work mailing list
[email protected]
http://fluidproject.org/mailman/listinfo/fluid-work
