Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

My favorite Replit shortcuts: ⌘ shift i - toggle agent sidebar ⌘ i - cycle through build, plan, & edit modes ⌘ shift b - toggle folders sidebar ⌘ k - command bar ⌥ r - refresh preview These shortcuts can be configured in the 'user settings' tab in...

12,455 Aufrufe • vor 9 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Obsidian 1.11 is now available for desktop and mobile! Mobile: - The interface has been refreshed to improve the editing and reading experience. - Lock Screen, Control Center, and Home Screen widgets let you quickly create a new note, open a specific note, open daily note, open search, or open Obsidian. - When scrolling down in a note, the navigation hides to maximize screen space for reading. - New sidebar navigation for switching sidebar tabs and actions, aligned to the bottom for better ergonomics. - Added double-tap to switch a note from reading mode to editing mode. iOS - Shortcuts to open a note, open daily note, capture to a note. Capture shortcuts allow you to append or prepend text to a note, without opening the Obsidian app. - Siri integration such as "Capture using Obsidian", "Capture to Obsidian", "Open my daily note in Obsidian", "Search in Obsidian". -Searching for Obsidian in Spotlight shows additional actions: New Note, Search, and Daily Note. Android - New widgets: Open Note, New Note, Search, Daily Note, Open Obsidian. You can add multiple widgets of the same type to open different files, or trigger different search queries. - Quick Settings Tile and new shortcuts: Open note, Daily note. Editor - Markdown links are now supported in text and list properties. Internal links are automatically updated when the destination file is moved or renamed. - When text is selected, pasting a URL into the editor will convert the selection into a Markdown link using the URL. Settings - New "Keychain" settings section for storing plugin secrets. A guide for plugin developers is published in our docs. - Added icons to settings sections. - Community Plugins › Automatically check for plugin updates. Obsidian will check for plugin updates in the background every 3 days, or after the app updates. - New setting Files & links › Default file to open. Choose between "Last opened files", "New note", "Specific note", or "Daily note". - The daily note format can be selected from a list of predefined formats. Obsidian URI - New, open, and daily URI actions now support a new paneType param.

Obsidian

191,929 Aufrufe • vor 9 Monaten

long time no posting, here's some of the stuff we released in helium recently: - customizable keyboard shortcuts on all platforms - automatic updates on windows - frameless mode (previously zen mode), with floating sidebar, is now out of beta and included in settings by default - improved fingerprint noising: fixed the canvas noising algorithm and added protections against analysis attacks (thank you Cynthia 🐈 for your report, research, and assistance) - tab URL copying, one or multiple, formatted as a list with line breaks - manual tab hibernation, with an option to hibernate all tabs except for selected/active ones - an option to close tabs to the left (or above, in vertical layout) - redesigned toast notifications, now anchored to the active web page, and no longer blinding in dark mode - toast notification about newly opened background tabs in frameless mode (can be disabled in settings) - redesigned the infobar, it no longer looks out of place - improved QR code generation, now it's actually useful - downloads bubble is now shown instead of the full page whenever applicable - kagi search now supports reverse image search from image context menu - frameless mode animations are now smoother - better color contrast in light and dark modes - a lot of bug fixes and other minor improvements all of these changes are present in the latest version of helium. if you're using helium on windows, please update to the latest version, so your browser can be updated automatically from now on!

Helium

185,981 Aufrufe • vor 4 Monaten

When I’m trying to improve the user experience of my applications, one of the most valuable things is being able to see an entire user flow as a storyboard. Not just one screen or screenshot at a time. This is something I love using the `/visual-plan` skill for. You can describe any flow you want, and the agent will look through your code and wireframe out a storyboard of what the flow looks like. Then you can visualize the steps in a simplified way and spot areas to improve. Recently, I found that in certain flows we were still asking for organizations, even though I thought I had gotten rid of that and made it automatic. A quick storyboard let me see all the different code paths in a simple, visual, intuitive way. Spot the areas of the flow I didn’t want. And have the agent fix it. Sign up, onboarding, and setup flows are usually some of the most important experiences in your app. And usually the least looked at. Especially because it can be hard to reproduce every flow, for every situation, for every user type, feature flag, or whatever else you have. The `/visual-plan` skill lets you visualize any part of your code. Either to understand the current state, plan out a new state, or recap updates that were made. I’m pretty addicted to this skill. I use it for a lot of other things too, so let me know if you want to see videos on those. And of course it’s all open source. You can grab it on my GitHub. I'll link to it in the thread. If you try it, let me know your feedback.

Steve (Builder.io)

148,886 Aufrufe • vor 3 Monaten

A little look behind the scenes: Many of you asked how I handle switching from SwiftData & CloudKit to Firebase and a different way of sharing entries with your friends. Previously, there was no need to create an account and the app just used the user's iCloud ID in the background to "sign up". Why did I do this? SwiftData is really nice to use but after working with it for over a year now, it feels still quite unstable, buggy and errors are super hard to track. Same goes for CloudKit and the CloudKit sharing that I implemented. For a growing app, in my opinion, it's just not feasible to use because errors happen regularly, you don't really know if the data is stored (and shared) correctly and the documentation on CK is just bad. I have big plans for this app (reacting to your friends' entries, Apple Health integration, tagging multiple friends in entries etc.) and all of it is now much simpler - and faster to build. The Migration part When an existing user starts the app, a little migration sheet with a couple of steps opens which can't be dismissed. The goal is that the user maintains all entries and can use the app like before :) Steps: 1) Create an Account using Apple Sign In and Firebase Auth 2) Migrate your user profile (profile picture etc.) and all your friends from SwiftData to Firestore. Here I basically iterate over all the data that is there, run a custom conversion for all the fields (some things need to be stored differently) and save them. Profile Images are now saved in Firebase Storage 3) Migrate all entries to Firestore the same way. Images and Voice Notes are now saved in Firebase Storage (that might take a bit of time, video is sped up) 4) After that, migration is basically done and the user can use the app like before. In the settings, the user can now log out or delete the account, things that weren't possible before. If for any reason the migration has to be done again, this can be triggered from the settings as well. How do I decide if a user needs to migrate? Previously, I saved the user's profile in SwiftData under a specific key (simplified). If the app finds something under this key, user is prompted for a migration. New users don't have to run through the migration. They simply start fresh with the Apple Sign in in the onboarding like seen in the referenced post. How does sharing entries now work? For sharing, I create deeplinks using branch . io now. These links basically work like every other Invite Link you've received or created. The friend opens the link, can accept your invitation and now both of you are connected as buddies. Previously using CloudKit Sharing, this process took two steps - each user had to share a link to give access to their entries. The process now is much simpler and better understand for the user. Developing the migration Tbh I thought this would be way quicker. In the end it was > 100 commits since I had to basically change every screen in the app. Working with SwiftData is quite different to how things work with Firebase (and most other frameworks), so every interaction where data was involved had to be reworked. Now the app runs on a combination of Firestore, Cloud Functions and Firebase Storage. In terms of memory, the app feels notably faster and only needs around 1/4 of the memory bandwidth it needed before. Let's see if it will be worth it! All in all super happy with the new flexibility for the app and not being limited by the technology anymore 👀

Fabian Gruß

26,827 Aufrufe • vor 1 Jahr