Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

understanding blueprint colourscheme #69

Closed
kbuzzard opened this issue May 9, 2024 · 3 comments · Fixed by #261
Closed

understanding blueprint colourscheme #69

kbuzzard opened this issue May 9, 2024 · 3 comments · Fixed by #261
Assignees

Comments

@kbuzzard
Copy link
Collaborator

kbuzzard commented May 9, 2024

This code

\begin{lemma}
    \label{ZHat.e_not_in_Int}
    \lean{ZHat.e_not_in_Int}
    \uses{ZHat.e}
    \leanok
    The element $(e_N)_N$ of $\Zhat$ is not in $\Z$.
\end{lemma}
\begin{proof}\notready
    I don't have a proof of this but it doesn't look too bad; maybe I'm wrong
    and it's hard? We will not need it later on.
\end{proof}

produces (on FLT) an oval with a green border (fine) but a blue interior. I want that interior to be orange or red or something.

In fact there seem to be two kinds of \notready proofs -- one is "I didn't write the LaTeX yet, feel free to write it for me" and the other is "this is a multi-year project, please see the discussion link".
Maybe I want \needsLaTeX to be orange, and \noplans to be grey?

Can I also edit the legend to explain my personal colour system?

@kbuzzard kbuzzard changed the title a not-ready proof understanding blueprint colourscheme Nov 25, 2024
@pitmonticone
Copy link
Collaborator

pitmonticone commented Dec 2, 2024

Hi @kbuzzard,

I want that interior to be orange or red or something.

This is the current (default) colour scheme:

  1. Statement Status
    • Blue border: The statement of the result is ready to be formalized; all prerequisites are complete.
    • Orange border: The statement of the result is not ready to be formalised; additional work is required on the blueprint.
    • Green border: The statement of the result has been formalised.
  2. Proof Status
    • Blue background: The proof of the result is ready to be formalised; all prerequisites are complete.
    • Green background: The proof of the result has been formalised.
    • Dark green background: The proof of the result and all its ancestors have been formalized.

We can change this scheme very easily. If I understand you correctly, you want to change the Blue background into an Orange / Red background, right? Please notice that this choice might be a bit unfortunate since Orange is associated with \notready when placed in the statement environment.

In fact there seem to be two kinds of \notready proofs -- one is "I didn't write the LaTeX yet, feel free to write it for me" and the other is "this is a multi-year project, please see the discussion link". Maybe I want \needsLaTeX to be orange, and \noplans to be grey?

First of all, \notready is not supposed to be inserted in the proof environment, but in the statement one: \notready claims that the surrounding statement environment is not ready to be formalized, typically because it requires more blueprint work. For more details you can see the implementation here.

If you want to change this, it's going to be a bit trickier because it requires changes upstream (i.e. in the LeanBlueprint library).

Can I also edit the legend to explain my personal colour system?

I can make it explicit in the web.tex preamble so that you can change the colours as you like, but to add new status commands and change the legend we need to modify the implementation upstream (here and here).

@pitmonticone
Copy link
Collaborator

claim

@github-project-automation github-project-automation bot moved this to Unclaimed in FLT Project Dec 2, 2024
@kbuzzard kbuzzard moved this from Unclaimed to Claimed in FLT Project Dec 2, 2024
@pitmonticone
Copy link
Collaborator

propose #261

@kbuzzard kbuzzard moved this from Claimed to In Progress in FLT Project Dec 2, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Completed in FLT Project Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Completed
Development

Successfully merging a pull request may close this issue.

2 participants