Many designers strive to create products that are so easy to navigate, their users can flow through them at first glance. To design something with this level of intuitiveness, it’s imperative designers understand affordances—what they are and how to use them.

Identifiability: The number of correct versus incorrect clicks

Find-ability / scan-ability: The time it took a participant to find and click on a requested element

To make sure that participants couldn’t learn and predict where text field alternatives might show up during the test, we randomized the order in which we presented those text fields.

To improve the usability of text fields and to determine which text field variables to alter, our researchers and designers conducted two studies between November 2016 and February 2017, with actual users.

You might not always notice, but Material Design is constantly evolving and iterating based on research.

However, some users didn’t know that they could interact with and click on the text field. It looked like an empty box. The line affordance under the old text fields was not clear to some users. The line was confused with a divider.

The label and input were confused with body text, especially in dense compositions.

But floats are still useful and relevant! In fact, we have to use them for the shape-outside property to work.

Now that we’ve gotten newer layout features — again, like grid and flexbox — floats, too, have sort of fallen by the wayside, perhaps either because there are better ways to accomplish what they do

This way the text will wrap above the shape even though the div extends to the top.

shape-outside: inset(100px 100px 100px 100px 10px);

It might be better to think of it this way: with the shape-outside property we’re changing the relationship of other elements around an element, not the geometry of the element itself.

The default fill_in method of Capybara is case sensitive. This is apparently due to their use of XPath. Anyhow, this seems to not be very well aligned with the entire idea of DSLs and letting non programmers write tests.

After some searching i found a stack overflow problem that didn't fix my issue but anyhow… I simply used a little ruby and the capybara library to find the field myself with some case insensitive regex and the ruby detect method

It's strange to me that the text returned is in all caps (how it's styled after CSS), but the matcher is actually testing against the text in the unstyled HTML. I spent a while digging through the source code and I still can't figure out why this works.

CSS-generated content is not included in the DOM. Because of this, it will not be represented in the accessibility tree and certain assistive technology/browser combinations will not announce it. If the content conveys information that is critical to understanding the page's purpose, it is better to include it in the main document.

A falsey return value from #validate will deviate the flow and go straight to End.fail_fast.

inline-block

Also, the img is liquid/fluid, the height of the div/img are unknown, and the width is set to 800px and max-width to 80%.

vertical-align: -50%;

Requirement #2 contains an unwarranted assumption. The body needs to flow not around the sidebar, but around the sidebar's position. That may seem like splitting hairs, but it isn't -- because what if there were something floated where we want to put the sidebar? The body would flow around that space. If we could put the sidebar in that same location, we'd have a solution.

There has been some Quality-of-Life changes as well, which I really appreciate. For example, the long elevator in level 10 has been replaced with a teleporter. There's been some balance changes as well, but aside from level 10, I haven't checked them out.

Vitaly Friedman loves beautiful content and doesn’t like to give in easily.

However, the reason for these problems isn’t the theory itself, but the way the theory is interpreted - by developers and browsers.

Which HTML tag I should use to enclose such notes to add a semantic meaning of a note that may be useful to read at a given point of a tutorial, but is not part of the main tutorial flow?

A better description is in the specification itself. Why read secondary remarks when the source is written so good?

I respectfully disagree with your assessment. You are referencing the quote "It's not appropriate to use the aside element just for parentheticals, since those are part of the main flow of the document." However the OP specifically said that they are looking for a semantic element for "a note that may be useful to read at a given point of a tutorial, but is not part of the main tutorial flow". That is what "aside" is for. It's not part of the main content flow.

An admonition is a parenthetical

<aside> is appropriate if the side note "could be considered separate from the content"

<aside> is not appropriate if the side note is "a parenthetical". The W3C gives no examples of what it means.

In my opinion, the W3C definition is unnecessarily confusing and restrictive. The dictionary definition of aside is "a temporary departure from a main theme or topic", and the spec should just stick to that, rather than introducing subtle distinctions.

I believe the accepted answer is not quite correct. According to the HTML5 working draft, the <aside> element can be used to mark up side notes in certain, but not all cases:

Of course, there is no reason why you can't use <aside> for all sidenotes, if it makes your code simpler. Think of it as civil disobedience. :)

The dictionary definition of aside is "a temporary departure from a main theme or topic"

I actually think this is Not Constructive, since there's no absolute rule about which pairings can be joined into a single word or hyhenated, and it's pointless having "votes" here about each specific case. Follow a style guide if you have one, or search Google Books and copy whatever the majority do. Or just make your own decision.

a temporary departure from a main theme or topic; brief digression.

A temporary departure from a main theme or topic, esp. a parenthetical comment or remark; short digression.

(of a subject or activity) different than the one you are talking about or doing: a tangential issue

