On Thu, Feb 21, 2013 at 12:13 PM, Pascal Obry <[email protected]> wrote: > Jeremy, > >> I'd like to point out that there are use case for "resetting image to >> default processing" (including gps data) and that use case is handled >> by DT, but I don't really see a use case for resetting only GPS data. > > Agreed. I think it would be nice to be able to reset data from the RAW/jpeg > and not only GPS data. My point is that this is only possible today by > loosing the development process which I find not acceptable. >
I think you mean meta-data, i.e everything that is handled in LT/map view but not what is handled in DR mode (white balance for instance wouldn't be reset to camera) I understand the idea. I personally don't really have a need for that and that info is quite limited (comments from the camera, gps position, maybe tags I am not sure) > From a technical point of view I think it would be nice to be able to re-do > what is done while importing and keeping the current development. > I am not sure I understand that last sentence. I don't think there is "technically" any difficulty, it's only a question of UI as far as I can tell, but that's probably waht you mean by technically. what confuses me is that importing is a developement. unless you mean "pre-opening in DR developement" I am not quite sure exactly what that covers. When importing some presets might be auto-applied on top of the image (in particular copyright info) do we want to re-add them ? Overall I still can't really see a use-case which reduces my capacity to understant what you are trying to achieve. AFAICT there is very little data that is not developement. A comment, maybe tags and rating and that's it (maybe a little more in case of LR import, i'm not sure) That sort of stuff is easy to redo manually, and resetting only really make sense for developement to me. I don't want to have too many ways of reseting/undoing etc... I like the idea of having either undo or restart from scratch which is what we currentlyu have and is very simple. For me, everything else would need a "clear semantic" i.e a good use case and a simple explanation, so I can have the underlying idea. right now i'm really not clear here... ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ darktable-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/darktable-devel
