Harshad,
Re your queries:
>1) Some sort of user friendly windows type Command file Builder, which
>would ask the user to specify numbers of nodes, names, search and code
>specifics etc. This might prevent being bogged down in remebering Nudist
>command linguistics.
Try setting up your names and nodes in a table, creating a form letter with
the search command, and using the table as the data source for the merge
process. Merge to new document, and save as text. Saves a huge amount of
time when you're writing a long repetitive command file.
>
>2) Within the command file construction, it may be helpful to have a
>type of Auto-Numbering system for the node sepcification. The reason for
>this suggestion is that for a project such as mine, where I have 120
>nodes in total, if one mistake is made in the file, then I have to run
>the command file, and see where the problem lies by examining the node
>explorer, each time. The alternative is to check 20 pages of code.
I think the above methods would help with this.
>
>4) Is it possible to Free form code within a search result txt file, and
>import this coding into the project?
You could import the search report as a file and code it - but why would
you? You get the results of any search as a node, and you can code from the
node browser to any node you like (including new freenodes). Note that if
the line of text that is found by the search is inadequate, then you can
'Jump to source' and add coding of as much text as is relevant.
Dr Patricia Bazeley
Head, Research Development Unit
University of Western Sydney Macarthur
PO Box 555 Campbelltown 2560
Australia
ph: +61 2 4620 3268
fax: +61 2 4627 2406
email: [log in to unmask]
http://btwebsh.macarthur.uws.edu.au/patB/
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|