Tangentially is defined as briefly mentioning a subject but not going into it in detail, or is defined as going off in a different direction.

1a : touching lightly : incidental, peripheral tangential involvement also : of little relevance arguments tangential to the main point

The informative asides about rural life make this wine guide rather special.

a remark or story in a speech or text that is not part of the main subject:

He frequently interrupted his narrative with amusing asides.

a comment or discussion that does not relate directly to the main subject being discussed : digression

A parenthetical remark is said in addition to the main part of what you are saying or writing.

to expand (something, such as a statement) by the use of detail or illustration or by closer analysis

a remark or passage that departs from the theme of a discourse : digression The speaker inserted some often amusing parentheses during his speech.

an amplifying (see amplify sense 1) or explanatory word, phrase, or sentence inserted in a passage from which it is usually set off by punctuation explained further in a parenthesis

one or both of the curved marks ( )

Show/hide output and metadata differences in the diff editor

We are continuing an overhaul of our default startup editor in order to provide relevant extension-contributed tips and walkthroughs, intended to make both core VS Code features and extension contributions more approachable to new users.

We continued improving our support extending the Markdown renderer in Notebooks.

Limitations: When there are multiple distinct ranges of cells selected, most commands will only be executed against the first range or the focused range. We will continue improving this experience in upcoming releases.

Now VS Code's generic debugger UI supports all data breakpoint access types defined in the Debug Adapter Protocol as context menu actions in the VARIABLES view: Break on Value Read: breakpoint will be hit every time a variable gets read. Break on Value Change: breakpoint will be hit every time a variable gets changed (this action was previously available). Break on Value Access: breakpoint will be hit every time a variable is read or changed.

Warning: might be influenced by nostalgiaI'm really happy to have found this little gem on steam :)

This is the game that introduced me to RTS genre in the 90s though it might be nostalgia speaking but i absolutely adore this game.

Maybe its a bit of nostalgia, but that can't change anything on greatness of the game.

believe me, they are not just copy paste each and every single mission is completely different

If you like puzzle games, this is certainly a game for you. Well designed level progression that helps you build a good understanding of the underlying rules of the world

But there ARE invincibility frames. 0.5 seconds.

the game is designed in such a way that you don't need too many tries to figure out boss patterns or tricky platforming sections. Another nice feature is that you can warp between different areas so you don't have to do a bunch of backtracking.

Mir wurde das Spiel glücklicherweise empfohlen und möchte es weiterempfehlen :)

this game is - well not exactly bad, but it also isn't a very good game of the genre - there are some riddles and puzzles that can give you quite the headache. I like hard puzzles, I like games where all isn't quite obvious - but I also like a barrier-free gaming experience.

It feels like it was thrown together in a weekend using parts from "Think To Die" since even the successful act of feeding your chickens has the same blood-splatter-on-camera-lens that you would get from scoring in Think To Die where your goal is to kill all of your people as opposed to this where you are feeding animals, so what's with the blood splatter? It just shows a lack of attention to detail.

The blood when you get the animal to food is really off putting. It doesn't make sense, is the player suppose to be eating the animal once you get it to food? If the dev just removed that it would make this game MUCH MUCH better.

It is also the first game I've seen whose icon for "mute" is not a crossed-out speaker/note, but a symbol for "pause" in musical notation...

Inspired by Minesweeper.

The problem is the 'power-ups' (aka cheats?): the ice cubes, bombs, and especially the teleports. They seem needed to solve some levels (at least for 3 stars completion), but because they are widely available (5 of each / level) they are completely overpowered. Why would you try to solve a level without them, when you can use them? It removes the incentive to actually solve the puzzles the hard way. It breaks the game. Shame.

The Not So Good: The Dev/s seems to be in hiatus -- still waiting for the "coming soon" additional levels: Laser Land.

This is an unfinished/abandoned 2D "diving" game (basically a flyer/"platformer") where you swim through an underwater maze and collect various objects. The game wasn't finished, it's clunky, and lacks polish. The developer dumped it on Steam as a quick cash grab and ran. This should be removed from Steam until completed (if ever). I can't recommend incomplete games,

I would be really proud to show it off it was "my baby", but as a player, it's incredibly boring.

The gameplay (swim to treasure chests to loot them and kill sharks on your way) is basic.

The movement speed is painfully slow. There's nothing to do on your way.

I love puzzles.I love detective games.I love story rich adventures.I love point and click games.Somehow this title FAILED in all four departments.The gameplay is Painfully broken.

these events can break the flow of the game and force the player to repeat sections until they master the event, adding false difficulty to the game.

Made with love an care.

An ingenious and adorable piece of casual gaming. Definitely recommended.

Motivation is provided by an ever-escalating difficulty, though not to the point where you feel frustrated.

A non-pretentious yet funny and innovative physics puzzle game

