At the moment, things are a little on the quiet side due to the number of things I've got on, however, I'm currently working on the following:
1) Removal of the hard-wired database name so that users who are given only one database can use xdbcms. The database name will default to xdbcms, but can be changed in one central file.
2) I've been working on-and-off on a facility called 'in-situ' edit. Where the page edit screen is actually a mock-up of the final page - i.e. it looks as if you're actually editing the web page directly rather than templates in one page, and the text in another.
3) I've been experimenting with XML in my spare time over the last couple of months, and I'm perfecting XML export and import routines from a mysql database. The net upshot will be the ability to 'save' fragments (or whole websites) and share them - i.e. it will be possible to set up and share website 'look and feel' templates. I'm envisaging that you will be able to 'import' a template into a website you're defining, and it will include the page layout template, the cascading stylesheet definitions, and standard text blocks and graphics. It should be able to give any novice use a very quick head start, and it will allow more experienced users of XDBCMS the ability to contribute more easily.
I see this last facility as being one of the major improvements - of the system.
I'm working on the first two areas at the moment, and these will be in the next release. The XML items will be in the following release, with refinements and bug fixes following that.
Given work commitments, I'm expecting that the above will probably see the system into the new year.
Hopefully that gives you an indication of the future - please let me know if you need any more detail...
Thanks
Carl.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Carl,
Can you detail/share your plans for XDBCMS ?
Thankyou
Ian South
Hi Ian,
Thanks for the interest -
At the moment, things are a little on the quiet side due to the number of things I've got on, however, I'm currently working on the following:
1) Removal of the hard-wired database name so that users who are given only one database can use xdbcms. The database name will default to xdbcms, but can be changed in one central file.
2) I've been working on-and-off on a facility called 'in-situ' edit. Where the page edit screen is actually a mock-up of the final page - i.e. it looks as if you're actually editing the web page directly rather than templates in one page, and the text in another.
3) I've been experimenting with XML in my spare time over the last couple of months, and I'm perfecting XML export and import routines from a mysql database. The net upshot will be the ability to 'save' fragments (or whole websites) and share them - i.e. it will be possible to set up and share website 'look and feel' templates. I'm envisaging that you will be able to 'import' a template into a website you're defining, and it will include the page layout template, the cascading stylesheet definitions, and standard text blocks and graphics. It should be able to give any novice use a very quick head start, and it will allow more experienced users of XDBCMS the ability to contribute more easily.
I see this last facility as being one of the major improvements - of the system.
I'm working on the first two areas at the moment, and these will be in the next release. The XML items will be in the following release, with refinements and bug fixes following that.
Given work commitments, I'm expecting that the above will probably see the system into the new year.
Hopefully that gives you an indication of the future - please let me know if you need any more detail...
Thanks
Carl.
Sorry, the words I was looking for was 'theme support' (that's what you get for writing things at midnight!).
- Carl.
Thanks for the update..
Ian