Since version 1.0 was released back in 1995 we are approaching 30-year anniversary and I thought that it would be good to celebrate it with the "next big release", i.e. AmiBroker version 7.
If you have specific wishes regarding what you would like to see in version 7 please share your ideas in this thread.
Note that advertising of 3rd party products is not allowed.
Implementation schedule
Shows features already being worked on or implemented in the development phase for versions 6.90...7.00
No.
Description
Development Time
Status
Version
1
Text tool new "Use pixel co-ordinates" mode that allows to fix position of text to pixel coordinates so it stays in place when you move the chart (link)
Part 1 of support for translucency/alpha channel in QuickGFX (this is biggie as it requires separate new code for all graphical primitives). Part 1 covers most common Plot() styles
@Tomasz, for the aesthetic part, it wouldn't hurt to have RGBA colors to create graphics with a more sophisticated look by creating "translucency" type effects in charts and using gfx functions.
Gee, this is akin to finding a magic lantern on the beach.
These are the things I have thought about over the years, so I'll share them.
Having an ability to have one AB instance on a local network be a data server to our own projects/apps and other running AB instances on other computers. I was thinking, if the data storage and real-time data processing was in its own sole modular program, it could be multi threaded and asynchronous and utilize RDMA? Thus messaging and data pipe tie-ins galore.
A modular orders and positions program, which can "Work" an order once given from the host AB module. This would allow certain order algorithms based on instrument and dynamic immediacy based on the type of system? We could write execution algorithms, like.... Match the bid to buy for 3 seconds, if not filled then split the spread, if the market is moving offer plus 1c etc. Orders would run and be "Worked" outside of AB and report back to it etc.
An easy way to plot graphics, trades and other data on AB charts from external running program, easier than the SDK route?
Maybe a C# wrapper SDK for easier use? (Don't understand why C# OLE is worlds slower than a VB one, another topic no doubt).
An optional user definable database fields (Strongly typed so it can be easily implemented) as well as user defined option for a symbol info fields.
A global clock (historical) and RT? To automatically setup/build a Pad-And-Align Symbol (or make one unnecessary?), that builds itself based on lowest bar price resolution (Not tick obviously). Perhaps a alternative to move thru time with a master clock and time align evey symbol, no matter where it is traded. The symbol information would have the GMT of the data as well as any historical Daylight savings and align every symbol furthest to date-time line in the background. FYI, if you had a master clock that moved thru time across every instrument in an "as it happens" in real life, then it would be easy to support concurrent multi-systems testing and automation where each system can talk to each other. I.e., System(A) has an order to place for X instrument, do any of you other strategies System(B), System(C)...System(N), have the a position in the same instrument or a highly correlated one? Moving thru time would also allow multiple concurrent systems in differing data resolutions and asset classes all while managing system and over all risk and heat.
These ideas are probably too big, but I thought I would share anyway. Don't shoot the messenger lol.
A ASCII database (NOT imported option). If the user sets up one of these, the symbols are read in with the user definable format file as well as the file(s) root parent directory. An auto import toggle set would read in all symbol files that have changed size or modification date. Toggle off would mean data would be read in when symbol is selected or typed in. Another toggle setting would be for whether to save to data to AB local database. If toggle is set to import to local DB then AB could check the file size and file modification data against its saved last vales and if it is different then import it again other wise there would be no need to. If toggle is off then when the user type in the symbol it gets immediately imported into a chart. AB would store it's last file size and modification date etc. This would play nice with our ASCII databases we manage outside AB, without the need to manually import new data, or if we just want to view the chart, then it would just bring it in on demand.
"ABC" tool: lock text position of the text according to the coordinates on the panel, not just according to price/datetime (always visible notes on the chart).
Just few basic requirements which is badly needed:
(1) Heikin Ashi chart in basic charts
(2) SuperTrend Indicators and consider other few popular indicator
(3) Somewhere we need option to make the parameter window sticky on chart and concise
because sometimes we need to access parameter window frequently and also
don't want to give it much space
(4) Once we backtest in Analysis window, if we click on trade list, it should only
open chart window with parameter set as per analysis window, this is cause
of most confusion when we find why a trade is not matching with chart, and it takes a while
to realize that parameters are different.
(5) When running multiple analysis with same afl or similar parameter name string they got
changed from both analysis, mean changing in one analysis, result in change in another window
this is real problem.
(6) auto suggestion in AFL editor should include user defined variable also, this would be great help
(7) we can save some vertical space if user is allowed to mix menu bar and tools bar
because menu bar's left half is always blank
(8) new symbol should be dynamically created/deleted from AFL even if it is not present in database, I know it is both powerful and dangerous but for stock option symbol
it is required, normally we do this manually but it is monotonous and boring manual task and that's why right candidate for programmer.
Please ignore or give some hints if these are already done in other version, I am not so much updated. I will be sharing more as I will get the chance. Thanks.
Generally speaking things that are easily implementable in AFL like indicators or HeikinAshi charts are already available. AmiBroker is programmable for a reason so you can use formulas. HeikinAshi in AmiBroker was made available in 2004. It is essentially just 5 lines of AFL.
When you like somebody's else idea that is already present in this thread - consider giving it a LIKE (heart) on previous (original) post, instead of repeating the same thing. If you feel like you need to repeat please quote original or refer to original poster so it is easier to find original reference.
A.)Level 2 Data Support for IQFeed etc, and the possibility to code your own Depth Of Market (DOM) and other interesting ways to display the Level 2 Data. Despite the existence of Dark Pools, having Level 2 Data can truly help us Retail Traders to get an extra edge in Intraday Trading!
B.) beppe's suggestion - graphics with translucency, that would be very nice and useful.
Create/delete study ( line, rectangle ) with all necessary properties via AFL
Drawing studies outside visible bars without "Right extend"
"Freehand drawing" in transparent layer overlaying the "moving/realtime/live chart". it should be possible to draw outside the last visible bar/candle area.
I would like to suggest the integration of additional broker dat through their free/paid API. This would involve fetching data from brokers across the top ten countries globally. Specifically, for India, implementing integration with Zerodha would be highly beneficial.
Amibroker is an excellent platform; however, due to the cost of data, many users are transitioning to alternatives. Enhancing our data sources with these integrations would provide a more cost-effective and comprehensive solution for us.
You are right again, i created a new blank chart with price only and it works correct, so it is my mistake and i never recogniced this behavior in the past ...
Chart panes arranged vertically instead of horizontally. It makes more sense this way for some studies. I know it's possible to use multiple windows, but their borders are thick (or thin them ?)
Global AFL functions and procedures, precompiled and available for each script, as if they were predefined/native
A simple module system for AFL, to avoid name clashes between scripts, maybe as simple as using the script name as module name (like MyScript.MyFunctionDefinedInMyScript(...))
a struct type for AFL, to replace actual use of a mix of matrices and strings (easier/simpler)Recently introduced Maps serve this purpose
F4 search working similar to F3 search. Search across symbol, name etc. If possible, as we start typing, Amibroker should search across symbols and names.
Risk Reward drawings from buy point.
Predefined layouts with crosshair syncing and different intervals
Trendlines snapping to open and close. currently I can snap a trend line only to highs and lows only and manually change them.(available now)
Copying watchlist/favorites to clipboard in a comma separated format so that they can be easily pasted in other charting softwares. Currently I achieved this using 2 AFL's and a Batch job.
Apologize if any of these are already available in Amibroker and I am not aware of them.
I have wishlist for AFL Editor as well but I am reserving them until I test the latest version 6.9.
You might consider just added MAP type for that purpose.
x = MapCreate();
x["field1"] = ...whatever field value (can be string, number or array)
x["field2"] = ...whatever field value (can be string, number or array)
x["field3"] = ...whatever field value (can be string, number or array)
