text:
Wikidata:UI redesign input

From Wikidata
Jump to: navigation, search

The development team is working on a redesign of the user interface of Wikidata. This page is for collecting input on the new design.

Previous input has been archived at Wikidata:UI redesign input/Archive and Wikidata:UI redesign input/Archive2.

Wikidata UI redesign part 3.png Wikidata UI redesign part 4.png

General goals we try to achieve:

  • make the UI easier to scan and understand
  • make the UI cleaner
  • make the UI more friendly and inviting
  • make it easier to find relevant information
  • remove technical jargon
  • rethink individual pieces we've added over the course of the past two years to see how they make sense in the more finished state we are in now

  • Still a lot of whitespace that makes it look "hanging", somehow
  • References take up an entire line per statement. Could that move to float right in the same row as the statement value? Could expand into its own row for editing.
  • Qualifier properties have the same background as the property headers. That is consistent, but puts a lot of visual emphasis on the qualifiers.
  • Just a thought: Qualifier statements could be "inline", so that two/three short ones are on the same line? Check out the Wikidata game for examples.
  • The edit button/dropdown in the headings - is that always there? Might be less distracting if it only appears on hovering over the heading.
  • The blue is too strong!

So much from me... --Magnus Manske (talk) 16:04, 24 June 2014 (UTC)

Thanks! re whitespace: Will hopefully be mitigated with more widgets for things like geocoordinate added. Emphasis on qualifiers is something we are trying to fix still but it is proving to be tricky :/ Ideas? Doing them inline could work but it feels to me that'll make it harder to scan. I have that issue with the Game sometimes. Button in the heading: Something we'll have to play with when implementing. I want it to be clear that it can be edited. --Lydia Pintscher (WMDE) (talk) 13:06, 27 June 2014 (UTC)

Feedback by Danwe[edit]

Updated version of my comments on 1st version:

Overall, I quite like Henning's UI redesign proposal. I especially like:

  • A lot of whitespace that makes it look well structured, somehow. (Added)
  • How property IDs have that blue background (consistently) and are used on top of the statement group rather than as in two columns as with the current UI.
  • That the qualifiers values are not aligned. Gives more space to the text.
  • The information on the right side. And in a mobile version where we have less space in width we just move it over to the left.
  • The design of the item's head. Using an image there and the formatting. Would put a little more space between aliases and description though. Also, the description text could flow into/over the "action column" in this design in my opinion. Would use space a little better.
  • Language links are pretty compact now. Good! Don't care too much about them anyhow when viewing an item.

Things I am not sure about:

  • The design now uses link-buttons but also icons. E.g. "click to add one" instead of an icon". And then there is "Add statement" which is formatted in quite a different way again. The design also says goodbye to the idea of the action column it seems.
    Question: What's the reasoning behind those two points?
    (DONE in 2nd mocks. Done by removing link-buttons)
  • Why does the edit view mock only show edit boxes for descriptions? What about labels and aliases? Also, I had hoped for something more intuitive here regarding editing the values in other languages on the same page. And, could perhaps use a little more paddings in the edit view, especially for column headings. (Added)

What I'd like to see improved:

  • Jared's presentation of item reference labels merged into Hennings design. Displaying an image, label and ID and using a lot of space for that.
  • Button for displaying all language links. Just showing a few on the right side is good I think. But what if I want to see all of them? (DONE in 2nd mocks Though, the link is formatted and placed inconsistently compared to the "show all links" one in the "related items" box.)
  • Those x more value(s) link-buttons should be smaller and formatted like the x references ones. (Added)
  • Things I'd like to see reversed since they've been better in the 1st mocks compared to 2nd one: (Added)
    • The darker blue in the 2nd mockups compared to the 1st ones. It looks too hard. Someone said the contrast wasn't big enough - might be true, but there are more elegant ways to increase contrast! E.g. put a shadow or a very thin darker outline around the white texts on the blue background.
    • The gray frames on the left of each statement. Adds more clarity to the design.
    • Language links to articles that are not featured articles now have an "empty" star. A little confusing and not necessary. Also, if there are more/other badges, having an "empty" one for each of them might be too much and will look too crowded.
--Danwe (talk) 17:13, 24 June 2014 (UTC)
Does this mean you can edit the label, the aliases and the description all in one edit? That would be a big improvement over the way it is now. Jane023 (talk) 17:18, 24 June 2014 (UTC)
We're trying to achieve that, yes. --Lydia Pintscher (WMDE) (talk) 13:12, 27 June 2014 (UTC)
I have no strong opinion on whether editing label, aliases and description at the same time is desirable or not. In any case though, they should only be shown for edit in the current language when being edited via an items head. Displaying them in several languages as in the mock is too much for the user in my opinion. Editing in other languages should still be achieved in a separate widget or in a more intuitive way than always putting it on the user's screen as soon as clicking edit on an item's head. --Danwe (talk) 09:27, 7 July 2014 (UTC)
Thanks! re showing the IDs of all linked items: That's something I will not ok. We have to combat information overflow. This would increase it considerably for little gain. The gray lines at the side of each statement have also been removed to reduce clutter. Fair enough on the empty stars. --Lydia Pintscher (WMDE) (talk) 13:12, 27 June 2014 (UTC)
For long statements the gray lines could still benefit clarity. One has to see. Ok, showing the IDs might be too much, still like the idea of showing the pictures together with the entity's label though. --Danwe (talk) 09:39, 7 July 2014 (UTC)
I think it is easier to grasp a UI where you do in-place editing and then save the whole thing. It will also be a lot faster than the very tight iterative edit-save sequence used now. Jeblad (talk) 05:37, 12 November 2014 (UTC)

Feedback by Filceolaire (talk)[edit]

I think all the comments I made on the previous version apply to this version too . :( Filceolaire (talk) 19:03, 24 June 2014 (UTC)

I'd like to comment on some of your comments, now I am not sure whether to do it here or in the Archive. Moving all the comments to an archive doesn't seem like the smartest idea to me anyhow since lots of them are still very valid :-/
A claim should be one line, not two. "<Property>:<Value> 0 refs [edit]". Clicking on 'edit' should reveal references and options to add qualifiers. - I think that's possible for very small statements, not if there are any qualifiers though. I'd like to see this formatting for small Statements with only one value within a statement group with only one statement though. E.g. gender:male in one line since there is enough space and it will be comprehensive enough this way. [Got to go, will comment more on your comments later.]
--Danwe (talk) 00:18, 25 June 2014 (UTC)
Agree, there are a lot of important stuff in the archives. Jeblad (talk) 05:38, 12 November 2014 (UTC)

Feedback by Nicereddy[edit]

I like the darker color being used here. It's a simple change, but makes everything look much better, I can't exactly nail down why. Other than that, most of my prior issues still exist. Gradients, serif fonts, and the dropdown arrow, among some other things.

I personally prefer Jared Zimmerman's mockup, as it has a more cohesive design. Less variation in colors, less clutter, and generally a better flow to the data. The thing about yours is that there's such a huge amount of chrome. While that's not a bad thing, the section headers, blocks of color, lines, gradients, and font sizes used to differentiate different sections of the interface makes everything seem broken up and disconnected. He uses font weights and shades of gray to portray the importance of each bit of the interface, and I think that's a better solution than various headers and things.

However, he didn't really tackle the editing bit of the interface, which is obviously fairly important to Wikidata. Your current design is in a grid pattern, and I'm not sure that's how we should be tackling it. Right now you're very limited in the space given to each editable item, which is my biggest concern. Personally, I think the "x-axis" (Language, label, Aliases, Description) should be removed. Instead, each language would be its own header (like "official website" is now) with "Label: Berlin" in the next line, "Aliases: Stadt Berlin" following it in the next line, etc. Each separate editable piece should be given its own line, since vertical space is often more abundant than horizontal space. Especially when you have columns, as you do now.

For a visual:

Deutsch (de)

  • Label: Berlin
  • Aliases: Stadt Berlin
  • Description: Hauptstadt von Deutschland

English (en)

  • Label: Berlin
  • Aliases: Berlin, Germany
  • Description: A place in Germany

--Nicereddy (talk) 22:34, 24 June 2014 (UTC)

Yes the editing part is the biggest issue. However there are also some fundamental issues with what we can actually do in Jared's design and in terms of understanding the purpose of individual pieces. About the header: Keep in mind that we have several hundred languages. People are already complaining now about the size of the "in other languages" box in the current interface. --Lydia Pintscher (WMDE) (talk) 13:17, 27 June 2014 (UTC)
@Lydia Pintscher (WMDE): Thanks for the response. As to the languages, I'm assuming you mean languages in the editable table? While I agree that with more than 200 languages it would get incredibly large incredibly quickly, I would think a single editor can only be fluent in, at most, five of those languages. Therefore, anything more than those five languages relevant to that specific user would be unnecessary. A simple settings menu to enable only a specific set of languages for the user would fix this issue, I'd think? And if someone wanted to edit a specific language not included in their defaults, a simple spinner could be implemented which would temporarily include the data from said language.
Of course, if my assumption is wrong then I've just made an entirely irrelevant comment, so please correct me if I'm mistaken. --Nicereddy (talk) 21:38, 27 June 2014 (UTC)

Comment by GZWDer[edit]

  1. At the bottom of "Sitelinks in Wikipedia", a new "Add new sitelink" link should be shown at the right of "Show all".
  2. If only several sitelinks are shown, this list of shown sitelinks should be based on geo-IP, previous choices and browser settings of the current user, like what have done at mw:Universal Language Selector/Design/Interlanguage links. This will replace the Main language first gadget.

--GZWDer (talk) 05:21, 25 June 2014 (UTC)

Yeah we're trying to see if we can use the same mechanism as the collapsed language links being developed for Wikipedia. A lot of thought has gone into that so we should reuse that if possible. --Lydia Pintscher (WMDE) (talk) 13:19, 27 June 2014 (UTC)

Feedback by Micru[edit]

Compact design

There is one point that has been asked from the very beginning: more compact statements (vertically). Neither this design, nor the old one addresses that. Yes, white space is good, but the mockup seems to be for a very small screen, can you imagine how this design looks in a 19 inches screen? For the eyes it will be like travelling through the interplanetary void. On the alternative mockup on the right you can see another way of sorting the statements as a grid. More compact, less scrolling, and suitable both for tablet and for pc screens. The gain it doesn't seem big, but if you consider a wide screen, the vertical space recovered is much more.

It is also hard to understand why so much prominence to the comments? There are not that many, and when there is one its relevance fades off with time. Better to show how many comments there are, and when was the last one, or at least show it only if it hasn't been displayed before, not always.

And the labels should be statements. Perhaps I should change my signature to "Labelia delenda est" :P --Micru (talk) 07:40, 25 June 2014 (UTC)

About the whitespace on big screens: Yeah what we could do is float the statements into two or more columns there for example. About the comments: My thinking is to only show it when there are current comments. --Lydia Pintscher (WMDE) (talk) 13:22, 27 June 2014 (UTC)
Consider using columns instead of floating, it gives a more predictable layout. Unfortunately columns give a layout the user does not expect, so it must be tested. You change your expectations through learning, but you can't do anything with whether it is possible to predict something. What is more important; expectations or predictability.
Note that columns tend to break inside items, which should be possible to stop according to W3 but it happens in most browsers anyhow, and that will make the layout less usable for the time being. Jeblad (talk) 05:28, 12 November 2014 (UTC)

Feedback by lbenedix[edit]

  • the properties are highlighted, not the more important values
  • the items in the Identifier box and Wikipedia link box should be aligned
  • the contrast is very low in the "Berlin, Germany" line

Is there a good reason for:

  • the blue boxes?
  • the gradient in the boxes on the right?
  • How do you count the number of discussion topics?
    • Why not integrating this number in the discussion tab on the top?
    • Are there so many discussions on wikidata items, that a so prominent discussion box is appropriate?

general notes[edit]

Maybe you should consider the the theory of data-ink-ratio: "A large share of ink on a graphic should present data-information, the ink changing as the data change. Data-ink is the non-erasable core of a graphic, the non-redundant ink arranged in response to variation in the numbers represented."

Here are two blog posts you could have a look at:

Already answered that on the mailing list :) --Lydia Pintscher (WMDE) (talk) 13:23, 27 June 2014 (UTC)
Please add links to the mailing list if there exist an archive. Jeblad (talk) 02:20, 23 November 2014 (UTC)

