![[To web textures]](../tools/tbu.gif)
![[To Index]](../tools/tbx.gif)
ATType - Text description of the type of texture to be generated;
ATData=#xyz...- Parameters for ATType;
BGColor=#rrggbb- Background colour for simple textures;
FGColor=#rrggbb- Foreground colour for simple textures;
ATDim=<x> - Fractal dimension for fractal-noise type textures;
ATSeed=<x> - The seed for the pseudo-random number generator.
ATContrast=<x> - How much variation from the main colour is present.
Not all of these would be needed in each texture. Missing attributes could be assumed to have sensible default values.
New attributes could be added easily at a later date if required in order to improve the scope of the texture generation.
Simply by using ATType=LanguageName
and then using an extended string in the parameter of the ATDim
attribute, any existing texture generation language could be embedded within web pages.
Instead of this UUcode-like format, it would be possible to use a very compressed format which but still maintained the texture in an editable and comprehensible form.
The UUcode-like solution is to be preferred. This makes the documents more compact. Editing of textures is best performed using a graphical front-end, and a translation program to translate between the coded form and the expanded high-level texture-generation language would be trivial to write.
Once a protocol for attributes to the body tag is in place, the data format used could be compressed further and contained in a file to be used in a similar manner to other graphic images.
These, in common with many object oriented graphics formats could contain a default size, but could be rendered equally well at any specified size or scale at the request of the browser.