Hello. I was wondering about where global user functions should be put. In the application that I am working on, I have created a function that is responsible for updating the "navigation path" (i.e. the asset that allows users to know where they are at and to jump to any previous locations). This function is called by every fuseaction that results in a change of page. My question is where should I put this function so that it would be visible by all circuits of the application. Would it be appropriate to place it in the home circuit's settings file?
While writing the above question, two thoughts came to my mind. The first is whether I should forget about a user function and have an action fuse to do that instead (which would be called via cfmodule). How is that? It certainly sounds more FBish, but are there any cons (e.g. performance hit)? The second thought is in fact another question: what are the common practices when implementing the aforementioned asset? Is there any FB classical way of doing it? I though about taking advantage of the fusebox.circuits structure, but that would not do, since the text to be shown will seldom correspond to the keys used. That would require me to create a parallel structure, mapping circuit names to user-friendly names. Thank you for your ideas and comments, -- Ney Andr� de Mello Zunino Media and Technology Laboratory Campus Computing Centre United Nations University ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