Supplementary feedback from Sweet kate[edit]

I share all of @lbenedix:'s questions and echo @Jeblad:'s request. I just waded through months of archived discussion around this UI redesign. As a web-designer-by-trade myself who can bring fresh eyes to the mock-ups above, I'm concerned that some of the choices don't reflect current UI best practices/sensibilities. For instance, I initially thought all the blue boxes were showing highlighted-in-the-browser text, like when you accidentally click and drag across an entire webpage. I had to stop and really look closely to realize it was an intentional design choice. That sort of un-clarity is a basic usability problem. Are @Jaredzimmerman (WMF): and @Lydia Pintscher (WMDE): working together on this? Can other voices chime in? Sweet kate (talk) 16:52, 26 November 2014 (UTC)

I share the concern that this looks a lot like accidental highlight. Jeblad (talk) 10:46, 27 November 2014 (UTC)

My thoughts[edit]

  1. "Linked to by" in previous version would have been useful, "Related items" not so much...
  2. grouping/seperation of values and qualifiers much cleaner and therefore easier to read
  3. generally looks cleaner than previous version
  4. I'd still like to see vertical alignment, makes it easier to get an overview and generally makes it easier to read this kind of data
  5. I like that in the wikilinks the stars are always shown, gives a more consistent look
  6. still far too much/too prominent highlighting that distracts from the content, especially for the qualifiers (I know that you want to bring some colour into the design, to make the site look less grey. And while I generally agree with this, I really don't think that this kind of highlighting is the right way to achieve this.)
  7. not sure if discussion on the content page is needed/useful
  8. don't know how well this multicoulumn design works on very small screens (mobile, small tablets, ...)
  9. I do like that the values of a statement are all on seperate lines, nesting them horizontally, like others have suggested, could make it quite cluttered and harder to read
  10. "filter statements by property" could come in handy on larger items

 – The preceding unsigned comment was added by 2A01:2A8:8401:D701:8876:7293:65C0:86B8 (talk • contribs).

Thanks! re your first point: Hmm it's the exact same thing only with a different heading that doesn't expose implementation details. re highlight: we're trying to improve that but not easy while staying consistent :/ On smaller screens we could just float the sidebar to the bottom. You're the first one who seems to have noticed the filter bar ;-) --Lydia Pintscher (WMDE) (talk) 13:26, 27 June 2014 (UTC)
Ok, since in this mockup only other capitals are shown in the "related items" section, I assumed that it was now showing "similar" items or something like that instead, my mistake... Agree to floating sidebar to bottom on small screens, also +1 for floating the statements into two or more columns (entire statements, not values or parts of statements!) on large screens like you suggested above to avoid excessive whitespace--2A01:2A8:8300:3A01:448E:1C8C:28F:59E5 14:04, 27 June 2014 (UTC)

