tag:blogger.com,1999:blog-4848054445359851090.post8799928807070982208..comments2023-07-01T07:39:00.539-07:00Comments on University Software Development: AJAX and PeopleSoftJohn Wagenleitnerhttp://www.blogger.com/profile/00224676480093217330noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-4848054445359851090.post-72805527909118865852012-12-03T09:03:41.542-08:002012-12-03T09:03:41.542-08:00oJohn,
I tried the same as you mentioned
Step 1...oJohn,<br /><br />I tried the same as you mentioned <br /><br />Step 1:<br /><br />Included the Jquery in Message catalog .<br /><br />Created a HTML Area and mapped to DERIVED.HTMLAREA field.<br /><br />HTML Code:<br /><br />Same HTML code you provided<br />Step 2:<br />Created the function <br /><br />WEBLIB_TEST.ISCRIPT1.FieldFormula.IScript_jQuery1<br /><br />Function IScript_jQuery1 Returns Rowset<br /> &rs = CreateRowset(Record.TEST);<br /> &rs.Fill();<br /> Return &rs;<br />End-Function;<br /><br />Step:3<br /><br />Page activate code:<br /><br />Local string &jquery = MsgGetExplainText(29000, 1, "message not found");<br />DERIVED.HTMLAREA.Value = GetHTMLText(HTML.TEST, &jquery);<br /><br />Result:<br /><br />Result Page is having all the letters from message catalog ( i mean Jquery library) Not sure what mistake i am doing here ?sabarinathanhttps://www.blogger.com/profile/15740674658526333747noreply@blogger.comtag:blogger.com,1999:blog-4848054445359851090.post-77407897575768367382009-09-14T04:35:46.300-07:002009-09-14T04:35:46.300-07:00This is a very good article and I tried to follow ...This is a very good article and I tried to follow all steps, facing issues and not clear, I'm sure I've missed a few or misinterpreted. Step 2 and 5 are not very clear as in Step 2 code is given but not sure where to post it, similarly step 5 mentions writing an IScript Function again not sure what and where, how to code. Seek help, throw some light.<br /><br />This is anand.pandit@adityabirla.comAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4848054445359851090.post-88051861880042791362009-01-06T10:13:00.000-08:002009-01-06T10:13:00.000-08:00John, I just found this post that looks amazingly ...John, I just found this post that looks amazingly similar to yours: <A HREF="http://community.psoftpros.net/profiles/blogs/injecting-javascript-amp-ajax" REL="nofollow">Injecting Javascript & AJAX into a PeopleSoft Page</A>.Jim Marionhttps://www.blogger.com/profile/12995110203807924786noreply@blogger.comtag:blogger.com,1999:blog-4848054445359851090.post-9334636194459995352008-12-31T01:59:00.000-08:002008-12-31T01:59:00.000-08:00Hi I have tried the same steps as mentioned by you...Hi I have tried the same steps as mentioned by you in this Post.But when page opens I get following html error.<BR/><BR/>Expected Identifier, String or Number.<BR/><BR/>Please Help.Atul Yadavhttps://www.blogger.com/profile/13604876432685871788noreply@blogger.comtag:blogger.com,1999:blog-4848054445359851090.post-34996500403699460782008-07-24T19:40:00.000-07:002008-07-24T19:40:00.000-07:00John, I've been thinking more about developers...John, I've been thinking more about developers being able to use libraries like jQuery even though they don't have access to the web server's directory structure. Like your solution, a developer in this situation needs to put the "large" JavaScript library in the database, but can't put it in a managed HTML object due to HTML object size limitations. Rather than load the jQuery contents into the page source, however, I recommend using an IScript to serve the jQuery library. From an IScript, you would use the same MsgGetxxx function to fetch the jQuery library from the database. Rather than put the entire contents into an HTML area on the page, you would just put a <script> tag that points to your IScript. Of course, this isn't as efficient as placing the file on the web server, but, for most developers, it is much more practical.Jim Marionhttps://www.blogger.com/profile/12995110203807924786noreply@blogger.comtag:blogger.com,1999:blog-4848054445359851090.post-29268239245767861852007-09-26T19:20:00.000-07:002007-09-26T19:20:00.000-07:00Thanks for the comment, I really appreciate the in...Thanks for the comment, I really appreciate the information. I had never given much thought to the packed version causing that much of a performance hit, but it makes sense. As you can probably can tell from this post and several others, the lack of control we have over our production environment often requires us to take unusual steps to implement certain things. <BR/><BR/>I will definitely take your advice and for production use I will bribe the powers that be to just load the unpacked version of jQuery on the web server. I try cookies and beer, maybe not in that order.John Wagenleitnerhttps://www.blogger.com/profile/08325979399918779570noreply@blogger.comtag:blogger.com,1999:blog-4848054445359851090.post-74690788741323721352007-09-25T23:31:00.000-07:002007-09-25T23:31:00.000-07:00Brilliant post John. It is great to see customers ...Brilliant post John. It is great to see customers customizing PeopleSoft like this. I've been using jQuery for quite some time. One thing I've found is that, even though the packed version is small, it takes an extremely long time for the browser to parse. In my tests I found that the packed version of jQuery took between 250 to 500 milliseconds (nearly half a second) to parse whereas the full and minified versions only took 60 milliseconds. Therefore, I prefer the minimified version. In fact, I actually downloaded the full jQuery and used the <A HREF="http://developer.yahoo.com/yui/compressor/" REL="nofollow">YUI Compressor</A> to compress the jQuery library. I found that combining this with a gzip compression filter like com.cj.gzipflt.GzipFilter results in the smallest download and the shortest parse time. You can read more about the different jQuery distibutions on <A HREF="http://www.julienlecomte.net/blog/2007/08/21/gzip-your-minified-javascript-files/" REL="nofollow">Julien Lecomte's</A> blog.<BR/><BR/>If you plan to use this in production, I strongly encourage you to place your preferred jQuery distribution on your wb server. Here is why... While your message catalog approach gets the job done (and I must commend you on the unorthodox approach), it will result in a much larger file download that will have to be re-downloaded on every page refresh/server round trip. Likewise, if you decide to use the jQuery library on multiple pages, your users will have to re-download the jQuery library with each request. Basically, you loose the benefit of client side browser cache and increase your downloads by at least 20k. By placing the jQuery library on the web server, your users will be able to download the jQuery library once, and then just take the 60ms re-parse hit on every page that uses jQuery.<BR/><BR/>I read that you don't have access to your web server to change files. I feel your pain. If that is the case, then you do what you have to do to get the job done. Maybe if you buy your web server admin cookies?Jim Marionhttps://www.blogger.com/profile/12995110203807924786noreply@blogger.com