Latest News: (loading..)

Mark Evans

  • Content count

  • Joined

  • Last visited

  • Days Won


Mark Evans last won the day on November 5 2011

Mark Evans had the most liked content!

About Mark Evans

  • Rank
    Code Monkey Rockstar
  • Birthday 08/20/1977

Profile Information

  • Real Name
  • Gender
  • Location
    Behind you :-P
  • Interests
    work, work, work, work, then on weekends I enjoy to work :)
  • Website
  1. I'm not sure we need yet another place to do things, redmine is great if you don't have Github but I don't really see the point in using it for osCommerce, we can easily achieve the same thing with the tools we already have
  2. I'd use 2.3.3 as the base, 2.4 will be on the way soon but will be pretty similar in terms of functionality, I would then suggest keeping an eye on the 3.x development as once we get closer to stabilising the core codebase we will look to prepare a full functionality release which will be radically different to the 2.x series
  3. I have some proof of concept code lying around somewhere which made the caching system work with APC, Memcache, Wincache and the current file based system. APC is great for working across just a single webserver but when you need to deal with load balancing APC is a pain, in this scenario memcache is the better solution. I'll see if I can dig it out if anyone is interested? I also wanted to look into Redis support at somepoint as well, maybe during the Xmas break I'll get some time to do some proper coding again!
  4. jQuery is already used in the front-end of osCommerce, integration into the backend was only a matter of time. Personally I think the many benefits of jQuery far outweigh the few negatives and the no-support for older browsers is a good thing, the whole world would be better off not supporting IE7,IE8 and IE9
  5. The roadmap can be seen at In short, there is a lot of work to do on 3.0 and it will take a while, if your a developer then why not help out
  6. There was no way we could be backwards compatible and move the codebase forward enough to be a good base for the future. As I've said a few times recently, if your not a developer don't use v3.x for now, 2.3 is a supported released and will receive more updates to keep the general userbase busy. If you really want v3.x then you pay a little more per month and get a VPS, there are 1000's of companies offering them which will give you PHP 5.3. Supporting every shared hosting company out there will do nothing but hold everyone back
  7. If your that desperate to take a look just download it from there is no need to wait
  8. Yep totally agree, if you also add VPS / Cloud / Dedicated servers into the mix you are into 1000's of hosting companies as well so I think people jumping up and down saying its wrong to have PHP 5.3 as a minimum requirement are just spreading pointless FUD. 2.3 is also a supported release and will be getting some updates soon to fix some of the known bugs so people have a real choice, stick with the 2.3 series which while its a pain to modify and upgrade will run just about anywhere, or use 3.x which is a little more strict but will be what the future is built on.
  9. So your the cup 1/2 empty then
  10. There are now 9 and thats just the shared packages , I can probably make that into the 100's if we included VPS / Dedicated servers. To make a long story short, 3.x is in it for the long haul, its not ready to be used by people that don't know what they are doing and I think thats a good thing. We should all stop looking for the new shiny thing and lets give it time to bed down and stabalise, get other developers trained up and get the community addons and contributions to core rolling in. This will all benefit the codebase and the userbase considerably for the future and was one of the core goals of the 3.x series. Its "cup 1/2 full" time and not "cup 1/2 empty"
  11. Wordpress is a good example of how a modular approach can be implemented, there are also quite a few other open-source solutions which have tackled the same problem in different ways, I intend to look into a number of different solutions to this and hopefully what we can get out of it is something which will stand us in good stead for years to come.
  12. It will be possible to change even core functionality without changing core code. With over 6000 contributions currently available this is not a viable solution in any sense of the word. The osCommerce team will ensure that the functionality in core continues to work at all times but we will not be testing every single addon, that is the responsibility of the addon developers themselves.
  13. With the development of the 3.x series we will be moving towards an approach where modules can be installed and changes to osCommerce made without the need to edit core code which is the problem with the 2.x series. This will handle the installation of modules and the removal of modules. I am not sure when this will be ready but hopefully we can start on this soon. If anyone has any thoughts on how this process should work or how modules could be implemented I am of course interested to hear idea's.
  14. Just so I don't need to keep repeating myself Read This