Seriously, I hate touchpads. The touchpad era in notebooks started many years ago, but I still remember what an excellent pointing device trackball was. I tried many notebooks, IBMs, Dells, Asus and Apple among them and find that none of them has touchpad useful enough for me. It is because touchpads start to react on (surprise, surprise) touch. It wouldn't be that bad, but they also react on pull-off. Why don't I set touch pad sensitivity to small number? Because I don't like it this way either. Trackballs react only on move, you can touch and off the ball as much as you want and the pointer will stand still. Until you roll. I'd really love to see Powerbook 140-like trackball in new Dells.
You pointed many common issues and annoyances with general purpose frameworks. I strongly agree with some of them. The main problem in a larger perspective is that most frameworks tends to do too many things at a time. In my opinion there are three or four main areas that frameworks should focus on. 1. Infrastructure. A good transmission and request routing architecture is needed. This covers handling requests, XMLHttpRequest stuff, timeouts, cancellation, queuing, repeating, ordering and error reporting. A good infrastructure library should provide easy to use communication channel to and (often underestimated) from server. 2. UI library. Tight coupling user interface (widgets) with Ajax libraries is in my opinion frequent design flaw of frameworks. 3. Model classes. Often tied closely to format provided by UI or communication layer. General purpose model classes should be kept separate at all cost. 4. Other libraries, like newsletter or access control, should be kept separate as well. The more are these areas tied together, the faster you hit the limit of a framework. Bearing that, it is amazing how much are general purpose all-in-one frameworks overhyped. They all bring a promise of delivering ultimate solution with no extra coding, which is in _many_ (no, I don't know how many) cases difficult to achieve (if ever possible).
And now some advertisement blurb. Skip if not interested.
I run sourceforge project Tigermouse PHP/AJAX framework, which aims to be enterprise-grade ready web application framework. This is why I tend to keep its parts loosely coupled. Each part can be easily replaced using the same interface (or adapter). Keeping codebase small allows you to integrate almost any existing library into it, but that means some extra coding (that breaks the unspoken promise I mentioned above).
Simply don't accept format other than html. Deploy a simple and useful HTMLArea script so users can edit document (or copy-paste from Word) directly inside web browser. You can learn more on HTMLArea at http://www.htmlarea.com/> - there are plenty of them. My choice is the one from InteractiveTools http://sourceforge.net/projects/itools-htmlarea/>. It is released under BSD license and plays nice with Mozilla and IE 5.5+.
I do not know much about MOX, but since it's basen on Unix you may want to have a simple script that reverts 'student' account everytime system boots up.
Here is what I did to make sure 6 PC are running reliabily in my former high scool: - created 'student' account - created backup of clean/home/student somewhere else - created a small boot script that was purging and reverting from backup copy of/home/student Additionally I had a remote users database and home directories via NIS and NFS.
So, my advice is: keep backup copy of clean/home/student and bring it back periodicaly.
Slashdot Mirror
Paddy Power is an Irish company you insensitive clod! The one I had chance to work for as web developer - I would surely know if they were from UK.
Seriously, I hate touchpads. The touchpad era in notebooks started many years ago, but I still remember what an excellent pointing device trackball was. I tried many notebooks, IBMs, Dells, Asus and Apple among them and find that none of them has touchpad useful enough for me. It is because touchpads start to react on (surprise, surprise) touch. It wouldn't be that bad, but they also react on pull-off. Why don't I set touch pad sensitivity to small number? Because I don't like it this way either.
Trackballs react only on move, you can touch and off the ball as much as you want and the pointer will stand still. Until you roll.
I'd really love to see Powerbook 140-like trackball in new Dells.
You pointed many common issues and annoyances with general purpose frameworks. I strongly agree with some of them. The main problem in a larger perspective is that most frameworks tends to do too many things at a time. In my opinion there are three or four main areas that frameworks should focus on.
1. Infrastructure. A good transmission and request routing architecture is needed. This covers handling requests, XMLHttpRequest stuff, timeouts, cancellation, queuing, repeating, ordering and error reporting. A good infrastructure library should provide easy to use communication channel to and (often underestimated) from server.
2. UI library. Tight coupling user interface (widgets) with Ajax libraries is in my opinion frequent design flaw of frameworks.
3. Model classes. Often tied closely to format provided by UI or communication layer. General purpose model classes should be kept separate at all cost.
4. Other libraries, like newsletter or access control, should be kept separate as well.
The more are these areas tied together, the faster you hit the limit of a framework. Bearing that, it is amazing how much are general purpose all-in-one frameworks overhyped. They all bring a promise of delivering ultimate solution with no extra coding, which is in _many_ (no, I don't know how many) cases difficult to achieve (if ever possible).
And now some advertisement blurb. Skip if not interested.
I run sourceforge project Tigermouse PHP/AJAX framework, which aims to be enterprise-grade ready web application framework. This is why I tend to keep its parts loosely coupled. Each part can be easily replaced using the same interface (or adapter). Keeping codebase small allows you to integrate almost any existing library into it, but that means some extra coding (that breaks the unspoken promise I mentioned above).
Simply don't accept format other than html. Deploy a simple and useful HTMLArea script so users can edit document (or copy-paste from Word) directly inside web browser. You can learn more on HTMLArea at http://www.htmlarea.com/> - there are plenty of them.. It is released under BSD license and plays nice with Mozilla and IE 5.5+.
My choice is the one from InteractiveTools http://sourceforge.net/projects/itools-htmlarea/>
I do not know much about MOX, but since it's basen on Unix you may want to have a simple script that reverts 'student' account everytime system boots up.
/home/student somewhere else /home/student
/home/student and bring it back periodicaly.
Here is what I did to make sure 6 PC are running reliabily in my former high scool:
- created 'student' account
- created backup of clean
- created a small boot script that was purging and reverting from backup copy of
Additionally I had a remote users database and home directories via NIS and NFS.
So, my advice is: keep backup copy of clean
1. Mark a selection
2. "Ctrl+C"
3. Mark another selection
4. "Delete"
5. Click somewhere
6. "Ctrl+V"
7. Enjoy pasting your first selection
I find your problem nonexistent.