Right, the T900 is from 5 years ago, the EEE Slate is almost as old.
I'd like something contemporary, ideally something w/ the potential to last as long as my Stylistic (oh yeah, and it needs to fit in my old laptop bag, so no larger than the ST-4121, which both machines you noted fail at).
Currently making do w/ a Toshiba Encore 2 Write 10, but the lack of a daylight viewable display is really starting to annoy me.
Yeah, I'd give my interest in hell for a copy of OS/2 for Pens.
The initial ThinkPad was conceived as a tablet computer (named for the leather pad holders embossed w/ ``THINK'' which IBM issued to its employees — see the book _ThinkPad: A Different Shade of Blue_ for the backstory on that).
Really wishing that my ThinkPad x61T were a real replacement for my Fujitsu Stylistic ST-4121 --- features I need:
- better stylus implementation (Wacom EMR is fine, so long as it's done well, Samsung certainly has this down, Toshiba w/ Wacom’s new AES has done well)
- daylight viewable display --- that's the big failing on most machines now, one can only get a true daylight viewable display on rugged machines sold to (and priced for) military, LEO and construction
Here, like this one:
This is something which I've been wondering about for a while --- given that people won't be disciplined enough to use a wiki or other content management system, why not just dump all corporate communications into a single archive?
Use some sort of expert system to make an initial effort at putting things into a hierarchy based on sender, recipient and subject line, strip out all attachments and replace them w/ a link to the stored copy of the file.
If need be, have some sort of system for determining access levels based on recipient.
Bonus is people would be forced to accept that work e-mail was to be used for work stuff only.
Libraries will get you through times of no money better than money will get you through times of no libraries.
—Anne Herbert (writer)
The problem for how most people use technology is that they accept the defaults, then laboriously, manually, at each necessary point, alter things by hand so as to achieve the desired effect.
Understanding how to set up:
- style sheets (even in a basic word processor)
- macros (yep, word processors have these too)
- piping commands at the command line
- semantic tagging
will go a long way towards making them more productive (and me much happier when I get book manuscripts which are properly set up).
Hint, if you find it necessary to turn off the viewing of special characters 'cause of the visual noise, you're doing it wrong.
Convert to your choice of XML and store that
Use pandoc to convert to whatever format is requested. If a document is requested and edited, use pandoc to read in the edited version and store that.
Once you've trained everyone to accept the lowest common denominator, it'll work.
For bonus points you could go straight to MediaWiki markup and put everything into a wiki.
Paper ballot --- if need be a scanning machine, but there _has_ to be a physical audit trail verifiable w/o the use of a machine.
Some awkward aspects are imposed by the source being Markdown on Github, so lowest common denominator for special characters such as what should be em-dashes.
Interesting footnote to the project is that the note explaining how to use the interactive diagrams was deleted by a person who thought it was unnecessary --- less than half of the people who responded to a poll figured out the interactivity and almost all those who did find it were surprised by it.
Part of the reason it's hard to write good documentation is that it's hard to get people to make use of it --- similarly we've tried to get everything about this CNC router onto the wiki, but there are still an awful lot of forum posts which I answer w/:
``That's on the wiki:
AOL will allow one to convert a paid account to a free one when one cancels --- one keeps all one's old e-mail addresses, and they've increased the number of free ones allowed per account so one doesn't have to delete any.
I had a paid dial-up for a long, long while and would probably still have it if they hadn't cancelled the members.aol.com webhosting --- if they'd charged for that separately and maintained it, I'd still have it.
1+1 == 2 --- the rear seat looks to be downright claustrophobic though.
I don't get it. If they're so incompetent that they can't be kept as workers, how can they be competent enough to be training their replacements?
Why don't all the workers collectively agree to not impart their obviously flawed work skills and knowledge to their replacements?
If my boss came to me and said that he was replacing me, I'd say fine. Documentation is on the wiki, the source for everything is written up as literate programs, the only things out-of-date are and --- if you want me to up-date those, call me tomorrow and we'll work up rates.
Here's to hoping that they actually go into production: