Haha, no problem. I am still alive even if the post was old.
Since then I discovered timthumb - and that's what I'd use today. But still - it makes more sense in my head that the CMS should do that processing when the image is changed, and not when the user views the image.
Or should I think differently? :-)
I think I can give valuable input in betatesting. The thing of it is... I come have a background as core developer (actually system owner for seven years) for a successful commercial cms system. I recently switched to a new (smaller) company, and now I am looking for CMS systems to use for our different projects.
My current company is primarily focussing on campaigns and corporate sites that want to stand out. We are in other words not going to make great portals for multinational companies.
However, as I have roamed the net looking for CMS systems to use, I have been let down by the more popular systems like Wordpress, Joomla, Drupal and so on. Rich feature set is not enough for me, as I believe it is vital that the admin UI is simple and clean. Therefore I (thus far) ended up with Symphony and Ionize CMS.
Symphony gives me tears (of joy) just by looking at the documentation, but IO is not far behind. As I mentioned in my post on Why Ionize (http://www.ionizecms.com/forum/viewtopi … 3156#p3156), I am new to PHP. My entire programming life has been Classic ASP, VBS, .Net, etc, but I have quite some experience with CMS systems and interaction design. After a few months with PHP. I am starting to become confident. For non standard solutions I started using CodeIgniter - and quickly fell in love with it. So it was natural to look for a CMS system based on CI.
I believe my main strength is the ability to understand what is best for the customer. I live on the west coast of Norway, where we produce a lot of fish. I often tell my co-workers that our objective is to help the customer sell more fish. That is always my focus when developing. "Can this make the world easier for the customer - or is it just fancyness?"
When I first saw Ionize, I was surprised at it's simpleness and slick UI. When I digged deeper and looked at the syntax for templating, I was also surprised at the clean code. Although Wordpress is immensely popular, I get the impression that it's really just a very extensible blogging plattform that people believe is a CMS-system - to the extent that big corporations demand that their site be driven by Wordpress.
I cannot guarantee that I will pour my effort into IO. I have to know it better before I decide. But if IO is the best system for my time, my time will be valuable for IO.
Instead of defining thumbnails at site level, we should be able to do it per view.
And perhaps be able to invoke custom function that lets you manipulate the image the way you want (water mark, annotate etc) using any of the CI supported frameworks.
Hey Michel-Ange, this is my story:
First, let me clarify that I haven't tried Ionize CMS more than fiddling around with the admin for 20 minutes, but the thing of it is, I've been the lead developer of a commercial CMS system for almost eight years until recently when I left to try something new.
During my years as a CMS developer, I've made my opinion of how a CMS system should be - and though I realize one system cannot easily satisfy all customer groups, ranging from blogs to multinational companies, I believe one system can satisfy most customers from one-man-companies up to 2-3000 employees without problem.
I've wanted to dig deeper into Wordpress for a while, and that's what I'm doing now. What strikes me though is that the user interface, organization and "template system" is aimed heavily at 3rd party developers and blogs - thus the focus on templates and plugins. And the interface itself reminds me much of A List Apart, trying to be artistic at the cost of simplicity. Don't get me wrong though. Wordpress seems wonderful at many areas.
However, when I bumped into a strange and surprising problem with how to display second level menus at a different place in the template, I went looking around at the other CMS plattforms out there.
I believe simple admin UI is crucial to the end user. We might think open source is heaven, but Lisa at SimpleFish Inc doesn't need fancy html5 and open standards - she needs our skills to help her sell more fish - and the simpler and cleaner UI, the more she can concentrate on selling fish instead of fancying around the user interface.
After having tried Joomla, Ez, Wordpress and a whole lot of others, I was stumped at the simple and beautiful interface. Love the way you solved multilingual interface.
I'll be hanging around.
© 2010-2012 Partikule | Web agency Paris, France