Closed cromefire closed 4 years ago
I've started to like yarn more recently, so that choice is excellent. I can't say I have an opinion on TypeScript yet, but since no one else has stepped up yet to modernize this client for Jellyfin I'd say the rest of your choices are fine as well. Double quotes are best in my opinion.
If you keep your commit messages detailed we can merge the entire history to master, but fixed another error
is a bit vague as a description.
If you keep your commit messages detailed we can merge the entire history to master, but fixed another error is a bit vague as a description.
Yes I'm generally trying that
I've started to like yarn more recently, so that choice is excellent. I can't say I have an opinion on TypeScript yet, but since no one else has stepped up yet to modernize this client for Jellyfin I'd say the rest of your choices are fine as well. Double quotes are best in my opinion.
Well then I'll try to do what I can
One last question, is there a minimum node version or can I just target node 12?
Does it just get bundled with electron, or is it an external dependency? As long as most modern systems would work fine with node 12 I'd say that's fine.
It's bundled, but the developer has to have it
Node 12 sounds fine then!
Ramped up the communication (at least for main
-> renderer
, other way coming soon) to use comlink
(A lot more user friendly than postMessage()
and removes the need for all the sendJavascript("Random, I bet exploitable, code")
)
And mpv is currently broken
Is there a svg
of jellyfin?
Bocked on jellyfin/jellyfin-web#392
Hey @cromefire I just wanted to touch base on this one. I'm definitely grateful for the work, but it might be a better idea to split this up a bit to reduce the burden of a major rewrite all at once. Any thoughts on this?
I think once I'm able to have an api to work with it's like a few days to get this done
The infrastructure is mostly in place I'm only waiting to interface with the web ui (Most things aside from mpv do already work)
@cromefire https://github.com/jellyfin/jellyfin-web/issues/392 is there, can you please continue this PR?
I'm on it, I'm waiting on the API
I'm on it, I'm waiting on the API
What API are you waiting for specifically @cromefire ?
See jellyfin/jellyfin-web#392
Oh, I saw that but, as it was closed, I didn't look too close into that. Correct link would be this: https://features.jellyfin.org/posts/148/extend-nativeshell-for-jellyfin-theater
Goals of this PR:
NativeShell
comlink
es2018
typescript
electron-builder
prettier
yarn
This was the original bug to be fixed (fullscreen):![image](https://user-images.githubusercontent.com/26320625/61336730-ba5d0400-a832-11e9-9543-6defd41635f7.png)
It would be nice if some one confirms that
typescript
,prettier
andyarn
are okay (also"
or'
, I would prefer"
)BLOCKED BY: https://features.jellyfin.org/posts/148/extend-nativeshell-for-jellyfin-theater