shawnjgoff

Thanks! That looks superb.

I agree. It's like Photoshop: at first you're like "WTF were they thinking?" until you really use it and see what geniuses they were.

Or joke about you in irc while secretly not using either tool themselves.

Jedit is amazing. It's like the Firefox of text editors - not the smallest or fastest, not the biggest or slowest, but reasonably quick and very very extensible. I would say that other tools (vi and especially emacs) are also very extensible, but Jedit has no learning curve and fits in well with Windows.

That said, I'm slowly becoming more efficient in vi and it will eventually overtake Jedit for myself.

The problem is that your "object code" is someone else's "source code". When you follow standards, it's easy for people to use what you've published; when you don't, it's painful.

A simplistic example: say you put out a typical web page with a navigation area and content area. Maybe for some reason, your website is much easier for me to use if I put the navigation above or below the content or maybe you put it on the left, and it works better for me on the right. If you used standard practices (CSS) to position your elements on the page, it's really easy for me to go in and mold that to exactly what I want. Why? Because it's the standard, so there are plenty of tools out there for this. All I do is tell the browser to overlay my css rule on your page and I'm done. On the other hand, if your layout is done with tables, well then it becomes much more difficult because you didn't follow the rules that the majority of us have agreed to.

Okay, I really don't understand this part: while (q) {G;} If p is true before the loop, then it must be true after the loop unless your loop has a break.

What if the condition p is that var_p == 1. And in the loop you decrement var_p. If the condition was true before the loop, it certainly is not if the loop ever runs.

It kind of is an operating system. Check out Process Manager. Read the developer manual.