|
I found where it puts the output file. The last line in the log ends with \build\OPS/content.mobi. but that file's deleted when it's done. The output file gets put in the same folder as the source files.
So why is that last thing not in the log eh? A dialog box informing the user (with a Don't show this again checkbox) of the final output's location would be nice.
eCub is like so many programs where the author is re-writing all the stuff the GUI already provides, specifically file dialogs. GUI systems have standard dialogs so that programmers do not have to spend time and code doing *everything* like they did with commandline systems- yet for the past 25 years programmers have mostly persisted in reinventing the wheel rather than simply using the built in system calls etc. Adobe is a most extreme offender on both Mac and Windows, then there's MS Office that is just as bad as Adobe products at not using Windows' built in stuff.
Do you remember one of the big marketing points for Windows in the early 90's? Something about once you learned to use one program, you could use them all. Would be true IF programmers would use the standard dialog boxes instead of creating their own, usually worse than the OS default, boxes.
I did some programming in the 80's and 90's. Things like error trapping, garbage collection, making sure error messages were actually informative and useful, making the program make sense to people who didn't know how every little bit of it worked (ie everyone *not me*, the author)... for me it was *work* so I quit. But those are just the things any programmer who expects anyone *not them* to use their software must do to create a good and useful and *useable* product.
|