Comment Just one bit of advice (Score 1) 268
Ensuring everyone in project is using same one is more important than which one is chosen.
If you can use the same one for a whole company even better
Ensuring everyone in project is using same one is more important than which one is chosen.
If you can use the same one for a whole company even better
1) Install Wikipedia software locally and use this for any locally created articles
2) The web server running this simply proxies out to en.wikipedia.org for that request if not available in the local version. The easiest way to do this is with Apache + rewrite rules
This means that users can get to articles locally and on wikipedia from the same command
You then need to consider the following
1) The search request needs to go to the local version of wikipedia then the external one and concatinate the results together - a small proxy script should be more than capable of doing this
2) You may want to create a reference table which maps external wiki articles to related internal ones. Again a small script could insert these into the external wikipedia articles during rendering
If you are running a bog standard desktop or laptop you probably have some basic requirement
* when I turn up at my computer after having a cup of coffee and hit slashdot.org into firefox I expect it to launch straight away
* when I shutdown my computer I expect it to happen instantly
* when I start up my computer I expect it to happen instantly
* when I save my music/words/picture I expect it to be reliable and nothing my computer will do after I save my file will affect it
* under no circumstance will my mouse, keyboard or icons on desktop not perform to my actions - I want no hang.
This is not the fault of disk swapping it is just an example about how 5 utterly straightforward requirements have not been addressed in over 20 years of desktop development.
First OS which has this gets my vote
You knew the job was dangerous when you took it, Fred. -- Superchicken