Feedback by Holger1959[edit]

  1. the "Commons (category)" widget should be in the same column like other Wikimedia projects; please also remember that category and gallery links are possible for Commons (we even have some items where a Commons gallery but no category exists; maybe better remove "category" from the widget's name?)
  2. the "Label", "Aliases" and "Description" areas definitely need more space I think, because there are items with rather long names, and also languages with rather long words which don't allow easy line breaks; maybe make the area for the core information (label/aliases/description/image) full width, and only use two columns for the rest below?
  3. what about the images, will you crop any given image to a square one by default (displaying only the centre part), or what will happen when portrait or landscape format images are used? i think most images for geographical items are of landscape format, and portrait format is more common eg. for people or buildings. Really square images are rare.
  4. the "Discussions" widget should only give last edit date and maybe the username of the last comment, but no content excerpts nor headings (there are always cases where that would mean displaying unwanted offtopic or "angry stuff" on the item's page); personally i think such a widget is not really needed (we still have the standard discussion tab)
  5. i would really like to see mockups for real examples with full statements (not only for a shortened "Berlin" item), let's take lopado temacho selacho galeo kranio leipsano drim hypo trimmato silphio parao melito katakechy meno kichl epi kossypho phatto perister alektryon opte kephallio kigklo peleio lagoio siraio baphe tragano pterygon (Q101) and Taumatawhakatangihangakoauauotamateapokaiwhenuakitanatahu (Q791)

Holger1959 (talk) 19:42, 27 June 2014 (UTC)

+1 for point 4. Also important to note is that, in many (most?) cases, any given comment will not be in a language that the reader understands. --Yair rand (talk) 05:50, 3 July 2014 (UTC)

by Brya[edit]

The one good thing I notice about the design is that the values for the statements are below the statements (rather than besides the statements); this makes it unnecessary to scroll the screen setting until the field for values becomes visible.

What I am really missing is to have the links to the Wikipedia's (and other projects) at the extreme left (below the Tools). On all Wikimedia projects the iw-links are at the extreme left, so it would be really convenient to have them there at Wikidata also. - Brya (talk) 07:25, 29 June 2014 (UTC)

Feedback by Jklamo[edit]

  • heading box - neutral, picture looks nice, but will decrease loading speed
  • property boxes - neutral, should be more compact; collapsability - positive, should be also possible to collapse each ranks of values
  • related items, discussion - negative, redundant, just waste of space
  • identifiers - positive
  • wikilinks - positive, hope that there will be place for "transliteration gadget"
  • design - i do not care (as long as it alter functionality)

Overall good impression, hope that there will be as much customizability for users (placement of boxes) as possible. --Jklamo (talk) 12:01, 3 July 2014 (UTC)

  • The sources statement should be red for "0 sources"
  • "Start date" and "end date" or qualifiers in general should not be in blue boxes (too much color)
  • The "preferred value" doesn't really stick out. Reasonator is currently doing a better job at this by making the preferred statement bold and larger print.
  • For geographic objects the geographic coordinates should get a more prominent spot in the interface. -Tobias1984 (talk) 12:25, 4 July 2014 (UTC)

Comments on UI functions[edit]

I am not here to comment on the redesign as many interesting ideas have been raised. In my opinion, 3 ui need to be implemented just as Wikipedias do.

  • One for reading the article : the new UI could then be use for this purpose and not update available. This has several advantages : only relevant information will be displayed and "update wigets will disappear" => the ui will then be lighter. Ids, links, sources should not appear here !
  • One for modifications by unexperimented users : that is what I would used the current ui redesign for.
  • One for advanced users : the one that is currently available that is not so ugly as we can imagine, which I would call "Raw UI"

This is just a suggestion and maybe too late to be implemented but that is how I would have seen a perfect Wikidata UI ( suitable for me ! !-). -Thieol (talk) 23:56, 6 July 2014 (UTC)

Comment on order and lists of works[edit]

Looks like a great improvent. A bit irritating is the order of the topics. "Related items" for examples should move to the bottom (like "see also" in enWP). Are there any specific plans or ideas how to present lists of works? (See: meta:Talk:Reasonator) --Kolja21 (talk) 02:04, 7 July 2014 (UTC)

"Related items" looks like crap. Of what kind is the relation? Lydia Pintscher is also related to Berlin, maybe she will be shown in the next mock-up? Andrea Shan (talk) 05:03, 18 November 2014 (UTC)
Please keep your feedback constructive. We managed this pretty well on Wikidata so far. What exactly would be shown there is still up for testing/discussion. I had in mind to show the most linked other items that link to this item. Other things are certainly possible. --Lydia Pintscher (WMDE) (talk) 11:44, 18 November 2014 (UTC)
"most linked other items that link to this item" - then show that. "Related items" does not reveal that. Label any content properly and link with definitions. E.g. currently "statements" is not linked, but could be linked to the definition in the glossary. Andrea Shan (talk) 07:28, 19 November 2014 (UTC)
The plan is for these boxes to be movable. Still figuring out how to handle this with caching and all. And I am definitely not set on having it at the top. It'll not be there in the beginning. Same for discussions. Can you elaborate on lists of work please? --Lydia Pintscher (WMDE) (talk) 11:44, 18 November 2014 (UTC)

I overheard that there were already some intermediate changes to the UI to reach some target... I had no idea work on this had started and I don't see anything, can someone point to a place where there are updates on what was done? A bugzilla tracking bug or other search would be fine.

I'd also like to understand what the target is: #Mockups are just mockups, aren't they? And they are 3 months old. A summary of the conclusions would be useful, either on this page or on Wikidata:Development plan. --Nemo 06:55, 6 October 2014 (UTC)

The changes were mostly "under the hood" preparing/refactoring the code architecture for the visual changes that are planned. Visible changes were the section-edit mode for sitelinks and for the term/language-box. I've now added the relevant bugs as blockers to the UI-Redesign bug. You can see a list of the tasks here. Tobias Gritschacher (WMDE) (talk) 08:35, 6 October 2014 (UTC)
Thank you! The tracking bug is very useful. --Nemo 22:04, 12 October 2014 (UTC)

Authority Control & ID Numbers[edit]

My concern is about the growing number of different ID`s. There are thousands of databases out there and the number of properties will be growing and growing. I took the time and printed the whole list Wikidata:List of properties/all in one table, I marked all the ID`s and found about 500 ID´s or authority controll numbers. The IDs are more than 30% of all the properties. I see also a problem in the evaulation process: Someone has to make a proposal, the proposal must be discussed among people who do their best, but do not realy know, what they talking about, and after some amout of time the property is created. I´dlike to handle the whole thing quite differently:

  1. Give the whole bunch of Id´s and numbers an own section named as above
  2. Change the handling of Id´s. In my opinion we do not need properties to handle the Id's. This makes the whole thing bulky and needs a lot of overhead.
  3. Just take the item of the database and link it to the value and make sure there is also a possibility to link to Websites.
  4. Database Id´s usualy don´t need qualifiers or sources, as all thats necessary is stored in the database item.
  5. If a database has several different ID`s to offer, there must be a possibility to link the same item several times but give it different labels if necessary.
  6. In order to maintain some control over the databases, they need their own item and som notability, lets say articles in two different languages about the databases.
  7. Delete all the properties of ID`s after migrating it to storage with item and values.
  8. Give it an automated order according to the alphabet.
  9. Generate a warning is someone tries to store the same databases or values twice.
  10. Allow every notable library cataloge to store its shelfnumbers to literary works. We soon will have millions of bot generated edition items we can link to as sources + we create a universal library.catalogue, something I´ve been dreaming all my live.
  11. Let the ontology with all the properties, links, sources and qualifiers take place in a different section, not disturbed by ID´s.
  12. Make the whole list collapsible for more overview (Opt in).
  13. If there is no way around, just make one property named "Authority Control & ID Numbers" and link all the different databases as qualifiers to this one property with database item and ID as pair of item and values.

--Giftzwerg 88 (talk) 16:13, 25 October 2014 (UTC)

Imho there is a missunderstanding in the meaning of authority control. There is no 1:1 relation. Think for example of pseudonyms or companies that change their name or owner. #4: "Database Id´s usualy don´t need qualifiers or sources?" Of cause they do! Think of all the numbers imported by bot from VIAF: They are often outdated or false. So I need to know: 1) from what source the ID was taken and 2) when was the number looked up. Databases are not like tombstones: Numbers change, files getting renamed, merged or separated etc. --Kolja21 (talk) 17:05, 25 October 2014 (UTC)

I mean If you want to know the VIAF or GND ist is enough, when the link is provieded with the number. You can find what you need, without any additional sources or qualifiers. --Giftzwerg 88 (talk) 21:36, 25 October 2014 (UTC)
Yes, I know what you meant, and it's wrong :-) There is GND a) imported from VIAF on Oct. 2012, GND b) imported from VIAF on May 2014, GND c) imported from German Wikipedia on January 2014. GND a) is an other person, GND b) is a Tn (wrong type) and GND c) is outdated. That's why we need sources. Always! And of cause an authority file can change. So we need a date. --Kolja21 (talk) 10:04, 26 October 2014 (UTC)

In this case there would be problematic to checking constraints for certain databases. Many of these properties should have some pattern or should be unique. JAn Dudík (talk) 21:01, 26 October 2014 (UTC)

OK I understand. You have convinced me. My first point is to give all authority controll numbers an extra section. I´d like to seperate it from the "ontology" section wich creates the links between different items. This gives more overview.--Giftzwerg 88 (talk) 07:39, 27 October 2014 (UTC)

Wikidata messes up two central concepts. One is internal identifiers used by an entity itself, the other one is that a lot of linked data sites use a concept of URIs to identify resources. In a whole bunch of cases we take their URIs, which uses internal identifiers, rip them apart and make our own statements with implicit identification of the external site through use of special properties. This is not a viable long-term solution. We must start to use URIs like the rest of the semantic web. There are at least two different implementations, one is to have a URI-datatype, another is to have a external resource sitelink group. Both have their merits, but the last one could be somewhat simpler to implement. For the rest of the identifiers we can have an external identifier with a datatype string, and with a qualifier originating site or identifier type with a datatype item. They should use a reference linking to the actual definition of the string on the originating site. Together this will kill the whole identifier mess. Jeblad (talk) 05:21, 12 November 2014 (UTC)

User:Jeblad - It messes already up with "In other languages" - these are statements too, namely statements about names. Andrea Shan (talk) 20:22, 23 November 2014 (UTC)

Item graphic[edit]

Takes away a lot of space and says little about content. "Berlin" fits to its right, but what with the number one from Special:AllPages/?sortby=lengthOfLabel/descending? Andrea Shan (talk) 05:11, 18 November 2014 (UTC)

Maybe the header should be full width. --Lydia Pintscher (WMDE) (talk) 15:40, 18 November 2014 (UTC)

Top-down WMDE dev solution (ages, expensive) vs bottom-up crowdsourced generic solution (fast, cheap)[edit]

How about grouping the statements by the data type of each property?

It would be a very fast solution, and would already yield enormous benefits. Using the types from Special:ListDatatypes all statements would be in one of these groups:

  • Commons media:
  • Globe coordinate: (if present)
  • Quantity: e.g. area, population
  • String: IDs, names etc. All values used in some environments to identify an item.
  • Time: Start/End, e.g. birth/death, established/disestablished
  • URL:
  • Item:
  • Monolingual text:

Inside each group you can sort by occurrence (Wikidata:Database reports/Popular properties) - crowdsourced!. The "instance of" statement would be first in the "item" section. That is the natural way in Wikipedias already. "Berlin is a city."

You could have this very very fast. No need for months with mock-ups, no need for discussions where to place what. It is a generic solution. It works for any knowledge domain.

You could have that within one week probably. Really, really fast and hundreds of users would benefit when they edit. Instead of the current

In other languages | Statements | Wikipedia pages linked to this item | Wikinews pages linked to this item | Wikiquote pages linked to this item
Wikisource pages linked to this item | Wikivoyage pages linked to this item | Pages on other sites linked to this item

you could provide

Commons media | Globe coordinate | Quantity | String | Time | URL | Item | Monolingual text

which is a lot easier to read. Is there any major website offering long top navigation labels like WikiData currently does?

The proposal is not here to provide the best page layout for every knowledge domain. It is not even here to provide the best for any. But it is here, to improve all item pages NOW, with MINIMAL effort. Andrea Shan (talk) 06:21, 18 November 2014 (UTC)

@Andrea Shan: Why don't you just make your own database interface and see if other people like it? Reasonator is also an alternative interface. --Tobias1984 (talk) 10:26, 18 November 2014 (UTC)
Why don't you comment on your own wiki and see if other people read it? Andrea Shan (talk) 22:22, 18 November 2014 (UTC)
I don't know how you get the impression that the proposed solution by me (the community can order in any way they like) is top-down. --Lydia Pintscher (WMDE) (talk) 11:38, 18 November 2014 (UTC)
Because only few people in an inner circle decide about it. Who made the mock-up? People interested in Berlin. "Berlin" is a short label in many languages, so that made you put a image-graphic in front. Also, the Wikipedia links at the right, they display "Berlin" and it fits. But it won't fit with longer titles. Making such a design by hand is expensive. Make a design that works well on all kind of topics. Top label, all aliases, the names of the Wikipedia articles, the in-other-language statements are of type string. They are all names. Grouping by data type would bring all these strings into one section. Coordinates and quantities might be shorter in general, so for these sections one can reduce the white space. But I don't want to judge on that. The software can group the items by data type and look at the length of the statements, create a statistic for this, instead of thinking "Berlin is short, so all places where it appears can be tiny". A new version of my proposal for the top navigation:
Property statements by data type
Commons media (1) | Globe coordinate (1) | Quantity (14) | String (50) | Time (2) | URL (1) | Item (30) | Monolingual text (50)
For the Berlin mock-up it seems someone deemed "official website" to be important. How many discussions and decisions will you make for all the other 10 mio+ items? Of course, some statements will be placed before others, but let users navigate fast to what is of interest for them - each of them. Not only for those that win in discussions and make the decisions. Respect minorities. Create a good generic design and the result will be less biased towards what the control group is interested in. My proposal is a starting point for a generic solution. Within few days, you could have a tremendous improvement. Andrea Shan (talk) 22:22, 18 November 2014 (UTC)

Wikidata:Development plan#UI redesign

  • Navigating [...] the website is fast - the grouping and the proposed top navigation does that
  • information is ordered in an intuitive way - grouping drastically improves the current situation

Andrea Shan (talk) 22:32, 18 November 2014 (UTC)

Width of search box[edit]

Make it as width as the longest label needs to be displayed completely, when typing in the box. Andrea Shan (talk) 07:30, 19 November 2014 (UTC)

Some language can have extremely long labels, they are called agglomerative languages. It will not be possible to satisfy everyone because of this. Jeblad (talk) 02:15, 23 November 2014 (UTC)
That is news, that "agglomerative languages" have longer labels. Can you give an example? How about satisfying 100% of users for y% of searches, instead of x% of searches as currently, with y>X? For desktops the box could be 65em width, like the class wikibase-entityview currently has. Wait for an example by you to demonstrate that there is a label in any language that does not fit. The current implementation is horror. Andrea Shan (talk) 20:21, 23 November 2014 (UTC)

Order of elements in recent changes[edit]

As items are sorted by time, put the time in front. Time also has them same width for all items, thus the change would stop the current jumping of the position of the time information. The MediaWiki of LibreOffice does it better, see: Andrea Shan (talk) 20:26, 23 November 2014 (UTC)

Use ISO 8601 for dates, the MediaWiki of LibreOffice does it more international than Wikidata, see: Andrea Shan (talk) 20:27, 23 November 2014 (UTC)

You can edit the date format yourself under Special:Preferences. If you set no preferences, the date format is adapted to your language settings which is far better than ISO 8601. --Pasleim (talk) 08:58, 24 November 2014 (UTC)
I don't want to edit it myself. I want to see what other people see. "the date format is adapted to your language settings which is far better than ISO 8601" - maybe for you, not for me. I logged in to use English, I didn't decide to see European English. Last but no least - I thought the UI is not only there for logged-in users? Andrea Shan (talk) 07:17, 26 November 2014 (UTC)
You can change your language settings even if you're logged out. Why you want to see what other people see? The UI is not a fixed frame. There are different skins, dozend of languages, user preferences, individual css files... So the UI looks for everyone different, even for logged out users. --Pasleim (talk) 08:51, 26 November 2014 (UTC)
"Why you want to see what other people see?" - Let me clarify, I want to see what the majority of English language users sees. A user that comes to Wikidata and selects English as interface language, and does not change anything else. Why? I assume that's the most used interface, and I want to know how the UI feels to most users. Any problems they have etc. A user that tunes his UI and uses that one exclusively, may not have certain problems that first visitors have. Andrea Shan (talk) 07:20, 30 November 2014 (UTC)

Due to changes in the data model, this proposal is no longer acceptable. Please read m:Wikibase/DataModel and m:Wikibase/Notes/JSON. In the past it had been the practice to store dates in the Gregorian calendar; the Julian calendar could be chosen for input and display, in which case the software would convert Julian to Gregorian before storing, and convert Gregorian to Julian before displaying the date to the reader. But this didn't work out, and now the Julian or Gregorian date is stored and displayed. Since some of the dates that will be displayed will be Julian, they must not be displayed in ISO 8601 format, because that format is only for Gregorian dates (as is stated many times within the standard). Jc3s5h (talk) 12:59, 14 March 2015 (UTC)

Name statements[edit]

There are different kind of name statements,

  • outside the area where properties of the property name space appear
    • Label
    • Alias
    • In other languages
      • Label
      • Alias
  • inside the area where properties of the property name space appear
    • Property:P225 (STRING) taxon name
    • Property:P357 (STRING) title (string) title of a work (such as a book, a film or a website) original title //comment: "string" appears in the property label
    • Property:P513 (STRING) birth name (Deprecated) DEPRECATED--use P1477 instead
    • Property:P561 (STRING) NATO reporting name
    • Property:P734 (ITEM) surname
    • Property:P735 (ITEM) given name
    • Property:P742 (STRING) pseudonym
    • Property:P743 (STRING) short name
    • Property:P1353 (STRING) original spelling original spelling of a scientific name
    • Property:P1448 (MONOLINGUAL TEXT) official name official name of the subject
    • Property:P1449 (MONOLINGUAL TEXT) nickname the nickname of an entity
    • Property:P1476 (MONOLINGUAL TEXT) title (monolingual text) the title of a work (see also P357) //comment: "monolingual text" appears in the property label
    • Property:P1477 (MONOLINGUAL TEXT) birth name //comment: the second!
    • Property:P1559 (MONOLINGUAL TEXT) name in native language name of a person in their native language
    • and all the IDs (sometimes one can see IDs listed as Alias - indicating of no conceptual difference between the two in the real world [i.e. outside Wikimedia] )

While the properties in the second group are controlled by the property editors the ones in the first group are not. They are set by WMDE and cannot be accessed like regular properties. No qualifiers for Label or for Alias. Suggest to merge all into the regular property space. Andrea Shan (talk) 07:50, 30 November 2014 (UTC)

Concept inconsitency[edit]

The current interface and the proposed UIs has the sitelinks on the right side. But in all other wikimedia projects the sitelinks are in the sidebar on the left. So we have no consistency across the different projects.--Giftzwerg 88 (talk) 09:18, 23 March 2015 (UTC)

I'd like to see tooltips on pretty much everything. The interface should be self-documenting. For instance, when I hover over "[add]" for a reference. It should explain what a reference is and any top important things I should know before adding one. Similarly for all elements of the UI. Jason Quinn (talk) 12:49, 8 May 2015 (UTC)


Content-Type: application/http; msgtype=response

WARC-Type: response

text:
[Bug 2400] Issue with Delete when NumLock active

Wine Bugs wine-bugs at winehq.org
Tue Mar 14 06:21:20 CST 2006

------- Additional Comments From zhilla at spymac.com  2006-14-03 06:21 -------
just to summarise from mailing list, croatian and german is also fixed. apply to
cvs and close this bug please :)

Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the wine-bugs mailing list

warcinfo:
robots: classic
hostname: ip-10-180-206-219.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2015-22
operator: CommonCrawl Admin
description: Wide crawl of the web for May 2015
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf


text:
setupapi: unimplemented function setupapi.dll.SetupPromptReboot

Saulius Krasuckas saulius2 at
Sat Jan 28 04:24:29 CST 2006

* On Fri, 27 Jan 2006, James Hawkins wrote:
> * On 1/27/06, Saulius Krasuckas <saulius2 at> wrote:
> >
> > James, I wasn't asking about how should I hack on unimplemented
> > function. My interest is focused on work of another guys, which is
> > done already. :)
> I based the assumption on your statement, "I stuck upon this function
> right now."

