Hey, just wanted to ask how to proceed with the pipe patch because I have a few other patches in the queue (multiple input files now also under recentfiles, arbitrary position of CLI options / files...) :)
How do you want them? Everthing together in one diff or two different diffs refering to r107,... or should I wait with the second one and make it refering to future r108? Am Donnerstag, 6. Dezember 2007 14:11 schrieb Michael Riepe: > Hi! > > Ralph Glasstetter wrote: > > Hmmm,... > > > > I don't know what general solution Michael was thinking about but > > at least I don't mind about the little bit more compact layout with > > margin set to 0... if these 20 pixels help seeing everything on a 1280px > > screen... why not...? :) > > Okay, you convinced me. Doesn't look bad either, so I made r106. That was also my thought when I saw it... :) > The > improved pipe command stuff also went in, so we're now at r107. Great... but what should we do with the checks for executable and/or return codes? I tried checking waitpid but this returned nothing special when the executable is not found! So the 'which'-version is working for me, but maybe neither "universal" nor "elegant" ... the QFileInfo-Version is better concerning this but not making use of $PATH, so one has to specify the full path for the pipe commands... And how should we proceed with the interface? Again, for me it's already enough as it is now... configurable for often used / complicated commands and still working for new ones directly specified as output file... I play arround a bit with QT-designer (see attached picture), creating an export dialog for pipe commands, but I'm not convinced if that would be the best solution (beside the fact that I don't know at the moment how to integrate the new ui into the rest of the code... technically & logically). Another option would be just to stick with the current export dialog (with pipes integrated) and implement a proper Settings-Menu, which we need anyow and then (among other stuff) also allows to edit / configure the pipes! BTW,... dvbcut -batch -exp "|dvdauthor -t -o dvd -" recording.ts; dvdauthor -o dvd -T is also a nice option which I just realized that is working now (of course) ... ;-) But we need a -format switch to select the output type... guess that fit's into my above mentioned CLI-patch! ;-) > > I just changed the settings file format a little, therefore everybody > who is using Ralph's patch should adapt his settings file: > > /pipe/0-command > > becomes > > /pipe/0/command > > and so on. OK, doesn't matters for me... just a question... Should I implement something similar for the recentfiles? At the moment I have implemented: recentfiles/0=/tmp/topf/test.rec_01 recentfiles/0-001=/tmp/topf/test.rec_02 recentfiles/0-idx=/tmp/topf/test.rec.idx to be backward compatible with the current scheme! But we could also have something like: recentfiles/0/0=/tmp/topf/test.rec_01 recentfiles/0/1=/tmp/topf/test.rec_02 recentfiles/0/idx=/tmp/topf/test.rec.idx and break with the current format! Or supply some code which is able to read both? What do you think? ciao Ralph
<<attachment: exportpipe.gif>>
------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________ DVBCUT-user mailing list DVBCUT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dvbcut-user
