| Commit message (Collapse) | Author | Age | Lines |
| ... | |
| | | | | | | | | | | | |
|
| | | | | | |/ / / / /
| | | | |/| | | | | |
|
| | | | | |/ / / / / |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
-Makes "main" function `color_embed` that takes an rgb tuple, calls
`all_colors` to get all other color types, gets a name from the hex
color, creates embed, calls `create_thumbnail` to get image, and
then sends main embed.
-Makes functions `xxx_to_rgb` functions to call `color_embed`
-Creates new `hex_to_rgb` function
-TODO: test all functions and continue restructure.
|
| | | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
The conversion functions from hsv, hsl and cmyk now return r, g, b
instead of a variable rgb_tuple.
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | | | | | | |
|
| | | | | |\ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
color-677
|
| | | | | | | | | | | |
|
| | | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
I made a few changes, the biggest being the fuzzy match function to
return a hex color code based on an input color name.
Open items that I can think of so far:
-Since the json file has color names and hex values, in order to
use fuzzy matching for a color name the color must first be
converted to hex. Currently there is only a rgb to anything function
which returns values in a dictionary.
-The main embed creation references the rgb_color before it is defined,
should the command function be moved to the bottom of the file or just
the main embed creation and sending?
-When using the rgb mode, should the user be forced to do (r, g, b) or
should the command handle an input of "r, g, b"?
If you are reading this, thank you.
|
| | | | | |\ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
color-677777777
|
| | | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Details: https://github.com/python-discord/sir-lancebot/issues/677
NOTE: get_color_fields (line 122) method explicity requires a valid tuple of RGB values.
|
| | | | | | | | | | | | |
|
| | | | | |/ / / / / / |
|
| | | | | | | | | | | |
|
| | | | | |\ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
color-677
|
| | | | | | |\ \ \ \ \ \ |
|
| | | | | |/ / / / / / /
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Updated the code to parse user_input depending on the color code
'mode' passed to the command. Added stub code for future color codes
and embeds if mode is None or wrong code.
|
| | | | | | | | | | | | |
|
| | | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Still a work in progress but commenting out stub code and unused
imports. List of To-Do's still applies.
|
| | | | | |\ \ \ \ \ \ \ |
|
| | | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
Implemented the thumbnail creation from CyberCitizen0,
worked on adding some features to the program.
Notable Changes:
-Check if user passes in hex color
-Create thumbnail based on rgb_color
To-Do:
-Create hex color from rgb color
-Create readable rgb color from user input
Co-authored-by: Mohammad Rafivulla <[email protected]>
|
| | | | | | |\ \ \ \ \ \ \
| | | | |_|/ / / / / / /
| | | |/| | | | | | | |
| | | | | | | | | | | | |
color-677
|
| | | | | | | | | | | | | |
|
| | | | | | | | | | | | | |
|
| | | | | | | | | | | | | |
|
| | | | | | |\ \ \ \ \ \ \ |
|
| | | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
- import PIL is the way to import pillow.
- discord-flags isn't being used yet.
- Fixed some of the linting issues.
|
| | | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | |
| | | | | | | | | | | | | |
Original source: https://github.com/ryanzec/name-that-color/blob/master/lib/ntc.js#L116-L1681
|
| | | | | |/ / / / / / / /
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
Original source: https://github.com/ryanzec/name-that-color/blob/master/lib/ntc.js#L116-L1681
|
| | | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
Co-authored-by: Mohammad Rafivulla <[email protected]>
|
| | | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
This is a large empty file with lots of comments. My general proposal
is outlined in the code stumps. Details will need to be hashed out and
decided on with CyberCitizen01.
In particular:
- How to use URLs that has list of color names? Read those into a
dictionary?
- How to handle the command call with options? `discord-flags`,
parsing, function call like:
.colour cmyk(49, 50, 0, 22)
.colour hsl(241, 47, 58)
.colour rgb 101 99 199
- How to implement fuzzy matching with rapidfuzz based on the color
names from those URLs?
- How to generate colors in other formats? Is this all possible in
pillow?
- How to generate photo to use in the embed? Do we temporarily create a
file in a cache, send it in embed, then delete?
This will be a fun project, and my first collab!
Co-authored-by: Mohammad Rafivulla
<[email protected]>
|
| | | | | | | | | | | | | |
|
| | |_|_|_|_|_|_|_|_|/ /
|/| | | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / / /
|/| | | | | | | | | | |
Use display_avatar instead of avatar in send_pride_image
|
| |/ / / / / / / / / /
| | | | | | | | | |
| | | | | | | | | | |
Discord.py 2.0 returns None for avatar if a user has default avatar. `display_avatar` returns always `Asset`.
|
| |\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Set `AI.user` to @Sir Lancebot
|
| | |\ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / / /
|/| | | | | | | | | | |
|
| |\ \ \ \ \ \ \ \ \ \ \
| | | | | | | | | | | |
| | | | | | | | | | | | |
Fix bugs in `.issue` command & add aliases
|
| |/ / / / / / / / / / /
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
- Now requires at least one issue/PR
- No longer continues to send issues/PRs when there's too many listed in the invocation
- Added plural aliases (`.issues` and `.prs`)
|
| |\ \ \ \ \ \ \ \ \ \ \
| | | | | | | | | | | |
| | | | | | | | | | | | |
Change pascal's triangle image
|
| | |\ \ \ \ \ \ \ \ \ \ \
| |/ / / / / / / / / / /
|/| | | | | | | | | | | |
|
| | | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | |
| | | | | | | | | | | | |
* Add support to query AoC results in respect of days and stars
From now on the AoC leaderboard command accepts a total of 2 optional arguments a day and star string (eg.: 1-2, for the second star of the first day) and a number of results they would like to see, with a total maximum of 15.
This commit also introduces a few minor fixes in the AoC helper.
* Improve overall code consitency in the AoC event Cog and helpers
* Improve indenting and code consistency in the AoC cog
* Improve code transparency in the AoC helpers
* Patch various inconsistencies in the AoC cog and helpers
* Migrate AoC Day and Star statistics filtering to Dropdowns
From now on when the AoC leadearboard command is used with the DayAndStar argument(bool)
the bot will send a View with two dropdowns and a button to Fetch the data based on the value
of the Dropdowns.
* Improve code and comment consistency in the AoC views and helpers
* Patch logic errors, improve consistency in the AoC cog and view.
* Add support to delete view from the message after timeout in the AoC cog
* Move the day_and_star logic out of the typing context manager in the AoC cog
* Revert season-locker in the AoC cog
* Improve overall code transparency and indenting in the AoC cog and views
* Remove unnecessary returns in the AoC cog and view
|