Hi,
yes,
for swf files with embedded, that's possible that way:
in the .config files it is possible to define parameters for the "kprotectcl" tool (the command line version of the krpano Protect Tool) by he kprotectclparameters setting:
|
Quellcode
|
1
2
3
4
5
|
# kprotectclparameters
# - parameter for the kprotectcl tool
# - only needed for buildembeddedswf=true
#
kprotectclparameters=-nomb -swfsize=900x600
|
and the kprotectcl tools allows domain limiting by the "-domain=###" parameters:
|
Quellcode
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
|
syntax: kprotectcl -o=output.swf [options] <file1|name> ... <fileN|name>
options:
-o=### ... path/name of output file
-xml=# ... startup xml file to embed
-domain=# ... limit to domain (can be used more than once)
-noep ... disable external parameters (http-get, flashvars)
-nojs ... disable javascript interface
-nolu ... disable local / offline usage
-bf ... branding free
-expire=YYYY-MM-DD ... set a panorama expire date
-expiredurl=# ... url to open at expire date
-swfsize=# ... set standalone size of the swf (WIDTHxHEIGHT)
-fs ... start in fullscreen mode (standalone only)
-nomb ... no menu bar (standalone only)
-baseswf=# ... path to the base krpano.swf (default is tool folder)
-licpath=# ... path to the folder with the krpano licenses
-fpexe=# ... path to flashplayer standalone player exe file (Windows only)
|
that means e.g. by adding:
|
Quellcode
|
1
|
kprotectclparameters=-domain=page1.com -domain=page2.com
|
in the .config file it's possible to create domain limited swf files automatically (note - buildembeddedswf must be also set to true
and for swf file without embedded data, generate once a domain limited swf file by the krpano Protect Tool, and change in the .config file the path to the source swf by file by the "krpanoswf" parameter:
|
Quellcode
|
1
|
krpanoswf=your-domain-limited.swf
|
best regards,
Klaus