Network graphs, maps - it's why canvas is the UI du jour, to go beyond linearity, lists and trees

It feels like a William Playfair moment - the idea that numbers can be represented in graphs, charts - can now be applied to anything else. We're still imagining the forms; network/knowledge graphs are trendy (to what end though) - what else?

This seems to be more than just a thin wrapper like https://github.com/rainerschuster/final-form-material-ui was. I kind of prefer the simplicity of focus of final-form-material-ui.

This appears to be attempting to do too much. Though if it gives you exactly what you want, great.

¿cuáles son experiencias de usuario vs categorías sociales existentes?

Essa página sobre Gestalt tem um conteudo sensacional, ótimo. Conteúdo que normalmente não é ensinado em nenhuma aula de design. Vai além do básico sobre Gestalt.

Sao principios gerais que explicam muito mais que os outros principios de Gestalt.

ui

Creating a "signpost user interface" can help to uncover directions to take in digital contexts as out of sight is out of mind. Having things sit in your way within one's note taking workflow can remind them to either link things, or move in particular directions for discovering new avenues of thought.

Example: it would be interesting if Jerry's The Brain would have links directly to material in Flancian's Agora to remind him to search or find relevant material there. This could help with combinatorial creativity with inputs from others, though it needs to be narrow so as not to result in rabbit holes which draw away attention.

Link to: https://hypothes.is/a/iQvo7l1zEe6dZ5_9d9rrVw

Jerry Michalski says that The Brain provides him with a "neighborhood perspective" of ideas when he reduces the external link number for his graph down to 1.

This is similar to Nicholas Luhmann's zettelkasten which provided neighborhoods of related notes based on distance from any particular note.

Also similar to oral cultures who relied on movement through their environment for encoding memories and later remembering them. [I'll use the tag "environmental memory" to track this until a better name comes along.]

This is an extremely important concept, no one team can create every solution possible most time workers do what works despite what would, in theory work better. Developing a new work flow involves a series of tests and a change in boundaries that might be risky for the company at large. But no one team knows every solution and multiple teams coming at a problem is good.

Having a variety of methods to get to a solution is exteremely important as a lot of people can come at a problem with different angles and solve it differently. However, this can breed confusion as to which way is the "right" way and which way is the "wrong way" It also may seem like their way might not work but we should do a though examination from their side to see why they think it might work and maybe square that up with the harsh reality.

yeah

https://web.archive.org/web/20230502113317/https://wattenberger.com/thoughts/boo-chatbots

This seem like a number of useful observations wrt interacting with LLM based tools, and how to prompt them. E.g. I've seen mention of prompt marketplaces where you can buy better prompts for your queries last week. Which reinforces some of the points here. Vgl [[Prompting skill in conversation and AI chat 20230301120740]] and [[Prompting valkuil instrumentaliseren conversatiepartner 20230301120937]]

Remove Add_FIELD_DATA column

!- insight for : user interface design - 3 feet field of view is critical - 160 degrees - VR and AR is able to meet this requirement

This describes one of the most pleasing hacks I've ever come across. I just now tracked it down and added it to my bookmarks. (Not sure why it wasn't already there.)

You could also conceive of going one step further. When your app (doesn't actually have to be a game, though admittedly it's much easier for you if it is) is compiled with tweak.h, it gives it the power to paint the source file on the screen—so you don't actually have to switch over to your text editor to save it, etc. Suppose you want to provide custom inputs like Bret Victor-style sliders for numeric values. You could edit it in your text editor, or you could derp around with it in-app. Tweaking the value in-app should of course both update it wrt the app runtime but also still write the file to disk, too, so if live reloading is turned on in your text editor, whatever changes you make inside the live process image gets synced out.

kong

利用依赖倒置，我们可以把 CalculateCart 定义在依赖关系的底层，由限时折扣，会员优惠这些 Git 仓库去做接口实现。

服务端数据集成的方式。 数据集成可以实现任意复杂的需求，是对需求形态限制最小的集成方式。

混合型 UI， 离散型 UI。

购物车是典型的混合型 UI。没有哪个 Git 仓库，可以声称对界面上的某个区块负责。

会员价和限时特价，都想给商品打上自己的标。但是实际算价格的时候，得看哪种优惠算得的价格更低。

在这种比较恶心的复杂需求下，如何最大化 autonomy 呢？

Some Test Scenarios: * Single or multi-browser testing * Downloading an app to the desktop * Installing browser extensions

This is now fixed. If the Sign In button is used then if the user/Display name does not exist then the page is cleared and refreshed.

The callback seems to receive 2 arguments. e and reactChild

