Drag and Drop in Jade.

[ConvertFromOldNGs]

by Carl Ranson >> Thu, 3 Feb 2000 21:09:27 GMT

I think there are pleanty of oppourtunities for drag and drop functionality in Jade.

for instance.

Drag a property to a class: Move/Copy the property.
Drag a method to a class: Move/Copy the method.
Drag a property/feature to the code window: paste the feature name or a method call template into code
Drag classes: Change heritage of a class (I realise thats a really tricky one)
Drag selected text in code window: Move code snippet.
Drag selected text to class or method list: add a new method containing that code

Drag selected controls to tab on a folder (without dropping): folder selects the new sheet so you can drop to a different sheet.

That last one deserves further explanation, it's inspired by a little know trick of windows. Try this. open two copies of explorer and maximise both. Drag a file from one to the button on the taskbar that represents the other - hold for a second. Windows brings the other window to focus to allow you to drop to it. Doing this for folders in painter would let you drag from one sheet to another. This is much easier than draging from the folder to the form, selecting the target sheet, reselecting the original controls and doing another drop to the folder.

Can anyone think of anything else that might be useful?

Regards,
CR

[ConvertFromOldNGs]

by Carl Ranson >> Thu, 3 Feb 2000 22:02:01 GMT

A further thought on the drag & drop classes case.
Presumably this feature would be much easier to implement if there were no objects for the classes in question -the class being dragged and subclasses, or the target class' subclasses.

Personally, I would be happy to accept this restriction if it meant getting this feature. Much of the time the classes are transient or the data can be rebuilt with scripts.

Any comments from the plant on the viability of this feature.

CR

[ConvertFromOldNGs]

by Dean Cooper >> Thu, 3 Feb 2000 23:01:14 GMT

Yes, dragging and dropping classes is viable with the restriction that the classes involved don't have instances. Without this restriction, depending on the kind of drags and drops you want to do, the reorg and inverse maintenance issues quickly can get horrendously complicated.

Dean.

[ConvertFromOldNGs]

by Carl Ranson >> Thu, 3 Feb 2000 23:05:58 GMT

Thats what I would have thought, I think its a fair enough restriction. Even with that restriction the feature would still save a lot of effort for those trying to rationalise a schema.

Care to put odds on it happening within our lifetimes?

CR

[ConvertFromOldNGs]

by Dean Cooper >> Thu, 3 Feb 2000 23:18:10 GMT

Care to put odds on it happening within our lifetimes?

Heck, I'm a developer, and you want me to commit to a date?

[ConvertFromOldNGs]

by Carl Ranson >> Thu, 3 Feb 2000 23:29:53 GMT

Care to put odds on it happening within our lifetimes?

Heck, I'm a developer, and you want me to commit to a date?

^^ Obviously I'm allowing for an error of plus or minus 25 years or so.

[ConvertFromOldNGs]

by Dean Cooper >> Thu, 3 Feb 2000 23:50:30 GMT

^^ Obviously I'm allowing for an error of plus or minus 25 years or so.

Ah, well in that case the odds are good! I might be retired by then anyway

[ConvertFromOldNGs]

by Craig Shearer >> Fri, 4 Feb 2000 2:56:06 GMT

You're too young to retire any time soon, Dean!

^^ Obviously I'm allowing for an error of plus or minus 25 years or so.

Ah, well in that case the odds are good! I might be retired by then anyway