Id like to make a new wiki type system for my intranet. I would like it to be like a wiki but some differences. Ill focus on the cool parts first
1-this wiki should allow a runtime and design time
-when in runtime you are looking at rendered html so it will be just like a webpage
-when youa re in design time it will be like a wysiwyg but allows you to type. The key here is i want _many_ people on this one page at the same time making changes. i want the changes to appear on each other screen in nearly real time. Very similiar to how some of google docs work.
Structure of the system
1- We have categories and sub categories
2- We have pages inside a category
I am very picky about the ui so we will use extjs for making most of the controls on the page like the tree and some of the edit functions.
As far as the page goes i dont know how you would like to plan on building this. I need a very basic wysiwyg. either the yui editor or maybe extjs has but im not sure what will perform the greatest.
This system will help to allow real time documentation accross a team of people without any conflicts that can happen with many people editing a wiki or a document.
I would like to run a yellow fade technique behind the text that was just updated so when you are looking at the page and working you can tell what just happened. Extjs has this.
server side i want to store the doc html as a log of changes.
We will test this up to 5 users on a document making changes
MS SQL, IIS, would be great to see .net server here but client side needs to be light and fast meaning js and json. (no heavy controls)
great example of what i want is
<[url removed, login to view]> click on EDITOR, open two windows and type, you see it works. I think it is a little slow but works
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).