$.serialize vs jQuery.param

[mbarkhau]

$.serialize vs jQuery.param

[imaffett]

I think the confusing part is $.serialize doesn't run on a jQ.Mobi object, but rather it's it's own function that takes in an object. jQuery takes in a selector and acts upon it.

I'm not a fan of making changes because "people prefer it", but I do agree this is confusing. We'll look into getting this changed for version 1.0

[mbarkhau]

My understanding from the naming was that jq.mobi would have a similar api to jQuery, but without all the ie compatibility cruft. So "prefer" was probably the wrong word. My expectation was that functions with the same name would do the same thing.

[imaffett]

Our focus is towards mobile devices, so there will be functions we will not implemented because they cause performance issues or are not relevant.

I've already renamed $.serialize to $.param locally. We will have a proper implementation of $().serialize for V1. If you find any other contradictions, please let us know!