QualityCentral

Public Report

Report From: Delphi-BCB/IDE/Open Tools API [ Add a report in this area ]

Report #: 75698

Status: Reported

Wizard for Wizards

Project: Delphi

Build #: 12.0.3420.21218

Version: 12.1

Submitted By: m. Th.

Report Type: New Feature Request

Date Reported: 7/12/2009 11:06:58 AM

Severity: Serious / Highly visible problem

Last Updated: 7/13/2009 7:53:47 AM

Platform: All platforms

Internal Tracking #:

Resolution: None

Resolved in Build: : None

Duplicate of: None

Voting and Rating

Overall Rating: No Ratings Yet

0.00 out of 5

Total Votes: None

Description

I had a look these days at the File | New... items and I think that a thing is missing there, thing which is badly needed.

Is a wizard to build IDE Experts/Add-ins.

Well, I don't know what amount to work is required to *fully* implement this but I'll present bellow my small analysis on theme:

Why should we implement this?

- Delphi is RAD, is about productivity, is about flexibility.

- big IDE plug-in market and important selling point, even if the feature is implemented partially (ie. only some plug-in types).

- the developer should concentrate on solving his _own_ problem not in figuring out how to code the infrastructure.

- building of wizards is 'scary', 'unknown', complicated and a lot from ToolsAPI functionality is unknown to the large user base. See

http://stackoverflow.com/questions/1102668/how-do-i-write-a-delphi-galileo-ide-expert

...and for the human factors:

http://chrisoleary.com/projects/TheParadoxOfPain/Essays/whatapita.html

- OTOH note that this thing is rather separate WRT to core code-base, hence testing is easier (no regresions etc.)

Also having a Wizard/Expert to start the things & do all the mundane work ('uses' clause, interfaces which need to be implemented, IDE linkage etc.) will break the ice in the plug-in development.

Steps to Reproduce:

None

Workarounds

None

Attachment

None

Comments

None

Developer Tools

Database Tools