Boltgreywing
Senior Member
When a user initially creates an account on Duelingpets they will start off with the default color applied to the site itself.
View attachment 826
However if they don't like the color they can then change color using the Add Avatar and Edit Browser button. When they do so they will come up to a screen that looks like this:
View attachment 827
In the bottom of the screen there is a colorscheme drop down box that by default holds the default color as you can see just now. Instead we are going to change the colorscheme by using the drop down arrow and selecting High-Contrast.
View attachment 828
For the purposes of this demo we will just be using High-Contrast color. However in later builds there might be even more options. The users themselves could potentially create a color choice of their own and select the color they wish and it would change to that. Now that we got High-contrast all we need to do is click the update userinfo button and our new colorscheme will be applied.
After we click the update button our new interface will now look like this:
View attachment 829
Now you can see we are now looking at the high-contrast view of the page of the user profile. However this change doesn't just only affect the user profile but other pages as well.
View attachment 830
Stats:
View attachment 831
The entire site gets converted to the new colorscheme only viewable by the current user who changed it. The other users keep the default color they start off with.
View attachment 832
So users can have whatever colorscheme they wish to without being restricted to the color of the site. If on the other hand a colorscheme winds up getting deleted at some point they will then revert to the default colorscheme if that were to happen.
Now this next screen will show only the current user the information of how he designed his pallete as well as the ability to edit and delete said pattern.
View attachment 833
The code itself to change colors is all in hexadecimal from 0-f which proceeded by a # symbol. This number symbol is important along with the number of digits that need to be in place for this system to work. When a user destroy a color pallete that he is currently using he defaults back down to the default color like so:
View attachment 834
When the user clicks okay their screen then looks like this:
View attachment 835
As you can see they have been returned to the default color. On top of that every user who used this color was also returned back to the default at the same time. This is a safety precaution to prevent the website from crashing should a user's colorscheme get deleted while still providing for colorblind to access the site itself.
This code is still in development and their is still many bugs for me to fix. This only works if the colorscheme is deleted by the user or admin. If a user's account gets deleted thats where things will get dicey as there will be more then one colorscheme that will be destroyed as well as needing to change multiple different users using each of the various ones.
This could break the site itself if not handled correctly and might require backend administration which will most likely have to be done manually if things do indeed go wrong. This will require a lot of time and sweet on my part to make certain every users colorscheme is not null and is instead the Default color.
So any questions?
View full news
View attachment 826
However if they don't like the color they can then change color using the Add Avatar and Edit Browser button. When they do so they will come up to a screen that looks like this:
View attachment 827
In the bottom of the screen there is a colorscheme drop down box that by default holds the default color as you can see just now. Instead we are going to change the colorscheme by using the drop down arrow and selecting High-Contrast.
View attachment 828
For the purposes of this demo we will just be using High-Contrast color. However in later builds there might be even more options. The users themselves could potentially create a color choice of their own and select the color they wish and it would change to that. Now that we got High-contrast all we need to do is click the update userinfo button and our new colorscheme will be applied.
After we click the update button our new interface will now look like this:
View attachment 829
Now you can see we are now looking at the high-contrast view of the page of the user profile. However this change doesn't just only affect the user profile but other pages as well.
View attachment 830
Stats:
View attachment 831
The entire site gets converted to the new colorscheme only viewable by the current user who changed it. The other users keep the default color they start off with.
View attachment 832
So users can have whatever colorscheme they wish to without being restricted to the color of the site. If on the other hand a colorscheme winds up getting deleted at some point they will then revert to the default colorscheme if that were to happen.
Now this next screen will show only the current user the information of how he designed his pallete as well as the ability to edit and delete said pattern.
View attachment 833
The code itself to change colors is all in hexadecimal from 0-f which proceeded by a # symbol. This number symbol is important along with the number of digits that need to be in place for this system to work. When a user destroy a color pallete that he is currently using he defaults back down to the default color like so:
View attachment 834
When the user clicks okay their screen then looks like this:
View attachment 835
As you can see they have been returned to the default color. On top of that every user who used this color was also returned back to the default at the same time. This is a safety precaution to prevent the website from crashing should a user's colorscheme get deleted while still providing for colorblind to access the site itself.
This code is still in development and their is still many bugs for me to fix. This only works if the colorscheme is deleted by the user or admin. If a user's account gets deleted thats where things will get dicey as there will be more then one colorscheme that will be destroyed as well as needing to change multiple different users using each of the various ones.
This could break the site itself if not handled correctly and might require backend administration which will most likely have to be done manually if things do indeed go wrong. This will require a lot of time and sweet on my part to make certain every users colorscheme is not null and is instead the Default color.
So any questions?
View full news