[Xerte-dev] Re: Searching inside a published object

Mark Berthelemy mberthelemy at wyversolutions.co.uk
Fri Jul 19 13:55:48 BST 2013


Thanks Julian,

I've found xenith.js in the Nottingham template. Where would I find it for the Bootstrap template? Or am I misunderstanding how the templates work?

I can't find any documentation about how XOT is structured from a code perspective? Does that exist yet?

Cheers,

Mark  

--  
Mark Berthelemy
Director - Wyver Solutions Ltd
Tel: 01773 318 962
Mob: 07922 146 761
Web: www.wyversolutions.co.uk


On Friday, 19 July 2013 at 11:16, Julian Tenney wrote:

> Read through the xenith.js
>   
> From: xerte-dev-bounces at lists.nottingham.ac.uk [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Mark Berthelemy
> Sent: 19 July 2013 11:14
> To: For Xerte technical developers
> Subject: [Xerte-dev] Re: Searching inside a published object
>   
> OK. That makes sense. I'm looking at a previewed object now. Where will I find the XML?
>   
>  
> Mark
>  
>  
>   
>  
> --  
>  
> Mark Berthelemy
>  
> Director - Wyver Solutions Ltd
>  
> Tel:      01773 318 962
>  
> Mob:    07922 146 761
>  
> Web:    www.wyversolutions.co.uk (http://www.wyversolutions.co.uk)
>  
>   
>  
>  
> On Friday, 19 July 2013 at 10:59, Julian Tenney wrote:
> >  
> > Once the piece has loaded you’ve got the XML, and can run over it with JQuery easily. Doing the search is easy, doing the next bits is a bit more difficult
> >  
> >  
> > From: xerte-dev-bounces at lists.nottingham.ac.uk (mailto:xerte-dev-bounces at lists.nottingham.ac.uk) [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Mark Berthelemy
> > Sent: 19 July 2013 10:46
> > To: For Xerte technical developers
> > Subject: [Xerte-dev] Re: Searching inside a published object
> >  
> >  
> >   
> >  
> >  
> > Hi Julian,
> >  
> >  
> >   
> >  
> >  
> >  
> > That's exactly what I'm expecting.
> >  
> >  
> >  
> >   
> >  
> >  
> >  
> > I thought PHP would be necessary, because somewhere you'd have to build an index file containing text and relevant page links. This index file would be created at the point of publishing and stored with the learning object. At that point you can start using Javascript in the browser to traverse the index when the form is submitted.
> >  
> >  
> >  
> >   
> >  
> >  
> >  
> > Javascript can't spider across all the pages can it? Unless you're using node.js on the server?
> >  
> >  
> >  
> >   
> >  
> >  
> >  
> > Mark
> >  
> >  
> >  
> >  
> >   
> >  
> >  
> >  
> > --  
> >  
> >  
> >  
> > Mark Berthelemy
> >  
> >  
> >  
> > Director - Wyver Solutions Ltd
> >  
> >  
> >  
> > Tel:      01773 318 962
> >  
> >  
> >  
> > Mob:    07922 146 761
> >  
> >  
> >  
> > Web:    www.wyversolutions.co.uk (http://www.wyversolutions.co.uk)
> >  
> >  
> >  
> >   
> >  
> >  
> >  
> > On Friday, 19 July 2013 at 10:26, Julian Tenney wrote:
> > >  
> > > This would be JavaScript / JQuery. It could work like this:
> > >  
> > >  
> > >   
> > >  
> > >  
> > > Show a find dialog;
> > >  
> > >  
> > > User enters phrase, hits ‘find’
> > >  
> > >  
> > > Then what? You get a list of pages where the text was found?  
> > >  
> > >  
> > > Click on each page to go there and the phrases are highlighted?
> > >  
> > >  
> > >   
> > >  
> > >  
> > > From: xerte-dev-bounces at lists.nottingham.ac.uk (mailto:xerte-dev-bounces at lists.nottingham.ac.uk) [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Mark Berthelemy
> > > Sent: 19 July 2013 10:21
> > > To: For Xerte technical developers
> > > Subject: [Xerte-dev] Re: Searching inside a published object
> > >  
> > >  
> > >   
> > >  
> > >  
> > > Oh, I wish…
> > >  
> > >  
> > >   
> > >  
> > >  
> > >  
> > > I'll look into it, but don't hold your breath… I'm just above beginner stage when it comes to PHP!
> > >  
> > >  
> > >  
> > >   
> > >  
> > >  
> > >  
> > > Mark
> > >  
> > >  
> > >  
> > >  
> > >   
> > >  
> > >  
> > >  
> > > --  
> > >  
> > >  
> > >  
> > > Mark Berthelemy
> > >  
> > >  
> > >  
> > > Director - Wyver Solutions Ltd
> > >  
> > >  
> > >  
> > > Tel:      01773 318 962
> > >  
> > >  
> > >  
> > > Mob:    07922 146 761
> > >  
> > >  
> > >  
> > > Web:    www.wyversolutions.co.uk (http://www.wyversolutions.co.uk)
> > >  
> > >  
> > >  
> > >   
> > >  
> > >  
> > >  
> > > On Friday, 19 July 2013 at 09:30, Julian Tenney wrote:
> > > >  
> > > > You could code a ‘find’ feature up if you write code?
> > > >  
> > > >  
> > > >   
> > > >  
> > > >  
> > > > From: xerte-dev-bounces at lists.nottingham.ac.uk (mailto:xerte-dev-bounces at lists.nottingham.ac.uk) [mailto:xerte-dev-bounces at lists.nottingham.ac.uk] On Behalf Of Mark Berthelemy
> > > > Sent: 19 July 2013 09:23
> > > > To: For Xerte technical developers
> > > > Subject: [Xerte-dev] Searching inside a published object
> > > >  
> > > >  
> > > >   
> > > >  
> > > >  
> > > > Hi there,  
> > > >  
> > > >  
> > > >  
> > > >   
> > > >  
> > > >  
> > > >  
> > > > As a learner, I would like to be able to search inside the learning objects that Xerte produces.
> > > >  
> > > >  
> > > >  
> > > >   
> > > >  
> > > >  
> > > >  
> > > > Is it possible to index the textual elements of the XML that produces a Xerte object? A bit like Zoomsearch (http://www.wrensoft.com/zoom/)
> > > >  
> > > >  
> > > >  
> > > >   
> > > >  
> > > >  
> > > >  
> > > > Thanks,
> > > >  
> > > >  
> > > >  
> > > >   
> > > >  
> > > >  
> > > >  
> > > > Mark
> > > >  
> > > >  
> > > >  
> > > >   
> > > >  
> > > >  
> > > >  
> > > > --  
> > > >  
> > > >  
> > > >  
> > > > Mark Berthelemy
> > > >  
> > > >  
> > > >  
> > > > Director - Wyver Solutions Ltd
> > > >  
> > > >  
> > > >  
> > > > Tel:      01773 318 962
> > > >  
> > > >  
> > > >  
> > > > Mob:    07922 146 761
> > > >  
> > > >  
> > > >  
> > > > Web:    www.wyversolutions.co.uk (http://www.wyversolutions.co.uk)
> > > >  
> > > >  
> > > >  
> > > >   
> > > >  
> > > >  
> > > >  
> > > >  
> > > >  
> > > >  
> > > > _______________________________________________
> > > >  
> > > >  
> > > >  
> > > > Xerte-dev mailing list
> > > >  
> > > >  
> > > >  
> > > > Xerte-dev at lists.nottingham.ac.uk (mailto:Xerte-dev at lists.nottingham.ac.uk)
> > > >  
> > > >  
> > > >  
> > > > http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
> > > >  
> > > >  
> > > >  
> > > >  
> > >  
> > >  
> > >   
> > >  
> > >  
> > >  
> > >  
> > >  
> > > _______________________________________________
> > >  
> > >  
> > >  
> > > Xerte-dev mailing list
> > >  
> > >  
> > >  
> > > Xerte-dev at lists.nottingham.ac.uk (mailto:Xerte-dev at lists.nottingham.ac.uk)
> > >  
> > >  
> > >  
> > > http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
> > >  
> > >  
> > >  
> > >  
> >  
> >  
> >   
> >  
> >  
> >  
> >  
> > _______________________________________________
> >  
> > Xerte-dev mailing list
> >  
> > Xerte-dev at lists.nottingham.ac.uk (mailto:Xerte-dev at lists.nottingham.ac.uk)
> >  
> > http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
> >  
> >  
> >  
>  
>   
>  
>  
>  
> _______________________________________________
> Xerte-dev mailing list
> Xerte-dev at lists.nottingham.ac.uk (mailto:Xerte-dev at lists.nottingham.ac.uk)
> http://lists.nottingham.ac.uk/mailman/listinfo/xerte-dev
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nottingham.ac.uk/pipermail/xerte-dev/attachments/20130719/7e33bab2/attachment-0001.html>


More information about the Xerte-dev mailing list