Wordprocessing on the web

I realized it had been awhile since I updated. I think most of my posts are starting this way it seems. But i have been working hard on a few things, one of which is all about wordprocessing on the web.

I have been working on bildr code a whole lot more than I care to say. I actually found a HUGE fundamental flaw in how the versions are created. Essentially I thought it was working because I wasn’t properly testing it. Every edit was being tracked, then one time I did a new edit and all my files disappeared. Long story short, the fact that it worked before was dumb luck. But all is fixed.

But on the productive side, I have been enabling bildrCode to allow users to evoke typical commands used by coders. One of them enabling tabs. Tabs are HUGE in code. You tab to indent your code for better communication, but some languages actually require this. So tabs, being so important, I worked long and hard to make them work.

Hitting the Tab will make a tab as it should.

I know that tabs are used to cycle through fields on a website. BUT you need to stop thinking of this as a website and start seeing that they are just applications that live on the web.

So tabs… Well you can now select a bunch of text, and hit tab, and all of the lines will shift over. Or you can hit shift-tab and they will shift back. The whole process is way complicated to get it working correctly, but to the user, it just works.

——————————————RANT——————————————

I have to make a plug here for webkit, specifically safari. I develop in safari. It’s fast. Maybe too fast. I move over to firefox and im annoyed with how slow its javascript performance is. Also you can see some fundamental flaws in the way the developers felt it should work.

Holding a button down only fires one event, but the computer knows to enter that key over and over until they let go. WHAT???? Like this aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa <– I just held down the a key down. Well safari knows that there are like 20 As there, so it fires a new event for each. But firefox feels this should just be the one, so the first a sends an event, but then the rest get no love.

Comments are closed.