openshot.developers team mailing list archive

[Jonathan Tan <jonathantan86@xxxxxxxxx>]

For the XML, I notice that OpenShot currently uses xml.dom.minidom for
all its XML parsing needs. Is it OK if I use xml.etree.ElementTree? It's
a new module that comes with Python 2.5 (and above). The version of
Python included with Ubuntu 8.04 (which is your earliest supported
version of Ubuntu?) is Python 2.5, so I don't think this will incur any
additional dependencies.

The advantage of ElementTree is that it has a (partial) implementation of XPath, which allows me to do
tree.find("body/p") # (from the sample)
rather than
tree.getElementsByTagName("body")[0].getElementsByTagName("p")[0] # (not sure of exact API, typing this from what I remember of DOM)

I'll get started anyway. Yup the current metrics are hardcoded, but it
seems like they are all in clip.py (and the relevant files that draw the
ruler and the whole timeline) so hopefully this won't be an
insurmountable task.


** Changed in: openshot
     Assignee: (unassigned) => Jonathan Tan (yondalf)

** Changed in: openshot
       Status: New => In Progress

-- 
Timeline too fat
https://bugs.launchpad.net/bugs/499860
You received this bug notification because you are a member of OpenShot
Developers, which is subscribed to OpenShot Video Editor.

Status in OpenShot Video Editor: In Progress

Bug description:
Hi!

I must say that Timeline in Openshot is really nice. But I think that is too fat. To much space between timelines, too fat  time ruler.

I would be very helpful, if there would be more thumbnails for each clip - user could see which part of clip is where