--- In [email protected],
http://finance.groups.yahoo.com/group/amibroker/message/140225
"Tomasz Janeczko" <gro...@...> wrote:  (partial quote)
>
> Naive views/opinions/beliefs from most participants of this thread are
pretty much do not have any impact on development of
> AmiBroker
> simply because development plans are made many years ahead ...
>

Could it be that

1.  un-naive views/opinions/beliefs might have an impact?
2.  naive views/opinions/beliefs from _some_ participants might have an
impact?

  [:D]

More seriously, if development plans are made so very far ahead, I think
it shows great respect for and appreciation of customers when they are
told "what AB will never be" (to the extent that is already decided).

For example, that AB will never store bid/ask info between transactions,
is an important thing for some people to know, and a fair thing for them
to expect to know.

I applaud the communication of this sort of information (whether on the
List, or in the Feedback Center), because I respect the huge amount of
time and effort people must commit to learning a platform and using it
well.

People tend to naturally expect that _someday_ a platform will implement
what they view as obvious and necessary for (their idea of) successful
trading.

Yes, there are many and sometimes differing views on what is "obvious
and necessary", but the point is that if the platform's developer
considers something to be impossible, not desirable, or just plain "not
going to happen"  (whether the reason be technical, philosophical,
personal or business) then it shows a fair respect for day-by-day lives
of those that are paying up to support the developer's own livelihood to
pass on that info.

The fact is, no platform "does it all, today".  The decision to invest
time (and money, though the time is the most important) often involves
some consideration of "how close" a platform is judged to be to
completing the missing pieces (per a given user's perception).

--- Also in [email protected],
http://finance.groups.yahoo.com/group/amibroker/message/140225
"Tomasz Janeczko" <gro...@...> wrote:  (partial quote)
>
> ... and features you are discussing now were planned 3 years ago long
before ...
> ... Moreover they are on the Feedback Center for years already ...
>

I have long thought the existence of the Feedback Center to be one of
the strong points of AmiBroker customer relations.

Indeed, in the Feedback Center some suggestions are laid to rest
(status:  Won't implement).  Bravo!

However, many (most) suggestion items in the FC have a blank status.
What does this mean?

1.  The item was never read?
2.  The item (or item submitter) is deemed unworthy of a reply?
3.  The status to be assigned the item is still being thought about?
4.  The item has been read and will not be considered further?
5.  TJ is waiting to see if others will respond/endorse/modify/reject
the idea first?
6.  Something else?

IMO, best use of the FC would see a status assigned to every item.

I suggest:

a)  If "blank" has an actual meaning, then express that meaning in words
and assign it.

b)  If "blank" has any of several meanings, then express those meanings
as separate statuses and assign them.

As it is, blank seems to mean that the Feedback Center is being
read/evaluated/updated on a sporodic, ad hoc basis.  (This may not be
the case, but that's how it seems ...)

As per TJ's quote above, a search on "Planned" status suggestions in the
FC reveals a great deal of work already accepted in principle.

A search on "Won't Implement" reveals 83 suggestions so marked.

It makes sense to me that the community can only gain by making maximum
use of the Feedback Center tool, and that would require interested
customers to familiarize themselves with what is already planned, and
what is already rejected.

Seeing every suggestion in the FC assigned a status (at, say, a monthly
frequency or greater) would encourage this, IMO.

Finally, I would agree with those who often find that a discussion on
the List can prune and crystalize general notions into concrete
suggestions, which are then well-framed for the Feedback Center.



Reply via email to