openshot.developers team mailing list archive
-
openshot.developers team
-
Mailing list archive
-
Message #00241
Re: Call for export settings
I think that would make sense.
2009/9/2 Jonathan Thomas <jonathan.oomph@xxxxxxxxx>
> Agreed. XML sounds like the way to go. Should we have a separate XML file
> for each "simple" item? That might make it easier to drop in new settings.
>
> Thanks,
> -Jonathan
>
>
> On Tue, Sep 1, 2009 at 4:46 PM, Andrew Finch <
> we.rocked.in79@xxxxxxxxxxxxxx> wrote:
>
>> XML sounds like a good way to go. We should also maybe think about adding
>> some kind of import feature somewhere down the line. When Device x and/or
>> Web site Y hit it big next year, it would make more sense to be able to
>> import the profile for that rather than us having to release a patch each
>> time. But that can wait for the time being...
>>
>> 2009/9/1 Helen McCall <sappho@xxxxxxxxxxxxxxxx>
>>
>> Hello Jonathan,
>>>
>>> This sounds a good plan.
>>>
>>> May I suggest that the settings/presets should be stored in an XML file.
>>> This is a current convention, and if all data stored, eg project files
>>> as well, were in XML files, it should standardise the parsing of stored
>>> data and make the programming more transparent.
>>>
>>> Best wishes, Helen
>>>
>>>
>>>
>>> On Tue, 2009-09-01 at 10:37 -0500, Jonathan Thomas wrote:
>>> > Andy, here are my thoughts on the "Simple" tab. Sorry this is so
>>> > long. =)
>>> >
>>> > Yeah, the simple tab would hopefully be a "simple" list of export
>>> > options. Here is the key... the simple export options should have
>>> > only 1 function, and that is to set the advanced widgets (which are on
>>> > the advanced tab) to their correct values. This way, the progress bar
>>> > and export button continue to work, without having to touch that
>>> > code.
>>> >
>>> > In fact, this would allow a user to select "YouTube" for example, and
>>> > then switch to the advanced tab to tweak any settings (if they want
>>> > to). Otherwise, the user could just hit the "Export" button, and it
>>> > would just work.
>>> >
>>> > Here are the fields that would be "Shared" (i.e. outside of the tab
>>> > interface):
>>> > 1) General Options (my mock-up should have the tabs appear below the
>>> > General Options)
>>> > 2) Progress Bar / Export Video button
>>> >
>>> > Here are the dropdown fields that would be on the "Simple" tab. I'm
>>> > imagining that these 3 fields would be like cascading dropdowns... As
>>> > you answer the 1st dropdown, the next dropdown populates, etc...
>>> > 1) Type (i.e. DVD, Blu-ray, YouTube, Vimeo, Xbox 360, Web, etc...)
>>> > 2) Size (i.e. Simple dropdown of valid profiles - example: HDV 720
>>> > 25p, HDV 720 30p)
>>> > 3) Quality (i.e. Maybe just a few options... like Low, Medium, High)
>>> >
>>> > The trickiest part of this feature (as I'm sure you've figured out),
>>> > is where and how do we store this "simple" info. Ideally it would not
>>> > be embedded into our code, you know. It should probably be easy to
>>> > update, so we can easily refine the list. Should it be in an XML
>>> > file? a Text file? a Python file with lots of lists / dictionaries?
>>> > Something to think about...
>>> >
>>> > Please let me know how this sounds. If anyone disagrees with this,
>>> > let's discuss and come to an agreement before we begin.
>>> >
>>> > Also, if for some reason you don't have time to work on this feature,
>>> > please let me know so I can jump on it after I finish the "effects"
>>> > module.
>>> >
>>> > Thanks!
>>> > -Jonathan
>>> >
>>> > On Tue, Sep 1, 2009 at 3:26 AM, Andrew Finch
>>> > <we.rocked.in79@xxxxxxxxxxxxxx> wrote:
>>> > Yeah, I can take a look at that as well - the simple tab is
>>> > for the 'preset' export options, right?
>>> >
>>> >
>>> >
>>> > 2009/8/31 Jonathan Thomas <jonathan.oomph@xxxxxxxxx>
>>> > Welcome back Andy! Darn, Helen got to you first. I
>>> > could use some help with the Export Dialog. I've
>>> > attached a screen with a laughably rough mock-up. If
>>> > you don't have time for this, let me know, and I will
>>> > start on it.
>>> >
>>> > I'm working on effects right now.
>>> >
>>> > Thanks,
>>> > -Jonathan
>>> >
>>> >
>>> >
>>> > On Mon, Aug 31, 2009 at 2:54 PM, Helen McCall
>>> > <sappho@xxxxxxxxxxxxxxxx> wrote:
>>> > Hello Andy,
>>> >
>>> > Welcome back. :-)
>>> >
>>> > I've got a simple programming job which needs
>>> > doing. It would take me a
>>> > month of Sundays to learn enough Glade to do
>>> > it.
>>> >
>>> > I need an entry in the Help menu dropdown, to
>>> > call yelp with the uri of
>>> > the openshot.xml file so that the help manual
>>> > can be launched from
>>> > OpenShot.
>>> >
>>> > Every time I try using Glade I manage to break
>>> > everything!
>>> >
>>> > Andy; would you be willing to take on this
>>> > task?
>>> >
>>> > Best wishes, Helen
>>> >
>>> > PS: I am adding some more Export Settings to
>>> > the table I have put in the
>>> > help manual. This has been a major labour of
>>> > love. I have had to
>>> > research all the formats and codecs from
>>> > sources like Final Cut Studio
>>> > documentation, the websites of vimeo and
>>> > youtube etc.
>>> >
>>> >
>>> >
>>> >
>>> > On Mon, 2009-08-31 at 20:32 +0100, Andrew
>>> > Finch wrote:
>>> > > Hi Everyone,
>>> > >
>>> > > Looks like lot's have been going on while
>>> > I've been away on
>>> > > holiday...at least I didn't miss the release
>>> > of 1.0!
>>> > >
>>> > > Jonathan, let me know if there is anything
>>> > you want me look at - my
>>> > > batteries are fully recharged at the moment!
>>> > >
>>> > > Cheers,
>>> > > Andy.
>>> > >
>>> > > 2009/8/31 Jonathan Thomas
>>> > <jonathan.oomph@xxxxxxxxx>
>>> > > Helen,
>>> > > I have added a new blog post tonight
>>> > trying to convince people
>>> > > to jump in and offer some common
>>> > export options for OpenShot.
>>> > > Hopefully this will work out, and
>>> > people will help out. Worst
>>> > > case, we'll get lots of crap added
>>> > to our Wikipedia page. =)
>>> > > Let's keep our fingers crossed.
>>> > >
>>> > > Thanks,
>>> > > -Jonathan
>>> > >
>>> > >
>>> > _______________________________________________
>>> > > Mailing list:
>>> > https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
>>> > > Post to :
>>> > openshot.developers@xxxxxxxxxxxxxxxxxxx
>>> > > Unsubscribe :
>>> > https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
>>> > > More help :
>>> > https://help.launchpad.net/ListHelp
>>> > >
>>> > >
>>> > >
>>> > _______________________________________________
>>> > > Mailing list:
>>> > https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
>>> > > Post to :
>>> > openshot.developers@xxxxxxxxxxxxxxxxxxx
>>> > > Unsubscribe :
>>> > https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
>>> > > More help :
>>> > https://help.launchpad.net/ListHelp
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > Mailing list: https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
>>> > Post to : openshot.developers@xxxxxxxxxxxxxxxxxxx
>>> > Unsubscribe : https://launchpad.net/~openshot.developers<https://launchpad.net/%7Eopenshot.developers>
>>> > More help : https://help.launchpad.net/ListHelp
>>>
>>>
>>>
>>
>
References