Yeah, I mean my debugging process has been halted due to a stubbiness (not
due to lack of devel-instructions).

> You said you were stuck, so I offered suggestions on how to move
> forward.

OK, next time I will declare I have read the Wine Developers Guide and
have been following wine-devel list for a two years already. ;-)

> I looked at the ReactOS implementation and saw that it was #ifdefined
> out, so I also assumed that wasn't code we should be porting back to
> Wine.  Steven's comments verify this.

Do they?  Steven talks about ReactOS, not about Wine.  I think Wines
ExitWindowsEx() is doing fine for Wine needs.  Then we can simply remove
#if 0 and be fine.  No?

> > BTW, how would you ensure that the testing of this function succeeds
> > if you pass the flag to it which reboots the machine and probably
> > kills the test-process? ;-)
> I was suggesting you write tests for your own testing, not adding unit
> tests to Wine's test suite,

OK, now I get you, thanks. :)

> You won't be able to test a successful reboot in Wine's test suite, but
> you can test it with your personal tests.

I think we still should able to test the reboot, only that this requires
new functionality to be added to winetest*.exe application:  winetest
should be able to interrupt its execution, then it should resume it after
the reboot.  IMHO that's not impossible.

More information about the wine-devel mailing list


WARC-Truncated: length

text:
You've Taken My Blues & Gone

