[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [amibroker] Re: Plot() and z-order



PureBytes Links

Trading Reference Links

I will stick with z-order in all docs. And layers will remain in original AB sense.
That is mainly because I don't want to change things that are already
described in Howard's books.

Best regards,
Tomasz Janeczko
amibroker.com
----- Original Message ----- 
From: "Dennis Brown" <see3d@xxxxxxxxxxx>
To: <amibroker@xxxxxxxxxxxxxxx>
Sent: Wednesday, February 18, 2009 9:21 PM
Subject: Re: [amibroker] Re: Plot() and z-order


> Of course they resort to: "This is the same as making "layers" of  
> objects where the Z-order determines what object is on top of  
> another." in order to help the reader visualize it.
> 
> Another word that was referenced was Planes.  Also Depth Buffers, and  
> Z-buffers relate to 3D methods.  Also it seams that "layers" as a term  
> is used for just about everything as a concept of hierarchy in  
> software, so I am ready to back away from that.  Z-order is more  
> widely used in windows programming due to what MS called it.
> 
> The Z-order of plots has always been there based on the order of  
> execution of AFL (forward or reverse).  Now we have this new idea of Z- 
> order that is based on discrete  numbered planes or buffers that also  
> have their own independent Z-order based on the previous sentence.
> 
> Ok, this will be my humble suggestion for the plot planes: Z-planes.   
> I can visualize that.  Each Z-plane can have the Z-order of plots as  
> forward or reversed as before.
> 
> I am done commenting on this subject now.   I will use whatever is  
> decided by Tomasz.
> 
> Best regards,
> Dennis
> 
> On Feb 18, 2009, at 2:28 PM, Mike wrote:
> 
>> z-order is a pretty standard reference in coding languages, and is
>> used as an adjective.
>>
>> http://en.wikipedia.org/wiki/Z-order
>>
>> Mike
>>
>> --- In amibroker@xxxxxxxxxxxxxxx, Dennis Brown <see3d@xxx> wrote:
>>>
>>> Tomasz,
>>>
>>> Thank you for making it possible for customers like me who use AFL
>> as
>>> a programming language to create trading "platforms".  Every time
>> you
>>> add some big or little thing that provides additional AFL
>> flexibility
>>> to control internal functions, I am able to quickly expand my
>> horizons
>>> with how I use AmiBroker.
>>>
>>> Yes, I struggled when writing the previous post when I realized that
>>> even though I had been thinking and referring to the Z-order as
>>> "layers" for a long time, that term had already been used in
>> AmiBroker
>>> for visibility layers.
>>>
>>> When trying to use only "Z-order", I struggled because, this implies
>> a
>>> verb, and conceptually I wanted to convey the idea of a noun of
>>> positions.  It can be visualized both ways -- as outputting plots in
>>> groups with the group order defined by Z-order parameter, or as
>>> implemented where each Z-order refers to a different Z-layer with
>> its
>>> own buffer.  I find it much easier to visualize it as different Z-
>>> layers on the chart.  I come from a background in CAD and photoshop
>>> type programs where layers refers to Z-layers.
>>>
>>> I don't have all  the answers, all I can do is provide some feedback
>>> from my experience.  I think Z-order is a good term to describe the
>>> "action" parameter of the command, and Z-layers or perhaps Z-levels
>> is
>>> the static "result" of executing the commands.  Perhaps someone else
>>> has a better idea about this.
>>>
>>> Best regards,
>>> Dennis
>>>
>>> On Feb 18, 2009, at 3:38 AM, Tomasz Janeczko wrote:
>>>
>>>> Dennis,
>>>>
>>>> Thank you for the feedback. All your findings are correct. It is
>>>> very encouraging seeing new feature being
>>>> fully utilised in such a short time.
>>>> Regarding naming conventions - yes I try to keep the "Z-order"
>> name
>>>> for new z-order feature
>>>> and do not use the word "layer" to avoid mix with old
>> functionality.
>>>> So, I would like to avoid names like z-layer.
>>>>
>>>> In fact the drawing studies (lines/rectangles/elipsses) can use
>> both
>>>> functionalities *independently*.
>>>> The z-order defines the drawing order (above/below), while the
>> layer
>>>> controls visibility (on/off) depending on interval displayed.
>>>> Having two as independent controls was intended and provided for
>>>> maximum flexibility.
>>>>
>>>> If anyone has better ideas on naming conventions, they can be
>> changed.
>>>>
>>>> For me "z-order" name represents actual functionality best. I have
>>>> some doubts regarding "layer" word, because
>>>> this old functionality actually is just visibility switch.
>>>>
>>>> Best regards,
>>>> Tomasz Janeczko
>>>> amibroker.com
>>>> ----- Original Message -----
>>>> From: "Dennis Brown" <see3d@xxx>
>>>> To: <amibroker@xxxxxxxxxxxxxxx>
>>>> Sent: Wednesday, February 18, 2009 3:01 AM
>>>> Subject: Re: [amibroker] Plot() and z-order
>>>>
>>>>
>>>>> Tomasz,
>>>>>
>>>>> Thanks for all the layers.  I have already added them to my
>> charts
>>>>> (which removed a bunch of spaghetti code) and have generically
>> used
>>>>> up
>>>>> all 11 already!
>>>>>
>>>>> Having plot Z-layers makes my AFL much more modular and the
>> includes
>>>>> are more complete.
>>>>>
>>>>> I just want to confirm that Gfx drawings plot above Z-layer 5 and
>>>>> below Z-layer -5.  This effectively adds one more Z-layers --
>> since
>>>>> you can't mix Gfx overlay modes in the same chart.
>>>>>
>>>>> It appears that shapes plot to Z-layer 0 of the specified layer
>> (like
>>>>> intraday layer).  Plotting text seems to got to Z-layer 0, as
>> well as
>>>>> drawing text studies.  Calling two different things "Layers" may
>>>>> cause
>>>>> confusion, so we all should stick with Z-order or Z-layer to make
>> it
>>>>> clear.
>>>>>
>>>>> For those who might wonder what to use all the Z-layers can be
>> used
>>>>> for, here is an example of how I apportioned them on my charts
>> for
>>>>> now
>>>>> --all are used (and I could even use a few more):
>>>>>
>>>>> -6 Gfx mode 1 (I do not use)
>>>>> -5 Bg fill area 1 (used for multiple overlapping bands layer
>> settable
>>>>> in each indicator)
>>>>> -4 Bg fill area 2
>>>>> -3 Bg fill area 3
>>>>> -2 Bg fill area 4
>>>>> -1 Ovals/Rectangles manual chart highlighting (default setting)
>>>>> 0 Study lines (default setting), PlotText(), PlotShapes()
>>>>> +1 Upper chart Volume bars, Middle chart Volume bars, Trade
>> equity
>>>>> histograms & lines
>>>>> +2 Under price bar shadow areas
>>>>> +3 Price bars/lines, -- stops & limits (plot under)
>>>>> +4 Signal Ribbon displays at bottom of chart
>>>>> +5 Lower overlapped Volume bars and Volume indicators, Volume and
>>>>> signal Ribbon grid lines
>>>>> +6 Gfx mode 0 (8 pseudo "Z-layers" of Gfx button arrays)
>>>>>
>>>>> The beauty of Z-layers is that the calculation order is decoupled
>>>>> from
>>>>> the plot order.
>>>>>
>>>>> The Gfx drawings do not have Z-order.  It would be nice to have
>> them,
>>>>> but since my Gfx buttons can all be drawn at the end of the AFL,
>> it
>>>>> is
>>>>> inconvenient, but not too difficult to arrange for the fact that
>> the
>>>>> detection order and the drawing order are reversed.  It just
>> means
>>>>> that it is not completely modular with includes, and a bit error
>>>>> prone
>>>>> from manual editing.  I can live with it though.
>>>>>
>>>>> This is a major milestone for my charts.
>>>>>
>>>>> Best regards,
>>>>> Dennis
>>>>>
>>>>> On Feb 15, 2009, at 4:12 AM, Tomasz Janeczko wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> With regard to 5.21.0 BETA new functionality
>>>>>> "Plot, PlotForeign and PlotOHLC now have new parameter zorder
>> which
>>>>>> defines the Z-axis position of given plot. (FC#257)"
>>>>>>
>>>>>> It works correctly for PlotOHLC and PlotForeign.
>>>>>> For Plot() function, the XShift parameter is incorrectly used as
>> z-
>>>>>> order.
>>>>>> This will be fixed in 5.22.
>>>>>>
>>>>>> So if you need z-ordering for Plot(), please use PlotOHLC
>> instead
>>>>>> until 5.22 comes up.
>>>>>>
>>>>>> Thanks to Dennis for reporting this.
>>>>>>
>>>>>> Best regards,
>>>>>> Tomasz Janeczko
>>>>>> amibroker.com
> 
> 
> ------------------------------------
> 
> **** IMPORTANT PLEASE READ ****
> This group is for the discussion between users only.
> This is *NOT* technical support channel.
> 
> TO GET TECHNICAL SUPPORT send an e-mail directly to 
> SUPPORT {at} amibroker.com
> 
> TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
> http://www.amibroker.com/feedback/
> (submissions sent via other channels won't be considered)
> 
> For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
> http://www.amibroker.com/devlog/
> 
> Yahoo! Groups Links
> 
> 
> 


------------------------------------

**** IMPORTANT PLEASE READ ****
This group is for the discussion between users only.
This is *NOT* technical support channel.

TO GET TECHNICAL SUPPORT send an e-mail directly to 
SUPPORT {at} amibroker.com

TO SUBMIT SUGGESTIONS please use FEEDBACK CENTER at
http://www.amibroker.com/feedback/
(submissions sent via other channels won't be considered)

For NEW RELEASE ANNOUNCEMENTS and other news always check DEVLOG:
http://www.amibroker.com/devlog/

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/amibroker/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/amibroker/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:amibroker-digest@xxxxxxxxxxxxxxx 
    mailto:amibroker-fullfeatured@xxxxxxxxxxxxxxx

<*> To unsubscribe from this group, send an email to:
    amibroker-unsubscribe@xxxxxxxxxxxxxxx

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/