Questions about extensions

[Dan Fournier]

Is this a legitimate use of extensions?

In flow.js...
--------------
//Build XML variable using document manipulations, etc...
var xml = "<page><document id="" title="" />...</page>";

//obligated to have publisher request here??
var viewdata = {"pageXml" : xml};
cocoon.sendPage("linksToResult2", viewdata);


In xsl...
--------------
<xsl:template match="page">
    <div class="linksTo">
    <ul>
    <xsl:apply-templates select="document"/>
    </ul>      
    </div>
  </xsl:template>

  <xsl:template match="document">
  <li>
  <a href="daisy:{@id}" title="{@title}"><xsl:value-of
select="@title"/></a>
  </li>
  </xsl:template>  

At the moment, it seems that I require a publisher request with params
before creating viewdata. So, is it even possible/suggested to attempt
this?

I'd also like to know, what is the best way to debug an extension, to
output information on screen for instance?

Thanks!

Danny Fournier
 
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[Karel Vervaeke-2]

There's no such thing as illegitimate use :)

You only need a publisher request when you want to pull in things from the repository (obviously).

You may need to wrap xml in an StringXMLizable otherwise the xml could be escaped in the output (&lt;page&gt;) (not sure, I haven't done this in a while ...)

Regards,

Karel

On Wed, Apr 4, 2012 at 9:08 PM, Fournier, Danny G <Danny.Fournier@...> wrote:

Is this a legitimate use of extensions?

In flow.js...
--------------
//Build XML variable using document manipulations, etc...
var xml = "<page><document id="" title="" />...</page>";

//obligated to have publisher request here??
var viewdata = {"pageXml" : xml};
cocoon.sendPage("linksToResult2", viewdata);


In xsl...
--------------
<xsl:template match="page">
   <div class="linksTo">
       <ul>
               <xsl:apply-templates select="document"/>
       </ul>
   </div>
 </xsl:template>

 <xsl:template match="document">
       <li>
               <a href="daisy:{@id}" title="{@title}"><xsl:value-of
select="@title"/></a>
       </li>
 </xsl:template>

At the moment, it seems that I require a publisher request with params
before creating viewdata. So, is it even possible/suggested to attempt
this?

I'd also like to know, what is the best way to debug an extension, to
output information on screen for instance?

Thanks!

Danny Fournier

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[Dan Fournier]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Karel,

 

thanks for letting me know that I wasn’t that off with my idea J

 

I’ve reworked everything and I’m closer to a working solution (no errors about Publishers missing and so forth). However, my XSL isn’t processing my XML due to the fact that it’s escaped as you had pointed out in your last email.

 

Could you provide a small hint on where/what is required to serialize the string  so that it gets parsed by the XSL? Since you say “wrap”, should I put that in the sitemap? Or would this be in the flow.js while implementing a certain class?

 

Dan

 

 

 

From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke
Sent: April 5, 2012 5:08 AM
To: Daisy: open source CMS - general mailinglist
Subject: Re: [daisy] Questions about extensions

 

There's no such thing as illegitimate use :)

 

You only need a publisher request when you want to pull in things from the repository (obviously).

You may need to wrap xml in an StringXMLizable otherwise the xml could be escaped in the output (&lt;page&gt;) (not sure, I haven't done this in a while ...)

 

Regards,

Karel

 

On Wed, Apr 4, 2012 at 9:08 PM, Fournier, Danny G <Danny.Fournier@...> wrote:

Is this a legitimate use of extensions?

In flow.js...
--------------
//Build XML variable using document manipulations, etc...
var xml = "<page><document id="" title="" />...</page>";

//obligated to have publisher request here??
var viewdata = {"pageXml" : xml};
cocoon.sendPage("linksToResult2", viewdata);


In xsl...
--------------
<xsl:template match="page">
   <div class="linksTo">
       <ul>
               <xsl:apply-templates select="document"/>
       </ul>
   </div>
 </xsl:template>

 <xsl:template match="document">
       <li>
               <a href="daisy:{@id}" title="{@title}"><xsl:value-of
select="@title"/></a>
       </li>
 </xsl:template>

At the moment, it seems that I require a publisher request with params
before creating viewdata. So, is it even possible/suggested to attempt
this?

I'd also like to know, what is the best way to debug an extension, to
output information on screen for instance?

Thanks!

Danny Fournier

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

 

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[Karel Vervaeke-2]

By 'wrapping' I mean putting a wrapper object around it, like such:

var xmlString = "<page>...</page>";
var xml = new Packages.org.apache.cocoon.xml.StringXMLizable(xmlString);

var xml = new Packages.org.outerj.daisy.frontend.util.ByteArrayXMLizable(xmlString.getBytes("UTF-8"));

HTH,
Karel




On Thu, Apr 5, 2012 at 4:48 PM, Fournier, Danny G
<Danny.Fournier@...> wrote:

>
> Karel,
>
>
>
> thanks for letting me know that I wasn’t that off with my idea J
>
>
>
> I’ve reworked everything and I’m closer to a working solution (no errors about Publishers missing and so forth). However, my XSL isn’t processing my XML due to the fact that it’s escaped as you had pointed out in your last email.
>
>
>
> Could you provide a small hint on where/what is required to serialize the string  so that it gets parsed by the XSL? Since you say “wrap”, should I put that in the sitemap? Or would this be in the flow.js while implementing a certain class?
>
>
>
> Dan
>
>
>
>
>
>
>
> From: daisy-bounces@... [mailto:daisy-bounces@...] On Behalf Of Karel Vervaeke
> Sent: April 5, 2012 5:08 AM
> To: Daisy: open source CMS - general mailinglist
> Subject: Re: [daisy] Questions about extensions
>
>
>
> There's no such thing as illegitimate use :)
>
>
>
> You only need a publisher request when you want to pull in things from the repository (obviously).
>
> You may need to wrap xml in an StringXMLizable otherwise the xml could be escaped in the output (<page>) (not sure, I haven't done this in a while ...)
>
>
>
> Regards,
>
> Karel
>
>
>
> On Wed, Apr 4, 2012 at 9:08 PM, Fournier, Danny G <Danny.Fournier@...> wrote:
>
> Is this a legitimate use of extensions?
>
> In flow.js...
> --------------
> //Build XML variable using document manipulations, etc...
> var xml = "<page><document id="" title="" />...</page>";
>
> //obligated to have publisher request here??
> var viewdata = {"pageXml" : xml};
> cocoon.sendPage("linksToResult2", viewdata);
>
>
> In xsl...
> --------------
> <xsl:template match="page">
>    <div class="linksTo">
>        <ul>
>                <xsl:apply-templates select="document"/>
>        </ul>
>    </div>
>  </xsl:template>
>
>  <xsl:template match="document">
>        <li>
>                <a href="daisy:{@id}" title="{@title}"><xsl:value-of
> select="@title"/></a>
>        </li>
>  </xsl:template>
>
> At the moment, it seems that I require a publisher request with params
> before creating viewdata. So, is it even possible/suggested to attempt
> this?
>
> I'd also like to know, what is the best way to debug an extension, to
> output information on screen for instance?
>
> Thanks!
>
> Danny Fournier
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>
>
>
>
> _______________________________________________
> daisy community mailing list
> Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy
>

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[Dan Fournier]

Thanks! This did the trick.

Dan

Ps: I wasn't sure about being able to import the classes, but that too works.

> -----Original Message-----
> From: daisy-bounces@... [mailto:daisy-
> bounces@...] On Behalf Of Karel Vervaeke
> Sent: April 5, 2012 12:15 PM
> To: Daisy: open source CMS - general mailinglist
> Subject: Re: [daisy] Questions about extensions
>
> By 'wrapping' I mean putting a wrapper object around it, like such:
>
> var xmlString = "<page>...</page>";
> var xml = new Packages.org.apache.cocoon.xml.StringXMLizable(xmlString);
>
> var xml = new
> Packages.org.outerj.daisy.frontend.util.ByteArrayXMLizable(xmlString.getBy
> tes("UTF-8"));
>
> HTH,
> Karel
>
>
>
>
> On Thu, Apr 5, 2012 at 4:48 PM, Fournier, Danny G
> <Danny.Fournier@...> wrote:
> >
> > Karel,
> >
> >
> >
> > thanks for letting me know that I wasn't that off with my idea J
> >
> >
> >
> > I've reworked everything and I'm closer to a working solution (no errors
> about Publishers missing and so forth). However, my XSL isn't processing my
> XML due to the fact that it's escaped as you had pointed out in your last
> email.
> >
> >
> >
> > Could you provide a small hint on where/what is required to serialize the
> string  so that it gets parsed by the XSL? Since you say "wrap", should I put
> that in the sitemap? Or would this be in the flow.js while implementing a
> certain class?
> >
> >
> >
> > Dan
> >
> >
> >
> >
> >
> >
> >
> > From: daisy-bounces@... [mailto:daisy-
> bounces@...] On Behalf Of Karel Vervaeke
> > Sent: April 5, 2012 5:08 AM
> > To: Daisy: open source CMS - general mailinglist
> > Subject: Re: [daisy] Questions about extensions
> >
> >
> >
> > There's no such thing as illegitimate use :)
> >
> >
> >
> > You only need a publisher request when you want to pull in things from the
> repository (obviously).
> >
> > You may need to wrap xml in an StringXMLizable otherwise the xml could
> be escaped in the output (<page>) (not sure, I haven't done this in a
> while ...)
> >
> >
> >
> > Regards,
> >
> > Karel
> >
> >
> >
> > On Wed, Apr 4, 2012 at 9:08 PM, Fournier, Danny G <Danny.Fournier@dfo-
> mpo.gc.ca> wrote:
> >
> > Is this a legitimate use of extensions?
> >
> > In flow.js...
> > --------------
> > //Build XML variable using document manipulations, etc...
> > var xml = "<page><document id="" title="" />...</page>";
> >
> > //obligated to have publisher request here??
> > var viewdata = {"pageXml" : xml};
> > cocoon.sendPage("linksToResult2", viewdata);
> >
> >
> > In xsl...
> > --------------
> > <xsl:template match="page">
> >    <div class="linksTo">
> >        <ul>
> >                <xsl:apply-templates select="document"/>
> >        </ul>
> >    </div>
> >  </xsl:template>
> >
> >  <xsl:template match="document">
> >        <li>
> >                <a href="daisy:{@id}" title="{@title}"><xsl:value-of
> > select="@title"/></a>
> >        </li>
> >  </xsl:template>
> >
> > At the moment, it seems that I require a publisher request with params
> > before creating viewdata. So, is it even possible/suggested to attempt
> > this?
> >
> > I'd also like to know, what is the best way to debug an extension, to
> > output information on screen for instance?
> >
> > Thanks!
> >
> > Danny Fournier
> >
> > _______________________________________________
> > daisy community mailing list
> > Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> > mail to: daisy@...
> > list information: http://lists.cocoondev.org/mailman/listinfo/daisy
> >
> >
> >
> >
> > _______________________________________________
> > daisy community mailing list
> > Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> > mail to: daisy@...
> > list information: http://lists.cocoondev.org/mailman/listinfo/daisy
> >
> _______________________________________________
> daisy community mailing list
> Professional Daisy support:
> http://outerthought.org/en/services/daisy/support.html
> mail to: daisy@...
> list information: http://lists.cocoondev.org/mailman/listinfo/daisy

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[Gabriel Gruber-2]

Hello folks,

just wanted to know, if someone has any news about the state of Daisy. When looking at the webpages of NGDATA and www.daisycms.org I stumbled over several broken links. Also it is not clear, if there is still a public available sourcecode repository?

This link is not working:
http://dev.outerthought.org/svn_public/outerthought_daisy/trunk

Is this project still maintained and are there plans for any future versions?

Thanx in advance for clarification!

Gabriel
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

[sam blake]

Hi,

I too am wondering about the roadmap for Daisy.  NGData corporate website does not list any information about daisy.

Thanks-

Sam

On Mon, Apr 1, 2013 at 11:14 AM, Gabriel Gruber <Gabriel.Gruber@...> wrote:

Hello folks,

just wanted to know, if someone has any news about the state of Daisy. When looking at the webpages of NGDATA and www.daisycms.org I stumbled over several broken links. Also it is not clear, if there is still a public available sourcecode repository?

This link is not working:
http://dev.outerthought.org/svn_public/outerthought_daisy/trunk

Is this project still maintained and are there plans for any future versions?

Thanx in advance for clarification!

Gabriel
_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy

_______________________________________________
daisy community mailing list
Professional Daisy support: http://outerthought.org/en/services/daisy/support.html
mail to: daisy@...
list information: http://lists.cocoondev.org/mailman/listinfo/daisy