|
|
|
In the Build Code section it was shown how the code generated by the applet program was modified so that it would work in DellT@lk. This particular code was copied to the clipboard as text rather than HTML because it is easier to find the items that must be changed when it is displayed in short lines. However, if this text were to be pasted into DellT@lk it may contain unwanted breaks (<br>) which will cause it not to work. To avoid this problem, before pasting it, go through it and delete all spaces. After this is done, the code will look like this: <applet archive="AnFade.jar" codebase="http://www.mysite.com"
code="AnFade.class" width="186" height="207"><param name="credits" value="Applet by Fabio Ciucci
(www.anfyjava.com)"><param name="res" value="1"><param name="image1"
value="http://www.mysite.com/canale.jpg"> This is not as easy to read as it was with the spaces, but it will now not have any unwanted breaks. (Note that depending on the resolution of your monitor it may appear to have breaks--this is not intentional, if you do it in a word processor any spaces required because of word length will not convert to breaks). At this point, you are ready to try it in DellT@lk. This is why the Scratch Pad conference was provided. In the older version of DellT@lk there was a "Delete Message" option, so if you posted something that didn't work, you could remove it. That option is no longer there, so you must approach your trials using different options. Please follow these suggested steps: 1. Enter your applet with whatever text you desire using whatever title to the post you think appropriate. 2. After you have completed the text and applet lines for your post, click on "Preview." The screen will then show you what your applet looks like. If it looks like a gray rectangle, it didn't work. Scroll down below the preview and look at the HTML that DellT@lk has converted your pasted applet into. If you see any <BR>s in it, delete them, and click Preview again. If after you repeat this a couple of times and nothing has worked, click "Post." 3. If you post the message, the chances are that someone will take a look at your HTML and if they see some error that perhaps you have missed, will point out where to look and/or make the appropriate changes and post your applet as a response to your post. If this happens, right-click their post, copy their HTML which worked and compare it with yours. If you think you have now solved the problem please don't post another message with the changes. Go to your original message, click "Edit" and make the changes, then click "Edit" again to post the changed message. 4. Once you have the applet working properly, go ahead and make little changes to the various parameters if you want to see modest changes in the appearance of the applet (or if you want to solicit readers' opinions on what looks best) and post them. Posting repeated failed attempts results in a very congested conference and will discourage some readers who might offer help from wading through dozens of messages to find the one that they might help with. 5. Once your applet is functional, save your applet lines to your signature box in your Preferences or as a text file which is easily accessible.
|
|
|