Re: [FFmpeg-devel] [PATCH] web: Update Bower dependencies
Did you check that the latest versions of the dependencies still make the website look the same? I remember having retro-compatibility issues with Bootstrap in the past, but that was a long time ago, so it's probably OK. -- db0 - Deby Barbara Lepage http://db0.fr/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 3/4] web/style.less: colors: Reindent and use more obvious functions
On Mon, Nov 10, 2014 at 10:10 PM, Timothy Gu timothyg...@gmail.com wrote: Ping, and CC'ing db0 who is the maintainer of the website. I can't apply it myself. It looks good to me. -- db0 - Deby Barbara Lepage http://db0.fr/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] Facebook page
On Sat, Oct 4, 2014 at 10:28 PM, Clément Bœsch u...@pkh.me wrote: We hard already a hard time trying to keep up things up to date with the twitter and Google+ in addition to our mailing-list, IRC channels and web news. Sorry if I sound very negative about it, I'm not opposing to it, I just think we should instead try to improve the mediums we currently support. FFmpeg could use IFTTT (https://ifttt.com/myrecipes/personal) or Zapier (https://zapier.com/) to automatically update the Facebook page from the RSS feed. It could also work for the Twitter account, instead of posting manually. I've been using both for a while now for the same purpose and it works very well. I'm not exactly sure how adding yet another communication medium will help, especially on such a portal where the majority of people don't care about it, and those who do are already tracking our mailing-list, IRC channels, or web/RSS. Facebook is undoubtedly the most used social network. It's becoming a pretty standard way of communicating with users, even for developers-related products and in the open-source community. -- db0 - Deby Barbara Lepage http://db0.fr/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] new webpage design patches
On Mon, Jul 21, 2014 at 2:25 PM, compn te...@mi.rr.com wrote: On Sun, 20 Jul 2014 09:20:30 -0800 Lou Logan l...@lrcd.com wrote: On Sat, Jul 19, 2014, at 11:49 PM, Clément Bœsch wrote: libx264 is not always available and not that much common (it requires special permissions), and the avi to mp4 is IMO not that much common: it's not going to improve quality, while mp4 to avi has the benefit of creating videos compatible with old devices, which sounds like a more common use case. I'll disagree with these points from what I've seen from what users tend to be doing and what they are using. But it's a nit. More importantly, the link to John's builds is wrong. Under Linux Static Builds, the link to 64-bit with kernel 2.6.32 and above should be http://johnvansickle.com/ffmpeg/ i can fix this, unless someone beats me to it. Also, the old # anchors have changed. For example, I provided many links to download.html#LinuxBuilds for users on various help resources, but that has changed to download.html#build-linux. We can either revert to the old names, provide a dummy link using the old names, forget about the old names and do nothing, or maybe do some redirection magic. probably revert the name/urls back. i dont think the names are set in stone ? i'd like to see an example so i dont break things further though. I'll fix those two ASAP. I hope the anchors from the download page are the only ones that changed. I don't even remember renaming them. -- db0 - Deby Barbara Lepage http://db0.fr/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
Re: [FFmpeg-devel] [PATCH 3/3] [WEB] Add generate-doc.sh to generate makeinfo-based ffmpeg docs
On Sun, Jul 20, 2014 at 8:09 PM, Clément Bœsch u...@pkh.me wrote: On Sun, Jul 20, 2014 at 10:03:49AM -0700, Timothy Gu wrote: [...] +!-- Please keep this in sync with template_head_prod and template_head2 -- [...] +!-- Please keep this in sync with template_head2 -- [...] +!-- Please keep this in sync with template_doc_head2 -- [...] +!-- Please keep this in sync with template_head3 -- [...] +!-- Please keep this in sync with template_doc_head[1-3] -- [...] +!-- Please keep this in sync with template_doc_head4 -- [...] This is extremely clumsy, please find another way. I agree. The pieces of code from the header and footer were not split the same way as in the texi2html generator, but I found a way: https://github.com/db0company/FFmpeg/commit/9ce64ba111221a37bdd78204b67330a6120f6c50#diff-2 I haven't looked at the makeinfo doc but there's probably a way to do it like this as well and therefore avoid duplication. -- db0 - Deby Barbara Lepage http://db0.fr/ ___ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
