Yeah, I think "drag-and-drop" somewhat understates the effort involved, but the truth is that it's pretty easy.  With practice, you start developing your circuits with the idea that they will be used whole in different contexts.

This means that you build some logic into fbx_layouts so that your circuit dirplays itself a little differently when it stands alone.  It also means that you choose circuit aliases that are likely to remain unique no matter what the context.

For example, if you are building an issues tracking circuit, don't call the issues administration circuit "admin".  Call it "issuesadmin" perhaps.  That way, when you "plug" the issues tracker into your higher-level home app, you won't have a conflict with several other "admin" circuits. Etc, etc.

Have fun, you'll be surprised how sweet FB3 is when you have tried a few things.

See ya,
St Lee.

----- Original Message -----


Thanks for the reply Lee, actually that’s what I have ended up doing. I went in and took out all the core files that weren’t needed in all the sub circuits including the layout files. Then pasted and adjusted the circuit aliases. Beyond fixing some cfmodule calls it seems to have been pretty effective and easier then I thought.

 

I always look for the difficult solution when the answer is the easy way right in front of me.

 

-----Original Message-----
From: Lee Borkman [mailto:[EMAIL PROTECTED]]

 

Hi Shane,

 

In your example, your new circuit is already physically located underneath the home circuit (ie., /testapps/ugc/).

 

Now, in order for the home circuit to know about your new "users" circuit, you need to give your new circuit an alias in the home circuit's fbx_circuits.cfm.  Then when you refer to "user.home", your home app wil understand what you are talking about.

 

So, open up /testapps/ugc/fbx_circuits.cfm, and add new aliases for the "user" circuit and all of its descendents.  That's about it.

 

You may also have to do some fine-tuning of the nested layouts in order to get "users" to integrate nicely into the home circuit's layout.  A common method would be to test the "fusebox.ishomecircuit" flag in the user circuit's fbx_layout,cfm.  If it IS the home circuit, then you probably need to wrap some extra bumph around the output.  It it's NOT the home circuit, then you may need to wrap less around your output, etc.

 ...

----- Original Message -----

 

Hey all,

 

I am struggling to grasp how this works.  If you have an application that runs perfectly as a standalone, and in this instance I am referring to Tom’s security manager, how do you incorporate it into another existing application seamlessly so that you call it as a native circuit like so…

 

http://localhost/testapps/ugc/index.cfm?fuseaction=user.home

 

Instead of …

 

http://localhost/testapps/ugc/users/index.cfm?fuseaction=main.home

 

Note the extra directory in there.  I am about to embark on a major rewrite so that it is just like any other circuit and with its circuit definitions moved to the root applications fbx_circuits.cfm, but I have a nagging feeling that I am missing something conceptual here that will result in my not having to do that.

 

The security manager, which I am calling “users” here, has its own fbx_circuits of course and it even has a nested app that in turn has its own fbx_circuits.  In fact his app has every circuit as a standalone in that they all have the core files in their respective directories.

 

Is what I am asking making any sense to anyone? I have a nasty habit of asking questions on this list that get few if any responses. I suspect because they are too boneheadish.

 

==^================================================================
==^================================================================
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
==^================================================================

Reply via email to