Scientific Calculator Demo

A test to see whether use of an AddOn is necessary, or whether the almighty ComponentPlugin CommentPlugin is all we need.

It works very nicely:

calc

-- MartinCleaver - 11 Nov 2004

I think it is worth while creating an AddOnPackage that contains the source (if license permits) with instructions on how to add a link to a skin, for example with a calculator icon. If it is in the skin there is no need to define a CommentPlugin template. BTW, I have a rendering issue on my Windows machine with IE 6, rendering the calculator unusable.

Screenshot with rendering issue:

Screenshot of calculator:

-- PeterThoeny - 12 Nov 2004

Are you running XP, Peter? I ask because I tested on IE6/XP and the render comes out fine for me. Perhaps some others can test it too.

AddOns have poorly defined scope to me (some have CgiScripts, some alter control to make TWiki subservient to an external program).

In summary, my view is that AddOns - unlike Contribs and Plugins - have become somewhat of a dumping ground.

So, for reasons of coherency, I would prefer JavaScript components NOT be addons, but be in a separate category.

-- MartinCleaver - 12 Nov 2004

bah, why another category? you've already tried to generalise things as TWikiExtensions. why do i care which language it was written in?

-- WillNorris - 12 Nov 2004

No, we definitely do not need a new category. An Add-on is anything not Plugin/Skin/Contrib-ish. For example, it can be a complete TWiki application without additional scripts.

I am on XP with IE 6. Works OK if I tell IE to View => Text Size => Smaller

-- PeterThoeny - 13 Nov 2004