[
Lists Home |
Date Index |
Thread Index
]
personally i like the context highlighting editors that don't do
anything except highlight context. so eg a tag is in a color and you
know you haven't entered the closing > because the whole page is in a
ghastly cyan. or red if you haven't terminated a string, etc.
not a bad compromise for experts. saves time without interfering :)
rick
On Sat, 2004-04-10 at 04:28, Bullard, Claude L (Len) wrote:
> That's the behavior of auto-complete in MS Access
> that causes extra quote marks when cutting and
> pasting too. Spend some hours hunting those down.
>
> The requirement is to be able to turn it on
> and off. It is also useful if the auto-completes
> are customizable. But they aren't useless.
> Many code editors do nice things like keeping
> up with all of the class methods and offering
> them as a select as one types.
>
> You do point out the right question: is it interfering
> with the flow of an expert because it is designed
> to help an occasional user?
>
> All the same issues came up when discussing SGML
> editors. Over time it was observed that experts
> eventually moved back to ASCII editors and on
> demand parsing for document types they knew well
> (they are experts) and back to the context-based
> editors (even had names like InContext, or Context)
> for types that they only use occasionally.
>
> Dedicated application editors are useful when
> the content types themselves require more than
> text knowledge; they require look and feel: the
> dominant characteristics of WYSIWYG. Again,
> graphics, real time animation, etc. Even then,
> highly associative data types still need more
> context checking (interference, race conditions,
> etc.), or the document type is too deep and
> broad for one to become an expert (eg, MIL-D-28001).
> And that is why subset DTDs and DTD-driven editors
> became useful when organizing an enterprise system:
> each authoring role created their own documents
> and these are later merged automatically.
>
> The most requested features for report systems
> is that the interface exactly match the typical
> entry pattern for a standard report. The rub
> is, that susses out to 'local standard' and one
> is right back to the high costs of local
> customization for otherwise shrinkwrap systems.
>
> No free lunch.
>
> len
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://www.oasis-open.org/mlmanage/index.php>
>
|
