Added ability to control the "grid width" used with Arrange Fields.
 It is on the settings page.  Default is 10px.  If set to 1px, this
 allows users to move fields with a complete freedom of movement.
 Based on issue: http://drupal.org/node/1456534

2-22-2012
 Changed how the Arrange Fields style tag is set, as well as how
 the form is targetted in CSS to be more specific.
 based on advice from this issue: http://drupal.org/node/1450450

 sometimes have a height of only 1px.  To this end, this module no
 longer attempts to set the height of textfields, only textareas.
 The orignal issue is: http://drupal.org/node/1241750

 that CCK fields have, so you can edit the properties of the field w/o having
 to leave the page.

 Cleaned up the code a bit, removing unused or old functions.

 though, until webform 3.0 moves out of beta (I am afraid of their code
 continuing to move around, and then I will have to keep making changes to catch
 up).

 the initial javascript and css bugs which some new users experience.

 the default with all themes, and sometimes they look funny w/o it.
 Of course, this can be overridden in the theme's CSS files.

 of when to add a draggable wrapper to a CCK element.  For most elements, the way I was
 doing it worked, but not for "imagefield_widget" for some reason.

 Fixed a bug where the submit/preview buttons were not being disabled during arrangement.

 up the label, if the label was a certain length.

 CCK content types you can arrange, as it was a little confusing
 and shouldn't have been in the list anyway.

 Placement of buttons on a CCK form now work the way they did in
 the alpha releases; that is, you do not position each button separately.
 Instead, you drag the "buttons" wrapper around, and all buttons will
 appear there.  This is to fix a bug where the Delete button and Diff's
 View changes button were not arrangeable w/o major kludgy hacks, because
 those buttons only appear on submitted forms.  This change in code
 is a compromise-- I would rather each button be arrangeable, but since
 I can't forsee every possible button that may be there (placed by
 other modules), this is the best way to ensure they will all be arrangeable
 as a whole.

 Took t() off menu items to be in complience with:
 http://drupal.org/node/323101.

 using to save position data, I have converted that textarea back to a regular
 hidden textfield with a very long length.  I had to make a few javascript changes
 to get that to work too.

 to a CCK function.  This was a holdover to when this module was for CCK only.

 being added twice.

Fixed a bug where, for webforms, the submit buttons were not getting a draggable handle with an icon.

 Added the "add markup" button to webform as well as generic forms, not just CCK.

 regardless of how many levels deep they are nested.  I still can't guarantee
 that it will work on $form arrays with very complicated structures, but it
 at least lets you have 2 or more levels of nesting w/o causing a problem.  This
 is mostly for custom forms which the developer herself might have created.
 $form's from CCK and Webform have never used nesting in this way.

 Fixed a bug where javascript couldn't save the form correctly.  Happened
 after you make changes to a CCK field in the popup, then close the popup.  It
 was supposed to save the form, but it wasn't doing it correctly.

an HR, or any other valid HTML, anywhere you want.

 fieldset.  Also, added some new CSS styles (and a new Configure image
 thanks to the mini set at famfamfam.com).  Also, tightened up the look
 of the config dialog.

 Made it so you can set width and height of fieldset wrappers, which will
 possibly correct some ugliness without needing the user to go edit
 CSS files themselves.

Made some more javascript bug fixes.  Also, added in the admin settings form which lets users edit any form, not just cck and webform.

Fixed a bug with my jquery selector and IE, so that IE users can now use the resizable() function without a problem.  No other code changes than that.

 which lets you change the width and height of the wrapper, as well as whether
 or not the label is inline.

 Also, added the menu items to let you edit any form, though this is still not
 well fleshed out.

After doing a lot of cvs testing, I am refreshing this branch with my latest files.  should be the same as the alpha6 release files.