[personal profile] swaldman
Hi Styles people :-)

I've just finished working on Bug 1723 and, pending reviews etc, it will probably appear in a code push soon. It makes a couple of changes to how things in the TagDetails class behave, so I thought I should do a post here and warn you.

Firstly: The use_count variable currently gives the total number of posts on which a tag is used. This will change to the number of posts visible to the current user on which the tag is used. This fixes a privacy issue, whereby somebody without access could see how often the journal owner wrote about that tag in locked posts. Note that for performance reasons, the new value will sometimes be an approximation. It may be accurate or it may underestimate. It should never overestimate.

Secondly: There is a data structure called security_counts, which is not used by any of the DW official styles, and which I suspect nobody actually used because half of it didn't work. Here's how it will work in future:
  • security_counts{"public"} will give the number of public posts on which the tag is used.

  • security_counts{"protected"} will give the number of friends-locked (members-only for comms) posts on which the tag is used, if the current user has access to those posts. If not, it will be undefined.

  • security_counts{"private"} will give the number of private (admin-only for comms) posts on which the tag is used, if the current user has access to those posts. If not, it will be undefined.

  • EDIT TO ADD: security_counts{"group"} will give the number of posts on which the tag is used that are locked to access groups (also called access filters). This will only be visible to the journal owner (admin for comms). If the current user is no the journal owner, it will be undefined.

Note that security_counts{"group"}, which used to exist but frequently gave the wrong value, is deprecated. There is no way to provide this info for access filter groups without thrashing the database.

Also, security_counts{"friends"} is deprecated because it never worked anyway! It has been replaced by security_counts{"protected"}.

I hope that all makes sense; please ask questions if you have them.

EDIT: I realised that we can do security_counts{"group"} properly for journal owners, because we can assume that they can see all groups. There's still no way to work it out for other users without database-thrashing. Unlike before, for those who can see it it will now give the right number ;-)

stormy: βͺ ππŽπ“πˆπ‚π„ ❫ 𝑫𝑢 𝑡𝑢𝑻 𝑻𝑨𝑲𝑬 𝑴𝒀 𝑰π‘ͺ𝑢𝑡𝑺 ⊘ (Default)
[personal profile] stormy
Good morning, Styles team!

At 7am, I had an epiphany. The largest complaint we hear at Dreamwidth is that we don't have enough good layouts. Well, we've had much less time to create our layouts than the competition, but that's not the issue; The problem is that not enough people have come forward to say what they want and how they want it placed. It's not even a matter of colors or design as much as where elements are on the page that people can't seem to get around. Colors and customization are easy, but positioning the elements fluidly so that they'll work for multiple users, and appear roughly the same on any monitor is very difficult. It's an even larger task to do this so that you can support some of the customization options on Dreamwidth - how many columns, where to place the metadata, etc.

I can make something look pretty, but positioning the elements fluidly so that they'll work for most people and still look the same is very difficult for me personally. It's why I don't submit things to styles (especially since I'm a fixed width girl), not that I wouldn't like to help elsewhere.

Might I suggest an entry or community for user submitted "paint layers"? More information right this way and an example! )
aveleh: Close up picture of a vibrantly coloured lime (Default)
[personal profile] aveleh
We're still going through old comments to add bugs into the ticket tracker, but there will be some top-level posts in between working on replies. I promise someone will get to everyone :)

With the last code push, a new style "Transmogrified" is now live. This layout was designed by [livejournal.com profile] absolut for the LiveJournal Style Contest in 2005. Most of the legwork on getting it to work with core2 was done by [personal profile] dani_the_girl and [personal profile] draigwen, who have been working with [personal profile] afuna, [personal profile] av8rmike, [personal profile] jadelennox, [personal profile] liv and [personal profile] rich. This style has really gentle default colours, and is a great option to have. You can see it in action at [site community profile] dw_styles or Select it as your Journal Style.

With beta opening up, now's the ideal time to talk about more about "the styles overhaul." In order to ensure that Dreamwidth styles are more accessible, easier to write, and easier to update, a number of volunteers have been working together over the last few months to complete a significant overhaul of various styles and the core code that powers them. Until open-beta, our priority is working to ensure that core and individual styles are working as expected, and then after that, we'll be able to start adding new features. And, wow, are there ever a lot of features we're going to be able to add!

One of our goals is that users will never have to choose a style because of the functionality it offers. Instead, you can choose a style because you prefer the way that it lays out items on your journal. So, options like "put icons on the left side of each entry" would be a per-style option. But we think that options like "only display the mini-calendar on the Recent Items page" should be available on all styles, and style designers should never have to write new code to implement it.

The way we're accomplishing this is to remove these options from each individual style, make sure that the basics are working in each style, and then start adding awesome new features to core2. I know this means that things are a little sparse and frustrating during the beta process. But this is really going to help the long-term growth of the style-system and make it easier to update old styles and write new styles.

I also wanted to add a reminder that if you're moving S2 styles over from other LiveJournal-based sites, you probably want to use core1, because that version of core is (almost) the same and is more likely to produce expected results :)
dani_the_girl: (Default)
[personal profile] dani_the_girl
* Or header code or footer code....

And who can blame you! Fortunately, Core v2 is here to help :) Yes, you can now get a whole batch of juicy sidebar modules for free along with some EXTREMELY SHINY wizard options to go with them (and then you will bow down and kiss the ground under [personal profile] afunas feet). The process is simple, assuming you know the basics of what S2 is and what writing your own layout layer involves. If you do and you want to get in on the action, read on and I will explain it herein. )
aveleh: Close up picture of a vibrantly coloured lime (Default)
[personal profile] 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 [site community profile] 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, [personal profile] 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!

Notes on core2 functions and properties that have changed from one code release to the next )

