I'm thinking this ought to be split into 2 posts. One gives an in depth list of all the changes and defines what a bug fix, added option, and code optimization is, while the other does an FAQ on the new code. I've added a list of all the official tutorials (ie ones tagged as !tutorial) and noted which have been integrated, which ones need to be changed, and which are still relevant. I figure that list ought to go in an lj-cut.
Sounds good. I'm assuming the split will be where it says "see below", so that it will say "see [this entry]", instead? :).
Splitting it up into two entries should also make it easier to go indepth into certain features when necessary, without now having to worry about making the entry too long.
You did an awesome job of organizing this. I can barely recognize it, it's improved so much!
Have only had a chance to read the top part, and haven't seen if you've added anything to the list at the bottom, but wow. Just... wow!
Yeah, the "see below" part was going to link to the FAQ post. I've changed that now so that there's an lj-cut (eventually it will be a fake lj-cut leading to the in depth post).
I was lazy earlier and didn't want to go through the 2nd half since it's a pain in the butt to check and see if you've missed anything. :P I did elaborate some on print_entry's modularization and added bullets for known issues.
Right now I'm going through the 2nd half more, but I think I'm going to assume you've gotten everything unless cyrnelle says otherwise because I'm still too lazy to check over everything. :P
I think the in-depth post is still going to be really long, but at least people will have a shorter one they can dig through for answers.
Re: One last thing...s2flexisquaredSeptember 6 2005, 04:39:41 UTC
It's already in the current code, but some of the people who did overrides early still haven't updated their print_entry code to have that, so better to mention it again methinks :)
Comments 38
Reply
Splitting it up into two entries should also make it easier to go indepth into certain features when necessary, without now having to worry about making the entry too long.
You did an awesome job of organizing this. I can barely recognize it, it's improved so much!
Have only had a chance to read the top part, and haven't seen if you've added anything to the list at the bottom, but wow. Just... wow!
Reply
I was lazy earlier and didn't want to go through the 2nd half since it's a pain in the butt to check and see if you've missed anything. :P I did elaborate some on print_entry's modularization and added bullets for known issues.
Right now I'm going through the 2nd half more, but I think I'm going to assume you've gotten everything unless cyrnelle says otherwise because I'm still too lazy to check over everything. :P
I think the in-depth post is still going to be really long, but at least people will have a shorter one they can dig through for answers.
Reply
By the way! I can't remember clearly but in the old code, the commentbar doesn't show up in the Entry/comments page?
Reply
entry wrapped in entry_text div
Wasn't that already in the current code? Isn't the entry2 wrapper the new one?
Reply
Reply
Reply
Reply
Feature may still be removed
Reply
Reply
Leave a comment