View Single Post
Old 09-24-2009, 10:55 AM   #14
dmikov has learned how to read e-booksdmikov has learned how to read e-booksdmikov has learned how to read e-booksdmikov has learned how to read e-booksdmikov has learned how to read e-booksdmikov has learned how to read e-booksdmikov has learned how to read e-booksdmikov has learned how to read e-books
dmikov's Avatar
Posts: 257
Karma: 960
Join Date: Dec 2006
Device: REB1200; REB2150; Sony 500/350; EZReader; IREX DR800SG; Nook/Color
Originally Posted by rogue_ronin View Post
It is "more typing" that makes it easier. I can remember what GetDocumentName means (NoteTab example.) When I drop to, say, bash, I have to use Google whenever I want to script something. What the hell is a '[', and where can I find documentation? It isn't an enclosure, that's for sure. It's actually a word of some sort, related to 'if'.

When I said BASIC, I basically (hah!) meant that it should be relatively easy to learn and simple in syntax. The example I gave with NoteTab falls into that paradigm. It can do amazing stuff, but it is really easy to learn. Over time, it added more than just text manipulation -- it moved into regex, file management, disk-access, web-capability, and more.

The point is to make it accessible to non-programmers. Folks editing and formatting their favorite books are not likely to be conversant with the ins and outs of proper programming. But if you can come at it from a simpler format, you'll get a lot more people contributing useful macros. And you can always add complexity.

I'm not a complete idiot, and I've programmed macros for years -- but when I start seeing massively indented bracket outlines, I just turn right off, lose enthusiasm. When I switched to Linux, I looked for a text editor that was programmable, comparable to NoteTab. I found Nedit, and a few others -- but they all required knowledge of C, or C structuring, familiarity with low-level use of environment variables, sed, etc. They were programmer's editors (which is natural, considering the nature of Linux.) I still keep a Virtual Machine of Win2K in order to run the latest NoteTab because I can't find a replacement (what, 8 or 9 years later...)

A macro in a text (or HTML, or writer's) editor is a list of instructions, manipulating (in this case) text and variables -- do this, then this, add it to the other thing, and put it over here. I feel that it should be as straightforward and simple as possible, while still retaining capacity to do anything at all that the host editor can do. Add hooks to other scripting languages if you want, but keep the native language simple.

BASIC is a good example of this sort of thinking (and Clip, from NoteTab) -- javascript is not, nor C*. Perhaps AppleScript, too, is a good example. What I remember of it was some sort of 'natural' language syntax. I thought it was a little loose, but better too loose than too strict.

Book editing is much closer to artistry (writing) than programming (as it is usually performed.) Make tools that enable the likely sort of people that will be using the editor.


m a r
I have to disagree with you on this one. Easy macro languages are hardest to learn, they are usually proprietary to one piece of software and there fore hard rationalize investing too much time into. Add to it, that vbscript or jscript or ruby or etc has oh around thousands books to learn and NoteTab or whatever < 1, situation becomes even more hard on developer to support it.

I like notepad++ and ultraedit. I would use notepad++ since it's free and has good plugins, but I am using ultraedit since on top of macro language (which both have) it has scripting with a normal language.
I think Microsoft Office can be commanded for at least this accomplishment of including nice scripting capability. Hate their code storage paradigm though.
dmikov is offline   Reply With Quote