The Origin Forum
File Exchange
Try Origin for Free
The Origin Forum
Home | Profile | Register | Active Topics | Members | Search | FAQ | Send File to Tech support
Username:
Password:
Save Password
Forgot your Password? | Admin Options

 All Forums
 Origin Forum for Programming
 LabTalk Forum
 Sharing Scripts via Network Drive
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic Lock Topic Edit Topic Delete Topic New Topic Reply to Topic

tib

Switzerland
105 Posts

Posted - 07/27/2006 :  04:55:45 AM  Show Profile  Edit Topic  Reply with Quote  View user's IP address  Delete Topic
Origin Version (Select Help-->About Origin): 7.5SR4
Operating System: WinXP


Hi there,

I once wrote quite a few Origin buttons which could be shared with other users via sending them OPK files.
Now, pretty often there are many little changes in the .OGS scripts. Packing OPKs on my computer and installing on all the other computers is time consuming and annoying.

Now, there should be the possibility to put the scripts into a network directory where all computers have access to.
When I do changes on the scripts they immediately apply on all computers.

The routines are now used in the way "run.section(OGSFile,Section)".
How do I transfer my scripts, INI-files, etc. and buttons (now on my local user drive)
to the network drive that they will have the same look on every computer?
Just copying OGS, INI, BMP does not work. How can I change all the path information?
I tried with Options|File locations ... didn't work. (BMP not found...)
I want to avoid to drag and drop more than 40 Buttons onto toolbars on 4 or more computers...

Mike Buess, you once said
http://www.originlab.com/forum/topic.asp?TOPIC_ID=2124
that you have a way that toolbars changes can also be transferred.
How does this work?

Greetings,
Tilman.

Mike Buess

USA
3037 Posts

Posted - 07/27/2006 :  09:05:33 AM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Hi Tilman,
quote:
The routines are now used in the way "run.section(OGSFile,Section)".
How do I transfer my scripts, INI-files, etc. and buttons (now on my local user drive)
to the network drive that they will have the same look on every computer?
Just copying OGS, INI, BMP does not work. How can I change all the path information?
When Origin encounters a file with a relative path in run.section or INI key it looks first for the file on the User path and then the program or Network path. If you avoid absolute paths in your scripts then copying the OGS, INI, BMP should work as long as the user is not running Origin at the time. In fact, you might get by with saving your OGS, INI, BMP to the Network path and deleting the corresponding files from each User path.
quote:
you have a way that toolbars changes can also be transferred.
How does this work?
Depends on the changes but in general it involves uninstalling/reinstalling the toolbar and/or restarting Origin.
quote:
I want to avoid to drag and drop more than 40 Buttons onto toolbars on 4 or more computers...
OPKs can be run via script with the OPK object. You might consider creating a master OPK that installs all others.

Mike Buess
Origin WebRing Member
Go to Top of Page

tib

Switzerland
105 Posts

Posted - 07/27/2006 :  09:59:45 AM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Thanks Mike,

User path is %Y...
C:\Documents and Settings\user\Application Data\OriginLab\Origin75E\User Files
Program path is %a=system.path.program$
C:\Program Files\OriginLab\OriginPro75
How can I teach Origin to search OGS,BMP,INI etc. in a specific Network path?
for example P:\Common\Software\Origin\Buttons
What is the network path you mentioned?
Would this be a third path where Origin is seraching in?

Tilman.
Go to Top of Page

Mike Buess

USA
3037 Posts

Posted - 07/27/2006 :  10:20:03 AM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Hi Tilman,

I got the impression from your original post that you had a server + client Origin installation. Now it looks like you have standalone installations (Origin is installed on each computer). In that case you can add the files to %A=system.path.program$ on each PC. (There is no third "network" path.) The files should be in the same location relative to %A as they were in %Y.

Mike Buess
Origin WebRing Member

Edited by - Mike Buess on 07/27/2006 10:32:16 AM
Go to Top of Page

tib

Switzerland
105 Posts

Posted - 07/27/2006 :  10:59:56 AM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Hi Mike,
sorry, I did not write it clear:
I have a standalone version on my computer.
Some users also have a standalone on their computer.
Some are using a "network license", where Origin seems to be locally installed on each computer but only one user in the network can use it at a time.

So the system.path on each machine is something like C:\programs\Origin

But from my computer I have no access to these local directories to update my scripts and buttons.
That's why I want to have the buttons on a directory where all users have access to, e.g. P:\Software\Origin...

I still do not see how to tell Origin on all the other computers that the buttons are located somewhere on P:\Software\Origin...
Do I have to copy OPK there and install them from there? I will try...

Go to Top of Page

Hideo Fujii

USA
1582 Posts

Posted - 07/27/2006 :  2:55:04 PM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Hi Tilman,

Just a general comment: Having an initialization file(.INI) in a remote place is not generally recommended, even if it may be technically possible. This is because your Origin becomes communication-error-prone to start or run. When the script file path is not specified, Run.section first look at the script at the User Files path(=%Y), then Origin program path (system.path.program$), but you can specify any path if you like. Note that don't use double quatation for around the path+file name. E.g.:

  run.section(P:\His Apps\hisogs,Section1, %A $(B)); //%A and B are arguments

So, your client button can always call the same remote(e.g. P:) entry OGS, which can then do whatever your updated application. Also, Mike's master OPK is a very good idea.

--Hideo Fujii
OriginLab

Edited by - Hideo Fujii on 07/27/2006 3:07:28 PM
Go to Top of Page
  Previous Topic Topic Next Topic Lock Topic Edit Topic Delete Topic New Topic Reply to Topic
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
The Origin Forum © 2020 Originlab Corporation Go To Top Of Page
Snitz Forums 2000