A Game-design MasterpieceTake one simple game mechanic, and make the absolute most of it – that's exactly what the developers of Jim is Moving Out did, and it worked really well! The core of this game is stunningly simple: a few little boxes (furniture) inside a big box (Jim's house), one or two flying fellas (the players) and a physics engine. Think about the most creative ways you could make this into a game. Anything you think about, this game did it. What if you had to squeeze through narrow holes without breaking too much furniture? It's in the game. What if the room had wheels? Yep, it's there too. What if one of the walls was missing and you had to avoid losing the furniture? The whole co-op is about this. Zero gravity? Yes, even that is in the game.

I must say I am quite surprised by so many negative reviews. To me this little game is pure genius. There's something about it you just can't put your finger on... something strange, hard to define. The premise is utterly simple - roll left or right - but the game keeps adding new possibilities every level. And it doesn't make a fuzz about it. "Here's something completely new, it's there, who cares". The mechanics and physics are spot on and the game explores them brilliantly. Visually it's beautiful and the characters you interact with are strange and fascinating. A feeling of novelty and discovery permeates the game from start to finish.Here's my suggestion: watch some videos of the gameplay and see if it bothers you. If not, go for it, for you've barely seen the tip of the iceberg.

is a casual indie game inspired by the old Tom & Jerry (NES) game

There were a few times I felt like making notes, but never ended up needing to because the scale of the puzzles is kept manageable throughout.

A very creative concept that i`ve never seen before in a video game.

A PvP level was added just for the sake of ♥♥♥♥♥ and giggles, the only purpose of this this is game is achievement farming.

however the biomass that you collect does nothing but gives "yay for you" points

Fortunately for fans of high quality puzzle games, RUSH is anything but simple.

Colormeleons

I'll tell you my intention right away, because the language difference between us may offend you. For those things I don't understand, I apologize in advance (if you don't need my apology and feel that my apology is offensive to you, I firmly withdraw my apology).

{Graphics}☐ Great - ☐ Good - ☑ Simple - ☐ Bad{Gameplay}☐ Great - ☑ Good - ☐ Meh - ☐ Unplayable{Audio}☐ Great - ☑ Good - ☐ Nothing Special -☐ Bad{Audience}☑ Kids - ☑ Teens - ☑ Adults{Difficulty} ☐ Too easy -☑ Just Right - ☐ Easy to Play/Hard to Master - ☐ Too Hard{Story}☐ Great - ☐ Good -☐ Simple - ☐ Barely a Story - ☑ No Story{Game Time}☐ 100+ - ☐ 61-99 - ☐ 39-60 - ☐ 11-30 -☑ 0-10 {Overall}Very enjoyable Chess Puzzle Game that should appeal to both Chess and Puzzle Gamers.

Many hand made levels

Academy Games has always prided itself in the quality of its rules. Most of our rules are taught in stages, allowing you to start playing as soon as possible without needing to read everything. We are very careful about the order we teach rules and rely heavily on graphics and pictures to facilitate understanding. We also include a large number of detailed picture examples, often with 3D renders, that help you understand the context of the rules.

During development, we are constantly trying new and diverse game mechanics. The game's rules can change hour to hour as we test which ideas work best. Rules start out as just ideas and we record which ideas work and which ones don't. This forms the first development ruleset which is essentially a change log that notes why ideas do or don't. As the rules are consolidated, there are rarely any pictures to indicate what a rule is referring to,  since prototype art is also changing constantly. Terminology can also change section to section as we explore what wording works best. This makes the development rules impossible to understand for anyone other than the development team.

We also include a large number of detailed picture examples, often with 3D renders, that help you understand the context of the rules. For these reason, we generally don't start laying out the final rulebook until production art is complete. Writing and laying out a 20 page rule book like this generally takes about 3 months from start to finish, usually requiring a complete rewrite or two, and involves dozens of editors.

We use an online editing program called ProofHQ, where you and our development team will review the rules, discuss ideas, and add comments and suggestions, so that these rules are of the same high quality as our other game rules. We have used this process for years, because integrating outside eyes and ears is an invaluable asset.

The story behind this game started many years ago. My two sons were playing Pokemon, collecting cards and constantly talking about these fantasy creatures. I noticed, amazed, that after a while they knew by heart names, complicated properties and relations of somewhere around hundred, maybe more, characters! How did it happen, seemingly effortless? Did they study hard? Not in the sense we normaly think about studying. They were playing. They were having fun. And their hungry brains, like kids have, just absorbed the names, properties and relations. Seemingly effortless.

[0.5] Controls & Training & Help[0.1] Menu & Settings[0.4] Sound & Music[0.1] Graphics[0.1] Game Design[0.3] Game Story[0.1] Game Content[0] Completion time (level/game)?[0] is it Enjoyable & Fun?[0] Could it hold a spot in Favorites? (& if the Game can be repeatedly played again)[0] BONUS point: Multi-Player related[0] BONUS point: Review for VRStars received: 1.6/10

Nothing but a lazy asset flip from the Unity Asset Store:https://assetstore.unity.com/packages/templates/systems/sky-flight-full-game-template-113460And yeah, the developer bought a low poly winter landscape as well. Buy two asset kits, replace above asset kit for gameplay and then replace the map with a new winter low poly asset map to try and "hide" the laziness and using asset kits. SMH.https://www.youtube.com/watch?v=RJPJqok8iecExport, change the name to "Bird" and ready for Steam in less than 10 minutes of work! The developer couldn't even be bothered to make a way to EXIT the game much less add Steam high scores, controller support, or achievements! NOT RECOMMENDED! *Refunded this myself* ..Let your wallet talk and Please don't support lazy developers like this one.

Onto the review!

Yeah, I probably think of using foam before anyone else does.

You can add-on more copies of the game

In MetalSkies we take the approachability of Risk and combine it with greater strategic depth. That's why we've spent dozens of hours perfecting MetalSkies' gameplay mechanics and strategic balance.

Have you ever played Risk? If you're looking at this game, there's a good chance you have! I wager you know the frustration of losing your huge army to one a third its size because of a handful of random dice rolls. The pace of Risk is great, but I find it hard to take the 5th straight roll of snake eyes.

Have you ever tried Axis and Allies? I did too. And by tried, I mean just that!  Two hours after opening the box, we finished the manual and nearly died laughing. There was no way we'd have enough time left to play the game, AND we had already forgotten the first half of the directions anyway!

Fatum Betula is, arguably, a nearly perfect video game, depending upon your philosophy when it comes to criticism. If you, like me, believe that to a large extent the success of a game depends upon how well it achieved what it set out to do, I think you can get very far with such an argument.

And Ashampoo Office 8 doesn't save your files in some online cloud service but where they belong: on your PC!

# unauthenticated do # as :user do # root to: 'devise/registrations#new' # end # end

# authenticated :user, lambda {|u| u.role == "admin"} do # root to: "admin/dashboard#show", as: :user_root # end

# +devise_for+ is meant to play nicely with other routes methods. For example, # by calling +devise_for+ inside a namespace, it automatically nests your devise # controllers: # # namespace :publisher do # devise_for :account # end

This approach is preferable to overriding authenticate_user! in your controller because it won't clobber a lot of "behind the scenes" stuff Devise does (such as storing the attempted URL so the user can be redirected after successful sign in).

however, if this is relevant to just one spec, you don't necessarily need to include devise helpers to all your controllers specs, you can just explicitly include those helpers in that one controller describe block: require 'spec_helper' describe MyCoolController include Devise::TestHelpers it { } end

Scholar@UC: University of Cincinnati's self-submission institutional repository

let(:warden) do instance_double('Warden::Proxy').tap do |warden| allow(warden).to receive(:authenticate!).with(scope: :user) .and_return(authenticated?) allow(warden).to receive(:user).with(:user).and_return(user) end end let(:user) { instance_double(User) } let(:authenticated?) { true } def simulate_running_with_devise stub_const( 'Rack::MockRequest::DEFAULT_ENV', Rack::MockRequest::DEFAULT_ENV.merge('warden' => warden), ) end

Yes, you are right. That was a very bad workaround. Stubbing methods on NilClass can be compared to switching to dark side of force. Powerful but comes with a huge price. I highly don't recommend using my workaround from 1 year ago.

There is no request.env in functional tests because the functional tests are supposed to remain at the controller level.

Could you please update the wiki yourself? Thanks!

Wasn't sure if this belonged as an issue in Devise or Rails though.

For now, you will need to give the second root a different named route: authenticated :user do root to: "users#index", as: :authenticated_root end unauthenticated do root to: "main#index" end

This is a Rails change of behaviour and Rails is not going back.

class LoggedInConstraint def self.matches?(request) request.env['warden'].authenticate? end end

I'm closing this issue. If you have any problem, please comment to this issue :-)

class AuthConstraint def initialize(&block) @block = block || ->(_) { true } end def matches?(req) user = current_user(req) user.present? && @block.call(user) end def current_user(req) User.find_by_id(session[:user_id]) end end This is a flexible approach to defining route access based on any desired variable (roles, auth, etc...)

This is a great application for using route constraints.

scope module: 'authenticated', constraints: AuthConstraint.new { |user| user.present? } do # Management dashboard root 'dashboards#index' end root 'home#index'

answered

authenticated :user do root 'calendars#index', as: :authenticated_root end unauthenticated :user do root 'pages#home', as: :unauthenticated_root end

You can also specify constraints as a lambda: