-
Notifications
You must be signed in to change notification settings - Fork 397
Graphical/usability improvements to cmsMake #414
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
Conversation
|
👍 |
1 similar comment
|
👍 |
|
This is very helpful indeed! |
|
👍 |
1 similar comment
|
👍 |
|
I'm having a look at this. The contribution is mostly good and welcome, but the code quality definitely needs some improvement.
I will add more specific feedback in diff comments. |
|
It was basically a quick-and-dirty improvement to use during the stage - I Most decisions were made considering if something had actually been used
|
|
It definitely seemed to be quick-and-dirty. Let me just notice that there is not much point to creating a PR and adding half a dozen +1 to it if you are aware that it still requires work... However, other than the hundreds of details that I pinpointed, it appears to be ok (you may also want to squash the commits together, since there is more or less nothing that separates them). |
|
I agree on that - I had some peer pressure :P
|
That was the buzz of having a really nicer cmsMake that we all locally patched immediately, and the +1 wave was a display of that (just some CMS love 😄) On a side note: I was under the impression that cmsMake was almost a separated piece of CMS and didn't really require its code standards, I see that I was wrong (BTW: it would be awesome to brainstorm a polygon-like cmsMake, or convince polygon authors to release their code 😛) |
|
Well, I admit that the code quality is much lower, but that's not a good reason to include more code with low code quality :) |
|
Definitely +1 for Stefano. |
|
Merged, at last. Backers, please be happy! :-) |

Depends on cms-dev/isolate#4.