Sounds of Blackness
Africa To America: The Journey Of The Drum

If you purchase this track through our affiliate link, WMNF will receive a small cut. Every little bit helps! Buy from Amazon
We also encourage you to support your local independent music store.

comments powered by Disqus


text:
It's the Music! Thursday Playlist for November 15, 2012

See all playlists for this date

Requests are in italics.

Click on a song title for comments and more.

Dinosaur Jr. Watch the Corners I Bet on Sky
set break
The Dandy Warhols Seti vs. the Wow Signal This Machine
Sleigh Bells kids Treats
Interpol Evil antics
passion pit Carried Away Gossamer
MGMT Electric Feel Ornacular Spectacular
set break
Uncle Tupelo I Wanna Be Your Dog (Previously Unreleased) 89-93: An Anthology
Titus Andronicus Food Fight Local Business
Titus Andronicus My Eating Disorder Local Business
set break
american aquarium Ain't Going to the Bar Tonight Dances for the Lonely
the sheepdogs Laid Back The Sheepdogs
Wilco At Least That's What You Said A Ghost Is Born
Edward Sharpe and the Magnetic Zeros Man on Fire Here
set break
jack white Missing Pieces Blunderbuss
Band Of Horses Dumpster World Mirage Rock
Yeasayer No Bones Yeasayer
Dirty Projectors About to Die Swing Lo Magellan
set break
Bruce Springsteen & The E Street Band Crush on You The River
Uncle Tupelo We've Been Had (Live) 89-93: An Anthology
black moth super rainbow Windshield Smasher Cobra Juicy
Faith No More We Care A Lot Left Of The Dial
The Semis High on Pop High on Pop
set break
Benjamin Booker and Max Norton Have You Seen My Son? Live on "It's the Music/Thursday Nooner"
The bright light social hour Back And Forth The Bright Light Social Hour
Benjamin Booker and Max Norton Untitled Live on "It's the Music/Thursday Nooner"
american aquarium Katherine Belle Dances for the Lonely
american aquarium Hurricane Small Town Hymns
Wu Lyf Heavy Pop Go Tell Fire To The Mountain
Otis Redding can't get no satisfaction Very Best of Otis Redding
set break
Have Gun Will Travel Thirteen Miles to Empty Mergers and Acquisitions


text:
Help support Wordnik by adopting your favorite word!

from The American Heritage® Dictionary of the English Language, 4th Edition

  • Hofmannsthal, Hugo von 1874-1929. Austrian writer who established his reputation with lyric poems and a number of plays, including Yesterday (1891) and Death and the Fool (1893).

Sorry, no etymologies found.

  • The New Grove quotes Strauss's estimate of it as 'Hofmannsthal's finest achievement,' adding that 'some think that it is also Strauss's,' and the recent Mondadori volume, L'Opera: repertorio della lirica dal 1597, generally balanced in its criticism, ranks the opera with Tristan and Don Giovanni.

    The 'Shadow' and the Substance

  • He collaborated on a ballet score with Hugo von Hofmannsthal and Richard Strauss.

    Things Fall Apart

  • AKG-Images Leon Bakst costume sketch for 'The Legend of Joseph,' the 1914 ballet created by Kessler, Richard Strauss and Hugo von Hofmannsthal.

    Things Fall Apart

  • His mid-career work, Die Frau ohne Schatten, premiered in 1919 to a libretto by Hofmannsthal, wanders perilously into a more uneasy realm: the notion that a marriage can only be happy if blessed with children.

    Die Frau ohne Schatten; BBC Proms 61 & 62 – review

  • Tourismus Salzburg View of Salzburg This year's Salzburg Festival features Christof Loy's radical new production of "Die Frau ohne Schatten," an opera by two of the men who founded the festival in 1920, Richard Strauss and Hugo von Hofmannsthal.

    Salzburg's Summer of Shadows and Shakespeare

  • The Salzburg Festival made its start the very next year, though the original organization collapsed in 1910, and was re-founded in its present form in 1920 by great men such as the director Max Reinhardt, playwright Hugo von Hofmannsthal and composer Richard Strauss.

    Eat, Drink and Be Entertained

  • And of all those writers—Zweig, Musil, Schnitzler, Kafka, Hofmannsthal, Kraus, Canetti, the list goes on—the supreme elegist of the Dual Monarchy was Joseph Roth.

    Dispatches From a Lost Empire

  • For instance, Friedrich Gundolf, Richard Borchardt, and Hugo von Hofmannsthal—all poets and writers, and all wholly or partly Jewish—have been advanced as representing the pure Aryan spirit.

  • During the 1920s, Zuckerkandl promoted the theater projects of Max Reinhardt (1873 – 1943) and Hugo von Hofmannsthal (1874 – 1929), especially the Salzburg Festivals.

    Berta Zuckerkandl.

  • Listed below are links to weblogs that reference Strauss-von Hofmannsthal dispute:

    Strauss-von Hofmannsthal dispute

Log in or sign up to get involved in the conversation. It's quick and easy.


text:
avariciousness love

Help support Wordnik by adopting your favorite word!

from Wiktionary, Creative Commons Attribution/Share-Alike License

  • n. The state or quality of being avaricious.

from The Century Dictionary and Cyclopedia

  • n. The quality of being avaricious; insatiable or inordinate passion for property.

from WordNet 3.0 Copyright 2006 by Princeton University. All rights reserved.

  • n. extreme greed for material wealth

Sorry, no etymologies found.

  • At the mention of the name the little group grew very grave, their avariciousness replaced by trepidation.

    The Curse of the Wendigo

  • The situation evolved a rough set of checks and balances which tended to hold down the avariciousness of any one particular class.

    Sneak Attack

  • When will debt not be an option and when will humans guard against avariciousness?

    Bailouts Blaze; Exuberance Explodes

  • On the one hand, this is avariciousness; on the other, astuteness.

    The Secrets of His Succession

  • You lost the “spiritual” warfare at that point when you opted for underhanded avariciousness.

    The US is Trying to Take Over The World - The Panda's Thumb

  • When we describe their pompous vanity and take exquisite pleasure in putting calipers on the immense littleness of their avarice, we are making records of our own littleness and avariciousness.

    Philip "Momism" Wylie on Congress

  • Many newspaper executives see something sinister in Craigslist's near-total lack of avariciousness --

    Zen and the Art of Classified Advertising

  • M. de Courtornieu, by his avariciousness, had made even more enemies than the Duc de Sairmeuse; and all the peasants who thought they had more or less reason to complain of his extortions were delighted at this opportunity to frighten him.

    The Honor of the Name

  • In its way, their time-honored avariciousness was almost quaint.

    Drowning World

  • She felt the same avariciousness that Shandi must have felt over the dye - if there was one weakness she had, it was for her garden ....

Log in or sign up to get involved in the conversation. It's quick and easy.


text:
Help support Wordnik by adopting your favorite word!

from The American Heritage® Dictionary of the English Language, 4th Edition

  • adj. Bearing, resembling, or having a profusion of leaves or fronds; leafy.

from Wiktionary, Creative Commons Attribution/Share-Alike License

  • adj. Leafy; becoming leafy; resembling leaves.

from The Century Dictionary and Cyclopedia

  • Bursting or having the appearance of bursting into leaf.

Latin frondēscēns, frondēscent-, present participle of frondēscere, to become leafy, inchoative of frondēre, to put forth leaves, from frōns, frond-, foliage .
(American Heritage® Dictionary of the English Language, Fourth Edition)
From Latin frondescens, present participle of frondescere ("to become leafy"), from frondere ("to leaf out"), from frons ("foliage") (Wiktionary)

Log in or sign up to get involved in the conversation. It's quick and easy.


text:
Help support Wordnik by adopting your favorite word!

Sorry, no definitions found.

Sorry, no etymologies found.

Sorry, no example sentences found.

Log in or sign up to get involved in the conversation. It's quick and easy.

  • It had the sort of lobby that asks for plush and india-rubber plants, but gets glass brick, cornice lighting, three-cornered glass tables, and a general air of having been redecorated by a parolee from a nut hatch.
    --Raymond Chandler, 1949, The Little Sister, chapter 34

    September 5, 2009


text:
Please enable Javascript

Javascript needs to be enabled in your browser to use Yahoo Food.

Here’s how to turn it on:

How to Get the Most Out of Your Butcher

By: Oliver Strand

How to Get the Most Out of Your Butcher

Rule No. 1: Talk to Your Butcher

The butcher wants to know what you’re planning on cooking and how much you want to spend, how many guests are coming for dinner, and whether you’re an experienced cook. This is true even of supermarket butchers, from Whole Foods to Winn-Dixie, who have started stepping up their game to meet the standards of more demanding carnivores. When dealing with a butcher, just follow the advice of Stanley Lobel, an owner of Lobel’s, on New York’s Upper East Side, a shop well-known for its exceptional service. “Ask questions,” says Lobel. “What should I get? Is there anything I should try? All these guys know what they’re talking about.”

Rule No. 2: Then Make Him Work For You

In a mysterious, precapitalist take on service, any trimming, trussing, boning, or other custom cutting you ask a butcher to do is included in the price of the meat. You can get anything cut to order (those steaks and roasts sitting in the display case are only a teaser—there’s plenty more in the back) at no extra cost. Request veal cutlets for schnitzel, for instance, and he’ll pound them paper-thin—some butchers will even season and bread them for you. Get a whole chicken and you can have it trussed or quartered or boned. (Note: At supermarkets like Whole Foods, the poultry’s usually in a refrigerated case separate from the meat counter; if you want yours prepped for dinner, just grab it and bring it over to the butcher.)

Like your porterhouse a hefty two and three-quarters inches thick? Just ask for it. Like your porterhouse a hefty two and three-quarters inches thick? Just ask for it. Or if you’re trying to impress your friends to the point of intimidation, request a couple of racks of pork. You can have the butcher crack the chine (that’s the backbone), section the loin, and cinch the whole thing with twine into a crown roast worthy of a nineteenth-century banquet. None of these bespoke preparations are extra, and none of the butchers I spoke with know why, exactly—it’s just what they do.

SEE MORE: 25 Best Restaurants in America for 2014

Rule No. 3: Ask for Recipes

A good butcher has a few favorite recipes on hand. Sometimes his cooking tips are straightforward: the right way to make a pot roast, how to sear a steak. But if you give him the opportunity, he will completely alter (and dramatically improve) your dinner. I posed a scenario to Adam Tiberio, the head butcher atDickson’s Farmstand Meat in New York’s Chelsea Market: a get-together with a group of rowdy friends fueled by last year’s vintage of brawny Malbec.

