suppose when you needed to make a permanent edit to the style sheet on your homepage, you opened up the CSS viewer, made the edit, and the result persists—not just in your browser, but by changing the very style sheet itself

V$A*$*=0"$1&$10+'('+,Y$0)#1+'&2$1&4$=*'&2$1$&-+#7--@$0-&*+'+=+#4$1$C-4#$-.$)#18+'C#$'&+#).10#V

Another fourteenth- century manuscript of Hautfuney’s index to Vincent of Beauvais’s Speculum historiale. The absence of rubrication and the narrower columns make the entries harder to identify although the two indexes contain the same information.

Is there a setting (or would it be possible to add one) so I can change the width of the sidebar with the annotations? On my bigger monitor it's ok, but on my normal screen I can barely see the actual PDF and the side bar covers almost half the screen. Also, I had a very hard time getting the plugin to actually find the file. It couldn't find it anywhere aside from the same folder the annotation note is in. (I tried a different folder in the vault, as well as an absolute path on my PC.) Aside from that, love the plugin! Thanks :)

Capybara can get us part of the way there. It allows us to work with an API rather than manipulating the HTML directly, but what it provides isn't an application specific API. It gives us low-level API methods like find, fill_in, and click_button, but it doesn't provide us with high-level methods to do things like "sign in to the app" or "click the Dashboard item in the navigation bar".

A major advance in user interfaces that supports creative exploration would the capacity to go back in time, to review and manipulate the history of actions taken during an entire session. Users will be able to see all the steps in designing an engine and change an early design decision. They will be able to extract sections of the history to replay them or to convert into permanent macros that can be applied in similar situations. Extracting and replaying sections of history is a form of direct man ipulation programming. It enables users to explore every alternative in a decision-making situation, and then chose the one with the most favorable outcomes.

Learning how to learn is often listed as a goal of education, but acquiring the goal-directed discipline, critical thinking skills, and cognitive self-awareness that support collection of knowledge is difficult. Advanced user interfaces may be able to help users better formulate their information needs, identify what information gaps impede them, and fabricate plans to satisfy their needs. Often as information is acquired, the users's knowledge shifts enough to require a reformulation of their plans. Information visualization interfaces and hypertext environments are a first step in supporting incidental learning, exploratory browsing, and then rapid reformulation of plans. As a refined theory of knowledge acquisition emerges, improved tools will f ollow.

Since any powerful tool, such as a genex, can be used for destructive purposes, the cautions are discussed in Section 5.

Users who expe rience empowering designs that are comprehensible, predictable, and controllable, may be inspired to pursue quality in their work products.

As John Palmer points out in his brilliant posts on Spatial Interfaces and Spatial Software, “Humans are spatial creatures [who] experience most of life in relation to space”.

Even more important is that all this isn’t about the software. It is about the system you set up. Some software nudges you, sometimes even pushes you, towards system design decisions. Take Wikis as an example. Most of them have two different modes: The reading mode. The editing mode. The reading mode is the default. But most of the time you should create, edit and re-edit the content. This default, this separation of reading and editing, is a small but significant barrier on producing content. You will behave differently. This is one reason I don’t like wikis for knowledge work. They are clumsy and work better for different purposes.

Bret Victor: email (9/3/04) Interface matters to me more than anything else, and it always has. I just never realized that. I've spent a lot of time over the years desperately trying to think of a "thing" to change the world. I now know why the search was fruitless -- things don't change the world. People change the world by using things. The focus must be on the "using", not the "thing". Now that I'm looking through the right end of the binoculars, I can see a lot more clearly, and there are projects and possibilities that genuinely interest me deeply.

flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepoflatpak install flathub org.chromium.Chromium

Error: Index signature for type 'string' is missing in type 'someInterface'. Because `interface` can be re-opened

// Second case (unexpected) interface C { [x:string]: number } interface D { x: number } const d: D = { x: 1 }; const c: C = d; // error // Type 'D' is not assignable to type 'C'. // Index signature is missing in type 'D'.

