-
Notifications
You must be signed in to change notification settings - Fork 230
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
Use image listing from registry-image-widgets #1136
Use image listing from registry-image-widgets #1136
Conversation
CC @dperpeet |
Very cool |
20e21d0
to
0dbefb1
Compare
I see this is pulling in gettext now @stefwalter is this going to cause the image stream bits to be translated when the rest of the console is not? or does something have to be enabled for gettext to use a different language other than the default |
It won't. The because project does not initiallize angular-gettext ... nor does the project load any translations. |
OK sounds good, I will pull this down today and try it out
…On Jan 19, 2017 2:49 AM, "Stef Walter" ***@***.***> wrote:
I see this is pulling in gettext now @stefwalter
<https://github.com/stefwalter> is this going to cause the image stream
bits to be translated when the rest of the console is not? or does
something have to be enabled for gettext to use a different language other
than the default.
It won't. The because project does not initiallize angular-gettext ... nor
does the project load any translations.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1136 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABZk7WEMyYkGIvOTvcaF8sAhqScOeHIvks5rTxVpgaJpZM4LnUmW>
.
|
When no tags have been pushed it says "No image streams are present" seems like that should say "No tags are present" When no tags have been pushed the Image count is empty instead of saying '0'. Also noticed it is inconsistent on this screen whether the labels have a ':' after them. The rest of the console does have ':' after any labels. This version of the image widgets has some kind of issue with the image layers widget, when i revert back to master and use the image widgets version that points to this same image shows up just fine in the layers widget: |
The text "To push to an image to this image stream:" isnt right, should be "To push an image to this image stream:" |
What is expanding a tag supposed to do? I thought maybe it was supposed to show the history for that tag, but when I expand it then it isn't showing me anything different, even when I know a tag has had multiple images pushed to it. It just seems to add a line between the sha and the timestamp. |
I'm actually seeing similar issues on the image widget page with long identifiers pushing off the page at mobile |
There is a couple of things I'm not currently satisfied about how this view works, also in the registry.
I'll put together a suggestion in a mockup for how to solve these. |
Thanks for the review @andreasn. May I suggest changes as a follow up pull request, and the first one gets the two projects mostly in sync on the view? Are you okay with that @jwforres @jwforres and @andreasn: The inline expansion stuff wasn't supposed to show up in the Openshift Web Console. That's a bug. @andreasn In the registry the entire sha256 is necessary as the docker command line doesn't support abbreviated SHA identifiers for images. But perhaps that's a place where the Openshift Web Console can diverge and the implementation can take a CSS option to truncate this ... just thinking outloud. |
I'm OK with doing it as a followup if @jwforres is. |
Fixed.
Fixed.
The Registry Console doesn't use colons, and uses different styling for metadata/data. So to make it consistent I've just added these colons via CSS in the Openshift Web Console use of the widgets.
Fixed. This was a regression from when we marked is translatable. Now works.
This doesn't happen for me. Maybe I tagged the bower registry-image-widgets build incorrectly or something. Should work now. The dropdown arrow is not part of the changes we intended to share with the Openshift Web Console. The Registry Console has a listing pattern that allows expansion of data inline, but that doesn't need to be carried over into the Openshift Web Console.
I'll leave this up to @andreasn's follow up pull request.
Fixed.
Fixed.
Added word-break. |
Everything fixed except for the row redesign, which should be done as a follow up, so this feature can get "in" before the feature freeze. |
0dbefb1
to
e3cb5cc
Compare
@stefwalter please rebase @jwforres @spadgett bump for another review since a lot of things have been fixed 👍 |
e3cb5cc
to
da7ab4a
Compare
Rebased. |
However origin-web-console no longer authenticates my version of openshift, and I'm running out of time to sort that all out, so I've been unable to do any smoke test after the rebase.
|
@jwforres, Thanks, rebased and updated this one. |
thanks @petervo I'm seeing two bugs currently
|
</tr> | ||
</tbody> | ||
</table> | ||
<registry-imagestream-body imagestream="imageStream"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sorry I didn't notice it before, but the switch to use registry-imagestream-body changes the behavior of how annotations are presented to the user, everywhere else in the UI we do not show these to the user unless they click a link to reveal them. This is because annotations are typically intended for machine use and not end user facing.
@jwforres, for the docker commands do you want ellipsis or line wrapping with small sizes. Line wraping looks weird but is better for copy/paste. Is that ok? |
<dt>Docker pull spec:</dt> | ||
<dd>{{imageStream.status.dockerImageRepository}}</dd> | ||
</dl> | ||
<annotations annotations="imageStream.metadata.annotations"></annotations> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for reference, this is the annotations directive we use today that handles the show/hide behavior plus how we format annotations when visible
agree wrapping is probably better. i know we do multi-line code style in
other places and managed to make it look alright, one example is in
_pod-template.html L94, i suspect the "command" class was probably adding
some special multi-line stuff
…On Mon, Jun 12, 2017 at 5:57 PM, petervo ***@***.***> wrote:
@jwforres <https://github.com/jwforres>, for the docker commands do you
want ellipsis or line wrapping with small sizes. Line wraping looks weird
but is better for copy/paste. Is that ok?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1136 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABZk7U3uoWlKRAw6WjXoUaUubDCOmo_zks5sDbQygaJpZM4LnUmW>
.
|
This starts work to share code between the Registry Console and Openshift Web Console for the imagestream page. In particular this commit changes the body and push sections of the page.
This shares code with the Registry Console and Openshift Web Console for the ImageStream image listing.
In the Registry, they use styling rather than colons to differentiate metadata from data. However we can simply add colons via CSS to make these parts consistent with the rest of the Openshift Web Console.
e89a66b
to
13ac6a9
Compare
@jwforres, opened openshift/registry-image-widgets#8 and built this with that so you can check this out first before merging the other one. Once that is in i can do a rebuild |
looks like the table still has an issue at iphone 5 res which is 320px width the quick fix is in imagestream.html to wrap this will prevent the layout like the nav from getting messed up when the table overflows the page, it wraps the table in a scrollable content area with a border when at mobile resolutions if you are fine just making that change in this PR then we can merge the PR to image-registry-widgets and cut that release, let me know |
13ac6a9
to
b4bf383
Compare
@jwforres pushed an update that fixes it for me. |
@petervo I have your latest changes but I can still reproduce it with a tag name that is long |
b4bf383
to
7f36fa2
Compare
@jwforres updated again. |
thanks LGTM now, think we can merge the other PR |
I'll LGTM the other PR and you can merge/release it if you are ready |
@jwforres, i don't have access to marge or deploy to npm. I'll see if can I track down someone who does. |
@petervo ah k i can merge and create the tag for bower, i dont think i have the npm access but bower is all we need to the console |
@petervo ok 0.0.9 should be available for bower now |
7f36fa2
to
3ac0f90
Compare
[merge] |
Evaluated for origin web console merge up to 3ac0f90 |
Origin Web Console Merge Results: SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_web_console/1511/) (Base Commit: 9c3ecd1) |
This shares code with the Registry Console and Openshift Web Console for the ImageStream image listing.