The codebase is simply composed of two parts, Core and pluginis “Elements”

Each draggable element is handled by a 2 files

• A javascript file that does the rendering and the event handling “Events are triggered by the core and passed down to each individual element”.
• A php file that defines what properties the element has, these information are used by the core to generate property page, this file is just meant to hold configuration parameters, no actual coding involved.

Adding a new element would just require writing two files and the core handles the rest.

I’m using Prototype, script.aculo.us and Webtoolkit context menu, No true AJAX has been used so far, everything is done on the client side.

Now the question is , what does the end user see?

• Drag and drop environment
• Context menu for each element
• Properties for each element
• Simple keyboard interaction “Selected element can be deleted by pressing the (del) button (except textfield and textarea)”

I’ve tested this on FF2 and IE6.

What I really need to implement right now is the “Resize” function

Why don’t you check A demo of the code in action

I plan to turn this into a Joomla! forms component soon Insh’Allah.

Update: My Proposal to Google Summer of Code has been accepted and I’ll be working on implementing this form editor as a Joomla! 1.5 component, You can find more information about my progress on my GSoC blog

I had no doubts about parseInt() I thought it was my code that’s causing this problem, I double checked everything and I finally turned to parseInt() ,Everything seemed to work very well “Before” parseInt() enters.

I check w3schools and found this

If the radix parameter is omitted, JavaScript assumes the following:

* If the string begins with “0x”, the radix is 16 (hexadecimal)
* If the string begins with “0″, the radix is 8 (octal). This feature is deprecated
* If the string begins with any other value, the radix is 10 (decimal)

so if the string begins with “0″ , the radix is automatically assumed to be 8 (octal) but it seems that this feature is still Not deprecated on FF 2.0.0.4 (not sure about IE) .

To fix this I had to force parseInt() to use Decimal numeral system by explicitly specifying the radix (10).

Example:

Update June 9th 2007: I’ve came to discover that this issue is very well known and well documented all over the web , The funny thing is that Microsoft’s Solution is based on “manual” approach “that is using a loop that removes every leading ’0′ by string functions!”, although specifying the radix explicitly would solve the whole situation.