On 04/22/2014 06:08 AM, Izack Varsanno wrote:
Hi!
>> Additionally, though I admit that I like python, I could
[...]
>> could give you a helping hand there.
>>
> Before writing the python code, I looked into LUA. If
> there is a way to access presets and manipulate them from
> within LUA API, I missed it and would love to get some
> pointers.
I fear I'm no expert on this, but the lua stuff developed
quite fast recently, so I understood it is the prefered
interface. Maybe for a concrete usecase the necessary
functionality is easily added?
> It is possible to add options to DT via LUA and let those
> options call external program to manipulate the DB.
Hm, I wonder if one really needs this.
[...]
> I might try to build a real script (with GUI) that can
> handle presets (and maybe more objects) in a more full
> way.
I was wondering if not basically two "hooks" would be
sufficient go get everything done that is required. One hook
called upon dt's startup, that just reads in the external
configs, the other that gets called upon shutdown and just
dumps current styles and presets to the files again... This
would just use what's there already, have dt take care of
all things and would in a way be "micro invasive".
> Right now what I have in mind is:
> - Backup/Restore (or/and Export/Import) for presets
> - List presets
> - Copy specific preset between 2 DBs
> - Copy all NEW presets from one DB to another (Copy unless already exist
> in the destination)
> - Force Copy of presets from one DB to another (If preset exist,
> overwrite it)
> - Central place to store user's presets only (and then users can just
> share presets file between them)
I think one could accomodate everything by this more
simplistic approach outlined above.
1. git commit / git push / cp
2. ls
3. git pull; darktable
4. cp
5. cp
6. <central repository>
If one is not in the liking of git and friends one could
replace the git part by just copy/rsync of files.
Just a thought though on a very *ixish workflow.
> Three things I concern about:
> 1. Before putting in the work, not sure what is the demand
> for those "features"
I think there is. At least I have a use case for this
myself, bascially stemming from the fact that I have a new
database all the time.
> 2. Such a program will requite a GUI and therefore will
> need some "installation"
Personally, I'd avoid this. Just adds complexity and code
and I think it is not necessary.
> 3. It is reasonable that one of the next DT releases will
> separate presets from pictures management.
IMHO this would be the best way to go and avoid the
necessity to do anything else.
--
Kind regards, / War is Peace.
| Freedom is Slavery.
Alexander Wagner | Ignorance is Strength.
|
| Theory : G. Orwell, "1984"
/ In practice: USA, since 2001
------------------------------------------------------------------------------
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
