[jawsscripts] Re: Linking a file to the compiler
- From: Soronel Haetir <soronel.haetir@xxxxxxxxx>
- To: jawsscripts@xxxxxxxxxxxxx
- Date: Sat, 16 Nov 2013 19:21:53 -0900
If you copied examples 3 and 4 rather than re-typing them you appear
to have mistyped things.
I was then expecting the following file organization:
<user_script_directory>\my_script.jss
<user_script_directory>\custom_dir\custom_script1.jss
<user_script_dir>\custom_dir\custom_script2.jss
With the following in <user_script_dir>\my_script.jss:
Use "custom_dir\\custom_script1.jsb"
I would expect that if your script is in a file outside the usual jaws
script directories then you would need to use fully qualified paths.
I am also not aware whether it is actually possible to run the script
compiler by any method other than running the script editor and saving
the script file.
On 11/16/13, Csaba Godo <arpadhazi68.jawsul@xxxxxxxxx> wrote:
>
>
>
> Hi Haetir,
>
> It semms that the JAWS complier could accept only fully qualified
> pathes. I have played araound with the folloving variations:
>
> 1.: use "Lib.Message.jsb" - it was accepted.
> 2.: use "C:\\JFW Extentions\\Lib.Message.jsb" - it was accepted, too.
> 3.: use "\\JFW Extentiosn\\Lib.Message.jsb" - was unaccepted.
> 4.: use "JFW Extentiosn\\Lib.Message.jsb" - was unaccepted.
>
> So I will install my library scripts on the user's machine into a fixed
> folder in the root of the C:\ drive. In this case teh recompilation
> process can be avoided.
>
> By the way, how is it possible to recompile programatically a script
> after its installation?
>
> Cheers,
>
> Csaba
> 2013.11.16. 23:06 keltezéssel, Soronel Haetir írta:
>> I'm pretty sure you would need to know the name of the child directory at
>> least.
>>
>> I would expect
>>
>> Use "ChildDir\\MyFile.jsb"
>>
>> To work, finding ChildDir relative to the current file, but you would
>> certainly need to know what ChildDir is going to be. If you wanted to
>> get fasncy I suppose you could have an installer that overwrites the
>> script file with the actual value of ChildDir and then somehow
>> triggers the jaws script compiler, but that honestly seems like it
>> would be a lot more work than it is worth, even if you could make it
>> work.
>>
>> On 11/16/13, Csaba Godo <arpadhazi68.jawsul@xxxxxxxxx> wrote:
>>> Hi guys,
>>>
>>> I'm back in with a question. Now it concerns about the use and include
>>> directrives in JAWS Basic. Mmy question is whether they can accept only
>>> fully qualified pathes or not? I mean if it is somehow possible to use
>>> path string with them like in HTML pages, where it is not necessary to
>>> fuly qualify the path if it refers to a subdirectory of the directory
>>> where the actual page is located. Like this "../pages/x.jpg". I'm not at
>>> home in C programming, so I do not know how files can be linked into the
>>> compilation process.
>>>
>>> I would like to separate my scripts into two parts and place the
>>> reusable library scripts into a subdirectory of the common directory of
>>> JAWS. When I pass only the file name then the compiler looks for the
>>> referred file in the same directory where the JSS file, which refers to
>>> it is located. If I pass the fully qualified path, like the one below,
>>> it works.
>>>
>>> This works: use "C:\\JFW Extensions\\Lib.Messages.jsb".
>>> But I'd like to put them into a subdirectory of the common JAWS
>>> directory, whose exact path is unknown.
>>>
>>> Thanks in advance for your help!
>>>
>>> Csaba
>>>
>>> __________ďż˝
>>>
>>> View the list's information and change your settings at
>>> http://www.freelists.org/list/jawsscripts
>>>
>>>
>>
>>
> __________ďż˝
>
> View the list's information and change your settings at
> http://www.freelists.org/list/jawsscripts
>
>
--
Soronel Haetir
soronel.haetir@xxxxxxxxx
__________ďż˝
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
Other related posts: