On Feb 6, 2009, at 9:35 AM, Jeremy Slade wrote:
I've been using laconica for a couple weeks now, and it's been
working well -- props to the team.
My instance is deployed in a corporate internet, so there are a
number of features that simply don't make sense (SMS, twitter
integration). It's easiest to deal with just by hacking references
to those things out of the rendered html.
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. Any
thought been given to making laconica follow more of an MVC
architecture? I'm a PHP noob myself, but I've seen that work very
well for other frameworks (rails, catalyst ...)
Laconica does have a sort of MVC-ish framework that it uses. It has
templating functions that generate the code in actions (views) and
these action classes all reside under $LACONICA_ROOT/actions.
One much easier way to remove the rendering of things you don't want
on screen is to define your own template and declare display:none; as
a CSS rule that targets those elements.
If that doesn't let you get rid of the things you want, you probably
should set up a "vendor branch" of Laconica and keep your changes in
your own branch. Merge new official versions of Laconica into your own
changed branch. This is what I do for projects I need to segregate in
that way, and it works a treat. (Especially with git.)
It's also fair to tell me this is a pre-1.0 version, so I just have
to expect the code to be very unstable.
Regards,
Jeremy
I *think* I recall chatter here a little earlier about providing more
templating functionality, but I can't remember off the top of my head.
I'm just starting to get familiar with the sources myself, and I would
also like to see greater control in templates.
Hope this helps,
-Meitar Moscovitz
Personal: http://maymay.net
Professional: http://MeitarMoscovitz.com
_______________________________________________
Laconica-dev mailing list
[email protected]
http://mail.laconi.ca/mailman/listinfo/laconica-dev
