- again pointing out that there is no conversion done
- it’s just bad user experience
- i am done with this thread
I guess you mean if I would have checked out tag 0.3.3, then version 1 would have been there and the update tool would have again done what it did before …
2 problems :
- which tags are version 1 ?! the versioning issue is missing in the readme
- we still have the update tool in that picture
- it was what I was saying!
- yea having a conversion tool and converting from one primary source is obviously good engineering. I never challenged that. In fact I didn’t even knew there was a conversion tool.
Its not what i was complaining about.
My point was that the tool that was meant to update did not bother to gather the one primary source and convert, but rather utilize an artifact from a different place over running a conversion.
And that’s crude at least.
darktable is using a library it knows it may be outdated and even suggests to the user in a tiny tool tip to run that tool … guess its on me then
i’m not insulting if i say its crude. maybe you don’t understand the word as I do. what I mean by that is that it is not easily understandable why things happen the way they do, and yes I know “organically grown” software does often do things like that . It is crude just as windows is crude.
maybe you didn’t realize it. but I did put my free time into this by reporting on an UX issue with the software.
what I meant was look at that crude manual deployment.
However I still don’t know what I should have been looking for.
I looked at the readme and no it doesn’t state anything about the version issues there.
Yea, i could have compiled and stepped through the code and find the usage of the v1, or as i did looking how it would behave if the update was run.
but no code for conversion is actually invoked, except by the user that’s building the artifact.
who is “insulting” now?
Even your first reply wasn’t very nice and in my opinion you conveyed that not just in writing, but also in omitting the actual link to the conversion tool.
It is not just an inconvenience to me but also to all the others that may find this post, looking for an answer. (but i guess this is not stackoverflow or something?)
Anyway, your replies have shown me that I REALLY do not want to communicate with you. ( take it as the SNR is too low). So please take that as my last reply to you no matter how tempting responding to you ever may be.
for what it’s worth, hopefully my UX report will be helpful to some of the devs in improving the UX.
yes in my opinion the thread is done. i am the problem for not understanding the mysterious ways of dt … its ok.
i already spent too much time on that argument anyway.
any devs out there, try to look at the docs and try to imagine how a new user/dev would penetrate the source/documentation. often it is not the stupidity of the newbie but rather the enigmatic ways of the docs/code .
Simply ask yourself whom do you write the software for. should the code be hard to read because it was hard to write?
good code explains itself through its unit tests. documentation never is good enough