fusebox: Question about fuseactions and sidebar menu
The fusebox forum isn't that active and I've seen some fusebox posts here so hopefully someone can give me a little advice... I'm trying to figure out the best way to design my menu system Fuseactions. I have a sidebar menu that changes for given main menu nav items. So, let's say the top main nav bar has ABOUT, NEWS, etc.. the ABOUT page sidebar links will be different from the NEWS sidebar links. Now, to handle this, I created separate ciruits/FAs: about.abouthome about.aboutnews about.maps and news.newshome news.newswhatsnew news.newsrandomstuff and so on... The way I have it designed now is if you call up about.abouthome, there is a preFA that calls up sidebarnav.navabout which has all of the XFAs for the various links from the ABOUT pages. sidebarnav.navabout in turns calls up the sidebar fuse which is stored in a CCV and then assembled later. Does this seem like a good setup? I'm not particularly happy with the the disconnect between the ABOUT FAs and the associated XFAs stored with the sidebar FA, but I thought it made more sense to put the XFAs with the sidebar FAs than it did in the main ABOUT FAs, especially because those XFAs need to be built in the sidebar fuses, not the ABOUT fuses. Does that make sense? I'd appreciate any feedback. Thanks, Mike ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228057 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: fusebox: Question about fuseactions and sidebar menu
First: about.abouthome you should have it be just about.home or better yet, about.index... the about should be implied by the circuit. In my design model I would have a action on the about news and anything else that would change up your navigation.. It would some how set/return a navigation object that would be able to draw it's self, aka, a list or something like that. Use CSS to do the formatting... On 12/30/05, Mike Soultanian [EMAIL PROTECTED] wrote: The fusebox forum isn't that active and I've seen some fusebox posts here so hopefully someone can give me a little advice... I'm trying to figure out the best way to design my menu system Fuseactions. I have a sidebar menu that changes for given main menu nav items. So, let's say the top main nav bar has ABOUT, NEWS, etc.. the ABOUT page sidebar links will be different from the NEWS sidebar links. Now, to handle this, I created separate ciruits/FAs: about.abouthome about.aboutnews about.maps and news.newshome news.newswhatsnew news.newsrandomstuff and so on... The way I have it designed now is if you call up about.abouthome, there is a preFA that calls up sidebarnav.navabout which has all of the XFAs for the various links from the ABOUT pages. sidebarnav.navabout in turns calls up the sidebar fuse which is stored in a CCV and then assembled later. Does this seem like a good setup? I'm not particularly happy with the the disconnect between the ABOUT FAs and the associated XFAs stored with the sidebar FA, but I thought it made more sense to put the XFAs with the sidebar FAs than it did in the main ABOUT FAs, especially because those XFAs need to be built in the sidebar fuses, not the ABOUT fuses. Does that make sense? I'd appreciate any feedback. Thanks, Mike ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228058 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: fusebox: Question about fuseactions and sidebar menu
Dustin Tinney wrote: First: about.abouthome you should have it be just about.home or better yet, about.index... the about should be implied by the circuit. Yeah, I was going through all my circuits changing them probably at the same time you were typing it ;) In my design model I would have a action on the about news and anything else that would change up your navigation.. It would some how set/return a navigation object that would be able to draw it's self, aka, a list or something like that. Use CSS to do the formatting... Within each section/circuit (news,about,etc.) the menu stays the same for all FAs within that section/circuit. It just changes from section to section. That's why I used the preFA within that circuit to include a fuse w/ the menu for that section. I figured that way, regardless which FA is called within that circuit, they're all going to get the same menu. Then the CSS takes care of the menu like you suggest. Sound similar to what you were thinking? thanks, Mike ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228060 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: fusebox: Question about fuseactions and sidebar menu
that would be one way to do it. Pre-fuseactions would give you that functionality. If I was using a pre-fuseaction I wouldn't have it pass back the nav or print it out. instead I would have it set a variable.. such as nav_template_file and then in your main template where you would have your sub nav instead you would do something like: cfInclude template=public/sub_templates/#nav_template_file#.cfm / On 12/31/05, Mike Soultanian [EMAIL PROTECTED] wrote: Dustin Tinney wrote: First: about.abouthome you should have it be just about.home or better yet, about.index... the about should be implied by the circuit. Yeah, I was going through all my circuits changing them probably at the same time you were typing it ;) In my design model I would have a action on the about news and anything else that would change up your navigation.. It would some how set/return a navigation object that would be able to draw it's self, aka, a list or something like that. Use CSS to do the formatting... Within each section/circuit (news,about,etc.) the menu stays the same for all FAs within that section/circuit. It just changes from section to section. That's why I used the preFA within that circuit to include a fuse w/ the menu for that section. I figured that way, regardless which FA is called within that circuit, they're all going to get the same menu. Then the CSS takes care of the menu like you suggest. Sound similar to what you were thinking? thanks, Mike ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228062 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