Please keep your eye on [site community profile] 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.
aveleh: Close up picture of a vibrantly coloured lime (Default)
[personal profile] aveleh
Hey guys,

We have some really exciting changes coming up in the next few days. However, it's going to break the styles of some people who are using core2-based non-official layers. That means that those of you who liked being on the cutting edge and so fiddled with a style to make it work with core2 or made changes to the functions in a core2 style to make your own style, you may end up having problems using your style as expected, or even getting it to compile.

I know we've already changed the names of the module function twice, but we've done it again, this time in a way that makes it more flexible. I can promise that when you see the way that [personal profile] nova designed and [personal profile] afuna implemented the modules, you won't care that you need to make some more edits. The new module functionality is amazing. If you're not already using Negatives, switch to it and see the Modules in action.

Anyway, core2 is giant enough that we're wanting to remove the depreciated functions earlier rather than later, especially for things like the modules which are already confusing. So, if you're a non-official core2 style user, you probably need to:

  1. Do a find and replace to replace print_module_group_one() with print_module_group( "one" ), and the same for two and/or three and/or four.

  2. Do a find for any instances of print_linkbar and replace it with print_management_links for EntryLite (entries and comments), and with print_interaction_links for UserLite.

  3. Do a find for any instances of print_entry_poster. This may say something like $p->print_entry_poster($e). It should now be $e->print_poster().

  4. Do a find for lang_user_wrote. Think about replacing it with print_entry_poster.

  5. Bookmark this post so you can yell at me for not properly making sure we documented our overhaul.

We're going to be making a series of posts in the next couple of days talking about the overhaul and porting process, and better explaining how what we've done isn't just renaming a few functions, and how this is going to be really awesome for everyone in the long run. This is, of course, just in preparation of getting some good official documentation aimed for users of all levels and interest.

In the meantime, I'm working [personal profile] afuna, [personal profile] av8rmike, [personal profile] dani_the_girl, [personal profile] draigwen, [personal profile] jadelennox, [personal profile] liv, [personal profile] nova, [personal profile] rich, and [personal profile] ysobel as hard as possible, so please don't hesitate to give them love.
aveleh: Close up picture of a vibrantly coloured lime (Default)
[personal profile] aveleh
Hey guys, I'm just checking in. We've got a whole huge heap of changes getting made in this weekend, and there will be a series of posts to talk about them. In the meantime, here's some pointers as to where to get styles help:

If you are using Negatives and are having problems, that link is the best place to list them.

If you are using core2 and are having problems, the earlier post is a good place to leave a note.

Mark also committed a new style, Zesty. The styles team hasn't had a chance to look at it, and so it's not considered supported. If you're having problems with it, you can leave a comment here. Other users might have suggestions for how to resolve your problem, and if not, it's a central place to collect these issues for later investigation.
aveleh: Close up picture of a vibrantly coloured lime (Default)
[personal profile] aveleh
For the last few months, one of the quiet projects that has been going on is an overhaul of the styles system on Dreamwidth. The styles system for LiveJournal code is mostly very powerful, but there are a number of problems associated with it. Most of these problems can only be fixed by breaking things first, which is what we've been doing.

Somewhat technical ramblings: )

What all this means:

If you aren't using a customized style, you may have noticed that the ugly and plain style you've been forced to use has now been replaced with a... still ugly and plain style, but one that has more functionality. This is our first draft of core2, the underlying code that is used to power all the other styles that are coming your way. We aim to have a stable building block with which to build other styles; styles won't have to create a lot of functionality from scratch each time.

The draft you're using doesn't have any wizard functionality, so you can't add headers or change background colours or make any of a million tweaks that will be standard. There will be features that you don't use that are showing up, that later you'll be able to remove them. And things that are ugly. But you guys all know this is beta :) So, please, poke at it, poke at journals, poke at communities, poke at syndicated feeds. If you're on the beta team, please follow your usual bug reporting procedures as per [personal profile] domtheknight. If you're not, please contact me (I like IRC) or [staff profile] denise for further instruction regarding any problems you find.

Current known issues (more edited in as reported):

  • ugly

  • No wizard

  • CSS incomplete

  • HTML not validated on all views

  • Two "tags" listings in sidebar - this is because one is to display multi-level tags. Multi-level tags are a change in display, only. Use : as a separator between words in your tags to make use of this feature.

  • openID user URLs in the sidebar overlap with the rest of the page text. Have to decide whether to make really wide sidebars, or do something else with the usernames.

  • On the Reading page sidebar, usernames are printed for users posting in communities, but not for users printing in their own journal.

  • On the Reading page sidebar, usernames are printed for users posting in communities, but not the community name.

  • On communities that you can manage tags, the "Manage Tags" link under the "Tags" modules will not appear, as S2 has no way of knowing who can manage tags.

  • On the month view, entries that have links will not work as expected. Instead, the HTML in the subject should be stripped and printed plain, and then linked to the entry.

  • The Month module shouldn't be displayed when viewing an openid's reading page

  • Unclosed h3 tag on the Day Page

Some example things to be expected:

  • You should be able to perform the same "user interactions menu" options on any journal page as you can on the profile page. This means adding and/or modifying your circle relationships, posting to a journal, and tracking entries. If you see something different, report it. If the text describing the action is incorrect, report it.

  • There are two linkbars for working on your entries, one for "edit entry, edit tags, add to memories, track this" and one for "x comments, leave a comment". Each link should only display to a user who can do that specific action. If you see something different, report it. If the action is describing the action is incorrect, report it.

  • etc, etc


Dreamwidth Styles

Resources for creating layouts

August 2014

17 181920212223


RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Oct. 18th, 2017 12:48 pm
Powered by Dreamwidth Studios