Now that ZOHO Creator has finally (a year after the initial suggestion; but better late than never) implemented the productivity-enhancing feature where Developers can have the scripting IDE start in Freeflow Mode (i.e. whatever was used last) ... there are a few other such productivity-sapping issues that were reported on this Forum before, but don't seem to be recorded on the Issues List ...

a) When you make a change to some script and click on a button to navigate away from the updated (but not Saved) script, ZOHO Creator warns you ... except in the most frequent usage pattern ... i.e. when you ask to Access This Application ... every few months, I lose about 20 minutes of work because I forgot to hit Save first !!!!

b) When you code something like input.myFieldX ... and myFieldX does not exist (perhaps mis-spelt) ... ZOHO Creator does not warn about this at Save time ... instead it changes it to myFieldX ... turning it into a Variable ... so naturally, the Application does not perform as anticipated ... and Developers have to go back and look for such auto-altered script code

c) The insertion point is hard to see on the screen ... why can the most followed item on an editable content be more visible ... a thicker or brighter color should not take months/years to implement ... should it ?

d) Finally, when making a "Delete this Field" request ... the corresponding "Confirmation" message says ...

Data corresponding to this field will be lost

etc. etc.

... it should explicitly name the field to be deleted ... this is because there are instances when ... the menu block that is popped up as you move your mouse cursor in the Form Canvas area ... will at times throw up the such a block for a field other than the one over which the mouse pointer was placed ... resulting in Developers deleting the wrong field.

Collectively, these problems sap the productivity of Developers ... and need to be addressed soon ... at least get on to the Issues List immediately.

Added Later:

Recently, I have noticed that when I ask to Save a Script section, it takes on avarage one second for every 6 script commands in the section (comment lines not counted).

Some of the Script sections for my HTML Views are around 100 to 200 lines of script ... so every Save takes 15 to 30 seconds !!! ... by comparison, the desktop Scripting Tool I use pseudo-compiles at the rate of over 500 commands per second.

Since the parser is not much help when you make mistakes in the syntax (e.g. often the error line is reported as Line 1) ... you have to Save after every small code snippet ... just to be able to zoom in (manually) to possible syntax errors.

Just another productivity sapping feature ... that needs to be addressed !!!

Gaev