Skip to content

Conversation

@unsoluble
Copy link
Contributor

Should have links to both bgclock.html and clock-color.html in the main link panel. Might be a tidier way of putting them both on one line, but didn't want to mess with the CSS.

@unsoluble
Copy link
Contributor Author

When I submitted this I was thinking only bgclock and clock-color need to be in here, but then when I was adding them to the Readme figured all three (including clock) ought to be in there, so maybe all three should be in here too. Just a little wary of it getting cluttered.

Tweak the styling perhaps so we can put all three view options on one line?

Copy link
Member

@sulkaharo sulkaharo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for slow review! Can you also include the change to the language.js that includes the corresponding localization keys?

@unsoluble
Copy link
Contributor Author

Updated the nav to show all three clocks in one row. Looks like this:
screen shot 2018-02-11 at 6 33 09 pm

Conflict with the dev progress on language.js there should be easily resolved; stems from the change to the plural "Clock Views".

@unsoluble
Copy link
Contributor Author

Any chance someone could offer a hand in finalizing this one? I don't think I'm able to resolve the language.js conflicts, or at least I'm not sure how to do that on my end. Should be an easy fix, and then this one could be merged.

@PieterGit
Copy link
Contributor

@unsoluble I resolved the merge errors for you. Is this ready to merge? LGTM but I didn't test it yet.

@unsoluble
Copy link
Contributor Author

Thanks! I think it should be good to go, yep.

@PieterGit
Copy link
Contributor

PieterGit commented Jun 25, 2018

Ok, I'll test it myself later this week and have a look at why this PR adds language lines. Then I merge it, unless @sulkaharo or @MilosKozak beat me.

@PieterGit PieterGit added this to the 0.10.3 milestone Jun 25, 2018
@PieterGit
Copy link
Contributor

PieterGit commented Jul 8, 2018

@unsoluble according to @sulkaharo there are some issues with this PR with mobile devices, see
See https://gitter.im/nightscout/public?at=5b42401dbd92d807829dfce8
This PR might be postponed to 0.11 release, because we want to release 0.10.3 soon.

I haven't tested this PR on mobile devices myself.

@unsoluble
Copy link
Contributor Author

Could try to fix if I had more information — not clear what the concern is.

@unsoluble
Copy link
Contributor Author

This is what it looks like on an iPhone SE, which has one of the smallest screens on the market right now:
img_0010

views/index.html Outdated
<li><a id="admintoolslink" href="admin" target="admintools" class="translate">Admin Tools</a></li>
<li><a id="clocklink" href="bgclock.html" target="admintools" class="translate">Clock View</a></li>
<li class="multilink">
<a>Clock Views:</a>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Clock Views part is not translatable

@PieterGit
Copy link
Contributor

Small issue: Clock Views: is not translatable. It shows fine with Samsung S7 and with Windows 10 and Chrome. I had bad luck with testing this, see other problems at #3709

@unsoluble
Copy link
Contributor Author

I don’t know what you mean by translatable. Can you elaborate?

@PieterGit
Copy link
Contributor

@unsoluble I added translation strings for it, but it does not translate. See
https://github.com/nightscout/cgm-remote-monitor/pull/3709/files#diff-29e70f5c52b22198247a7936ea3f1d7dR11476

image

I expected: Klokweergave instead of Clock Views

@unsoluble
Copy link
Contributor Author

unsoluble commented Jul 19, 2018

Oh I see it: should be a class=translate in that A tag. Can you add that? Would myself but will be on my phone only for a while.

@PieterGit
Copy link
Contributor

@unsoluble : please use https://github.com/PieterGit/cgm-remote-monitor/blob/201807_clock/lib/language.js to resolve the merge conflict. I think this PR is ok and can be merged after the merge conflict has been fixed.

@sulkaharo can you confirm there are no problems with this PR anymore?

@unsoluble
Copy link
Contributor Author

This conflict-resolving stuff is new to me; I'm not sure if I'm approaching it the right way. Tried to just commit with the updated contents of language.js that you linked, but that doesn't seem to have done the trick. Is there something else I need to do on my end?

PieterGit added a commit that referenced this pull request Jul 19, 2018
More clock options #3207 and some dutch language updates
@PieterGit
Copy link
Contributor

Merged with #3712
Closing PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants