atelierbram / base2tone Goto Github PK

Not sure on the process here (if any).

I'm sure this will sound stupid, but I'm not clear on how I'm supposed to generate a yml scheme for base16-builder given two hues. I see there are some sass files in the assets folder that seem to be the right direction, but I'm not clear on where to go from there. The cli/io.sh file mentioned in the readme no longer exists, and your commit messages don't really give me any clues on where it went and why. The readme doesn't really have any directions on what to do aside from "edit the demo tiles!"

Can you help me out? Thanks.

Frist of all, thanks for these schemes and project, they are awesome. Well done.

I wanted to ask you some clarifications on the relation between DuoTone themes and Base2Tone schemes. In the README you mention:

The light version of the Morning theme, and dark versions of Evening, Sea, Space, Earth and Forest were converted from DuoTone Themes for Atom by Simurai. Morning and Evening are the default Duotone Light and Duotone Dark schemes, but renamed here in order to have a consistent naming convention.

I've compared the colours in base2tone-earth.yml with those of the (compiled) DuoTone Dark Earth Theme but I've noticed that actual colour values differ.

Or is it me that I've done something wrong in extracting the final colours of the DuoTone themes? i.e. the Base2Tone schemes ported from DuoTone themes should contain all the base colours of the original scheme.

I'm asking because I wanted to create a unified collection of DuoTone schemes, but adopting the Base2Tone convention of storing 32 colours in a YAML file — as opposed to the LESS based approach used in the DuoTone Themes.

If I've understood correctly, the main difference between the two projects is that DuoTone relies entirely on procedural generation of the whole scheme from two base hues via colour formulas (in LESS), whereas Base2Tone schemes are manually edited before release.

What is not clear from the README and Issue #1 is how you actually generate the base scheme from those two hues — i.e. how the actual conversion was achieved:

… and Forest were converted from DuoTone Themes for Atom by Simurai.

I've understood that you manually tweak the colours of the generated Sass scheme until you're pleased with their perceptual appearance, but I'd like to understand better how you manipulate the two base hues to derive the 32 colours scheme in the initial stage — DuoTone themes rely on LESS to generate them.

Also, if I've understood correctly, some of the schemes in this project were ported from @simurai's DuoTone, while others where designed by you. Did you use a same formula/script to generate both types of schemes from two starting hues?

I suggest to update the README regarding the relation between the original DuoTone Themes that have been included in this project with the same name, to avoid confusion.

For example, I originally thought that I could contribute to this project by adding more new DuoTone themes for Atom that I've come across, created by third parties via @simurai's duotone-syntax template, only to discover that they don't fully overlap — in other words, you can't just take the two base hues from a DuoTone based project and auto-magically generate a Base2Tone scheme that will match the exact colours of the upstream project from which they were taken (or so it seems).