Dear AZ Forum Posters:
Recently we have seen some issues with posts containing several WeiTable layouts freezing up people's computers. This happens with both new and old machines so CPU speed is not the main deciding factor.
Example (Warning: Opening this might freeze up your browser, handle with care):
http://forums.azbilliards.com/showthread.php?t=36919
If you check carefully in this thread, all the table layouts in a thread are actually "running" programs instead of static images. (you can move the balls around on each table to test). Therefore they are "live".
Both WeiTable and CueTable are interactive web-base programs using an industry standard plug-in: Macromedia Shockwave (now Adobe Shockwave). The program will take up some system memory resource. The more table layout you open up, the more memory the computer requires. Unfortunately, in a discussion forum, we can't really predict whether there will be table layouts included and how many.
So, what can we do to avoid the problem?
IMHO, after more than 2 layouts has been posted in a thread, you should consider the following to protect your fellow readers.
1, Use screenshot (screen captures) instead of adding another table. You can upload your jpg or gif files using the attach functions in the advanced posting window. Also, you may want to include the code in the post so people can edit and respond to your layout.
Here is a thread about posting pictures on AZ
2, When quoting a post with layouts, remember to delete the [ WEI ]... [ /WEI ] layout codes to avoid repeats.
Here is another example post with CueTable data link and its image together to show a situation. If the user wants to edit the layout, he/she can do so by clicking on the link:
http://forums.azbilliards.com/showthread.php?p=417822#post417822
You can also use cuetable to do a discussion with many possible branching outcomes. With a carefully prepared structuring, the illustration can be very effective with low use on people's cpu memory. Please review the one pocket "what do you do here" posts last month:
Part I - What would you do here? (one pocket: return break)
part II: Possible shots after the return break
part III: Your shot again
Please let me know if there is any questions or suggestion. I will try my best to answer.
Recently we have seen some issues with posts containing several WeiTable layouts freezing up people's computers. This happens with both new and old machines so CPU speed is not the main deciding factor.
Example (Warning: Opening this might freeze up your browser, handle with care):
http://forums.azbilliards.com/showthread.php?t=36919
If you check carefully in this thread, all the table layouts in a thread are actually "running" programs instead of static images. (you can move the balls around on each table to test). Therefore they are "live".
Both WeiTable and CueTable are interactive web-base programs using an industry standard plug-in: Macromedia Shockwave (now Adobe Shockwave). The program will take up some system memory resource. The more table layout you open up, the more memory the computer requires. Unfortunately, in a discussion forum, we can't really predict whether there will be table layouts included and how many.
So, what can we do to avoid the problem?
IMHO, after more than 2 layouts has been posted in a thread, you should consider the following to protect your fellow readers.
1, Use screenshot (screen captures) instead of adding another table. You can upload your jpg or gif files using the attach functions in the advanced posting window. Also, you may want to include the code in the post so people can edit and respond to your layout.
Here is a thread about posting pictures on AZ
2, When quoting a post with layouts, remember to delete the [ WEI ]... [ /WEI ] layout codes to avoid repeats.
Here is another example post with CueTable data link and its image together to show a situation. If the user wants to edit the layout, he/she can do so by clicking on the link:
http://forums.azbilliards.com/showthread.php?p=417822#post417822
You can also use cuetable to do a discussion with many possible branching outcomes. With a carefully prepared structuring, the illustration can be very effective with low use on people's cpu memory. Please review the one pocket "what do you do here" posts last month:
Part I - What would you do here? (one pocket: return break)
part II: Possible shots after the return break
part III: Your shot again
Please let me know if there is any questions or suggestion. I will try my best to answer.
Attachments
Last edited:
