Will have to keep it short today; I'm in the process of re-installing my OS and really don't have the time or energy for writing a long message right now. So, Bird, you have decided the user interface wasn't "solid" after all, huh?... (: The options screen doesn't work correctly for me. Clicking on an option will sometimes, but not always, select the option above the one I clicked on. I don't know when and why, it just sometimes happens. Thanks for labelling the buttons; that makes it somewhat better.
that's because you made a change to the text, so it's making it impossible for you to continue until you have saved that change. just hit "save" and things will return to the way they were before.
I had _not_ changed the text yesterday when that huge Save button appeared. Guess it was just some kind of glitch, like the user interface not always looking correct; resizing the window usually resolves that, which does of course not make it any less irritating.
* links from the table of contents to the chapters * letting the user choose background and foreground colours * letting the user choose the font to use * jumping to the right spot in a chapter after a search
suggestions #2 and #3 are on the list for later coding. (but #3 is a bit ambiguous. where is the font "used"?)
You said they were; so when's "later" going to be? The font is used in the conversions; for now, that would mean the righthand side, because as I understand it, that's the only conversion we're doing right now: HTML. And in my HTML, why not let me choose the font I wanna see?
i doubt i will program #1. use the pop-up menu instead. (but, of course, in the conversions, the toc will be active.)
But that's exactly it! The righthand side _is_ a conversion, namely the HTML conversion. Are you telling me I need links from the table of contents to the chapters in epub, mobi and PDF, but not in HTML? That's just plain silly.
as for #4, i fail to see a need for that in a conversion tool, which is what this app is, at least for the time being, so if you can give some justification for that, i will consider it...
Then why allow for searching at all, if you're not willing to make it user-friendly? You can argue that the user doesn't need a search capability, and I would accept that. If we're building a conversion tool, let the user convert his text, and if he wants to edit (and search) it, let him use a text editor; I would be fine with that. But what you are doing is arguing that the user needs a _crippled_ search capability, but not a _decent_ one. That doesn't seem to make much sense to me, I must admit. Yes, I can of course use my browser search after I've used the built-in search; that's just not very intuitive, you know?... Why do I have to search _twice_ in order to find something _once_? That's it for today! Jana On 22 February 2011 10:04, <Bowerbird@aol.com> wrote:
tuesday's version is up:
fleurons installed at scene-breaks. navigation-buttons labeled. abort-button installed. find-field labeled. find-button installed. options-button installed. options-screen created, with a sampling offered.
the options are not used just yet, and there is not yet a way to change 'em, but an interface is now in place.
so i am ready for today's feedback and suggestions.
-bowerbird