The server needed a rebuild and it has taken me sooo long to work out that the inbuilt module for my control panel is useless and cannot work with many things that mysqldump drops into the exported sql file.
Next time, if I export it with a tool, use the same tool to reimport it!
I am working on my framework, up to internal version v3. I keep meaning to release a version but I am never happy with one. TwitWave uses v2 but noone is getting too see that awful mess.
I built v3 with some security features in it, such as if the global config file sets read only values in the config, nothing can unset it to manipulate it for any effect. Also cleaned up my output module, cut its dependencies on modules from 7 to 1. I am a happy bunny with that.
Am planning to build in some external caching functions, so I can cache to memcache or another server.
Will be starting my CMS on top of the framework soon and possibly redoing some of TwitWave on it too. Also, I am going to get qdbAlternative on the framework as its been waiting for 2 years or so now for it. Once I get that done, am going to release that too. Its a good project to get released and so many sites can spring up from it, like ConvoKiller.
Ok, so I never blogged about the development of TwitWave (TW), nor did I blog ontime about the launching of TW. But as they say in the world, better late than never.
I did tweet about its development, you can find them in my twitter archive – it shouldn’t be too far down – I don’t tweet much but alot more than blogging.
So yes, TW has been idealised, developed and launched in the time of my absence from this blog. It was used as a piece of coursework for my course but I still love it and am keeping it going. I do need to get some few features finished but I keep getting sidetracked by something/someone else’s project.
So yes, TW launched but publicity is null. If your one of the rare people who read this blog then feel free to explore TW and comment about it to me and also if you feel like its friend worthy, let them know!
Thanks