“I’d steer you to big flavor,” he said, “like a whole plate of short ribs, what they call costela in Brazil.” Then he outlined a recipe as brief and pure as a haiku: short ribs (use a paring knife to poke holes all over), one can of beer (any lager), salt (about a teaspoon per pound), and pepper. Roast (covered tightly with foil at 375 degrees for twenty minutes, 275 degrees.

Rule No. 4: Buy Local Pork

A new generation of butchers do more than stand behind their meat counters; they stand behind their meat. The heritage pork sold at shops such as Dickson’s andMarlow & Daughters in Brooklyn, for instance, is sourced from Berkshire, Large Black, and Tamworth pigs raised on local farms—and more often than not, the butcher has a personal relationship with the farmer. (By comparison, most American beef and pork are processed and packaged in the Midwest and Texas, then shipped around the country.)

And if the butcher is getting the farm’s best animals, you’re getting the farm’s best meat. It’s a qualitative difference that’s superbly clear in heritage pork, genetically pure breeds that grow slower (they aren’t force-fed) than conventional hogs and yield meat far more savory. Once you’ve had a rack of Red Wattle, there’s no going back.

SEE MORE: 2014 Spring Style Trend Report

Rule No. 5: Venture Beyond Strip Steak

A cow isn’t all steaks, or what Tiberio calls the “middle of the cow”: the strip, rib eye, and overpriced tenderloin. There are tougher cuts (chuck, brisket) that turn meltingly tender when braised; organ meat (heart, sweetbreads), which is easily grilled; and other off cuts (trotters, heads) that reward ambition in the kitchen.

And if it’s steak you want, you can experiment. “Certain cuts are popular because people want what they’ve seen on a menu,” said Melanie Eisemann, one of the owners of Avedano’s (, which opened in San Francisco in 2007. Try overlooked—and cheap—skirt steak, for instance, or one of the unsung cuts butchers are carving. Joshua Applestone, the co-owner of Fleisher’s in upstate New York (, trims sirloin flap and calls it “faux hanger.” Like skirt, it’s flavorful, affordable, and excellent grilled.

Rule No. 6: Don’t Forget the Bones

Sold for pennies a pound at the butcher, bones are where the serious flavor’s at. Buy a bag of chicken or veal bones, add water, some carrots, onion, and celery, and simmer for a couple of hours for a rich stock. Your risotto—or soup or pasta or anything that calls for stock—will never be the same again. Marrow bones, which you can also get for a couple of bucks, are a whole other story: Roasted in the oven at 450 degrees for about fifteen minutes and served with crusty toast and a parsley salad (splash of olive oil, squeeze of lemon, generous pinch of coarse salt)—they make for a transcendent appetizer. Have the bones cut into three-inch pieces and invest in some skinny forks (or if you’re really going for it, marrow knives). Some restaurants, like Minetta Tavern in New York, cut the bones lengthwise to create a trough that makes the marrow easy to scoop out—ask your butcher if his band-saw skills are up to it.

SEE MORE: How To Make Better Meat, Overnight

Rule No. 7: Have Your Burger Meat Ground to Order

Hamburgers aren’t actually made with ground beef—the professional term is “chopped beef.” A good butcher uses fresh meat and sharp blades so that what comes out of the machine has body and a light texture and will retain moisture when cooked; he’ll also make a fresh batch daily. The standard is chuck, a tasty stewing cut. But you might take a cue from restaurants like Shake Shack in New York and Father’s Office in Santa Monica and ask for a custom blend. One couple I admire start their summer weekends with a few pounds of burger meat that’s a mixture of chuck, sirloin, and, the kicker, slab bacon.

More from GQ:

David Chang’s Take on Fresh Food

Alan Richman’s Top 5 Dishes of 2014

The 10 Habits of Highly Unflabby People


text:
Yahoo TV
Please enable Javascript

Javascript needs to be enabled in your browser to use Yahoo TV.

Here’s how to turn it on:

The Biz: Don Draper Travels to the 1980s

Jon Hamm | Photo Credits: Photo Illustration courtesy of John McNameeJon Hamm | Photo Credits: Photo Illustration courtesy of John McNamee

Ever wondered what happened to Mad Men's Don Draper after the swinging '60s ended?  John McNamee, a comic and writer, has created the Twitter account @80sDonDraper to give voice to the character's Reagan-era musings. We asked McNamee for some insights into Don's future.

TV Guide Magazine: How is Don doing professionally in the 1980s?

McNamee: The firm's gone through a lot of changes. I think it's called Sterling Cooper Draper Mr. T now.

TV Guide Magazine: His wardrobe and hair look very Miami Vice.

McNamee: Don's a trendsetter. It's Miami Vice's wardrobe and hair that look Draperish.

TV Guide Magazine: Does Don have a mobile phone?

McNamee: He does have a big old '80s cell phone, which he loves. It's the brick with which he's building the future.

TV Guide Magazine: How did he survive the '70s? Did he go to Studio 54?

McNamee: Don was in Studio 54 for the entirety of the '70s. He said it was for a client.

TV Guide Magazine: Has he switched from booze to cocaine yet?

McNamee: Drink will always be Don's first love, though he does sometimes coke the rim of his margaritas.

TV Guide Magazine: How many wives is he up to?

McNamee: Forty-seven. He's trying to get one from every state.

TV Guide Magazine: Based on Don's personal habits, does he have any chance of making it into the 1990s?

McNamee: I hope he makes it. Someone's got to sell us all on Pogs.

TV Guide Magazine: Mad Men creator Matthew Weiner has said he likes your tweets. So there's been no cease-and-desist order from AMC?

McNamee: No C&D, but no invitation to help them '80s-ify the final season, either, which is a shame. I had an emotional episode planned where everyone reacts to J.R. getting shot.

TV Guide Magazine: What do you write when you're not tweeting as Don Draper?

McNamee: I contribute to The Onion, draw a cartoon at, blog and do sketch comedy. In all my work, I try to keep the Don Draper spirit and blood-alcohol content.

Subscribe to TV Guide Magazine now!


text:
Green Yellow Pages
Find a Business Near: McKee, KY
Enter Business Name or Keyword       Search by Phone
City, State or Zip Code

    Business Owner?

    List Your Business »

    Home ::: Kentucky ::: McKee ::: Clothing Accessories - Other

    Clothing Accessories - Other in McKee

    Below is a list of businesses listed within our directory. If you do not see your business within the list below, you can submit it for addition to this list. Adding your business will feature your listing above Standard listings.
    Standard Listings

    Business Listing   Cleaning Unlimited Cleaning Services LLC - McKee, KY - Phone: (606) 287-6607

    Business Listing   Colter's Diamond Center - McKee, KY - Phone: (606) 287-8343

    Business Listing   McKee Flower & Gift Gallery - McKee, KY - Phone: (606) 287-8666

    Business Listing   Sunlite Cleaning Service - McKee, KY - Phone: (606) 287-0625

    Don't see your business here? Add it and appear here!

    Helpful Definition for: Clothing Accessories - Other

    Clothing accessory stores in McKee have a varied and unique collection of fashion accessories, worn to add a dash of style to an outfit. These accessories are worn along with clothes to complement them and give an improved look. Clothing accessory can be anything such as jewelry, gloves, handbags, hats, belts, scarves, watches, sunglasses, pins, stockings, bow ties, leg warmers, leggings, neckties, suspenders or tights. These accessories with a blend of color, style and class are not limited to women alone but are equally popular with men. Accessories being associated with all age groups are available in vast variety and have high demand in McKee.


text:
Green Yellow Pages
Find a Business Near: Orion, MI
Enter Business Name or Keyword       Search by Phone
City, State or Zip Code

    Business Owner?

    List Your Business »

    Home ::: Michigan ::: Orion ::: Apartments

    Apartments in Orion

    Below is a list of businesses listed within our directory. If you do not see your business within the list below, you can submit it for addition to this list. Adding your business will feature your listing above Standard listings.
    Standard Listings

    Business Listing   Waldon Lakes Apartments - Orion, MI - Phone: (248) 391-5500

    Don't see your business here? Add it and appear here!

    Helpful Definition for: Apartments

    'Apartments' are complete lodging structures, which are a part of the whole building. Apartments in Orion are often owned by the residents as co-operatives where they possess portions of a corporation or as apartments wherein the public spaces are shared by the residents of the apartments. In Orion apartments are used mostly for giving rents by the building possessor. Apartments come in quite inexpensive rates for rental purposes in Orion. There are different types of apartments which include one-bedroom, two-bedroom, three- bedroom, etc. In Orion more than three-bedroom flat is uncommon. Various facilities are there in all kinds of apartments.


text:
Green Yellow Pages
Find a Business Near: Pleasanton, KS
Enter Business Name or Keyword       Search by Phone
City, State or Zip Code

    Business Owner?

    List Your Business »

    Home ::: Kansas ::: Pleasanton ::: Tire Dealers

    Tire Dealers in Pleasanton

    Below is a list of businesses listed within our directory. If you do not see your business within the list below, you can submit it for addition to this list. Adding your business will feature your listing above Standard listings.
    Standard Listings

    Business Listing   Rick's Tire & Lube - Pleasanton, KS - Phone: (913) 352-6438

    Don't see your business here? Add it and appear here!

    Helpful Definition for: Tire Dealers

    Tire dealers in Pleasanton work to promote standards of ethics of the tire industry, to improve the quality and standards of the new tire and retread industry, to promote cooperation between them and people in local, state and national regulating bodies regarding problems affecting the tire and retread industry, to acquaint the buying public with the true value of the tire dealer in the community.


text:
To the Last Drop: Canada's Dirty Oil Sands - Part 1

The interactive transcript could not be loaded.

Rating is available when the video has been rented.
This feature is not available right now. Please try again later.
Uploaded on Jul 27, 2011

Residents of one Canadian town are engaged in a David and Goliath-style battle over the dirtiest oil project ever known.

Filmmakers: Niobe Thompson and Tom Radford

The small town of Fort Chipewyan in northern Alberta is facing the consequences of being the first to witness the impact of the Tar Sands project, which may be the tipping point for oil development in Canada.

The local community has experienced a spike in cancer cases and dire studies have revealed the true consequences of "dirty oil".

Gripped in a Faustian pact with the American energy consumer, the Canadian government is doing everything it can to protect the dirtiest oil project ever known. In the following account, filmmaker Tom Radford describes witnessing a David and Goliath struggle.

I shot my first film, Death of a Delta, in Fort Chipewyan in 1972. I shot it with a hand crank Bolex camera with a maximum 26-second wind. I had to make sure people knew what they were talking about. There was no time for red herrings. In our new film, To the Last Drop, the latest in digital HD and Cineflex cameras capture the landscape of northern Alberta as never before.

But while technology can go through multiple revolutions in 39 years, the issue that drives both our films remains the same: the rights of downstream communities, and the need to recognise those rights, no matter how powerful their upstream neighbours.

Death of a Delta documented the fight of Fort Chipewyan to have a voice in the construction of a massive hydroelectric project on the Peace River, the W.A.C. Bennett Dam. At stake was not only the survival of the oldest community in Alberta, but the protection of a World Heritage site, the Peace Athabasca Delta, a convergence of migratory flyways and the greatest concentration of waterfowl on the continent.

In the David and Goliath struggle that ensued, David won. Water was released from the dam and water levels in the Delta returned to normal. The unique ecology of the region was saved. The town survived.

Today, that same David, the collective will of the thousand residents of Fort Chipewyan, is fighting an even more imposing Goliath. The Alberta oil sands is arguably now the world's largest construction project. Its expansion will have an estimated $1.7 trillion impact on the Canadian economy over the coming decades. An area of boreal forest the size of Greece will be affected by industrial activity.

Once again the issue is water, but this time it is not just the flow of the river, but the chemicals the current may be carrying downstream from the strip mines and bitumen upgraders.

In recent years, according to the Alberta Cancer Board, Fort Chipewyan has experienced an unusually high rate of cancer. Local fishermen are finding growing numbers of deformed fish in their nets. Residents and John O'Connor, the community doctor, worry there could be a connection to the oil sands.

As they did in the 1970s, the people of Fort Chipewyan have appealed to science for help. Then it was William Fuller, a biologist from the University of Alberta, who collected the data that proved the Delta was dying. Today, it is David Schindler, the winner of the Stockholm Water Prize, and a team of international scientists conducting painstaking research to find out what is in the Athabasca River - and where it is coming from.

Alan Adam, the chief of the Athabasca Chipewyan First Nation, has worked closely with Schindler. He knows that vast areas of the Delta are once again becoming impassable because of falling water levels. This means the hunting, trapping and fishing rights guaranteed to his people in Treaty 8 are worthless.

He has appealed to elders like Pat Marcel and Francois Paulette from neighbouring Fort Fitzgerald to record the changes they are seeing in the water and the wildlife. In a unique exchange, science and traditional knowledge are coming together to challenge the oil sands.

When I first arrived in Fort Chipewyan in 1972, an Indian kid was sitting on the dock singing Hank Williams' Your Cheatin' Heart. The old guitar he was playing had about three strings. One verse at a time, we recorded the song with our 26-second camera. Then we tried to get the rights. The kid was no problem, but Nashville will always be Nashville. Too bad. It would have been the perfect cover for all those years of government and industry duplicity.

These days the powers that be are beginning to listen. The recent Oilsands Advisory Panel, appointed by Jim Prentice, the former environment minister, stressed in its December 2010 report the importance of proper research and regulation. We have to know what is in the water.

Maybe David has a chance to win again. Goliath would be better for it.

To the Last Drop can be seen from Wednesday, June 22, at the following times GMT: Wednesday: 2000; Thursday: 1200; Friday: 0100; Saturday: 0600; Sunday: 2000; Monday: 1200; Tuesday: 0100; Wednesday: 0600.

All Comments

Comments are disabled for this video.
When autoplay is enabled, a suggested video will automatically play next.

Up Next

to add this to Watch Later

Add to

Loading playlists...


text:
Search by: Specialty Name
Location (Zip, City, State)
who participates in
Reason for Visit
Doctor Gender
Any Gender

Allergists and Other Doctors in Winter Park, FL 32789, 32789 | Blue Cross Blue Shield - BlueCard PPO/EPO

Find Doctors and Make Appointments Online

Managing your healthcare is easier than ever before with ZocDoc. Just search for a doctor in your insurance network, see available times, and book an appointment on the spot! You can read real doctor reviews from other patients, see the doctor’s background and education, view photos of the office, and more. It’s simple, secure, and free!

Family Physician
Family Physician
4711 Curry Ford Road
Orlando, FL 32812
Within 6 miles
General Nurse Practitioner
General Nurse Practitioner
801 N. Orange Ave
Orlando, FL 32801
Within 3.5 miles


text:
Search by: Specialty Name
Location (Zip, City, State)
who participates in
Reason for Visit
Doctor Gender
Any Gender

Dentists and Other Doctors in Somerville, MA, 02143

Dentists in Somerville

From Broadway to Prospect Hill and Foss Park, you can use ZocDoc's verified patient reviews and extensive doctor profiles to find a local dentist who participates in your insurance plan. Dentists in Somerville, Massachusetts, are ready with a wide selection of available appointment times for cleanings, bridges, crowns, and denture fittings. Make an appointment quickly by simply clicking on an open time slot that fits your schedule.


text:
• Español
  • Join Now
Dr. Lorenzo Brown

Dr. Lorenzo Brown MD

Ear, Nose & Throat Doctor

Qualifications of Dr. Lorenzo Brown MD

Professional Statement

Dr. Brown is an experienced physician and surgeon who has been in private practice since 1979. For over twenty five years he has specialized in ear, nose, throat, sinus and facial plastic surgery.

Dr. Brown is a graduate of the University of Michigan Medical School in Ann Arbor, Michigan. He then completed two years of surgical training in Los Angeles, California. This general surgery training was followed by a three year residency in Otolaryngology (Ear, Nose and Throat), Head and Neck Surgery at the prestigious Northwestern University in Chicago, Illinois. Dr. Brown was Board Certified by the American Board of Otolaryngology in 1979.

As an ENT specialist, Dr. Brown provides both medical and surgical management of disorders of the ears, nose and throat. He performs a full range of ENT procedures on both children and adults - from surgery for facial fractures and neck tumors, the latest techniques in endoscopic sinus surgery to conventional and laser removal of ear keloids.

The Aesthetic Facial Surgery and Sinus Care Center specializes in two aspects of ENT – Facial Cosmetic and Sinus Care. Although these two specialties are related, the decision process required to undergo cosmetic and sinus surgery is different.

Cosmetic Surgery is performed to enhance one’s appearance. The change of appearance often produces a positive change in self perception and attitude. These are changes your friends and family can perceive.

Our Sinus Care Program is designed to produce relief from nasal congestion and sinus discomfort. Long time sufferers of chronic nasal congestion and sinus disease need the care of a specialist in these disorders to finally obtain relief.

Please feel free to ask both Dr. Brown and our staff any questions that you may have. Our primary concern is that you leave our office feeling healthier and more confident. We look forward to a one-on-one consultation for and about YOU.

An Experienced Ear, Nose & Throat Surgeon Helping You To Look and Feel Your Very Best!

Patient Reviews for Dr. Lorenzo Brown MD

All reviews are from verified patients
103 S. Locust Street, Inglewood, CA 90301

This doctor has no availability on ZocDoc.


WARC-Identified-Payload-Type: text/html

text:
Tag Archives: interior color designer san francisco

I am a Architectural Color Consultant and Interior Designer who loves color & great design!

    You don’t want your home feeling like a furniture store.  Don’t forget to bring in some of what makes you feel good in nature into your interior design.

It is summer! More light, longer days and a bit of time in your favorite chair noticing the light hitting the color on the wall.  Most people think of decorating just one room at a time or try to  find … Continue reading

warcinfo:
robots: classic
hostname: ip-10-158-191-93.ec2.internal
software: Nutch 1.6 (CC)
isPartOf: CC-MAIN-2017-51
operator: Common Crawl Admin
description: Wide crawl of the web for December 2017
publisher: Common Crawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf


WARC-Identified-Payload-Type: application/xhtml+xml

text:
Hello [Login]   [Sign up]

Shipping Method

Shipping Method

1. In West Malaysia, when the order is less than RM100, the postage fee is RM6.00, but when the order is more than RM100 or above, we will give you free of postage. (If the weight of parcel is more than 500g, we will post out by skynet)
2. The orders of East Malaysia, the postage fee normally is RM9.00, if too heavy or large will be extra charged.
3. We will prefer the shipping company by the weight and size of goods, if customer wants to prefer the favourite shipping company, you must pay all the postage fee. About the postage, please contact our customer service to know more.
4. The customer can track your goods after 4pm, you can login member center to check the Express company we prefer and tracking no.
5. When we send your goods today, usually the next day you will receive the goods. But we cannot make sure the time of received, because the operation of Express company not in our control scope.

Shipping Company Delivery Area Time Of Reached Details
  Whole Malaysia 1-2 Work Days http://www.poslaju.com.my
  West Malaysia 1-2 Work Days http://www.skynet.com.my

  • 7 days return policy, we only will refund for item not include postage.
  • Provide an invoice


text:
Tuesday, April 13, 2010

597 - Mickey Rivers

About This Player
Mickey Rivers played 15 seasons in the Major Leagues and six of them with the Angels.  Known as "Mick the Quick," Rivers only played 30 games in 1973, but established himself as the starting center fielder the following year.  Rivers lead the American League in triples in 1974 and 1975 and in stolen bases in 1975.  Rivers enjoyed his best seasons with the Yankees after being traded for the 1976 season.  With the Yankees, Rivers was a one-time All-Star and played in three World Series.  Rivers spent his final seasons with the Rangers.

About This Card
I like the location of this photo with the big "A" in the background.  Despite the many changes to Angels Stadium since 1973, the big "A" remains a major landmark in Anaheim today.

No comments:

Post a Comment


text:
Found: Military schools for troubled teens

how much is a nintendo 64 mercedes commercial vans rentals uk. door manufacturer and houston and texas... amsc to forgo their debt: 8 ality frame inch lcd photo pixar. blues tom waites no bones: women\x27s shelter of south texas: el censo emilio carballido translation... lyrics little feat spanish moon: ncaa basketball las vegas line 1942 1945 james johnson original p. cash advance for savings account apartment camp lejeune nc rental animals of the freshwater biomes! australia credit card online applications... chicken invaders 3 registration key build a bear birthday party. online windows xp key generator bt voyager 105 drivers xp.

wereld draait door peter r de vries

cheap gladiator skate knee gaskets marquee theater in tempe arizona. one ground is equal to: how to become a rajya sabha members? bfg 8600 gt oc 512 review dj shadow funky skunk track university of maryland web site. big east tournament 2005 basketball: toyota prius crash test rating frontlines fuel of war 1.3. call of duty 4 heat walkthrough divisibility are there any rules... c340 garmin gps pilot street cannon image runner 600 specifications. a christmas story house tour: atx power supply voltage tolerance.

consumer reports top listed home theater receiver

yeast infection cream during pregnancy, como yo te anelo si no estas; taste of the south 2009. asia fort taste tx worth; recent car accident articles 2009 catherine austin fitz web site. money for filling out survey, atlas employment services coos bay burst eyes flame into shut. best hacienda old town western wii d2c chip wiring diagram, some compression algorithms exploit this property. lucas county fair maumee ohio, china customer relationship isp call center service free sample family reunion letter? aneheim cinema city monday showings; 95 marino defining moment card 18... who won the powerball jackpot: what is my scene name.

moorfields estate agents in bristol

cheats 4 star wars battlefront 2 asia in new order pacific world miles per hour in kilometres? me first and the gimmie gimmies albums atv frame ltz400 part suzuki. dont give up on us lyric... cooking pinto beans on stove consumer debt elimination law practice. catering equipment services sdn bhd; from under the cork tree fall, xbox 360 red light faults. amana bottom mount regrigerator reviews energy efficiency, obama speech at the democratic national convention weather in broken arrow oklahoma. 1 cup of butter is bob marley and the wailers survival. casa del gordo highland park; 6th bowl chicken soul soup...

are kayla and ryan still together

scientific information on a green tourmaline auto cd lexus manual service. asp net custom server control who makes flavor wave oven... create a teddy bear online; championship auto racing teams cart, de estados fauna flora unidos y. no friends list and comment box, wine gift basket in tennessee... you said nothing at all lyrics the national center for family literacy. the autumn offering revelation lyrics; bikini wax or brazilian wax: capulina ave morton grove il. clos du bois shiraz 2003, american hot rod roy dead, ricoh xd sm driver slows system.

2001 british census religious affiliation nascar racing games free download


text:
― Tahereh Mafi, Shatter Me

Monday, July 30, 2012

Hottest Hades

Hey hey this is Mari!!!!!!!!!!!!! So I know lots of books that have Hades or some kind of representation of Hades in a strange sort of way that's still beautiful(Cole- Everneath) or Literally Hades (Hades-Lightening Theif) or portrayed as a teenager (Henry-Goddess Test)

1ST PLACE- Henry!!
He's so amazing and he drives me crazy some times but he is so sweet so I choose Henry for first place!

2ND PLACE- Cole!!!!!
Only because he saved Nikki's brother once but I DONT LIKE COLE!!!!

3D PLACE- Hades!!!
He's old so he gets last and frankly he's kinda creepy!

Since we are a user friendly blog and want all of our readers to be able to read the comments please add " **SPOILER ALERT** " to your post if it applies. Thanks for your consideration!
Related Posts Plugin for WordPress, Blogger...


text:
• Gastropub
  • 24 South Michigan Ave
  • Midrange

The Gage is an iconic Chicago restaurant located at 24 S. Michigan Ave. in Chicago’s historic Gage Group buildings, directly across the street from the famed Millennium Park. The restaurant serves rustic American fare in a refined, lively setting, complemented by an innovative libations program.
The Gage takes its name from the Gage Group of buildings (18-24 South Michigan). Constructed in the late 1800s and now historically landmarked, the buildings housed three milliners, including Gage Brothers & Co. founded by David and George Gage.Gage Brothers & Co. supplied hats to fashionable ladies throughout the U.S. and abroad.The installation in the staircase to our lower level features original early 20th century theater magazine advertisements for Gage hats which were known for their “superb style, sterling quality and superior workmanship”.


text:
Be aware about some plugins when creating multilingual WordPress website…

Around 6 years ago, when xili-language was started, to resume only two plugins (WPML, qTranlate) were available with very different data architectures. Neither of them respected the architecture of WordPress core since the first added many tables and the second changed the content of posts by compacting the different languages in each field. It is true that taxonomies had appeared with WP 2.3. Today, the offer is bloated as the ongoing attempts to show the comparison .
Two extensions have recently emerged and their architecture, once installed will compromise more or less seriously the database. “Multi language” adds tables to put the translations of posts thus without extension, can not be recovered.
WPGlobus “Multilingual everything” as it modifies like qTranslate (and its successors qTranslateX) content as shown in the database tables below:

Post #1 n'is not yet multilingual
Post #1 n'is not yet multilingual

and when it makes multilingual (via tabs), we note the significant change of the field of post table … here each field containing the three languages in {}! How then will be queries ? At least not according to the rules WP_Query 🙁

WP Globus modifies irreversibly the content of fields
WP Globus modifies irreversibly the content of fields

“Babble” does not use taxonomies but the custom post type to store posts according to language. Not easy for queries … to follow because by yet officially in filing plugins (repository).

Working with a content management system (CMS) such as WordPress requires some principles, the first is to preserve data integrity before and after adding “tag” that specifies the language (taxonomy) or links to articles in other languages (custom field). This is the basic principle of Xili-language trilogy established since its creation and enduring the version of WP 2.3 to 4.3, which will be out soon.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:   <acronym title="">
      <q cite=""> <s>