[bookport] Re: new unit proposal
- From: "Kevin Jones" <kevin@xxxxxxxxxxx>
- To: <bookport@xxxxxxxxxxxxx>
- Date: Thu, 15 Sep 2005 12:42:29 -0500
Here's why I feel discussing resources,size, and cost are a good idea.
If users make lots of outlandish suggestions, the company is probably more
likely to ignore their suggestions; but if users understand how feasible or
probable a feature is, they can make more intelligent decisions on if they
should stand behind a suggestion or not. This would show the company that
their users are more serious when they strongly support a suggestion, thus
making their acceptance more likely.
Kevin
-----Original Message-----
From: bookport-bounce@xxxxxxxxxxxxx [mailto:bookport-bounce@xxxxxxxxxxxxx]
On Behalf Of Bruce Toews
Sent: Thursday, September 15, 2005 12:32 PM
To: bookport@xxxxxxxxxxxxx
Subject: [bookport] Re: new unit proposal
I think the discussion we've been having has been most productive. I also
can't think of another place where such discussion would be approrpiate.
Bruce
--
Bruce Toews
E-mail and MSN/Windows Messenger: dogriver@xxxxxxxx
Web Site (including info on my weekly commentaries): http://www.ogts.net
Info on the Best TV Show of All Time: http://www.cornergas.com
On Thu, 15 Sep 2005, Gary Wunder wrote:
> Folks, I'd like to respectfully suggest that when new features
> are presented here we ought to limit our comments about them
> simply to whether we like them or how better to implement them. I
> don't think it is our place to worry about the capacity of the
> unit - APH and Springer know about those things and if it can't
> be done, it won't. If APH doesn't think a feature will be worth
> enough in potential sales to justify implementing it, then that's
> their decision.
>
> I'd prefer to see more questions and less about reactions to
> reactions to feature suggestions. Can we refrain from telling one
> another the function of the BookPort, how some of us live in the
> stone age, and how still others want the BP to do everything. We
> have a wonderful product, a fantastic support team, and a list
> which has been a real source of good feedback and an instrument
> for learning. Let's not let it become a vehicle for argument
> please.
>
>
>
>
Other related posts:
