🚀 go-pugleaf

> In sum, my sense of what I read on this list is EndNote is being used in new
> ways; that's fine, and good, but also means that people posing "problems" to
> Niles should start w/ some awareness that those whose develop new uses for an
> application can't expect the designers of the application to have foreseen
> all their needs!
> 
> Greg.Finnegan@Dartmouth.edu

I aggree, use the right tool for the job at hand. For example, I use
WriteNow as it does everything that I need almost ALL of the time. If I
need layout capabilities I export to a DTP application. So with EndNote,
for text citations, reference lists, etc, it is wonderful. If I need
database capabilities export the data to a decent relational database. 

The "problems" are:
1. that applications like EndNote and WriteNow are so much easier to use
and wouldn't it be nice if these other applications were as simple.
2. we all have individual needs that we cannot see implemented elsewhere,
or have the time to create them, so why not add them into our favorite
application.

Some "solutions" are:
1. Niles should keep a crticial view on the ramblings of users in
newsgroups (they are not necessarily the majority of users). Many a good
program has been spoilt by feature creep. 
2. If there appears to be a need for more database capabilities then this
is an opportunity for a Super EndNote Plus Plus or, more sensibly, improved
interchange with existing database software. As one poster has pointed out,
and supplied an example, the latter could be achieved by templates for
various databases.