Previously I used the following to create a pop-up menu on the page:
<select name="keywords" onchange="MM_jumpMenu('parent',this,1)">
<option>Categories & Themes</option>
<% write(stavelib.KeywordMenu)%>
</select>
Would I now do the following: ( I know the following is not Fusebox
but
hopefully you know what I mean)
Include("qry_findcustomthemes.a4d")
Include("act_buildthemepopup.a4d") `results are placed in $results
Include("lay_printnavigation.a4d") ` contains the pop-up menu
``````` on the lay_printnavigation.a4d page
<select name="keywords" onchange="MM_jumpMenu('parent',this,1)">
<option>Categories & Themes</option>
<% write($results)%>
</select>
````````
Yes, that is more fusebox-ish.
BTW, when it comes to pop-up/drop-down menus, often they represent
attributes that don't change very often. In those cases I pre-build
the option list in a library, then call a method in the library to
get the option list. I gave an example of doing this in the Libraries
chapter.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoylibrary.com
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
