| Summary: | Store camera download settings into digiKam camera config file | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Eike Welk <eike.welk> |
| Component: | Import-Settings | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | caulier.gilles, marcel.wiesweg, marcus, tpr |
| Priority: | NOR | ||
| Version: | 0.9.3 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Eike Welk
2008-08-03 20:50:43 UTC
What about this one? Gilles, Marcel, Arnd, what do you think? Andi To get camera config from libgphoto2, we need to wait a better and universal) way from libgphoto2 to make config layout and widget list. The current one is oriented on GTK stuff (using GTK loop if i remember) and it's the hell to setup signal/slot connections. I have already tried to make a camera config dialog but it's cannot be completed as well. Loook in cameragui/gpconfigdlg.cpp I don't know if libgphoto2 will use a new method to get camera config. Something based on XML will be nice. Marcus, any news about it ? Gilles Caulier There is absolutely nothing GTK related in libgphoto2 since forever. ;) The configuration uses an abstract widget tree, which can be rendered any way you want. Check out the kdegraphics4/kamera/kcontrol/ configuration dialog in kameraconfigdialog.cpp. Perhaps we could even launch that module there in some way. However I do not really see the usefulness... ALmost modern cameras do not need to be configured for the usage pattern of digikam. "Autocreation of Albums" is not a gphoto settings, but a digikam setting I think. Maybe Gilles was thinking about glib event loop? That is/was problem for Qt3 but Qt4 uses it, so for >= 0.10 shouldn't create problems. I think the original report is about the download settings in the camera dialog, that is Jpeg rotate, rename by date, auto create albums etc. This is purely digikam code. Eike has two wishes as I understand that: 1) He want to have these settings in the main configuration dialog 2) He wants to store these settings per-camera and not globally For 1) I would vote for wontfix, because there is a certain movement to go away from enormous configuration dialog and make more options directly accessible where it is needed. 2) is a wish but currently I dont believe it is worth the effort. 1/ Agree : won't fix. 2/ i'm not sure. It's possible to store configuration by Camera using digiKam xml file. Any others viewpoints here ? Gilles Caulier Andi, About point 1/, i agree with Marcel : Won't fix. What do you think about point 2/ ? Gilles Caulier 1. Yes, I would also vote "wontfix", because our settings dialog is already MUCH too crowded. 2. If it is easy to implement with XML files, I would say yes. I also have two cameras, but I don't see the point in having multiple configuration here, at least for my workflow. But it could work somehow like this: a) camera not detected: load default.xml when CameraUI is opened, on close ask if you want to save the settings in a new config file b) camera detected: open and save in the appropriate xml file But there is a problem: You can also import from folders. We don't want to use custom settings for this, too. So the question is: is it easy or time-consuming to implement? We have already so much to do, maybe this is just not worth it? And: do most users really need this? Andi Is this still valid nowadays? |