📄 12_6.htm
字号:
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Author" content="Weng Kai">
<meta name="GENERATOR" content="Mozilla/4.5 [en] (Win95; I) [Netscape]">
<title>Applet restrictions and advantages</title>
</head>
<body>
<h2>
12.6 Applet restrictions and advantages</h2>
<hr WIDTH="100%">
<br>For safety's sake, applets are quite restricted and there are many
things you can't do. You can generally answer the question of what an applet
is able to do by looking at what it is supposed to do: extend the functionality
of a Web page in a browser. Since, as a net surfer, you never really know
if a Web page is from a friendly place or not, you want any code that
<br>it runs to be safe. So the biggest restrictions you'll notice are probably:
<ol>
<li>
An applet can't touch the local disk. This means writing or reading, since
you wouldn't want an applet to read and transmit important information
about you across the Web. Writing is prevented, of course, since that would
be an open invitation to a virus. These restrictions can be relaxed when
digital signing is fully implemented.</li>
<li>
An applet can't have menus. (Note: this is fixed in Swing) This is probably
less oriented toward safety and more toward reducing confusion. You might
have noticed that an applet looks like it blends right in as part of a
Web page; you often don' t see the boundaries of the applet. There's no
frame or title bar to hang the menu from, other than the one belonging
to the Web browser. Perhaps the design could be changed to allow you to
merge your applet menu with the browser menu ⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -