# View Published articles for View. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## A visual guide to troubleshooting search performance using Query Insights dashboards DevFeed: [A visual guide to troubleshooting search performance using Query Insights dashboards]() Original publisher: [Read original article]() Author: Chenyang Ji Published: 2026-09-04T20:11:52Z Content type: tutorial Language: en Sources: [OpenSearch]() Topics: [Amazon OpenSearch Service](), [dashboards](), [Monitoring](), [Latency](), [cpu]() Tags: [blog](), [configuration](), [cpu](), [dashboards](), [distribution](), [how-to](), [index](), [latency](), [memory](), [monitoring](), [navigation](), [opensearch](), [performance](), [real-time](), [technical](), [troubleshooting](), [view](), [visualization]() ### AI overview A visual guide to using OpenSearch Query Insights dashboards to investigate slow searches and unexpected resource usage. It covers the Live Queries and Top N Queries views, interactive visualizations, configuration, and metrics such as latency, CPU, and memory. ### Source excerpt OpenSearch Query Insights dashboards provide interactive visualizations for monitoring live queries, analyzing top N query performance, and viewing individual query details. This post explores each visualization and shows how to use visualizations to troubleshoot search performance issues. The post A visual guide to troubleshooting search performance using Query Insights dashboards appeared first on OpenSearch. ## Airflow Survey 2025 DevFeed: [Airflow Survey 2025]() Original publisher: [Read original article]() Author: Apache Airflow Published: 2026-01-22T00:00:00Z Content type: article Language: en Sources: [Apache Airflow Blog]() Topics: [airflow](), [data](), [CSV]() Tags: [2025](), [airflow](), [analysis](), [apache-airflow](), [community](), [csv](), [download](), [form](), [graphics](), [interactive](), [report](), [responses](), [share](), [survey](), [users](), [view]() ### AI overview This page presents the Airflow Survey 2025 interactive report, hosted by Astronomer and sponsored and supported by the Apache Airflow community. The supplied evidence does not include the survey findings. ### Source excerpt The interactive report is hosted by Astronomer. The Apache Airflow community thanks Astronomer for running this survey, for sponsoring it and providing the report in this form, and for their effort in marketing, analysis, and preparing the graphics. View raw data Download survey responses (CSV) ## How to Fix Kafka to ClickHouse® Performance Bottlenecks DevFeed: [How to Fix Kafka to ClickHouse® Performance Bottlenecks]() Original publisher: [Read original article]() Author: Alberto Romeu Published: 2025-12-30T00:00:00Z Content type: tutorial Language: en Sources: [Tinybird]() Topics: [clickhouse](), [Kafka](), [Optimization](), [Structured-data]() Tags: [best-practices](), [clickhouse](), [distribution](), [how-to](), [kafka](), [optimization](), [partition](), [performance](), [pipeline](), [scalable-analytics-architecture](), [schema](), [view]() ### AI overview A tutorial on optimizing performance in Kafka-to-ClickHouse pipelines through schema optimization, Materialized View tuning, partition distribution strategies, and throughput practices. ### Source excerpt Learn how to optimize your Kafka to ClickHouse pipeline performance with schema optimization, Materialized View tuning, partition distribution strategies and throughput best practices. ## Multiple monitors support DevFeed: [Multiple monitors support]() Original publisher: [Read original article]() Author: Nenad Rakocevic (noreply@blogger.com) Published: 2025-04-15T09:08:00Z Content type: release Language: en Sources: [Red]() Topics: [Red](), [GUI](), [Windows](), [Script](), [App]() Tags: [app](), [display](), [monitors](), [os](), [screen](), [script](), [view]() ### AI overview This blog entry describes Red View engine support for multiple monitors. It explains screen faces, virtual coordinates, scaling factors, monitor changes, and launching Red consoles and apps on different displays. View adjusts windows for displays with different DPI values, while Windows 7 uses a fallback API and some window-coordinate and child-window limitations remain. ### Source excerpt Here is a short blog entry just to explain the newly added multiple monitor support to View engine. Screen faces Each connected monitor gets associated with a screen face in system/view/screens list. You can check that all monitors have been detected correctly using (two monitors in this case): >> length? system/view/screens == 2 Each screen's /offset indicates the screen position using virtual screen coordinates. The main screen gets a (0, 0) offset. All other screens are positioned relatively to that, in the same virtual space. Screen sizes are also expressed in virtual coordinates. Screen's scaling factor is exposed in the /data facet as a float value. Monitors properties changes and adding/removing detection are also supported, updating the screens list. Windows present on removed monitors are automatically closed by the OS. A simple display-geometry.red script is provided to show how screen faces reflect the monitors topology in that virtual space: That script will also output the screen details in the console: >> do %tests/displays-geometry.red 1 - offset: (0, 0) size: (3840, 2160) scaling: 150% 2 - offset: (1165, 2160) size: (1480, 320) scaling: 100% NB: I am using a little 11.9inch screen below my main display for developing this specific feature, as it takes very little extra space on my desk. Red apps on multiple screens You can now launch Red consoles and apps on any display, the app will open on the screen it was launched from, using the specific scaling value of that screen. A get-current-screen function has been provided to return the current screen (where the mouse cursor is currently located). When displays have different scaling factor or DPI, View will adjust the window and its content to fit that scaling factor. This also works when dragging a View window between displays with different DPI, the window and its content will resize accordingly. On Windows, the API View requires, are not supported on pre-Windows8 platforms. So a new Windows7 compilat ## How to Use Discord's In-Game Overlay to Talk While Playing on PC DevFeed: [How to Use Discord's In-Game Overlay to Talk While Playing on PC]() Original publisher: [Read original article]() Author: Locke Published: 2025-04-10T00:00:00Z Content type: article Language: en Sources: [Discord Blog]() Topics: [Discord](), [pc](), [GUI](), [Streaming]() Tags: [desktop](), [discord](), [display](), [how-to](), [invites](), [layout](), [notifications](), [pc](), [screen](), [talk](), [video](), [view](), [voice](), [windows]() ### AI overview This guide explains how to use Discord's In-Game Overlay on Windows while playing on PC. It covers voice and video calls, screen sharing, gameplay streaming, notifications, and customizing the overlay layout with the default keyboard shortcut. ### Source excerpt Discord's In-Game Overlay lets you join voice and video calls, see who's talkin', and stream your gameplay without ever having to alt-tab out of your current match! Learn how it works and how you can customize it to your liking. ## Optimizing Data Reliability: Heroku Connect & Drift Detection DevFeed: [Optimizing Data Reliability: Heroku Connect & Drift Detection]() Original publisher: [Read original article]() Author: Siraj Ghaffar Published: 2024-06-26T02:43:00Z Content type: article Language: en Sources: [Heroku]() Topics: [Heroku Postgres](), [Heroku](), [Database](), [Monitoring](), [ui]() Tags: [crm](), [data](), [database](), [developer-tools](), [engineering](), [heroku](), [heroku-connect](), [heroku-postgres](), [integration](), [monitoring](), [salesforce](), [sync](), [ui](), [view]() ### AI overview This Heroku article explains improvements to Heroku Connect's drift detection. It describes how Salesforce data is polled into Heroku Postgres, why long-running transactions can cause missed changes, and how the updated feature detects and addresses drift more efficiently while maintaining eventual consistency. ### Source excerpt Heroku Connect makes it easy to sync data at scale between Salesforce and Heroku Postgres. You can build Heroku apps that bidirectionally share data in your Postgres database with your contacts, accounts, and other custom objects in Salesforce. Easily configured with a point-and-click UI, you can get the integration up and running in minutes without [...] The post Optimizing Data Reliability: Heroku Connect & Drift Detection appeared first on Heroku. ## Building a Note-Taking App in Compose DevFeed: [Building a Note-Taking App in Compose]() Original publisher: [Read original article]() Author: Doximity Published: 2023-07-05T19:47:00Z Content type: tutorial Language: en Sources: [Doximity]() Topics: [Jetpack Compose](), [App](), [Code](), [Template]() Tags: [app](), [architecture](), [build](), [building](), [class](), [clean-architecture](), [code](), [collect](), [compose](), [data-class](), [di](), [extension-function](), [flow](), [icons](), [implement](), [koin](), [list](), [state](), [state-management](), [view]() ### AI overview A case study showing how to build a note-taking app with Jetpack Compose. It models note state, renders the notes UI, collects note data through a presenter and Clean Architecture use cases, and plans events for adding, editing, checking, and deleting notes. ### Source excerpt In this case study, we will build a note-taking app that lets the user add, edit and delete notes. It uses Compose for both the view and presentation layers! Note: This is a follow up to Part 1: Simplifying State Management with Compose and assumes the reader is already familiar with Jetpack Compose. The Template I find it useful to start with the model that represents the state of the screen we're building. It will have a list of notes, with each note containing properties for the text and checkbox: data class NotesUiModel(val notes: List) : UiModel { data class Note(val text: String, val isChecked: Boolean) : UiModel } It'll be the job of the presenter to produce this model. Initially, let's implement a stub to return an empty list of notes (we'll ignore parameters for now): class NotesListPresenter : Presenter { @Composable override fun present(params: Unit): NotesUiModel { return NotesUiModel(notes = emptyList()) } } Then we can build our view to render the model that's returned by the presenter: @Composable fun NotesScreen() { val presenter: NotesListPresenter = koinInject() // we use koin for DI val uiModel = presenter.present(Unit) Column { TopAppBar(title = { Text("Notes") }) Notes(uiModel) } } } The View The views themselves are pretty self-explanatory if you're already familiar with building UIs in Compose. For the notes, we'll take in a NotesUiModel argument and create a LazyColumn with the notes property. A FAB button is used for adding new notes, although we'll skip the triggering of events and return to this part in a little bit: @Composable private fun Notes(uiModel: NotesUiModel) { Box { LazyColumn { items(uiModel.notes) { note -> Note(note) } } FloatingActionButton(onClick = { /* TODO */ }) { Icon(imageVector = Icons.Rounded.Add) } } } Then we can render each note with a checkbox, text field and delete button: @Composable private fun Note(uiModel: Note) { Row { Checkbox( checked = uiModel.isChecked, onCheckedChange = { /* T ## This Week at Zed Industries: #5 DevFeed: [This Week at Zed Industries: #5]() Original publisher: [Read original article]() Author: Max Brunsfeld Published: 2023-06-02T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [ui](), [App](), [dashboards](), [issue tracker](), [systems]() Tags: [app](), [features](), [issue-tracker](), [layout](), [os](), [screen](), [set](), [view]() ### AI overview Zed's weekly update covers the release of Zed 0.88, including a redesigned panel system and a zoom feature. It also describes crash problems after release, three patches issued to address them, new crash dashboards, and ongoing work on LSP server detection. ### Source excerpt Panels, panels, and more panels... ## Understanding SwiftUI view lifecycles DevFeed: [Understanding SwiftUI view lifecycles]() Original publisher: [Read original article]() Author: Ole Begemann Published: 2022-12-15T20:52:46Z Content type: tutorial Language: en Sources: [Ole Begemann]() Topics: [SwiftUI](), [App](), [Code](), [iOS](), [macOS]() Tags: [app](), [code](), [examples](), [ios](), [lifecycle](), [macos](), [render](), [screen](), [state](), [stateobject](), [swiftui](), [view]() ### AI overview This article explains how SwiftUI view and render trees affect view identity, lifecycle, and state. It describes how state changes can recreate view values while render-tree objects persist, and presents the SwiftUI View Lifecycle app as a way to observe lifecycle events. ### Source excerpt I wrote an app called SwiftUI View Lifecycle. The app allows you to observe how different SwiftUI constructs and containers affect a view's lifecycle, including the lifetime of its state and when onAppear gets called. The code for the app is on GitHub. It can be built for iOS and macOS. The view tree and the render tree When we write SwiftUI code, we construct a view tree that consists of nested view values. Instances of the view tree are ephemeral: SwiftUI constantly destroys and recreates (parts of) the view tree as it processes state changes. The view tree serves as a blueprint from which SwiftUI creates a second tree, which represents the actual view "objects" that are "on screen" at any given time (the "objects" could be actual UIView or NSView objects, but also other representations; the exact meaning of "on screen" can vary depending on context). Chris Eidhof likes to call this second tree the render tree (the link points to a 3 minute video where Chris demonstrates this duality, highly recommended). The render tree persists across state changes and is used by SwiftUI to establish view identity. When a state change causes a change in a view's value, SwiftUI will find the corresponding view object in the render tree and update it in place, rather than recreating a new view object from scratch. This is of course key to making SwiftUI efficient, but the render tree has another important function: it controls the lifetimes of views and their state. View lifecycles and state We can define a view's lifetime as the timespan it exists in the render tree. The lifetime begins with the insertion into the render tree and ends with the removal. Importantly, the lifetime extends to view state defined with @State and @StateObject: when a view gets removed from the render tree, its state is lost; when the view gets inserted again later, the state will be recreated with its initial value. The SwiftUI View Lifecycle app tracks three lifecycle events for a view and displays the ## Using an Activity from a Hilt ViewModel DevFeed: [Using an Activity from a Hilt ViewModel]() Original publisher: [Read original article]() Author: Pierre-Yves Ricau Published: 2022-09-07T21:59:49Z Content type: tutorial Language: en Sources: [Py's blog]() Topics: [Android](), [Code]() Tags: [android](), [blog](), [code](), [component](), [dagger-hilt](), [dependency-injection](), [lifecycle](), [state](), [view](), [viewmodel]() ### AI overview This tutorial presents a Hilt-based technique for accessing the current Android Activity from a Hilt ViewModel. It uses scoped activity storage, an activity-scoped entry point, and lifecycle callbacks to update the reference while accounting for configuration changes and multiple activities. ### Source excerpt 👋 Hi, this is P.Y., I work as an Android Engineer at Block. This blog shares a bit of hackery to be able to access an activity instance within a Hilt ViewModel. If you come up with other interesting ## Stateful Testing for Android App State Logic DevFeed: [Stateful Testing for Android App State Logic]() Original publisher: [Read original article]() Author: Sergio Sastre Florez Published: 2022-08-31T05:59:40Z Content type: tutorial Language: en Sources: [Sergio's little tech corner]() Topics: [Testing](), [Android](), [App](), [Requirements](), [test](), [ui]() Tags: [android](), [android-app-development](), [java](), [keyboard](), [kotlin](), [requirements](), [state](), [stateful](), [tdd](), [test](), [testing](), [ui](), [unit-testing](), [view]() ### AI overview This tutorial explains stateful testing for Android applications by modeling app state, user actions, preconditions, and postconditions. It uses a text editor with text changes, undo, and redo as an example. ### Source excerpt Broadly speaking, in an app, state is any value that can change over time. All Android apps display state to the user, e.g. an enabled/disabled button, the text displayed in a View, etc. We expect users to modify the state by performing actions throu... ## Announcing CodeRAD 2.0 Preview DevFeed: [Announcing CodeRAD 2.0 Preview]() Original publisher: [Read original article]() Author: Steve Hannah Published: 2021-08-13T00:00:00Z Content type: release Language: en Sources: [CodeName One]() Topics: [Framework](), [mvc](), [Java](), [Kotlin](), [Mobile](), [User Interfaces](), [Developer experience]() Tags: [announce](), [declarative](), [developer-experience](), [feature](), [framework](), [java](), [kotlin](), [mobile](), [mvc](), [native](), [performance](), [preview](), [productivity](), [real-time](), [user-interfaces](), [view](), [xml]() ### AI overview CodeRAD 2.0 is announced as a developer preview of an MVC framework for building native, mobile-first applications in Java and Kotlin. The release adds XML-based declarative views, property binding, and a simulator-based pseudo-hot-reload workflow with a stated 1-2 second update delay. ### Source excerpt We are proud to announce the immediate availability of the CodeRAD 2.0 developer preview. CodeRAD is a modern MVC framework for building truly native, mobile-first, pixel-perfect applications in Java and Kotlin. ## A Simple Laravel Hello World DevFeed: [A Simple Laravel Hello World]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2021-05-27T13:02:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Laravel](), [Composer](), [mvc](), [HTML](), [Rails]() Tags: [how-to](), [laravel](), [make](), [mvc](), [php](), [route](), [view]() ### AI overview A step-by-step Laravel tutorial that builds a minimal Hello World application using Composer, a controller, a route, a variable, and an HTML view. It explains that the example demonstrates parts of an MVC framework without covering models or database connectivity. ### Source excerpt As of late I've been working in Laravel and figuring out how Laravel differs from Rails. And while I have a bigger blog post in the works, I thought there was learning value in a simple Hello World implemented in Laravel. Hello World is a simple program that just puts Hello World on the screen. Here's how I thought a Laravel version of this should work: Be a whole Laravel application Be a single controller Be a single route Define the text "Hello World" as a variable, $text, in the controller Display that on the screen via an HTML template While this doesn't illustrated models and database connectivity, this actually illustrates how to use a surprising amount of an overall MVC framework. Step 1: Creating an Application The first step is to use composer to generate the overall application with: composer create-project laravel/laravel hello_world The next step is to change into the directory with: cd hello_world and then open the code base with: mate . or if you use Sublime: subl . Step 2: Generating a Controller Back at your command line, you want to generate a controller with: php artisan make:controller HelloController This will create a file named HelloController in app/http/Controllers: ls -l app/Http/Controllers total 16 -rw-r--r-- 1 sjohnson staff 361 May 18 11:37 Controller.php -rw-r--r-- 1 sjohnson staff 122 May 27 09:12 HelloController.php Inside the controller you want to add the following code (some of which will already be there from the generator): public function index() { return view('hello_index'); } inside the "class HelloController extends Controller" block of code (it goes inside the {} braces). Step 3: Adding a Route Moving back to the code base, you want to edit the file routes/web.php and add this line: Route::get('/hello', 'App\Http\Controllers\HelloController@index'); This adds a single route, /hello, which is then handled by the Hello controller and the hello_index action. You can test that this route is available by running: php artisan rout ## Keeping Form Elements Visible in Hybrid iOS Apps DevFeed: [Keeping Form Elements Visible in Hybrid iOS Apps]() Original publisher: [Read original article]() Author: Andy Weiss Published: 2021-02-28T14:19:06Z Content type: tutorial Language: en Sources: [RBI Tech]() Topics: [Forms](), [Ionic](), [iOS](), [Mobile]() Tags: [android-studio](), [forms](), [hybrid-app-development](), [ionic](), [ios](), [mobile](), [simulator](), [view]() ### AI overview This tutorial examines why form elements can be covered by the soft keyboard in hybrid iOS app web views, despite behaving correctly in mobile browsers. It demonstrates a Capacitor-based hybrid app and discusses using the Capacitor keyboard API to improve iOS behavior while leaving Android unchanged. ### Source excerpt Keeping Form Elements Visible in Hybrid iOS Apps Today's mobile browsers provide a pretty great default user experience for forms. For a very simple example, visit the following url from any mobile browser: https://VisualViewport.andyweiss1982.repl.co. The user experience is great from mobile Safari. When you focus on an input field, the phone's soft keyboard animates up from the bottom of the screen. All of the content comes along for the ride, intelligently sliding up so you can see each input's value as you type. Close out the form and the viewport gracefully recedes from view. However, the same exact code can become far less elegant when consumed from a web view inside of a hybrid iOS app. Not so great inside of an iOS web view Not only do we lose the "Done" button that closes the keyboard without submitting the form; in many cases, the keyboard will pop up without displacing the form elements, covering them entirely and making the form appear completely useless! Well, It works in my web browser? 🤷♂ For reference, here is the full code for the original user experience as viewed from the mobile web: https://medium.com/media/7d7adf83c321357f9af250d2c90d1d4e/href To move this code inside of a web view, we can use Ionic's capacitor package to generate a bare-bones hybrid app that can be run in a simulator. Following the docs, you can create a new project, give it a name and assign it a directory, and then add the Android and iOS platforms. npx @capacitor/cli create? App name hybrid-forms-test ? App Package ID (in Java package format, no dashes) com.example.app ? Directory for new app hybrid-forms-test ? Which npm client would you like to use? yarnAdd platforms using "npx cap add":npx cap add android npx cap add ios For the purposes of this demo, you can just copy and paste the following code into www/index.html to generate a carbon copy of the original example into a boilerplate capacitor web view that can be run as either an iOS or Android application: https://me ## Introducing Bookings API Beta DevFeed: [Introducing Bookings API Beta]() Original publisher: [Read original article]() Author: Leher Pathak Published: 2020-12-16T08:00:00Z Content type: release Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [API](), [App](), [Website](), [Availability]() Tags: [api](), [apis](), [app](), [apps](), [availability](), [customer](), [developers](), [payment](), [payments](), [search](), [services](), [third-party](), [update](), [view]() ### AI overview Square released the Bookings API in beta, enabling third-party booking apps and custom websites to integrate Square Appointments. Developers can manage booking availability, locations, customers, services, team members, reminders, calendars, and customer profiles, with bookings and payments visible in Square Dashboard. ### Source excerpt Integrate Square Appointments with your booking app or custom website ## Postgres Views DevFeed: [Postgres Views]() Original publisher: [Read original article]() Author: Paul Copplestone Published: 2020-11-18T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [PostgreSQL](), [Databases](), [Query (disambiguation)](), [Security]() Tags: [consistency](), [organization](), [postgres](), [postgresql](), [security](), [view]() ### AI overview The article introduces PostgreSQL views and materialized views. It explains that a view is a named shortcut to an underlying query and outlines benefits including simplicity, consistency, logical organization, and security. Materialized views physically store query results to make subsequent reads faster. ### Source excerpt Creating and using a view in PostgreSQL. ## When to Use a Helper Method in Rails DevFeed: [When to Use a Helper Method in Rails]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-03-04T00:00:00Z Content type: tutorial Language: en Sources: [Scott Johnson]() Topics: [Rails](), [Ruby](), [Code](), [HTML]() Tags: [code](), [data-structure](), [function](), [html](), [netlabeler](), [rails](), [rake](), [ruby](), [view]() ### AI overview This Rails tutorial explains when to use a helper method to transform stored hash data into HTML for display. It presents a testable display_labeled_data helper that builds paragraph output, converts newlines to HTML breaks, joins the result, and marks it html_safe. It also notes that Rails helpers share a global namespace. ### Source excerpt One of the more interesting facilities in Rails helpers which reside in app/helpers/*.rb and are used, well, as helpers. Helpers are basically display level execution of Ruby code. I recently wrote what I thought was a great example of a helper so I thought I'd document it. What I had was a object, stored in the database which had a bunch of data that I needed to display: the object, called a label A serialized hash called labeled_data label0 label1 label2 label3 label4 label5 label6 label7 label8 label9 What I wanted to do was transform this, at display time, to an HTML structure like this:

