User Details
- User Since
- Mar 7 2015, 11:28 PM (381 w, 4 d)
- Availability
- Available
- IRC Nick
- kiwi_0x010C
- LDAP User
- 0x010C
- MediaWiki User
- 0x010C [ Global Accounts ]
Jun 2 2020
To implement this new UI, I did a hard fork of the previous foreground-based skin to achieve a brand new skin, BlueLL. See all commits that lead to the current result.
Done in those 40 commits.
With the new UX implemented (T240552), you can now listen to records and delete them directly from the studio step, where you can also re-record them. Thereby I think we can consider this task as resolved.
Done in commit c9c510a7.
Done in commit 0bc7f91f.
Done in commit db030094.
Done in commit df2b0f8a. A little play button is positioned next to each stashed records in the studio; clicking on it stops the recorder and plays the recorded sound. Two shortcuts are also available: P and Enter.
Done in commit fa84d55c.
Switch done on Friday 29 May 2020 between 15h and 15h44 (CEST). Now domain lingualibre.fr redirect to lingualibre.org.
Jun 1 2020
A first attempt was made during T240552, but there was an issue (text overflowing outside viewbox) on browsers that didn't had the Linux Libertine font.
May 29 2020
May 21 2020
May 13 2020
May 11 2020
Oh, ok that's fine then :). Thanks @DannyS712
I'm reopening this task as it seems not completely fixed. Performing a check this morning on [[User:Karl Marx1844]] (frwiki), I still get an error (only through the API as previously):
May 9 2020
May 8 2020
May 7 2020
I just came with a not too complicated solution for the second option. As samples are coded on 16bits signed integer, and if we look at all the strings that need to be removed, we can actually just twist a bit (--> add 1) all occurrences of the 4 samples listed bellow to be negative in all cases:
- 0x003F = "\x00?"
- 0x3F00 = "?\x00"
- 0x7068 = "ph"
- 0x6870 = "hp"
For the record, an example of wav file that is concidered as application/x-php:
(that's just a generated test file, nothing really interesting)
After digging a bit in MW core's code, it seems that using an external mime-detection command through $wgMimeDetectorCommand will be useless, because this is used only if the internal mime detection did not find anything.
Looking at the log file:
Also got this error sometimes. When the error occured one time on a word, it keeps occuring during the whole session on this word. For the record, this is the error returned by the API:
{ "error": { "code": "verification-error", "info": "Files of the MIME type \"application/x-php\" are not allowed to be uploaded.", "details": [ "filetype-badmime", "application/x-php" ], "*": "See https://v2.lingualibre.fr/api.php for API usage. Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes." } }
For a reason I don't get yet, MW thinks the uploaded file is an "application/x-php" instead of the correct "audio/wav" type.
May 6 2020
Apr 28 2020
Apr 16 2020
If it can help, it just happend again with another user "Navsenar" (always on frwiki).
Apr 10 2020
Oh, got the difference. I have enabled the "new video player" in my preferences (in the "beta features" tab), when I disable it everything got blank again. The issue is definitely related to the move operation, but I can't help futher, I don't know much the TimedMediaHandler extension...
Everything is alright for me, both on the category and on the file itself (Firefox 74 on manjaro).
All the new RecordWizard-related mock-ups (see T212581) have been implemented using mustache as described. The result can for now on be seen on the development website. Note that all the interactions are not yet plugged with this new interface (T248983 is still a WIP), thus the two last steps may not work as intended yet.
A first version of this message was implemented following the mock-up shown in T240552. This can be tested on the development website (anyone can create a testing account there for this purpose).
The new skin made for T240552 uses now a vector logo. It is currently deployed on the development website.
I'm currently implementing a new UI (see T240552), where the "delete" feature is replaced by checkboxes in the "publish" step of the RecordWizard (more UX-friendly, easier for the end-user and less event-managment in the code). Thus, this feature request will soon be deprecated.