Board Logo

what about links elsewhere on the page ?
doonee - 3/14/2005 at 04:37 AM

hi all

i understand that defining a particular tree state for a
certain page is quite a bit easier to do in the PRO version,
right ?

for example, i would like all pages of subject 2 to open
with subject two items already expanded.

like this

-subject 1
+subject 2
-subject 3
-subject 4

how do i configure that in the PRO version ?

(obviously, this is a noframes scenario question)
even better, if each page could 'pass on' its particular
tree state to the next one.

like so:

user is happily clicking around the tree

-subject 1
+subject 2
-subject 3
-subject 4

having explored the tree, user finally decides to click
on 'page1'.

now, is it possible for 'page1' to show the exact same tree
state as the the page prior to it showed ?

in other words, no matter where he goes in the site, the tree user created by clicking around on it will follow him until he decides to change something.
possible ?

(another a noframes question)
and even better than that:
the text of page1 also contains links within the site (and thus
to other pages exhibiting the tree).

is it possible to pass on the current tree state of page1, to the next page, even if the link that was clicked is not part of the tree, but somewhere in the text ?

is there any way to use *relative* links (including the use subdirectories, such as /chapter1/page1.htm etc.) in the tree, instead of *absolute* links (http://www.blabla)?
Does tigra PRO 'notice' that its in subdirectory and is able subsequently link to a neighbouring directory ? (ig. ../chapter2/page3.htm)

i guess thats not vey important, but im curious.

best regards to all and thank you in advance.

rock - 3/14/2005 at 02:47 PM

1. You can force open state of the node by using 'st':1 key-value pair in its scope settings.
['subject 2' , 'link.html', {'st':1},
2. To share states through the site, use 'cookie_ext':'path=/;' key-value pair in the tree menu settings (tree_tpl variable).
3. Yes, it's default behavior of the control.
4. Both notation are possible.

doonee - 3/14/2005 at 10:18 PM

1 understood

2 not understood, but i gathered that theres no problem

(same as 3)
really ? :)
and that is brought about by the same cookie-thing as in 2 ?

4 cool

are all of these features unique to the PRO version ?

if i buy the PRO version, you guys (from support) are going to help me out with point 2 ?


rock - 3/15/2005 at 08:50 AM

All the features are implemented only in PRO version of the control.
No problem, we'll give you a hand with your point 2, or anything else.

doonee - 3/16/2005 at 12:11 AM


last question
'cookie ext' sounds like a cookie is involved.
if so, what happens when fe. user has cookies disabled etc. ?
how does it work anyway ?

(sorry if thats a dum question, but as i said, i didnt understand
point 2)


doonee - 3/19/2005 at 02:45 AM


doonee - 3/20/2005 at 02:21 AM

im ready to buy tree pro.

however, what i did not get is whether an actual cookie
is involved in sharing the tree state through the site.
if so, what happens when fe. user has cookies disabled etc. ?
(point 2)

best regards

rock - 3/21/2005 at 09:04 AM

If cookie is not aviliable then tree renders by default, i.e. all nodes are closed, roots are opened, no selected items.
Note: default behavior could be modified by using open tree API or item scope settings. For more details please refer to the product documentation.

Could you tell me what is seems unclear with Point 2, I thought you've asked for solution.

doonee - 3/23/2005 at 05:37 AM

posted on 3/23/05 at 02:36


what was unclear was whether cookies are involved.

that is quite an issue, in days where people install whatnot to
kill popups and what is considered their likes ....

and id hate to put up a message asking people to enable cookies

so if its possible id like to avoid cookies.

not that think its not safe.
its just that peoples reactions and attitudes about them arent 'safe' these days.

i also understand thats its hard to acomplish otherwise,
unless you start working with sessions, which is not the case either, for this particular site.

from what i understood, i could, for example, without a cookie, distribute 'chapters' over subdirectories, and then, somehow, make sure that the tree is open at that particular 'chapter'
by default, right ?

going with my head through the wall, i could even have once tree instance per directory if necessary, but there is probably something smarter.

just how far can i take all that *without* a cookie ?

regards +
thanks for your patience

rock - 3/23/2005 at 03:25 PM

I'd sugest you to handle onItemSelect event (or use JS function as item's href) to collect info about tree states before redirection to another page and pass the info via GET string to other page to handle. Using the GET value you could call JS method to open required nodes. Also you could preset open state of the items via 'st':1 key value pair in the items' scope settings.

doonee - 3/23/2005 at 10:04 PM

thanks rock ...

lets run through it once more ...

i CAN preset the open state for each document ?

I CAN have state sharing with a cookie ?

I CAN have state sharing without a cookie ?

youll give me a hand in setting this up

if you can confirm the tha above,
we can proceed to the counter .....


(im in a bit of a rush, actually)

Back to forum: