Log in

No account? Create an account
March 7th, 2004 - LiveJournal Development — LiveJournal [entries|archive|friends|userinfo]
LiveJournal Development

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

March 7th, 2004

Changing coding style on .bml pages. [Mar. 7th, 2004|12:09 pm]
LiveJournal Development


After posting http://www.livejournal.com/community/lj_dev/620282.html I got no response, and I guess that because I really didn't ask a question.

If you go back and read it I was talking about what seems like old vs. new coding pratices for .bml pages. I've found instances on my site in particular that variables weren't carying from the BODY=> are to other areas (including crumbs). I've foudn that if pages are coded in such a way that there is one large <?_code _code?> section before the <?page page?> section then all the variables carry across with no problem.

What I am proposing is that me (or someone else) go through all of the .bml files and convert them to use this method of coding. I have already started doing this on my LJ site and it wouldnt be a problem for me to submit patches to zilla if its decided that this will be used. Otherwise I'll just keep this stuff to myself.

I can't see how this will hurt, and it seems to me like a more efficient way of parsing the files, though I haven't really looked into the bml engine to see the internals.


Yeah, I guess I kinda suck at asking questions. Basically, if the work is done and submitted, will it be used?
link3 comments|post comment

Comment Tag Options [Mar. 7th, 2004|01:02 pm]
LiveJournal Development


First off, hello to all. I'm a new member to this community. That said, I've been playing with customization options, and have been thinking about the 'leave a comment' area.

Currently, it can be set to say something for a single comment, and something else for >1 comments. My question is, why don't we alter this a bit?

The ability to set something along the lines of:

1 comment // 2 comments // 3 boring comments // 4 more comments // # comments

...and so on could be a vaguely interesting addition. I imagine a reasonable limit would need to be set on how many custom comment definitions you could have, to prevent every user from having about a million, and eating up seven hard drives. But, the overall idea seems like a decent one.

Another way to go about it could be ranges, so that we have:

<1-10> comments // <11-20> complaints // <21-30> flames // # responses

Where # could either be considered any number greater than the greatest range set, or any number not within set ranges, so you could set <1-9> and <11-20>, and # would superimpose itself over comment 10, since it wasn't specified.

It's just an idea, anyway. I imagine it might be slightly difficult to implement, but I think it'd be enjoyed overall by users if it were. (Especially those with nothing better to do.)

link7 comments|post comment

[ viewing | March 7th, 2004 ]
[ go | Previous Day|Next Day ]