search

nublic / Nublic

Your home in Internet
6 stars 1 forks source link

File processors #3

Closed serras closed 12 years ago

serras commented 12 years ago

I'm currently implementing the set of processors for files, that is, things that get run when a file is created or modified (like thumbnailing). I would like to use this issue to discuss which processors should be implemented, and in which app.

filewatcher:

Browser (this should include previewing of things):

Images:

Music:

serras commented 12 years ago

I'm looking for ways to embed documents such as .doc and .pdf. Now, the best option I found is doing document -> PDF -> set of SVG files but with this is not entirely satisfactory because the user cannot select and copy text from the files, and some browsers don't support SVG (but Chrome, Firefox and newer versions of IE should).

The best option is really http://flexpaper.devaldi.com/, but there is a problem: it's GPL (viric free software license, if you use something in GPL, the entire app must be GPL), so we cannot use it in Nublic. They even have a HTML5 version of the viewer :O

Another thing would be using the Google Docs viewer, but I cannot find the Terms of Service. In any case, documents using them must be publicly available, so this is no option for Nublic.

serras commented 12 years ago

Another option from the Mozilla Foundation: natively rendering PDF to HTML5 -> https://github.com/andreasgal/pdf.js

serras commented 12 years ago

Really, just converting to PDF should be enough for 95% of the people, because everybody has a PDF viewer installed (aka Adobe Reader), and Android, iPhone and Chrome have native support for PDF.

davisein commented 12 years ago

For this problem, I think we should stick to the PDF viewer installed considering that the pdf will be showed in the screen. I think is good enough for the moment. But we should be able to create a thumbnail for .doc and .pdf documents so we still need to look for that reason.

In general the list looks quite good. It has some problems though. In the future we will need to think a general way to organize thumbnails to be able to delegate this function from the browser to applications.

The work for being able to visualize stuff directly on the browser should be in images and music aplications I think. But probable by now we should implement it in the browser when needed while we don't have a proper Image, Music and Video application.

It all good. Let's discuss it a bit more and close this problem.

serras commented 12 years ago

So, for the moment I won't create SVG images from PDF, only convert all kind of documents to PDF, and then generate a thumbnail of the first page of the resulting PDF, which should be the front page for most of the documents. There is still a question: which thumbnail sizes should I generate? This is not important as first, because I don't think I will include the numbers as magic numbers xD But I think it's good to discuss it a bit.

davisein commented 12 years ago

Um, we should check in internet

serras commented 12 years ago

In this moment, the following is implemented:

There is still that problem of things that should be in music or video applications to go into the browser app. Indeed, the recognition of EXIF metadata for images and ID3 metadata for music may be well in the Browser, because for the latter it can be used to download album art. Suggestions?

davisein commented 12 years ago

It is a way to check if the video has gone wrong with MPlayer? If we can check it we can try memcoder if it does not work check with the other system.

We can try with several videos with different formats to check how good or bad is each system.

serras commented 12 years ago

No, I cannot. The problem seems to be that ffmpeg is better handling details such as different framerates, whereas mencoder just uses a fixed number. So, if your video is encoded differently from what mencoder expects, you get a slow- or fast-motion video.

davisein commented 12 years ago

Then ffmpeg it's the way. For me it is better to have a consistent working functionality than a better but sometimes not working function.

Good work though!

2011/10/10 Alejandro Serrano < reply@reply.github.com>

No, I cannot. The problem seems to be that ffmpeg is better handling details such as different framerates, whereas mencoder just uses a fixed number. So, if your video is encoded differently from what mencoder expects, you get a slow- or fast-motion video.

Reply to this email directly or view it on GitHub: https://github.com/nublic/Nublic/issues/3#issuecomment-2348171

David Navarro Estruch

serras commented 12 years ago

I added recently some new processors:

I close the issue. If you have any more ideas for processors, just reopen the ticket.