Hi Stephen, Awwww yeeeaaaahhhh. JQuery Hive FTW.
Sorry, I misread your answer earlier. I thought you are doing the entire import via client side javascript. Sir, wish you the best of luck and please update us on how things are going. Thanks again, -Jian On Apr 13, 1:13 pm, Stephen Moore <[email protected]> wrote: > On Thu, Apr 14, 2011 at 12:02 AM, Jian Huang <[email protected]> wrote: > > Hi Stephen, > > Hello, > > > > > I personally prefer using JQuery. Manuel wrote a really good tutorial > > on using Jquery AJAX RQL. > > I essentially use jQuery for doing the actual Post of rql to the > server (which in turn passes that to the cms and returns the result). > > I use web workers to do the post to the server, with a fallback if the > browser doesn't support them. So I'm not restricted to one rql > statement at a time (There's quite a lot of rql statements involved > when you're trying to determine a page ioid for each page that is > published in a site and every speedup helps). > > To make the workers as minimal as possible, I > usedhttps://github.com/rwldrn/jquery-hiveas a reference and got the > minimum code required to do a post. The implementation in that library > is based off jQuery, so I'm essentially using jQuery :p > > (and I use jQuery itself in other sections of the tool for dom related stuff) > > >http://manuelschnitger.wordpress.com/2011/02/17/rql-in-a-nutshell-par... > > Also, my app isn't a plugin to the cms, it's completely standalone. > > > The asmx method is the method via webservice. I recommend against > > using the webservice because I found it much slower and unstable than > > the rqlconnector.asp method, especially in large scale RQLs. > > Fair enough. I'll have a play around with the soap interface vs that > asp page and see what happens :) > > > > > You mentioned that you will be writing a custom tool for import. > > Since javascript is not ideal for local file R/W, I would recommend > > writing a windows app for the import. Yes, windows app can send > > RQLs. Simply post the RQL to the rqlconnector.asp. > > I've actually made two tools: > > Pre-import, which is a python app that is used to transform the site > in such a way that we can use this content import manager plugin to > put the site into the cms. (there are a lot of sites that need to go > into the cms with varying ranges of complexity) > > Post-import, which is what this thread talks about, which just > modifies the pages in the cms so that we don't have to manually change > all the urls to point to the correct ioids. I could have also made > this a desktop app, but I wanted to play around with making a > completely client side javascript app :) > > As a side note, server side javascript is not too bad for file io (see > node.js), but this is all client side, so it has no direct access to a > filesystem anyways :p > > Thankyou > > Regards, > Stephen. -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/reddot-cms-users?hl=en.
