Core2 Release Candidate!

[aveleh]

Mark just pushed a whole bunch of changes. So, some notes:

• A reminder: If you're planning on using any layers written for other LiveJournal-based sites, and you're not planning on converting it to use any of core2's awesome new functionality, you may find it easier to have it inherit from core1.


• There's a number of big changes to core2 and negatives, so if you've edited any core2 layers, your style may break. Bookmark the Select Journal Style page and dw_styles so that you can get yourself sorted.


• This version of core2 should be considered our release candidate. (Yay!) We don't expect to rename any more functions or properties (you have to stop somewhere, zorkian tells me). That is, we've moved from the "overhaul" stage, to the "patching" stage.


• This version of Negatives continued with the overhaul, so there's some funky CSS going on. We figured it was a good opportunity to get it out, and to get people working. If you notice something wrong, leave a comment, and we'll confirm and move it into our ticket tracker. If you know how to fix it, leave a patch! Either way, thank you!


• After the patching stage, there will be lots of opportunity to increase the functionality and options available. If you're a dev or a wanna-be-dev, now's a good time to get thinking!

• UserLite::print_linkbar() no longer exists. This has been replaced by UserLite::print_interaction_links()


• EntryLite::print_linkbar() no longer exists. This has been replaced by EntryLite::print_management_links()


• EntryLite::print_item_linkbar() no longer exists. This has been replaced by EntryLite::print_interaction_links()


• print_entry_poster(EntryLite e) no longer exists. Now implemented as EntryLite::print_poster()


• ReplyPage::print_comment has been added in order to implement ReplyPage::print_body in a more consistent manner.


• property string[] show_sidebar_group, property bool show_sidebar_recent, property bool show_sidebar_reading, property bool show_sidebar_entry, and property bool show_sidebar_others have all been removed. Ticket 836 proposes that it is instead implemented for individual modules.


• property string[][] module_group_one, property string[][] module_group_two, property string[][] module_group_three, property string[][] module_group_four,Page::print_module_group_one, Page::print_module_group_two, Page::print_module_group_three, and Page::print_module_group_four removed. have been removed. These were replaced by various new properties and functions for module implementation. (Tutorial coming soon!)


• function print_custom_control_strip_css() has been removed a little early because of Ticket 630. Please let me know if causes any problems; I've already opened up a ticket to investigate.

Lazy diff format display of renamed properties:
-property Color entry_link_color { des = "Entry link color"; }
-property Color entry_link_color_hover { des = "Entry link color on hover"; }
-property Color entry_link_color_visited { des = "Entry link color when visited"; }
-property Color entry_border { des = "Color of entry border and comment background"; }
-property Color entry_background { des = "Entry background color"; }
-property Color comments_link_color { des="Color of comment section links and text"; }
-property Color comments_link_color_hover { des="Color of comment section links when hovered"; }
-property Color metadata_color { des= "Color of metadata (mood/music) text"; }

+property Color color_entry_link { des = "Entry link color"; }
+property Color color_entry_link_active { des = "Entry active link color"; }
+property Color color_entry_link_hover { des = "Entry hover link color"; }
+property Color color_entry_link_visited { des = "Entry visited link color"; }
+property Color color_entry_border { des = "Entry border color"; }
+property Color color_entry_background { des = "Entry background color"; }
+property Color color_entry_text { des = "Entry foreground color"; }
+property Color color_entry_title { des = "Entry title color"; }
+property Color color_entry_interaction_links { des = "Color of interaction links and text"; }

+property Color color_page_background { des = "Page background color"; }
+property Color color_page_text { des = "Page foreground/text color"; }
+property Color color_page_link { des = "Page link color"; }
+property Color color_page_link_active { des = "Page active link color"; }
+property Color color_page_link_hover { des = "Page hover link color"; }
+property Color color_page_link_visited { des = "Page visited link color"; }
+property Color color_page_title { des = "Page title color"; }
+
+property Color color_module_background { des = "Module background color"; }
+property Color color_module_text { des = "Module foreground color"; }
+property Color color_module_border { des = "Module border color"; }
+property Color color_module_link { des = "Module link color"; }
+property Color color_module_link_active { des = "Module active link color"; }
+property Color color_module_link_hover { des = "Module hover link color"; }
+property Color color_module_link_visited { des = "Module visited link color"; }
+property Color color_module_title { des = "Module title color"; }



Please keep your eye on dw_styles for more posts, including use-questions, tutorials, and calls for all sorts of volunteers. We want your journals to be easy to make pretty and functional.

Comments

[aveleh]

I would definitely rather that people ask questions.

Because of changes to core2, putting those links onto two lines was an easy fix for how squished they were looking. So, it is supposed to have happened. However, it's on my list of requests for our CSS gurus to make it look better.

And, yes, I'm so excited too!