So now the question is, why does Session, an interface, not get implicit index signatures while SessionType, an identically-structured typealias, *does*? Surely, you might again think, the compiler does not simply deny implicit index signatures tointerface` types? Surprisingly enough, this is exactly what happens. See microsoft/TypeScript#15300, specifically this comment: Just to fill people in, this behavior is currently by design. Because interfaces can be augmented by additional declarations but type aliases can't, it's "safer" (heavy quotes on that one) to infer an implicit index signature for type aliases than for interfaces. But we'll consider doing it for interfaces as well if that seems to make sense And there you go. You cannot use a Session in place of a WithAdditionalParams<Session> because it's possible that someone might merge properties that conflict with the index signature at some later date. Whether or not that is a compelling reason is up for rather vigorous debate, as you can see if you read through microsoft/TypeScript#15300.

An interface can be re-opened. Whereas a type is sealed. So a solution for microsoft/TypeScript#15300 is to map the interface (which can be defined in many places) to a type.

Senseplay is an all-in-one ecosystem of biosensing hardware and software SDK to build anything from brain-computer interfaces, neurogames, biofeedback controlled installations and educational applications.

If you really don't want to use any, you could use an empty interface - {} - instead:

This is one of the points made in TheMythOfThePaperlessOffice -- that workplaces often shift from more efficient paper-based technologies to less efficient electronic technologies (electronic technologies can be either more or less efficient, of course) because computers symbolize The Future, Progress, and a New Way Of Doing Things. An office on the move, that's what an office that uses cutting-edge technology is. Not an office that is stuck in the past. And the employees are left to cope with the less productive, but shinier, New Way. -- ApoorvaMuralidhara

Hypothesis permet d’annoter et de commenter très simplement une page web, de manière collective

a principle I use is: If you have an accessor, use the accessor rather than the raw variable or mechanism it's hiding. The raw variable is the implementation, the accessor is the interface. Should I ignore the interface because I'm internal to the instance? I wouldn't if it was an attr_accessor.

Also, Sandi Metz mentions this in POODR. As I recall, she also advocates wrapping bare instance variables in methods, even when they're only used internally. It helps avoid mad refactoring later.

But suddenly I'm using a raw instance variable, which makes me twitch. I mean, if I needed to process has_sauce before setting at a future date, I'd potentially need to do a lot more refactoring than just overriding the accessor.

kdiff3 can be used solely with keyboard, so 5 conflict file takes when reading the code just few minutes.

Here's where I start to have a preference for Svelte; the two are very similar but once I got used to Svelte I found that React felt like jumping through hoops. You can't create a worker instance, it has to go in a useRef, and then you can't easily pull code out into a function without then requiring useCallback so it can be a safe dependency on useEffect. With Svelte I write code that's closer to "plain" JavaScript, whereas in React more of my code is wrapped in a React primitive.

Trailblazer::Developer.wtf?(Signup, ctx)

Admittedly, both the signature and the return values of invoke feel a bit clumsy. That’s becaus we’re currently working with the low-level interfaces.

You don’t have to stick to the task interface! The [circuit interface] is a bit more clumsy, but gives you much better control over how ctx and signals are handled.

The circuit interface is a bit more clumsy but it gives you unlimited power over the way the activity will be run.

Instead of having this confusing maze of lambdas, regexes, and strings, we could, in theory, introduce a single entry point of configuration for Sprockets to use, and in that file declare all assets we wanted to compile. Well, that’s exactly what the manifest.js file is.

I guess in short you could say that I don’t like this interface very much.

In object-oriented programming, information hiding (by way of nesting of types) reduces software development risk by shifting the code's dependency on an uncertain implementation (design decision) onto a well-defined interface. Clients of the interface perform operations purely through it so if the implementation changes, the clients do not have to change.

Programming to interfaces is at the core of flexible structure.

The more important point comes from a program design perspective. Here, "programming to an interface" means focusing your design on what the code is doing, not how it does it. This is a vital distinction that pushes your design towards correctness and flexibility.

My understanding of "programming to an interface" is different than what the question or the other answers suggest. Which is not to say that my understanding is correct, or that the things in the other answers aren't good ideas, just that they're not what I think of when I hear that term.

Programming to an interface means that when you are presented with some programming interface (be it a class library, a set of functions, a network protocol or anything else) that you keep to using only things guaranteed by the interface. You may have knowledge about the underlying implementation (you may have written it), but you should not ever use that knowledge.

If the program was important enough, Microsoft might actually go ahead and add some hack to their implementation so the the program would continue to work, but the cost of that is increased complexity (with all the ensuing problems) of the Windows code. It also makes life extra-hard for the Wine people, because they try to implement the WinAPI as well, but they can only refer to the documentation for how to do this, which leads to many programs not working as they should because they (accidentally or intentionally) rely on some implementation detail.

Abstract myself from the how it does and get focus on what to do.

Say you have software to keep track of your grocery list. In the 80's, this software would work against a command line and some flat files on floppy disk. Then you got a UI. Then you maybe put the list in the database. Later on it maybe moved to the cloud or mobile phones or facebook integration. If you designed your code specifically around the implementation (floppy disks and command lines) you would be ill-prepared for changes. If you designed your code around the interface (manipulating a grocery list) then the implementation is free to change.

It's more like providing an Employee object rather than the set of linked tables you use to store an Employee record. Or providing an interface to iterate through songs, and not caring if those songs are shuffled, or on a CD, or streaming from the internet. They're just a sequence of songs.

This assumes that the module has been given a well-defined, stable description (the interface in the sense of information hiding).

Source Code is a UX to interface with the raw machine.

I can't add special props and keywords to every single component I have and will ever create for this to work.

Explicitly exposing any attributes that might get overridden by a parent seems impractical to me.

Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.

Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.

Rule of Silence: When a program has nothing surprising to say, it should say nothing.

Write programs to handle text streams, because that is a universal interface.

multiple selections, keyboard layout agnostic, SOV (subject–object–verb) constructs and simple interaction with external programs

The gem provides a command line utility for checking passwords.

This is one possible path to take in that you simply reject the registration and ask the user to create another password. Per NIST's guidance though, do explain why the password has been rejected:

TUI

Avoiding complicated outlining or mind-mapping software saves a bunch of mouse clicks or dreaming up complicated visualizations (it helps if you are a linear thinker).

Might be a little too low-level (even with GUIs) for some teams of users. GPG and Git both require some setup and experience in these tools, or the willingness to learn. Porting a GPG key from machine to machine is not trivial.

    bar: {        (s: string): number;        (n: number): string;    }

(name: string): string

Unfortunately, numerous widely-used tagless-final interfaces (like Sync, Async, LiftIO, Concurrent, Effect, and ConcurrentEffect) encourage you to code to an implementation.

with either hand (one pen is positioned for each hand)

giving the human the minute-by-minute services of a digital computer equipped with computer-driven cathode-ray-tube display

interfaced in many different ways

One consequence of thisposition is a more radical understanding of the sense in whichmateriality is discursive (i.e., material phenomena are inseparable from theapparatuses of bodily production: matteremerges out of and includes as part of itsbeing the ongoing reconfiguring of boundaries), just as discursive practices arealways already material (i.e., they are ongoing material (re)configurings of theworld) (2003: 822).Brought back into the world oftechnology design, this intimate co-constitution ofconfigured materialities with configuring agencies clearly implies a very differentunderstanding of the ‘human-machine interface’.

Raccomandazione 3.6g - Definire un modello di governance del dato e progettare automatismi organizzativi e tecnologici

la estructura ontológica del diseño está compuesta de las interrelaciones entre la herramienta, el usuario y la tarea o propósito, todos reunidos por la interfaz.

<table style="width:100%"> <tbody><tr> <td> </td> <td> </td> </tr> </tbody></table>

Neither Apple nor Microsoft really captured the essence of what made the Smalltalk system powerful. They used it as a model to make computers more accessible, but they left out the aspect of letting people bend the system to their will, to customize it to be just what they want. Their systems were really an object-oriented facade over a traditional, non-object-oriented system. They lacked a consistent metaphore of everything being an object. The web has been even more stultifying in this regard (I mean the web interface), though Firefox has helped some, so I hear, with the concept of browser extensions.

Jessica Helfand in her essay The Dematerialism of Screen Space (2001) critiques the phenomenon of design practise being led by developments in software engineering. She argues that designers should take the initiative: “design must submit to a series of commands and regulations as rigourous as those that once defined Swiss typography. Aesthetic innovation, if it indeed exists at all, occurs within ridiculously preordained parameters: a new plug-in, a modified code, the capacity to make picture and words ‘flash’ with a mouse in a non-sensical little dance. We are all little filmmakers, directing on a pathetically small screen – yet broadcasting to a potentially infinite audience. This in itself is conflicting (not to mention corrupting), but more importantly, what are we making? What are we inventing? What are we saying that has not been said before?” Helfand here is referring to the web, but her argument applies equally well to designing tablet publications. Designers of book and magazine apps should be asking themselves those last three questions. Since tablet publishing conventions are in the process of being formed (like child invention), we have a unique opportunity right now to influence their direction.

Some key themes arise from the two NNG reports on iPad usability: App designers should ensure perceived affordances / discoverability There is a lack of consistency between apps, lots of ‘wacky’ interaction methods. Designers should draw upon existing conventions (either OS or web) or users won’t know what to do. These are practical interaction design observations, but from a particular perspective, that of perceptual psychology. These conclusions are arrived at through a linear, rather than lateral process. By giving weight to building upon existing convention, because they are familiar to the user, there is a danger that genuinely new ideas (and the kind of ambition called for by Victor Bret) within tablet design will be suppressed. Kay’s vision of the Dynabook came from lateral thinking, and thinking about how children learn. Shouldn’t the items that we design for this device be generated in the same way?

The document argues that the use of illusionary surfaces and objects will lead to a more intuitive and pleasurable experience for the user. It also, yet again, looks to prior conventions for solutions rather than starting afresh.

Every theorem of mathematics, every significant result of science, is a challenge to our imagination as interface designers. Can we find ways of expressing these principles in an interface? What new objects and new operations does a principle suggest? What a priori surprising relationship between those objects and operations are revealed by the principle? Can we find interfaces which vividly reveal those relationships, preferably in a way that is unique to the phenomenon being studied?

les interfaces ne sont nullement régulées par cette structure de regard, mais bien par une structure d'action.

TextpressoCentral

There is a lot of evidence that quite subtle changes to user interfaces can have dramatic effects on how the interfaces are used. For example, the size of a search box or the text that accompanies it can considerably influence the queries that people submit.

The whole gendered usage of hearts seems to have escaped Twitter. So does the fact that people fave (with stars) in complex ways - they are bookmarks, they are likes, they are nods of the head. But they are not indicators of love. I feel very weird loving tweets by random men I've only just started a conversation with. Not that there's anything wrong with feminine. But women - and men, in their own ways - are well-aware of how feminized visual signals get read by others, and in an identity space like Twitter, I suspect that will really minimize usage. Or at least until we all get used to it.

MyInterfaceImpl

The on-line annotations were also more likely to be anchored in complete sentences.

The book or physical instance, then, is one of many levels of address.

Because a text can be queried at the level of single words and then related to other texts at the same level of abstraction: the table of all possible words could be defined as the aggregate of points of address at a given level of abstraction (the word, as in Google’s new n-gram corpus).

the interface currently works quite slowly, much slower than regular web content.

Affinity Diagramming