1,633
edits
SigServer DEV: Difference between revisions
m
no edit summary
Fahrenheit (talk | contribs) m (→XML Parsing) |
mNo edit summary |
||
| Line 26: | Line 26: | ||
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. | 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, | ... if a users feels like having a total mess of a sig pic where every single character is done in a different font type, colour and size... why not let him do it? ... | ||
Some examples: | Some examples: | ||
| Line 41: | Line 41: | ||
(Let's call the new server "sig server" for now) | (Let's call the new server "sig server" for now) | ||
* The sig server has it's own user database | * The sig server has it's own user database | ||
* Users can configure the signature pics via a | * Users can configure the signature pics via a web interface of the sig server | ||
* The sig server provides an url which returns the sig pic | * The sig server provides an url which returns the sig pic | ||
* When the | * When the URL is requested the sig server will look for a locally cached pic or cached anidb status information for the user and will either return the cached pic, a new pic created with the cached information or will issue an http request to retrieve the needed stats via as XML and then create the pic. | ||
It is important to underline at this point that the sig server does never directly interact with the | It is important to underline at this point that the sig server does never directly interact with the AniDB database. It does not have SQL access, it does not store the users AniDB password (only their AniDB username) and it never modifies any information on AniDB. | ||
On suggestion for how things could look like (feel free to suggest other ways): | On suggestion for how things could look like (feel free to suggest other ways): | ||
* AniDB will link to the sig server | * AniDB will link to the sig server | ||
* A first time user will visit the sig server and register a new account (username and password can be different from | * A first time user will visit the sig server and register a new account (username and password can be different from AniDB) | ||
* Once registered the user gets to a configuration page where he has to enter his | * Once registered the user gets to a configuration page where he has to enter his AniDB username (without the AniDB password!) and there will be a help text explaining the required profile settings on AniDB for this to work (the AniDB XML interface will only provide the information if the user selected certain permissions for the guest user) | ||
* the user can then either select an image from a selection of publicly available pictures stored on the server or can upload is own picture (for each own picture the user can specify whether it should be made public or not (needs mod review)). | * the user can then either select an image from a selection of publicly available pictures stored on the server or can upload is own picture (for each own picture the user can specify whether it should be made public or not (needs mod review)). | ||
* once a picture is selected the user can select the type of data shown and the formatting from predefined profiles or can define his own profile (profile can be made public) | * once a picture is selected the user can select the type of data shown and the formatting from predefined profiles or can define his own profile (profile can be made public) | ||
| Line 57: | Line 57: | ||
** font/size/color/location/... for each part | ** font/size/color/location/... for each part | ||
** maybe some kind of basic scripting | ** maybe some kind of basic scripting | ||
* one user should be able to specify | * one user should be able to specify up to N signature picture+profile combinations which can all be active at the same time (maybe 5 ?) | ||
* some nice statistics and a modding interface would be good | * some nice statistics and a modding interface would be good | ||
| Line 92: | Line 92: | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=review http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=review] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=review http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=review] | ||
:* most | :* most recent reviews of a user | ||
* [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=recs http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=recs] | * [http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=recs http://anidb.net/perl-bin/animedb.pl?show=xmlsig&t=userlatest&uid=32&list=recs] | ||