> I'd prefer to have classes-based application, with some class(es)
> responsible for presentation tasks. Then anyone will be able to
> extend them to use templates (or even Smarty itself), XSLT or any
> other mechanism.
> I think some kind of MVC is needed.
Some kind of object model would be good. I'm crap at reading
procedural code nowadays - I've been spoiled. But it would help to
have an OO model as the basis for the architecture - just to give it
Out of curiousity, why avoid frameworks? Surely it's better to
leverage off common code than to recreate the same value as someone
else - just my personal beef about the way we software developers
tend to scratch the same itch over and over again.
>> I'm at a bit of a crossroad and am not sure whether I should be
>> time on the Rails port of PHPSurveyor or spend my time adding
>> to the PHP version. Knowing where we're going architectural-speaking
>> would help me understand where's the best place to throw my energies.
> Yes, applied to future development, this is exactly what I've meant.
> Not quite sure what you mean by "Rails port"...
> I was thinking of making some external classes to call their
> methods in current code (not too far in future, though :-)
The Rails port was my attempt at converting PhpSurveyor to Ruby on
Rails. I've just had a half hour talk with a mate of mine where I
pretty well convinced myself to drop the project - for the same
reasons as above. I'd rather add value to PHPSurveyor than recreate
that same value in a different language - even if I find Rails easier
to work with. What I'd like to do is give PhpSurveyor a RESTful
interface - possibly the same idea as your "external classes".
>> BTW, I'm also working on an updated admin interface based on the
>> BaseCamp UI.
> That would be great!
> So far I've got only an approx. idea of "my" interface (discussing
> user tasks with client). ...
> BTW, the BaseCamp UI seems a bit too heavy (at least for my needs)
> - it loads almost 1mb for each couple of screens. Are you
> reproducing the whole thing (ajax etc) or just the main look/
Errm.. what the hell are you doing to BaseCamp to pull down 1mb? The
BaseCamp UI is pretty light - no images per se and pretty simple
the most I came up with was 78Kb. And BaseCamp is the new 'Outlook'
you know.. everyone's copying it :)