Loading...
 

Tracker Item History


Version Date User Field ID Field Difference
5 2023-05-10 16:17 Marc Laporte 169 Assigned by
      171 Related
-DONE - Implement Multi-resolution images: srcset in Tiki trunk, SourceForge: High Resolution Project Icons for Tiki, Compression des images, Multiple resolutions / formats of same video or image, Add image manipulation tools to Tiki Diagram (ex.: crop, etc.), https://aomedia.org/av1-features/get-started/, MacauDEVpotential: Research MPEG-DASH players (after the server-side is looking good), Universal File Handling interface: brainstorming for Tiki22, MacauDEVpotential: Proof of concept of MPEG-DASH, What are our options for H.265 video files uploaded to Tiki? +DONE - Implement Multi-resolution images: srcset in Tiki trunk, SourceForge: High Resolution Project Icons for Tiki, Compression des images, Multiple resolutions / formats of same video or image, Add image manipulation tools to Tiki Diagram (ex.: crop, etc.), https://aomedia.org/av1-features/get-started/, MacauDEVpotential: Research MPEG-DASH players (after the server-side is looking good), Universal File Handling interface: brainstorming for Tiki22, MacauDEVpotential: Proof of concept of MPEG-DASH, What are our options for H.265 video files uploaded to Tiki?, Wrong mimetype detection? WebP images don't get thumbnailed in Tiki tracker attachments list, and are not shown inline in page contents, Image resize issue in articles, mPDF: PDF export of wiki pages: Add compression options , Optimize the website images for marclaporte website, Converse: Reduce size of uploaded pictures, to save bandwidth
4 2022-10-05 00:55 Marc Laporte 169 Assigned by
3 2022-08-21 10:29 Marc Laporte 55 Priority
-3 +5
      238 Resolution Status
      733 Emails
-+
2 2022-07-02 10:09 Marc Laporte 171 Related
- +DONE - Implement Multi-resolution images: srcset in Tiki trunk, SourceForge: High Resolution Project Icons for Tiki, Compression des images, Multiple resolutions / formats of same video or image, Add image manipulation tools to Tiki Diagram (ex.: crop, etc.), https://aomedia.org/av1-features/get-started/, MacauDEVpotential: Research MPEG-DASH players (after the server-side is looking good), Universal File Handling interface: brainstorming for Tiki22, MacauDEVpotential: Proof of concept of MPEG-DASH, What are our options for H.265 video files uploaded to Tiki?
1 2022-07-02 09:46 Jeff Fortin T. 54 Description
 Timeline: Timeline:
-* I think it would be worthwhile for Tiki to prepare for this and maybe announce it in time for the 20th anniversary. Once it is supported across browsers (see https://caniuse.com/jpegxl particularly its """"notes"""" tab) I believe it should be the default public-facing format for Tiki. +* I think it would be worthwhile for Tiki to prepare for this and maybe announce it in time for the 20th anniversary. Once it is supported across browsers (see https://caniuse.com/jpegxl particularly its """"notes"""" and """"resources"""" tabs) I believe it should be the default public-facing format for Tiki.
 * No rush to do it """"urgently this week"""" however, as the EvoluData website is not ready so we don't really have a nice home to receive public attention * No rush to do it """"urgently this week"""" however, as the EvoluData website is not ready so we don't really have a nice home to receive public attention
 * If we miss Tiki's 20th anniversary timeframe/deadline for this, no big deal, it could come in later as its own big piece of announcement, though in that case it would be PR-beneficial to publicly announce it as being on our roadmap. Not just for PR, but also commenting on browsers' bug trackers upstream to """"show traction"""" to help convince them that they should indeed intend to deploy the damned thing into production. We would be joining big guys like Adobe, Facebook, etc. in publicly stating our support, which certainly counts for something. * If we miss Tiki's 20th anniversary timeframe/deadline for this, no big deal, it could come in later as its own big piece of announcement, though in that case it would be PR-beneficial to publicly announce it as being on our roadmap. Not just for PR, but also commenting on browsers' bug trackers upstream to """"show traction"""" to help convince them that they should indeed intend to deploy the damned thing into production. We would be joining big guys like Adobe, Facebook, etc. in publicly stating our support, which certainly counts for something.