Followup: PHP Editing

[Anon]

Hi all, yet again.

I have uploaded my outline of my PHP editing program to http://www.activestudios.net/editor.html for all to read and give comments on.

Also, I have figured out how to put PHP code in a <textarea>: basically, fopen() the file, feed it into an array, htmlspecialchars() the array, and spit out in the middle of <textarea>...</textarea>. I gained this idea from a very simple php editing program (name unrememberable right now, full credit will go out though). It is also easy once i have the textarea, to simply fopen() a file and put the entire $textarea data into it with no processing.

Please, i would appreciate comments and ideas emailed to me.

Thanks a lot,

Ross
[e-mail]

[Anon]

A relativly simple project, about the only real concern is which security methood you wish to use. Really I think the best way to do a system like this is to use a standardized user database table and keep all account (normal and admin) in it using a binary flag based system to determine which sections the user has access to. As well you might want to toss in a project database to keep track of who has access to which projects or sections of projects. It's just a matter of simple number juggling.

[Anon]

Oh and a side thought, I wouldn't go locking the file while one person edits it, this could lead to all kinds of problems, maybe it'd be best to just warn the person if the script is currently in use by another person. There's always the posibility that someone else is just playing around with the script and isn't actualy going to do anything with it and the other person who logs in second who's is supposed to edit the file isn't able to access it cause it's already locked...

[Anon]

I agree with Shaun. What you might do is at this display:

(User) - Chooses a file to edit

Have another 2 columns to the right...
Out/Avail, Checked out by:

Then of course make the projects that are "out" unselectable.

--ph

[Anon]

I am currently building this exact same thing. So far I am calling it bullet. Here are some of the intended gaols of the project. I would consider Bullet to be more of a application server than I would a simple editor.

Bullet has esentially two pieces.

1. Administrator and editing program
2. The runtime engine.

The administrator and editing programs are what you use to build the programs and administrate developer access.

It has these features.

1. Automatic templates.
2. All recources are referenced by name only, you do not every have to reference a path.
3. All resources are seperated by projects.
4. Ability to upload files to a project.
5. Resources are managed by a database and bullet uses the database abstraction layer to allow it to support any database.

Future.
1. Ability to load a project from zip file.
This will allow a really nice plugin feature.

2. Considering a applet based syntax highlighting editor with the ability to hook to the debugger output.

Bullet uses the concept of event handlers for both get and post requests. You just pass the resource you wish to use as the handler. With bullet you never use any directories since location is handled by the runtime engine.

I am currently reworking and evolving the administrator / editor sections of the program. I am sure I will have to do some tweaks on the runtime engine but so far that is working correctly. I expect to release 0.1 by the end of this week.

If you are interested in looking at what I have just let me know and I can send you the source. It is still in a basic form but not a bad start.