--- Comment #11 from V Stuart Foote <[hidden email]> ---
(In reply to Heiko Tietze from comment #10)
> (In reply to V Stuart Foote from comment #9)
> > No, I would agree this is a reasonable capability to include for work needed
> > implementing a _Special_ panel function for Find and Replace.
> > The missing piece now is _exposing_ a graphic object....
> I don't get how we work. Do we wait for a commenter who agrees with an idea
> and implement all requests in the end? Usability is not to make one
> particular workflow comfortable.
Not at all, it is an enhancement and for such the threshold is appropriately
low. Describing what is a reasonable enhancement for implementation in core
framework is simply stating an opportunity for developer effort--whether it is
picked up or not will depend on its appeal to a developer, and some assessment
of its value to the project.
For issues we are able to develop ourselves we do so. For other more
challenging capabilities or refactorings we flesh out a recommendation, and
then answer questions developer(s) may have in implementation.
For controversial changes to GUI or work flow that impact the UX we ask the ESC
to adjudicate the requirements and development process.
In this case existing extension(s) are not very complete, and it is not clear
the SDK provides scripting hooks to support the needed capability. So I think
implementation in the core Find & Replace would be of interest to a potential
developer, and that it is certainly an enhancement of value to users needing
tools to edit their documents.