Jeremy Slade wrote:
Problem is, I first deployed on 0.6.4.3, and today I'm moving to
0.7.0, and I have to do the same changes all over again.
Sorry to hear about your trouble maintaining your private patchset.
That's one of the reasons that many organizations contribute their work
to the upstream distribution: you save a lot of time not effing around
with your private patchsets. And also a reason people make bug reports:
things get fixed in upstream, and then you don't have to maintain your
own silly work-arounds.
The other reason, of course, is because it's how decent people act.
Any thought been given to making laconica follow more of an MVC
architecture?
It follows an MVC architecture right now.
If your question is, "Are you going to use templates in the future?" the
answer is an almost definite no. Templating engines are slow and
difficult and 95% of the things people want to do with templates (like,
say, adding links to the page or adding scripts to the <head> area) are
better handled with configuration variables and/or a hooks system and
"lite" theming with CSS. See http://laconi.ca/trac/ticket/46 .
Clearly, the things you want to do (dike out SMS and Twitter
integration) should just be handled by config variables. It would be
downright stupid if our answer to the question, "How do I disable SMS
integration?" was, "Go to template 'connectmenu.templ' and comment out
line 347, then go to template 'smssettings.templ' and comment out lines
12-44 and change line 68 to say 'IM and Twitter' instead of 'IM, Twitter
and SMS'..." The answer "In config.php, set $config['sms']['enabled'] =
false" is much, much better.
I've set up tickets for your two problems (#1147 and #1148), and I'd
really appreciate it if you could report any other things you've had to
customize, so all Laconica admins can benefit from your experience.
-Evan
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
