Thank this awesome project that has made cross-platform UI development an easier way in the Rust world.

I know iced is just at a very early stage, we don't have enough good docs yet. We can get started through a set of examples. However, after insight a lot of examples, I still can't get a clear concept and relationship of every single component, such as the Application's lifecycle, when and

Do you guys have any roadmap for this project? What features are being worked on / will be worked on in the future, is there any specific skill that you would like a person to get in touch with.

Description

The basic animation section in the app has two new examples, AnimatedPositioned and AnimatedSwitcher which hasn't been updated in the README.md.

Should we consider add example to each topics?
How to use it and best practice to use it!

I.e: for helloworld demo the example would be http://localhost:8080/demo/hello?who=ibrahim

In the documentation it says:

Turns positive integers (indexes) into dense vectors of fixed size. eg. [[4], [20]] -> [[0.25, 0.1], [0.6, -0.2]]

Neither this explanation nor this example is very clear. I would suggest replacing this with

Turns positive integers (indexes) into dense vectors of fixed size. eg. [[4], [20]] -> [[0.25, 0.1], [0.6, -0.2]]

The following code causes an ICE:

fn main() {
    print!("\r¡{}");
}

As far as I can tell:

• Any number of characters can be inserted between \r and ¡ and the error will still happen.
• ¡ can be replaced with any unicode character and the error will still happen.
• No escape sequences other than \r cause the error.

The error is reproducible on the stable or nightl

Just a small type, in Typo in Course 1 - Part 6 - Lesson 2, Visualizing the Convolutions and Pooling section,

This code will show us the convolutions graphically. The print (test_labels[;100]) shows ...

test_labels[;100] should be test_labels[:100]

Feature request

Strip everything from the first back slash ' \ ' to the end of the line.

Steps to reproduce

use auxiliary/scanner/ftp/ftp_version
run

Example data:
(vsFTPd 2.0.1)\x0d\x0a

Microsoft FTP Service\x0d\x0a

FileZilla Server 0.9.60 beta\x0d\x0a220-written by Tim Kosse (tim.kosse@filezilla-project.org)\x0d\x0a220 Please visit https://filezilla-project.org/\x0d\x0a

Issue details

While in a LibGDX environment if you press down a key and then switch to any window outside of LibGDX's scope and release that key, the LibGDX environment does not detect that release event.

Upon re-entry to the LibGDX environment, there should probably be some re-polling evaluation of the keys LibGDX thinks are pressed keys to determine if they are still pressed or not.

A description is incomplete. It should mention:

These patterns are not competing, but complementing each other. To achieve availability, one needs both fail-over and replication.

right after

"There are two main patterns to support high availability: fail-over and replication. "

It seems there is a different raises behaviour for newTerminal()

Example

import terminal

proc test() {.raises:[IOError, ValueError].} =
  setBackgroundColor(stdout, bgRed)

test()

This will compile on Linux, but not on Windows. Error:

C:\Users\deme\repos\getterminalraises.nim(3, 22) templa

#5470 is great, but AFAICT it's not documented anywhere. I was writing a partial and thinking "I thought there was some way of getting a global site function?" and I only found it by just experimenting and trying {{ site }}. Maybe I saw it in a Regis blog post at some point or something. Anyway, it should be in the list of Functions, if nothing else.