|Slogan||:||Static Content Management System|
Last release 2012-Sept-02
|Subversion||:||Checkout the repository from http://downtown.trilo.de/svn/editpointstatic/trunk (2.7 MB)|
This project is retired.
Please see the successor project Daftari .
Below text about EditPointStatic
largely applies to Daftari as well.
EditPointStatic is a derivate of Edit-Point plus some other components. Though Edit-Point is a great little product, we wanted one specific feature different. It is not about a visible feature, but a backstage behaviour:
What does Edit-Point backstage? Inside the HTML file is a pointer to a separate data file with the contents of that point. If a user is viewing the page, the server fetches the content for the point from the data file and delivers the combined result. Means the full information of the page is located in two files on the server. This technique is called 'dynamic', and it is typical for all content management systems.
What does Edit-Point-Static backstage? Inside the HTML file is a marked region, which is offered the user for editing. Thus the full information of the page is stored in only one place, in the HTML file itself. This technique is called 'static'. Thus the name of the derivate: Edit-Point-Static.
The modification to achieve static pages was this: In the Edit-Point code, intercept the lines where it accesses the data-storage-file, and replace the separate data-storage-file by the live HTML file, plus doing some range-search, -cutout and -insert operations respectively.
So we have not points anymore inside the HTML file, which point to a separate data file, but ranges, which are cutout/edited/inserted. In the Browser, served by a PHP running server, you cannot see any difference, not even in the source view. But if you view the file on the local filesystem, or from a server not running PHP, it makes a huge difference.
Editpoints and editranges live peacefully side by side. Edit-Point-Static works exactly like Edit-Point, except you can additionally use the editranges if you want.
The purpose of the static feature is: e.g. you can view the files from the local filesystem without PHP running. You can edit the files not only through Edit-Point, but as well through Notepad or any other Web-Editor or technique. The files become independend! Edit-Point-Static is not anymore the single one program to access the contents, but just one tool of many possible.
How exactly to apply the Static feature to your pages ... you can find out by inspecting the HTML files in the release folder. The staticranges are not (yet) created from the Edit-Point user interface, but you have to insert them manually into your HTML file. Copy and paste an existing one into your target file, then adapt it. That's it. You must adapt three words: (1) The editrange name definition unique per file, (2) the edit button's editrange name parameter and (3) the edit button's filename parameter. Why give the filename as parameter at all? This is a workaround, to help out Edit-Point-Static, as long it is not smart enough yet to retrieve the filename on it's own. Here a sample editrange, the three words to be adapted are printed red:
Edit-Point and Edit-Point-Static are not full fledged foolproof CMS/Wiki or the like. For such purpose, they were missing e.g.:
Thus Edit-Point and Edit-Point-Static are not suited to run a big community. But they are well suited for individual websites or for small communities not needing strong control.
Edit-Point is the Simple Content Management System written by Todd Strattman and documented and made available for download at http://covertheweb.com/edit-point. Why is Edit-Point great? It is:
Edit-Point and Edit-Point-Static run under the LGPL (GNU Library General Public License Version 2, June 1991). The license text is provided in lgpl.txt . More information about the LGPL see http://www.gnu.org/licenses/lgpl-2.1.html .
Edit-Point and Edit-Point-Static incorporate several third party libraries and other work under various licenses. All of them with open source licenses running compatible under the umbrella of the LGPL. The third party libraries and contributions are:
Other products by Todd Strattman are e.g. http://covertheweb.com/upload-point
The logo for this chapter is called 'Blocco Notes', it was created by Architetto Francesco Rollandin, and we found it in the Open Clip Art Library 0.18 http://openclipart.org .
Imprint : www.trilo.de