webpad has been sorely neglected, and it is starting to show. I have a bad feeling that it won’t work on a default install of PHP anymore, and there are a number of reported bugs related to the install and configuration process which have done anything *but* go away with time. I think it is getting close to time that I need to re-write the core code for little-ole webpad, and try to bring things up to scratch.
There are also a number of improvements I would like to make to the system at the same time, but priority one will be to bring all of the existing code up to a certain level, then move forward to a new version.
And so… the requirements (as far as I am concerned) for version 2.1 public are;
- Re-write of backend code to standardize style/syntax etc.
- Ensure that all code is 100% compatible with a default installation (no register_globals being the big one here)
- Switch all of the Blogger.com operations over to using the new, inbuilt XML-RPC functions in PHP, rather than the external library it currently uses.
- Ensure that all Blogger.com operations still work (their API has been all over the place, so who knows??)
- Iron out any bugs in the install process to ensure that the app can be installed with a minimum of fuss.
With that out of the way, I will then look towards a 3.0 release, which should look something like this;
- Inclusion of ODBC, PostgreSQL and possibly Oracle plug-ins for authentication
- Streamlined setup/install and user management (*large* improvements planned)
- Improved support for authentication methods other than WIXAS
- Much better file management (directory creation, renaming, deleting etc)
- Integration with Blogger Pro, Radio and MovableType if possible (expanded to include template management and better post management)
- Ability to load a file from the filesystem via direct request (i.e. http://webpad/?file=/path/to/file.txt) assuming permissions allow it and it’s within the user’s home dir.
- Much better mult-user support
- Commercial licenses will attract a modest fee (in the vicinity of $USD15), while personal use will remain free
RESTments? REST-based comments for RESTxom
Am working on a commenting system for RESTxom which will store a parallel file for each entry called “<entry>.comments” and will act like a small flatfile database to store comments for each post, which will also, of course, have REST-friendly URLs.