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

Change to non-uglified emby-webcomponents #341

Closed
wants to merge 3 commits into from

Conversation

cvium
Copy link
Member

@cvium cvium commented Dec 31, 2018

Until the webui can be properly restructured (separate repo or whatever), any work on the UI is currently hampered by the main repo only having the uglyfied JS.

I've changed emby-webcomponents to the proper 1.5.323 from https://github.com/jellyfin/emby-webcomponents. It should be the one bundled with 3.5.2 (changes in 1.5.324 are not included in the main repo at least).

See discussion here: jellyfin-archive/emby-webcomponents#1

@cvium cvium force-pushed the unminify_webcomponents branch from f8f743d to 3e51b1f Compare December 31, 2018 06:23
Copy link
Contributor

@JustAMan JustAMan left a comment

Choose a reason for hiding this comment

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

I'm doing full reading of this as time permits.

I think my comments should probably be addressed in separate PRs, though, it would be easier to track that way, thus I'm putting my approval here but will continue reading and commenting this.

if (e.ctrlKey) {
return;
}
if (!!e.shiftKey) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Why shift is handled differently? Either all should be bool-forced or none, IMHO.

if (chr.length === 1) {
currentDisplayTextContainer = this.options.itemsContainer;
onAlphanumericKeyPress(e, chr);
}
}
}

function alphanumeric(value) {
var letterNumber = /^[0-9a-zA-Z]+$/;
Copy link
Contributor

Choose a reason for hiding this comment

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

so this basically screws non-English languages... isn't there a js builtin to be used instead of this alphanumeric thing?

}

var alpanumericShortcutTimeout;
Copy link
Contributor

Choose a reason for hiding this comment

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

shoudn't it be initialized upon definition?

}

function selectByShortcutValue(container, value) {

Copy link
Contributor

Choose a reason for hiding this comment

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

this empty line seems unnecessary

var focusElem;
"#" === value && (focusElem = container.querySelector("*[data-prefix]")), focusElem || (focusElem = container.querySelector("*[data-prefix^='" + value + "']")), focusElem && focusManager.focus(focusElem)
if (value === '#') {

Copy link
Contributor

Choose a reason for hiding this comment

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

This, too. And I think there would be more, but I won't nitpick further.


profile.MaxStreamingBitrate = bitrateSetting;
profile.MaxStaticBitrate = 100000000;
profile.MusicStreamingTranscodingBitrate = Math.min(bitrateSetting, 192000);
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks strange to artificially limit audio bitrate to 192kbps

null;

if (options.maxVideoWidth) {
maxVideoWidth = options.maxVideoWidth;
Copy link
Contributor

Choose a reason for hiding this comment

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

shouldn't we check if options.maxVideoWidth is less or equal to maxVideoWidth if latter is not null?..

VideoCodec: 'vpx',
Context: 'Streaming',
Protocol: 'http',
// If audio transcoding is needed, limit channels to number of physical audio channels
Copy link
Contributor

Choose a reason for hiding this comment

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

It is strange that this channel forcing is not applied for all transcodings, only for some

});
}

if (browser.chromecast) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Is it also true for Chromecast Ultra?..

@@ -1,384 +1,331 @@
.card,
Copy link
Contributor

Choose a reason for hiding this comment

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

Disregard this comment, it is for me to bookmark where I paused reading.

@sparky8251
Copy link
Contributor

These "conflicts" were introduced as a result of me changing the default themes to the dark theme for all UI elements. I've had similar merge "conflicts" in my own branches. Unlikely to need any actual work done to merge but if so ping me and I can make sure its merging without breaking my changes.

@cvium cvium changed the title Change to non-uglyfied emby-webcomponents WIP - Change to non-uglified emby-webcomponents Jan 3, 2019
@joshuaboniface joshuaboniface changed the title WIP - Change to non-uglified emby-webcomponents Change to non-uglified emby-webcomponents Jan 4, 2019
@anthonylavado
Copy link
Member

What's left to clean up here?

@anthonylavado
Copy link
Member

Also blocked by #424

@cvium
Copy link
Member Author

cvium commented Jan 10, 2019

Opened issue to track review comments: jellyfin/jellyfin-web#10

Opened new PR on web repo: jellyfin/jellyfin-web#1

@cvium cvium deleted the unminify_webcomponents branch January 25, 2019 19:31
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.

5 participants