Plugin Naming for 1.8

[Andrew Powell]

Hello All,

Please provide your input on naming for the following:

Input Mask Plugin

I'm presently planning a port of
http://digitalbush.com/projects/masked-input-plugin/ to jq ui. This
plugin is invoked by calling $(..).mask(..); It's original intent was
to provide input masking for text inputs. I've extended this to
include support for applying a mask pattern to other html display
elements (div, span, etc). Is 'mask' an appropriate name for this
plugin, or should we choose something more verbose like 'elementmask',
'inputmask', or 'masked'?

bgiframe

bgiframe will be ported to the jq ui framwork in the next few weeks
for testing. This has been planned for some time, per the wiki. Should
we choose a different name for this plugin to eliminate confusion
between the actual stand-alone bgiframe plugin and the plugin to be
used by jQuery UI?

DisableUI (http://wiki.jqueryui.com/DisableUI)

From the wiki; "Places a semi-transparent overlay over entire window
and makes all links and form controls in the main page completely
disabled (unable to recieve focus , out of tab order, etc.)" I am
planning an initial dev branch for a plugin which does just this and
will be making use of code already in the dialog plugin. It will also
be extended to allow for messages displayed within, and atop (zIndex)
the overlay. Since the verbiage used for this type of a behavior is
often simply 'overlay' (even the dialog plugin refers to it as such) I
would propose that we rename this as 'overlay'. Plugins such as the
dialog could then depend upon this plugin for that function.

Please do share your thoughts :)

Thanks,
Andrew

[Scott González]

On Fri, Mar 13, 2009 at 12:27 PM, Andrew Powell <pow...@gmail.com> wrote:

Hello All,

Please provide your input on naming for the following:

Input Mask Plugin

I'm presently planning a port of
http://digitalbush.com/projects/masked-input-plugin/ to jq ui. This
plugin is invoked by calling $(..).mask(..); It's original intent was
to provide input masking for text inputs. I've extended this to
include support for applying a mask pattern to other html display
elements (div, span, etc). Is 'mask' an appropriate name for this
plugin, or should we choose something more verbose like 'elementmask',
'inputmask', or 'masked'?

I'm okay with mask, maybe inputmask.  What's the use case for masking non-input elements?
 

bgiframe

bgiframe will be ported to the jq ui framwork in the next few weeks
for testing. This has been planned for some time, per the wiki. Should
we choose a different name for this plugin to eliminate confusion
between the actual stand-alone bgiframe plugin and the plugin to be
used by jQuery UI?

There has been talk about rolling this into the positionTo plugin, with the idea being that you only need this fix if you've positioned an element away from its normal position.  If we decide to go with this implementation, we won't need to name the plugin :-)
 

DisableUI (http://wiki.jqueryui.com/DisableUI)

From the wiki; "Places a semi-transparent overlay over entire window
and makes all links and form controls in the main page completely
disabled (unable to recieve focus , out of tab order, etc.)" I am
planning an initial dev branch for a plugin which does just this and
will be making use of code already in the dialog plugin. It will also
be extended to allow for messages displayed within, and atop (zIndex)
the overlay. Since the verbiage used for this type of a behavior is
often simply 'overlay' (even the dialog plugin refers to it as such) I
would propose that we rename this as 'overlay'. Plugins such as the
dialog could then depend upon this plugin for that function.

+1 for overlay

[Andrew Powell]

@ Scott

>> What's the use case for masking non-input elements?

The scenario in which I needed to be able to mask a non-input element
was as such:

Using the .mask() on an input.

The plugin is capable of returning the value of the input, minus the mask.
The plugin can also return the fully formatted value, based on the mask.

Because the mask can be changed by the person who is the acting admin
of the site. Say the admin wanted a phone number mask to be (###)
###-#### and then a week later the admin changes it to simply
###-###-####. So we store only the raw value in the database. Because
we're storing the raw value in the database, we need an efficient
means to show the data as the user expects. This is where the plugin's
ability to mask a non-input element comes into play. We retrieve the
data via an async call, put the data into a div and call the mask on
the div.

That's the gist of it.

:)

[Scott González]

That makes sense.