Hi Keith, Issues about using the WireframeTool's Code Generator aside, you really want to put all thoughts about circuits, etc, out of your head at such an early stage of gathering requirements. So whether your first instincts were correct or not, you should have ignored them ;-)
The Wireframetool generates a dirty great big cfswitch because it doesn't know or care about circuits, and neither should you, at that point in the process. It's true, though, I'm going to have to disconnect the Code Generator, and let users re-connect it by setting a flag in fbx_settings ;-( Bye now, LeeBB ----- Original Message ----- From: Keith Young Ok, good, I did the right thing up until I hit "generate code" ;p Ironically before using the wireframe I had it broken into three sub-circuits as you suggested... and then changed it after the code was generated :) I guess I'll follow my instincts more next time :) Cheers, Keith. >>> [EMAIL PROTECTED] 04/10/02 09:03am >>> > Keith wrote: > > Yeah, I figured that people would suggest to break it up...I > guess it is so large as a by-product of doing my first > Wireframe...I used the wireframe tool to map the whole > application, and then it generate one huge switch (which I > based mine on). I guess the trick with wireframing is to > know ahead of time what the sub-circuits will be and only map them? I think there was a discussion a while back on why we shouldn't generate code directly from the wireframe and it was a mistake to add that feature. Most people wireframe the whole application and then figure out the circuits by hand (or use a mindmapping tool). Patrick ==^================================================================ 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 ==^================================================================