In the past I got the selected value using e.target.value This seems to work.

Not sure of the use of the reactChild element that the callback receives.

Another important note regarding recording the recorded value of the select is noted in the "value" prop explanition ( below, on this very page )

You might want to turn it into a span for any number of reasons. eg if you want one word in a sentence to be another color / style eg. I wear a red hat

<Typography component="div" > Contact Details : <Typography component="div" display="inline" variant="body2" color="black"> elroinoronha2@gmail.com </Typography> </Typography>

(copy it to a code editor for the code to make sense)

is a good solution since it defeats the "h1 cannot be a child of h1" DOM error + let us use the sx prop.

We would not be able to use sx prop to style the inline part if we would use the native <span> component ie. <Typography > yo mama <span> so fat </span> </Typography>

You would have to use inline style styling instead.

This <Box/> method is the preffered way of doing it. The <Paper/> method too is a good idea. The basic reasoning is that only MUI components support the sx prop ie. only they can fully use the MUI systems features. Thus, it doesnt make sense to use the native <img/> component in the markup, as it does not support sx

The SX prop does not work with non MUI components eg. native <img/> component. To style this, you will have to use the native inline styling ie. <img style=" ............". /> If you want to style the img and use some MUI system specific features, ie. you need to use sx ; do the following. Use <Box component="img" sx={{ }} /> instead. This supports the sx prop, thus your image will be customizable with sx prop.

The color prop does not support all MUI theme colors / their shades DIRECTLY through its color prop. Eg. The color prop supports primary but not primary.main/dark. It does not support the palette warning color at all.

To remedy this you have 2 options 1 BETTER -- give the icon the desired color through the sx prop OR 2. wrap the icon in a box and give the box to desired color

https://dancohen.org/2019/07/23/engagement-is-the-enemy-of-serendipity/

Dan Cohen talks about a design change in the New York Times app that actively discourages exploration and discovery by serendipity.

This is similar to pulling out digital copies of books you're looking for instead of going to the library, tracking down the book on the shelf and in the process seeing and experiencing the books on the shelf which are nearby, or even the book that catches your eye across the aisle, wasn't in your sphere of search or interest, but you pick it up anyway.

How can we bring this sort of design back to digital experiences?

It's not just the algorithmic feeds which are narrowing our interests and exposure, but the design of our digital spaces as well.

Lots of interesting libraries for React UI components.

This plugin adds two new views to Obsidian, the breadcrumb matrix/list view, and the breadcrumbs trail view. The wiki has more in-depth info on the plugin than the readme.

<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Eleanor Konik</span> in 2021-07-24: Showcases, Link Cards, & Better Tablet Toolbars (<time class='dt-published'>07/29/2021 12:14:15</time>)</cite></small>

https://www.codica.com/blog/latest-ui-ux-design-trends/

http://epeus.blogspot.com/2005/10/tags-and-cognitive-load.html

The level of complexity to using some of these tools is also a huge hurdle for the everyday user as well. Some require deep knowledge of the tool along with coding ability as well.

Perhaps this complexity barrier will come down over time, but some projects don't seem to be working toward making things easier and simpler for the end user.

More than 86% of characters in Chinese function as significs, a linguistic term indicating an association to the word's meaning. Sometimes these meanings can change with time and drift from original meanings.

The drift can be interesting and important from the perspective of historical linguistics as well as to give clues to changes in culture.

An example in English might be the use in computer user interfaces that include telephone handset images or old 3.5" floppy disk images used to respectively indicate "call" or "save" despite the fact that these items have either changed shape or are no longer commonly used.

Perhaps a wiki (single or multiple user) would be a better tool for this?

Note the use of customers here. Who are the publishers effecting? This sentence would seem to imply that their customers are using these services because they are better (better UI and ease-of-use), which is something I recall having read about in articles in the past.

Link to that reference here if I can find it. I think it was a journal article in Science perhaps?

Image snippet on left side gets squeezed and links are hanging out in the open on macbook . Needs fixing

https://scribe.rip/

https://www.heise.de/newsticker/meldung/Missing-Link-Luhmanns-Denkmaschine-endlich-im-Netz-4364512.html?seite=all

An interesting overview of Niklas Luhmann's zettelkasten and how it was digitally archived with some potential ideas about how this might be done for other such systems or for ideas for those building and designing their own digital gardens.

Machine translation:

Luhmann names the disadvantage that the "originally running text is often interrupted by hundreds of slip sheets" - a problem that was solved in the digital edition described below using a navigation system.

One of the problems Luhmann had with his paper version of a zettelkasten is solved by the digital edition's navigation.

https://blog.remark.as/introducing-private-letters