Am Samstag, 30. November 2013, 17:23:39 schrieb Teodor Petrov: > Hi Pascal,
Not Pascal, but Hi anyway. > On 11/30/2013 11:38 AM, Pascal Obry wrote: > > To me all three points above are because you are trying to use dt in a > > way it was not design to be. dt is a all-in-one tool that also manage > > your collections so you never want to do anything with the images > > behind the scene. The moving can be done in dt. Then having the xmp > > next to the image or in a sub-directory is not an issue since you just > > don't see them. And doing the move in dt also move the .xmp, again no > > issue in this case. > > I know this is the case and that's why I'm asking if you plan to change > this. > I don't like softwares that want to store their data in their own database. > I love the simple file-system stuff. It is more reliable or at least > this is the > perception I have. And that's exactly the nice thing about darktable: it stores the image settings in sidecar files in the file system. The database is just a cache to speed things up (a lot). As long as you are not using presets it's safe to just delete your database or have it in-memory only. There is just one thing you shouldn't do: Edit the XMP files of images in the database. The database entries will be used and your changes will be overwritten eventually. There have been discussions about how to change that, we will continue these after the next release. > > To me dt and lightroom (I've been using lightroom extensively) are on > > par here. > > No they are not. In LR you get a history entry for every change you make on > your image. If you do change the same parameter twice you'll get two > entries. > In DT you get an entry for a plugin instance or something like that. I'm not > really sure how it works, yet, but I'm sure it is not that powerful and of > course > it is not obvious at all how it works. That's another topic that has been brought up every now and then. darktable does have a generic undo system which is completely unrelated to the history stack. Currently it's only used in map mode though. It might be possible to make use of that, however there needs to be proper planning and a solid design for such a feature before ANY code should be written (*hint* to all the people who want to start implementing this. I know that it's trivial from a coding point of view, but please, let us do something right for once. Not like masks which evolved over time). > BTW: I've used LR once or twice, but this feature is really great. I and most other darktable developers never used it, so please don't expect us to know about its way to do things. And I guess most of us don't want to know either. That way we can't be accused of copying. :) > Best regards, > Teodor Tobias
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________ Darktable-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-users
