|
Hello Brian,
Another of my old posts (2003) you refer to
;-)
As I said in last reply in AB world a lot of things
change in that time so many of the points you query have now been addressed
either directly or indirectly. Reading thru release notes history is a
useful way to pick up on features added/changed over time. I often miss things
that have sneaked in on a new release.
With reference to your list here is the current
status as I see it:-
1. Here I was suggesting a feature to make an
instant copy of an existing indicator. For example on indicator tree RMB gives
access to a Copy function (in addition to Edit etc...). This is just a
convenience suggestion - I tend to make lots of different versions of
indicators. You can of course achieve same by Edit existing indictor then Save
As - but this is less intuitive to me.
2 & 3. Formula Editor file open dialog allows
file list sorting as desired. The reference to builtin goes back to very old
version of AB where we had restricted number of custom indicator "slots" and a
number of standard builtin functions. This has all changed now. AB
ships with many standard indicators organised
into different folders by broad indicator type in the Chart tree. User is free
to edit or reorganise these as they see fit. Sometimes I wish the standard
indicators were either named in a way that immediatley identified them as
standard or they were write protected (I occasionally manage to inadvertently
corrupt one!)
4. AFAIK there are no issues now with AB Formula
Editor. Personally I use external editors to work with my code
files.
5. Quicklist was Metastock terminlogy for a
user defined list of favorite indicators which could be accessed
immediatley rather than trawling thru a huge list. With AB it is now easy to put
your favourite indictors into their own folder within the Chart tree for similar
fast access.
6. The paths for afl and #include files can be set
as required via Tools:Preferences:AFL
7 & 8. All AB code is now stored via standard
windows folders and files and can be manipulated with whatever tools you choose
(only very old version of AB had indicators stored in an internal
format).
Organisation of AB code files is really down to
user preference. Conventional suffix is .afl but I think you can use whatever
you want. In AB a single file can serve as an indicator, exploration,
system, optimisation test ... AB just uses the relevant content in the context
it is being used. There are pluses and minuses to this design but it makes
the onus of classification of file type purely with the
user.
HTH
John
----- Original Message -----
Sent: Monday, July 31, 2006 2:13 PM
Subject: [amibroker] Re: Indicator
Maintenance
Hello John,
Leaving the job of CEO firmly in Tomasz's grasp, from my
point of
view I agree with some if not all of your 'suggestions' in
principle.
Some are more compelling than others.
I think you have
covered all the possibilities but just in case
could you check my
list.
I might comment further once I am sure I understand what you are
saying.
I think some will need fleshing out a bit before submitting
them.
My interpretation of your list is:
1. copy/(paste?)
indicators
2. show date/time, uses built in code, uses formula
3. sort
indicators by (date/time as well as alphabetically)
4. prevent code
overwrite when loading
5. add an indicator quicklist
6. default path for
types of .afl files
7. share .afl files - export from AB and also import
directly to
default folders.
8. refer to .afl file by name in
formulas
Could you explain a little more on No2 - uses built in code or
uses
formula.
With code overwrite are you referring to when some
code has been
written and then if a .afl is opened or left mouse dragged
into
editor the original code is overwritten?
(It is interesting that a
.afl can be dragged into the editor and
its code is entered as long as
there is no pre-existing code).
What is your idea of a quicklist?
I like
the idea of a list of .afl favorites in editor where they can
be dragged
from a drop down list into the code and referenced by
name.
If you
wanted default directories for different types of .afl and
also import
into the default directory wouldn't that mean there
would have to be a
different default suffix for each class of
.afl?
Regards,
BrianB2.
--- In [EMAIL PROTECTED]ps.com,
"John R" <[EMAIL PROTECTED]> wrote:
>
> Having just corrupted some
of my indicators yet again I thought I
would post
> some personal
observations and suggested improvements on AB
indicator
>
maintenance. I am posting here rather than direct to the AB
suggestions
box
> to get the POV of other users. Hopefully others may be able to
offer some
> tips on best practice or point out the error of my ways
and also
if enough
> users chime in we can then compile a list of
agreed suggestions
for TJ to
> consider.
>
> OK here
are my observations:-
>
> It is *far* too easy to corrupt
indicators without even realising
it. I bet
> nearly everyone has
done this. For those who think you have never
done it
> try checking
thru the code of all your custom and builtin
indicators and see
> if
they contain what you expect ;-)
>
> In the early days of AB when
we only had slots for a few custom
indicators
> (20 was it?)
maintenance was not a problem. But with large and
increasing
>
numbers of indicators I find accurate maintenance a real problem.
In
> addition we have systems, explorations, scans, filters and
those
which do
> combinations. Over time I have tried various
methods of file
suffixes,
> prefixes, directories etc. to try and
keep things under control
but never
> been entirely happy with it.
My feeling is there must be a better
more
> organised solution with
maybe separate directories for these
specified via
>
Preferences.
>
> One of the big problems I have is indicators
getting out of sync
with the
> corresponding .afl file on disk. For
example it is very easy to
make an
> amendment to an indicator while
testing visually via charts/guru
commentary
> and forget to save to
the correct afl file on disk. Later when I
come to
> system test and
copy/paste the code into test afl from disk I get
unexpected
>
results. BTW I am sure the endless copy/edit/paste operations will
eventally
> drive me to complete baldness - my background is in
commericial IT
systems
> development so it goes very much against
the grain when you cannot
define a
> formula/module just once and
then just refrence it wherever
required. TJ
> has said he will add
this facility but will I have any hair left
by then ;^)
>
>
> Suggested improvements:-
>
> In IB add a Copy
button to enable a new version of an indictaor to
be
> created
quickly. Default new name = old name with numeric suffice
e.g.
>
HolyGrail[2]
>
> In indicator browse list add columns for date
and time last
modified. Allow
> sorting on name column or date and
time. At present you cannot
check dates
> or easily determine which
indciators you were last working on.
>
> In indicator browse list
add columns for In quick list, Uses
builtin code,
> Use formula
only. At present you must laboriously click down thru
every list
>
item to determine these.
>
> Provide some protection or warning
to prevent unintentional
overwriting when
> using Load.
>
> IMO indicators should be directly related by filename to the
corresponding
> disk file. For example the indicator HolyGrail7 is
defined via the
disk file
> HolyGrail7.afl Ideally AB preferences
would specify the directory
name(s)
> for custom and standard
indicators. This would prevent many
maintenance
> problems that the
current architecture invites and would also
facilitate
> many other
maintance operations (see below).
>
> Facility to bulk load
indicators from disk files into AB. i.e.
browse and
> select
multiple .afl disk files which are then loaded into
corresponding
>
custom or builtin indicator names.
>
> Facility to bulk copy
indicators from AB to disk files i.e.
browse and
> select multiple
AB indictors which are then copied to selected
windows
>
directory.
>
> Allow the default directories for custom and
bulitin indicators to
be
> specified via Preferences. Maybe also
systems, explorations,
scans....?
>
>
> All POVs
welcome.
>
> John
>
__._,_.___
Please note that this group is for discussion between users only.
To get support from AmiBroker please send an e-mail directly to
SUPPORT {at} amibroker.com
For other support material please check also:
http://www.amibroker.com/support.html
![]()
SPONSORED LINKS
YAHOO! GROUPS LINKS
__,_._,___
|
