Question thread #11

[pauamma]

It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer.

Comments

[kaberett]

I am having Feelings about Killing BML With Fire, but suspect that is better suited to ferreting out a recent pull request on the topic, observing what has been done, and writing the detailed guidance myself...

[swaldman]

There is a wiki article about how to do this somewhere. Short version: You have to learn about the new "controller" system, and learn the basics of TT.
(the best way to learn this might be to work through replacing a straightforward BML page though)

The complication is that so many of the "BML" pages on the site are actually mostly perl, you probably have to have a modest knowledge of perl as well to replicate the functionality.

EDIT: er, that was an entirely unhelpful answer. I apologise :-(

[kaberett]

At least one of the wiki pages was in fact written at my specific request ;) Nonetheless, I'd really like to have Someone Around so's I can be all "AM I DOING IT HORRIBLY WRONG" at them while I'm working through getting started.

Un/fortunately (?), it's actually dropped off the bottom of the do-soon pile, so it will probably wait :-)

[swaldman]

:-)
Dre is the person for all things related to controllers and TT, I think...but with that said, I've made a couple of TT pages and I can probably remember enough to help if I'm around.

One thing that I would say is "Don't try to change a page over if the perl on the page goes over your head to start with". Because so many of the "bml" pages actually have logic in them, and you need to replicate that functionality...

[cadenzamuse]

Can you clarify the guidelins from To Answer, Or Not To Answer? Are you suggesting a potential answerer hang back and see if someone else answers, or preface an uncertain answer with a clear label that it may be wrong, or something else entirely?

[pauamma]

I'd recommend the approach in either http://perlmonks.org/?node_id=917528 or http://perlmonks.org/?node_id=917529, that is "go ahead and answer", whether right ahead or after a bit. (Waiting for a bit may deprive you of a chance to answer yourself, but it also helps ensure that someone who doesn't get a quick answer has a better chance of getting an answer at all.)

But if you're more comfortable with hanging back and reading the discussion, or perhaps asking follow-up questions if you don't understand the answer or think the answerer misunderstood the question, that's fine too.

[cadenzamuse]

Thank you for the clarification.

[pauamma]

Also, hi! Nice to see you here.