Merge lp:~gary/juju-gui/favicon into lp:juju-gui/experimental
| Status: | Merged |
|---|---|
| Merged at revision: | 253 |
| Proposed branch: | lp:~gary/juju-gui/favicon |
| Merge into: | lp:juju-gui/experimental |
| Diff against target: |
247 lines (+110/-48) 3 files modified
Makefile (+105/-48) app/index.html (+1/-0) lib/server.js (+4/-0) |
| To merge this branch: | bzr merge lp:~gary/juju-gui/favicon |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Brad Crittenden (community) | 2012-11-20 | Approve on 2012-11-20 | |
|
Review via email:
|
|||
Description of the Change
Add favicon, tweak Makefile
Added the juju icon as a favicon, and then got lost in Makefile tweaks. Makefile now does not do unnecessary work, and no longer hides commands with @ so that we can see when we reintroduce unnecessary work. Also switch from a Makefile comment about the node_modules to a message generated by the Makefile.
| Gary Poster (gary) wrote : | # |
Reviewers: mp+135045_
Message:
Please take a look.
Description:
Add favicon, tweak Makefile
Added the juju icon as a favicon, and then got lost in Makefile tweaks.
Makefile now does not do unnecessary work, and no longer hides commands
with @ so that we can see when we reintroduce unnecessary work. Also
switch from a Makefile comment about the node_modules to a message
generated by the Makefile; maybe this should cause the make to fail, so
that we actually force this to be maintained?
https:/
(do not edit description out of merge proposal)
Please review this at https:/
Affected files:
M Makefile
A [revision details]
A app/favicon.ico
- 253. By Gary Poster on 2012-11-20
-
get debug and FF working
| Thiago Veronezi (tveronezi) wrote : | # |
Thanks Gary!
Seems good to me.
+1
https:/
File Makefile (right):
https:/
Makefile:27: test -d "$(BUILD_
"$(BUILD_
Whats wrong with the use of "@"? Don't we like it any more? :O)
https:/
Makefile:42: @# Check to see if we made what we expected to make, and
warn if we did not.
Do we need this @ before the comment?
| Gary Poster (gary) wrote : | # |
Thank you, Thiago. Replies below. I'm happy to make a change if you
prefer, but until you tell me otherwise I'm going to proceed with the
understanding that you are fine with it as is.
Gary
https:/
File Makefile (right):
https:/
Makefile:27: test -d "$(BUILD_
"$(BUILD_
On 2012/11/20 14:33:56, thiago wrote:
> Whats wrong with the use of "@"? Don't we like it any more? :O)
:-) "@" hides context when there are errors, and it hides the fact that
code is being re-run when it should not be in the Makefile. IMO, the
only advantage used to be that it made restarting the server (or running
tests or whatever) quieter, but now with the changes I've made it is
pretty quiet unless it is actually doing work. It didn't seem to get in
my way.
https:/
Makefile:42: @# Check to see if we made what we expected to make, and
warn if we did not.
On 2012/11/20 14:33:56, thiago wrote:
> Do we need this @ before the comment?
If you don't, it is sent to stdout, and in this particular case I didn't
think it brought value to have it in stdout. Maybe that's
idiosyncratic; if someone removes I'd be fine with it.
- 254. By Gary Poster on 2012-11-20
-
respond to bac review
| Gary Poster (gary) wrote : | # |
> Hi Gary,
Hi Brad. Thank you for the review. Replies inline.
>
> Thanks for the clean up to the Makefile and the addition of the favicon. I
> hadn't missed it before but think it'll be nice to have.
>
> I took the liberty of making a card for this task assuming you just forgot.
> Also I couldn't find a Rietveld proposal for this work so I'm reviewing old
> school.
Yes, thank you. Sorry, it was an evening hack that got bigger than I intended.
>
> Unfortunately, running 'make server' locally I do not see the favicon show up
> in Chromium (and FF is hopelessly broken ATM). Looking at the downloaded
> resources I see it was served up but it does not show in the address bar. Are
> you actually seeing it?
Yes. As I mentioned on IRC, it was not working in debug mode, and I fixed that. Firefox seemed happier when I was explicit about the ico file also, though that should not be necessary. I tested it on another computer as well and it seemed ok to me.
>
> I'm a bit confused by the NODE_TARGETS / EXPECTED_
> FOUND_NODE_TARGETS dance. I assume we can't just compute FOUND_NODE_TARGETS
> and use it directly. If that is really the case could you document exactly
> what is going on lest someone like the Future Me try to undo your work?
Good call. I added a comment and got your approval on IRC.
>
> The 'test -d' before 'mkdir -p' is nice but unnecessary ask 'mkdir -p' will
> happily do a no-op and exit with 0 if the directory already exists. I see it
> used in a few places.
Nice improvement, yes. Changed.
>
> Otherwise it looks good and is easier to follow. Thanks.
Thank you!
Gary
| Gary Poster (gary) wrote : | # |
*** Submitted:
Add favicon, tweak Makefile
Added the juju icon as a favicon, and then got lost in Makefile tweaks.
Makefile now does not do unnecessary work, and no longer hides commands
with @ so that we can see when we reintroduce unnecessary work. Also
switch from a Makefile comment about the node_modules to a message
generated by the Makefile.
R=thiago
CC=
https:/


Hi Gary,
Thanks for the clean up to the Makefile and the addition of the favicon. I hadn't missed it before but think it'll be nice to have.
I took the liberty of making a card for this task assuming you just forgot. Also I couldn't find a Rietveld proposal for this work so I'm reviewing old school.
Unfortunately, running 'make server' locally I do not see the favicon show up in Chromium (and FF is hopelessly broken ATM). Looking at the downloaded resources I see it was served up but it does not show in the address bar. Are you actually seeing it?
I'm a bit confused by the NODE_TARGETS / EXPECTED_ NODE_TARGETS / FOUND_NODE_TARGETS dance. I assume we can't just compute FOUND_NODE_TARGETS and use it directly. If that is really the case could you document exactly what is going on lest someone like the Future Me try to undo your work?
The 'test -d' before 'mkdir -p' is nice but unnecessary ask 'mkdir -p' will happily do a no-op and exit with 0 if the directory already exists. I see it used in a few places.
Otherwise it looks good and is easier to follow. Thanks.