forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "HANAX" <>
Subject RE: Re: voice plugin
Date Wed, 21 Sep 2005 11:27:54 GMT

Od: "Ross Gardler" <>
Predmet: Re: voice plugin
Dátum/Čas: 20. 9. 2005 23:28:55

> Ross Gardler wrote:
> > HANAX wrote:
> ...
> >> Ok, this seems that I need to rewrite some simple files and change it 
> >> to voice plugin or use voice plugin there?
> >> Sorry, I'am still lost... I have really big troubles to explain what 
> >> can't I undertand :( Sorry.
> > 
> > 
> > No problem. I will create the contract to put some meta informatio into 
> > head and commit it to the voice plugin. This will, hopefully serve as an 
> > example for you. We can then guide you on porting your XSLT to that 
> > contract.
> I've just created a skeleton contract for you [1]. All it does is place 
> a new meta element in head, look at the source of any page in the voice 
> plugin documentation and you'll see what I mean.

Ok, I've got problem with SVN, I don't have latest versions... :( Now it's ok and I see changes.
But... I don't understand how forrest knows that it should use voice.fv :) In my site, I don't
have this file and so that it does not contains added META element neither changed title.
Should I have also voice.fv in site dir? I'm confused - it seems that my plugin and voice
plugin are somehow unlinked... I can't explain good what I mean, sorry, but it's probably
I still don't understand well the "engine of plugins"... :) 

> What you need to do (at least if I understand your work on voiceML) is 
> use your existing XSLT code that generates the voiceML markup and use it 
> in this contract.

Yes this seems right way. 

> The template can operate on any part of the document just as it could 
> before. To see how take a look at the "content-main" template that puts 
> the body of a page into place [2]

Great, finally I understand basics now :) Seems that now I need to split my work to 2 contracts:
1. to generate VoiceXML into header
2. to generate body section of mxml file

Now it raises one question for me, how this differs from creating two stylesheets (one fore
header and secodn for body) and place them one after another? Maybe I miss some esential thing
about views :)

> Does this concrete example, and your earlier reading, help with 
> understanding what is going on?

Yes, big thanx!

> Ross
> [1]
> [2] 

View raw message