Jun 1 2021
@Gopavasanth I am happy to a co-maintainer as I have worked with the tool in past few months and I have good experience with the stack it uses.
Apr 15 2021
@Gopavasanth I tried to deploy it but received this error:
Apr 6 2021
I updated the code. I tested the code on Node 10.19.0 and it worked fine with no issues. (I tested it on windows because I could not install version 10.19 on linux).
Mar 29 2021
- Fixing the overlap issue with the player.
I will work on that.
Nah nah what I what was meaning is, Adding the trim section just below the video player such that trim section width and player width will be equal. But yeah I don't think doing this way will be very visible to users as per your comments above, yeah.
Thanks for the comment. I am glad it was useful :)
Mar 26 2021
Hi @Gopavasanth am happy to look at it. I am currently working on improving trim UI. Once I am done I can look into that. If it has more priority I can drop the trim UI and start looking into it.
Mar 23 2021
Mar 21 2021
thanks for you help to fix the remainder of the issues. It is awesome to see live after all that work :)
Ah I was meaning these are really nice and stunning updates xD. Also, sorry I didn't go through the all files in your code changes before, super excited to try out the first so tested the tool locally, just going through your code comments in the code. those are damn great. thank you!
Mar 20 2021
@Aklapper No problem.
@Aklapper Will it be fine to also change table container to flex layout since it is more modern and the data presented is not tabular.
Ah yeah, Is it being shown currently when you tried locally?
This issue does not seem related to the wiki editor but to how Firefox handles undo stack. You can reproduce the same issue here: https://jsfiddle.net/4n7s8p19/
Mar 19 2021
Mar 17 2021
I can either hide the overflowing text using ellipses
Mar 14 2021
@Gopavasanth I just tried it on local machine and did not see any quality loss.
Mar 13 2021
@Gopavasanth Yes. I realized that an hour ago. I will send a commit shortly to fix this issue.
Mar 3 2021
The .env file is missing socket_io_url in development object. I added: "socket_io_url: 'https://videocuttool.wmflabs.org'" and everything is working now :)
Thanks for the reply. I just tried it but received the same error.
@Gopavasanth I am trying to run the tool on my machine. I replaced backend_url in env.js with "https://videocuttool.wmflabs.org" but I keep getting this error: "http://localhost:3000/socket.io/?EIO=3&transport=polling&t=NVtn-ck 404 (Not Found)".
Feb 23 2021
@Uditdesai2206 Are you still working on this. I can help if you want.
Feb 22 2021
View of the latest change:
Feb 21 2021
Feb 20 2021
@Gopavasanth I think the main issue is styling header with float instead of flex. Since bootstrap is included already I though I make few changes to header section with few bootstrap classes. Also, bootstrap includes hamburger menu icon so no need to import another library.
Feb 18 2021
@Gopavasanth No problem. Happy to help :)
@Gopavasanth I am getting this issue in both Chrome and Firefox. I think I can see because of my screen dimensions. The viewport height is 977px in Chrome and 1006px in Firefox.
@Gopavasanth I was not able to post photo on Gerrit. That's why I am posting it here.
Feb 17 2021
Feb 14 2021
@Gopavasanth Thanks. It nice to see it live :)
@Gopavasanth It was mostly CSS and that a strong area for me. There is no text in textarea and that is why nothing is shwoing.
Thanks. I completed the design and I will add tasks later for the other issues.
Here are the screenshots. If they look ok I will push the commit.
Feb 13 2021
I have few questions:
1- Prettier config was rejected in this commit: https://gerrit.wikimedia.org/r/c/labs/tools/VideoCutTool/+/569593. Is there a possibly to revisit this as it will help with consistent coding style and auto format in vscode.
2- This what I have so far. I chose dark blue. I was wondering if you have any input on the colors.
3- There is an empty space at the bottom. I can fix this by making the main div full height. This will be universal not just part of dark theme. Should I add in this change (with a separate commit) or create a separate task for it?