svdl - i've never had the javascript editor i'm typing in now work properly.  and the pages are a labyrinth of html and css implemented in very, very inefficient ways.  in my experience, changes to an existing structure that's very clean, very precise, and very abstract still take about 3 to 10xs as long as it seems like they should and as people predict, because issues just come up.  i honestly don't know of a programmer or project manager that would suggest a structure change to something as extensive the bondware content management system, let alone something as messy as it appears, when they're still in the process of implementing existing technologies site wide.

i agree, if it's an mvc design pattern, it's shouldn't be but so bad.  my guess is that you'd still need to change each page to work with an image property that's an array instead of a string, but not so bad.  like i said, if this used a framework, then the change should be easy.  but most scripts and even tutorials i've encountered don't use php that way.   conversely, most content editors don't use tables any more (as this one does).  i've certainly never seen anything use css like (for instance) this forum does, or even the gallery does.  i've seen the .js text editor before, and personally i turned it down for exactly the reasons i'm having problems with it now.  i found it very flaky in testing.

i'm not impugning the designers and developers at bondware. i just know you have to design for extensibility in the first place, or it's pretty hard to grow in new directions.  and from looking at what i can see, i'd say they were a very small team doing just in time work, and focusing on what's most important.  not designing for huge amounts of possible futures.

i wouldn't be surprised that the staff has other priorities.  it seems like a lot of trouble for something that probably wouldn't get used much.