label0: The Data for Label 0

label1: The Data for Label 0 and, correctly, not show label2, etc if they were blank. And, naturally, do the right thing when there was no data in the labeled_data hash, etc. And while I could have done this with a view and code wrapped in evaluation / output tags: <% and %> or <%= or %> it is dramatically cleaner to write this type of thing as a helper and then call it as a function like display_labeled_data(label). Not only does this make the code much cleaner than evaluation / output tags, it also has the advantage of being testable. Now all that said, here is the code: def display_labeled_data(label) return if label.labeled_data.nil? return if label.labeled_data.keys.nil? output = [] label.labeled_data.keys.each do |key| output << "

" output << key output << ":" tmp = label.extracted_data[key] if tmp tmp = tmp.gsub(/\n/,' ') end output << tmp output << "

" end output.join("\n").html_safe end The key idea here is: create an output object, in this case an array or [] loop a data structure - label.labeled_data.keys as you loop the data structure, put things into the output object like a paragraph tag, the name of the key i.e. "label0", a ':' clean up the data by converting new lines to html line breaks add the data into the output element add a closing p tag add a line break onto every element of the output object (using ## SwiftUI: впечатления iOS-разработчика о реактивном UI-фреймворке и его синтаксисе DevFeed: [SwiftUI: впечатления iOS-разработчика о реактивном UI-фреймворке и его синтаксисе]() Original publisher: [Read original article]() Published: 2020-01-18T15:36:57Z Content type: opinion Language: ru Sources: [Tonsky Стой под стрелой]() Topics: [SwiftUI](), [iOS](), [ui]() Tags: [foreach](), [ios](), [livejournal](), [padding](), [swiftui](), [tag-5e1c061eda96](), [tag-c40b78a8c8a6](), [tag-d16a2c26554f](), [tag-e3028c5e0ab2](), [ui](), [view]() ### AI overview An experienced iOS developer shares impressions of SwiftUI after using it for roughly six months and releasing two production applications. The article praises its reactive, data-driven UI model and previews while criticizing its syntax, element-count limitation, opaque types, and inconsistent modifier and container design. ### Source excerpt Если вдруг вы еще не знаете, примерно полгода назад Эппл анонсировало новый UI фреймворк -- SwiftUI. Событие очень серьезное, и как iOS разработчик со стажем я тут же переключился на него -- сначала попробовать, а потом уже и выпускать production приложения. Спустя полгода и два заапрувленных релиза, хочу поделиться с вами мыслями о SwiftUI. Во-первых, то, что Эппл выпустило нормальный реактивный data-driven UI фреймворк, заслуживает исключительно всяческих похвал. Правильный тренд, правильный подход, _почти_ интерактивное превью, все вовремя и к месту. Нам, iOS-программистам, чего-то такого сильно не хватало. Во-вторых (и тут уже о сомнительном), количество синтаксического сахара, которым они там обмазываются, вызывает, скажем так, удивление. Им пришлось серьезно расширить язык, чтобы вместо условно VStack( Image(uiImage: image), Text(title), Text(subtitle) ) можно было писать VStack { Image(uiImage: image) Text(title) Text(subtitle) } На что только люди не пойдут чтобы избежать споров о том где ставить запятую! Работает это благодаря вот такому вот прекрасному интерфейсу: То есть не только не очень понятно зачем так усложнять себе жизнь, но еще и больше 10 элементов не засунешь. Может быть создатели руководствовались правилом 7±2 и решили, что пользователи айфона не смогут всерьез осознать более 10 одновременных элеметов на экране. То что в этом интерфейсе пропилена специальная дырка для if напрягает если честно еще больше: Не самим фактом дырки, а вопросом, где же собственно дырки под все остальное? (на самом деле, если хочется больше 10 элементов, есть целый специальный компонент -- ForEach, который -- уберите детей от экрана! -- принимает список) (этот курьез и необходимость вводить opaque types заставляет задуматься, насколько сильно нам вообще нужна статическая типизация и какой ценой. Конечно, сторонники статической типизации скажут, что это просто типизация неправильная, вот была бы правильная и проблем бы не было -- что, в общем-то, универсальный аргумент, удобн ## Build complex screens faster on Android with Epoxy DevFeed: [Build complex screens faster on Android with Epoxy]() Original publisher: [Read original article]() Author: Akshay Chordiya Published: 2019-12-30T13:31:50Z Content type: tutorial Language: en Sources: [Bleeding Edge - Medium]() Topics: [Android](), [Library](), [ui](), [implementation]() Tags: [android](), [architecture](), [class](), [component](), [components](), [declarative](), [epoxy](), [how-to](), [kotlin](), [layout](), [library](), [mvi](), [mvvm](), [performance](), [recyclerview](), [ui](), [view]() ### AI overview This tutorial explains how Clue adopted Airbnb's Epoxy library with RecyclerView to build complex Android screens. It covers Epoxy models, adapters and controllers, declarative layouts, and a unidirectional data-flow pattern related to MVVM and MVI. ### Source excerpt Rowing the boat -- Illustration by Marta PucciBuild complex screens faster on Android⚡ -- Our journey with Epoxy RecyclerView is such an important UI component on Android. But using it can get complex and error prone--especially when dealing with different view types and pagination. Moreover, it's hard when working on the same screen within the team. In this article, I'm going to share basics of Epoxy and an overview of the problems it helped us solve. Here's our journey of how we adopted Epoxy at Clue to build our UIs faster in parallel within the team.⚡ Backstory It all started with our users, who wanted a more understandable and interactive view of their historical tracking data. ✨(For Clue users, this is generally their menstrual cycles & symptoms.) So our awesome design team came up with this beautiful intuitive design 😍: Enhanced Analysis screen in Clue app I know what you're thinking already: that's a lot of view types. And we were definitely concerned about the performance and responsiveness of the screen. That's when we decided to see if we could use any third-party library to help us with our goal. Epoxy Epoxy is a library from Airbnb which takes a declarative / composable approach to build the UI--typically, a list. It uses RecyclerView under the hood It simplifies creation of static and dynamic layouts Each item in the list is associated to an epoxy model which defines the item's layout and manages binding the data and releasing the view's resources when it's recycled. Item <-> Epoxy Model <-> Layout resource The order of the items shown on the UI is based on how you add the model to the adapter or controller. Philosophy Epoxy encourages a usage pattern similar to the popular MVVM and MVI architecture where the data flows in one direction (UDF - uni-directional data flow). Flow with Epoxy The data forms the state of the UI then goes to EpoxyModel and to the views on the RecyclerView . The Epoxy Model behaves like a ViewModel and provides the interface betwe ## Namespacing in Kotlin DevFeed: [Namespacing in Kotlin]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2019-07-29T00:00:00Z Content type: tutorial Language: en Sources: [Artur Dryomov]() Topics: [Kotlin](), [Code](), [Development]() Tags: [architecture](), [c-plus-plus](), [c-sharp](), [classes](), [code](), [components](), [development-process](), [java](), [kotlin](), [php](), [typescript](), [view](), [viewmodel]() ### AI overview This article examines how to represent a fractal component structure in Kotlin, focusing on naming and namespace-like organization. It compares several implementation approaches, including their Java representations, compiler behavior, object creation, inheritance, semantics, and generated size. ### Source excerpt The development process is a research. Find the state machine, organize mutations, wire it for consumers. The process repeats and leads to the meta-research. We investigate scenarios and search for reusable parts. Patterns arise, implementations follow. Ideally, the code resembles a fractal structure. An architecture is said to be fractal if subcomponents are structured in the same way as the whole is. -- André Staltz The Problem Let's say we have a fractal components structure. Each one has a View and a ViewModel. ## Handling Transient Events DevFeed: [Handling Transient Events]() Original publisher: [Read original article]() Published: 2019-07-26T15:00:00Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [App]() Tags: [android](), [events](), [lifecycle](), [livedata](), [navigation](), [notifications](), [view]() ### AI overview This article explains why LiveData is well suited to persistent view state but less suited to transient view events. It distinguishes state that should be saved and restored from one-time events such as notifications, navigation, dialogs, and errors, using an Android app example. ### Source excerpt LiveData has become an important part of many Android apps. With it's elegant handling of the complex lifecycle inherent in many Android components, its understandable that we would try to use them everywhere we can. LiveData, however, was designed with a very specific use case in mind. Its intended to hold data for use by views in an application, and make that data available in a lifecycle-safe fashion, while helping us reduce the need to reload data unnecessarily. ## Investigating Memory Leaks in Square POS on Android Q DevFeed: [Investigating Memory Leaks in Square POS on Android Q]() Original publisher: [Read original article]() Author: P-Y Ricau Published: 2019-07-03T19:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Android](), [Memory Leaks](), [debugging](), [Large Screen]() Tags: [android](), [debugging](), [engineering](), [leak](), [leakcanary](), [lifecycle](), [memory](), [memory-leaks](), [view]() ### AI overview The article investigates unusually high memory leaks observed while testing Square POS on Android Q, focusing on leak traces involving an attached view and a destroyed activity. It also explains how LeakCanary 2 uses lifecycle heuristics when interpreting such traces. ### Source excerpt Debugging leaks for Square POS in Android Q ## Button Lists DevFeed: [Button Lists]() Original publisher: [Read original article]() Author: Shai Almog Published: 2018-12-04T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Code](), [API](), [data]() Tags: [android](), [api](), [demo](), [developers](), [dialog](), [ios](), [issue](), [layout](), [legacy](), [list](), [state](), [view]() ### AI overview This tutorial introduces ButtonList and its CheckBoxList, RadioButtonList, and SwitchList subclasses. It explains how they apply list-model concepts with a layout/container hierarchy, including sharing one model between lists and synchronizing checkbox and switch changes. ### Source excerpt I wrote in the past about the problems in the List class, so I won't rehash them here. However, the ideas behind list are still valuable. One such idea is the list model which allows us to separate the state from the view. Unfortunately the renderer architecture makes this hard to implement for most developers and limits the flexibility of the API. To leverage this idea with the easier to use layout/container hierarchy we introduced ButtonList and its subclasses: CheckBoxList, RadioButtonList & SwitchList. ## Better Redirects in Angular Route Guards DevFeed: [Better Redirects in Angular Route Guards]() Original publisher: [Read original article]() Published: 2018-11-28T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Angular](), [Authorization](), [User experience (UX)](), [Data structures]() Tags: [angular](), [async](), [blocking](), [bugfixes](), [data-structure](), [features](), [guards](), [implementation](), [object](), [route](), [router](), [state](), [view]() ### AI overview This tutorial explains Angular 7.1 route guard improvements, focusing on returning an UrlTree to redirect users when a route cannot be activated. It also distinguishes client-side route guards as a UX feature from server-side security checks. ### Source excerpt Lorem ipsum dolor sit amet [Next page]()