Nasher wrote:Afternoon,
What is the best way to handle complex intra-browser data manipulation?
Can eValid help solve this?
Good morning Nasher and welcome to the eValid forum.
To answer your question:
The quickest and most reliable is to use the DOM manipulation. In that
context you have internal variables as follows:
sourceIndex == either set with an IndexSet command or found with
an IndexFindElement or IndexFindElementEX (regular
expression search) command.
elementValue == either set with a a ValueSet or given a value
by a ValueGetElement command.
If you know a value (strings, always, into the DOM, you can use
ValuePutElement to insert it into the DOM.
The internal values for sourceIndex and elementValue are also settable
from the environment variables file...
This route is very efficient and allows for pick up from one page/window
and drop into another page/window...all in the same browser instance.
A VERY BIG advantage of this is that it can go on in multiple browsers
such as what you may do in a server loading context. Each browser
execution space is separate from each other one.
The other route, using the local file system for storage, e.g. with
SaveSelectedText or SaveSelectedObjProperties, etc., is also possible,
but operation with multiple browser is only possible when you fully
parameterize the local file names so that they are specific to the
browser instance. The use of "invisible" operations as described
above is FAR, FAR superior -- and also has virtually no overhead.
I hope this answers your question.
-eValid Support
Posted: Wed Oct 30, 2013 1:07 pm