Hello,

Thank you for your post. It makes perfect sense to me.

>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).

Generally there is agreement here. However making decisions in real world is 
not always as easy.
When I know that in advance that something won't be implemented I will tell you 
that (see FC "Won't implement" status).

However there are some ideas that are good ones, but not feasible at the moment 
for implementation because of dozens of reasons
including non technical ones. So some features may be put on hold until 
technology catches up or for example until market for particular feature
grows to make it economically worthwhile, etc.   

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

For freshly submitted items (within few days) it may mean that it was not read 
yet.
For older items it may mean:
a) the suggestion is a duplicated 
b) the suggestion is already existing feature 
c) it has not yet been decided what to do with this suggestion but the 
description is OK (not so long "not yet decided" status was added and it is 
used for such situation for new items)
d) the item is not well described and more info would be needed to decide
e) although suggestion may make sense, there is existing, easy AFL-based, or 
script based solution that does the same
f) it has been put on hold due to different reasons (see above) - (recently I 
added "put on hold" status for such cases)


I agree that giving all items non-blank status will give better picture and 
will work into that direction.

Best regards,
Tomasz Janeczko
amibroker.com
  ----- Original Message ----- 
  From: progster01 
  To: [email protected] 
  Sent: Tuesday, July 14, 2009 3:36 PM
  Subject: [amibroker] Ideas, Plans, Feedback Center




  --- 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?



  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