340
edits
SigServer DEV: Difference between revisions
→Vision
m (→Data Retrieval) |
(→Vision) |
||
| Line 17: | Line 17: | ||
The user would not need any webspace to host such images and would not need to update/regenerate them. All signature images would be directly loaded from an AniDB webserver. | The user would not need any webspace to host such images and would not need to update/regenerate them. All signature images would be directly loaded from an AniDB webserver. | ||
The idea is for the sig server to be the middle entity between AniDB and the user, which allows almost any kind of singature pic to be created, according to the personal preferences of the user. As such a lot of attention should go towards the configuration/customization interface of such a feature. We are aware that this is a hell lot of work, but it's the long term goal. The image generation itself is fairly easy. | |||
Basically AniDB will offer all kinds of stats data and more via xml, much more than is currently on offer. The sig server would transparently get it's data from AniDB and the user will be able to pick all kinds of information bits from the available data and position and format it freely on a background pic which he can upload himself. | |||
Of course many users wouldn't need this degree of flexibility, so there would need to be some common premade default selections for style/info combinations which are most commonly requested. Furthermore background images could be shared between users. | |||
... if a users feels like having a total mess of a sig pic where every single character is done in a different font type, color and size... why not let him do it? ... | |||
Some examples: | |||
[[Image:Sig1.png]] | |||
[[Image:Sig2.png]] | |||
=Data= | =Data= | ||