| 1 | Notes about plugins |
| 2 | |
| 3 | |
| 4 | I have users that want to visit my pages with tclets, but they do not |
| 5 | have the plugin. What can I do? |
| 6 | |
| 7 | Add a pluginspage=http://www.sunlabs.com/tcl/plugin/ name=value |
| 8 | pair to the embed statement. This will cause Navigator to find |
| 9 | the plugin for your user and suggest they install it. The user |
| 10 | is then prompted to download and install the plugin, and then she |
| 11 | has to restart the browser and revisit your page. Very inconvenient |
| 12 | and only slightly better than giving your users the broken image |
| 13 | icon. Netscape says they are working on a more automatic solution. |
| 14 | |
| 15 | |
| 16 | |
| 17 | |
| 18 | 14. Your demos work just fine, but when I visit my own pages with tclets in |
| 19 | them, at http://www.myserver.com/~mypages/mypage.html, I still get the |
| 20 | broken image icon. Why doesn't it work for me? |
| 21 | |
| 22 | This is likely because your web server -- the program that sends |
| 23 | the pages to your browser when you click on a URL -- is not |
| 24 | sending the right mime-type when it sends the '.tcl' file. You |
| 25 | can work around this by adding a type=application/x-tcl name=value |
| 26 | pair to the embed statement, which will cause Navigator to infer |
| 27 | that it should use the Tcl plugin anyways. A better solution is |
| 28 | to ask your system administrator to configure the web server to |
| 29 | send the mime type application/x-tcl when it sends files with a |
| 30 | '.tcl' extension. Nearly all web servers in the world nowadays |
| 31 | are already configured to do this, the only ones we are aware of |
| 32 | that do not are some older versions of Apache. |