> Folks, > > I'm in the midst of a FB3 application that can be used either through the > web or browed by a telephone using callXML from Voxeo. All of the logic > remains the same, but the all of the "display" pages are duplicated as an > HTML web version and a callXML version for the phone. How have folks on the > list handled this situation -- it would be akin to having an application > that is both HTML- and WML-based. > > For now, here's a snippet of what I've done in the fbx_switch file > > <cfcase value="showQuestion"> > <cfset XFA.submitForm="home.answerQuestion"> > <cfset XFA.finished="home.done"> > <cfinclude template="act_pickQuestion.cfm"> > <cfinclude template="qry_getQuestion.cfm"> > <cfif session.displayType EQ "voxeo"> > <cfinclude template="vox_askQuestion.cfm"> > <cfelse> > <cfinclude template="dsp_askQuestion.cfm"> > </cfif> > </cfcase> > > > <cfcase value="answerQuestion"> > <cfset XFA.followup="home.showFollowupQuestion"> > <cfinclude template="act_pickQuestion.cfm"> > <cfinclude template="act_answerQuestion.cfm"> > <cfinclude template="act_checkFollowups.cfm"> > <cfinclude template="act_setQuestion.cfm"> > <cflocation url="#request.self#?fuseaction=home.showQuestion"> > </cfcase> > > The differences are nowhere near enough to justify a separate fusebox since > the logic is identical -- its just that the pages are completely different > for display. I've modified the layout page to wrap the web content in the > standard HTML tags and the phone content in the standard xml tags which is > fine, but handling the same-but-different content is the issue. > > Thoughts? > > Regards, > > John Paul Ashenfelter > CTO/President > TransitionPoint > [EMAIL PROTECTED] > >
Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
