My favorite distro, PCLinuxOS, had just released early this week its long anticipated 2007 version. Linux.com has one of the early reviews.
Meanwhile, DSWD Bicol is set to adopt this distro. Cool.
My favorite distro, PCLinuxOS, had just released early this week its long anticipated 2007 version. Linux.com has one of the early reviews.
Meanwhile, DSWD Bicol is set to adopt this distro. Cool.
As discussed in the previous post, all actions in a component that eventually require a server trip would invoke %SubmitScriptName for submitting the page. As such, it sometimes provide a convenient point for performing javascript modifications on the page.
This is achieved by storing a reference to the original function, and redefining %SubmitScriptName to perform your custom logic — invoking the original function as needed.
The following sample scenarios may help to illustrate this technique.
Continue reading
In PeopleTools 8.4, %SubmitScriptName is the meta-HTML javascript function used by all PeopleSoft component pages for triggering server-side actions. %SubmitScriptName is translated at run time (i.e., when the page is rendered) to submitAction_win0. It may be related to %FormName as submitAction_%FormName, since %FormName is also translated to win0. I don’t know how PeopleTools internally translates %FormName, but as far as I can tell it is always translated to win0 inside any component.
The %SubmitScriptName function is passed 2 parameters:
* – I just made up this label for the purpose of discussion.
The action ID that can be passed to %SubmitScriptName can be categorized into the following type of actions:
Continue reading
Just a simple tip. When embedding static javascript code on a page, the obvious approach is to place the code as a constant value in the HTML Area control. For example, suppose the following code:
var something = "something";
function SomeThing() {
/* Something */
/* something... */
}