webxdc / webxdc-dev Goto Github PK

I would like to help developing webxdc-dev but I'm unable to even start the basic project:

Steps to reproduce:

• pnpm install
• pnpm run dev -- run /home/sebastian/coding/hello/hello.xdc

I'm running node v. 18.7 which might cause problems?

• missing updates (some devices don't get all updates)
• out of order update delivery
• delayed updates

And other things like that.

It's a bit annoying that you have to manually press the "start" button, so maybe makes sense to add a front-end option to do this automatically. It should default to true.

Or something like this, so it's more clear that it's not an app, but it's a tool to develop apps.

There are some long-unreleased changes. Looks like we can release them by simply pushing a tag.

I have the permission to do this, but I want someone's approval.

Reproduction

1. Create an app that executes fetch('/index.html').then(console.log)
2. Serve the app on a local server. Say, python -m http.server 8000.
3. webxdc-dev run http://localhost:8000.

Expected result

fetch succeeds.

Actual result

fetch fails because of connect-src CSP: default-src 'self' ;connect-src ws://localhost:7001 ws://localhost:8000.

Extra info

I think 'self' should be present it connect-src, I don't know why it's just ws://.

new webxdc.sendToChat() and webxdc.importFiles() API was introduced, the emulator needs to be updated

related issue for the old/simple emulator: webxdc/hello#45

discussion about the new API: https://support.delta.chat/t/planned-webxdc-apis-for-processing-files/2570

expected: app has all previous state updates, even if the update was sent before the instance was opened/started
actual: app only has updates from the time it was active, and on reload it looses all state.

When I hover the second devices start-button, the device begins to flicker and can not be activated.
For me it looks like if the device got a litte wider which makes it wrap to the next row. When wrapped the device is no longer under the mouse and the button is therefore not hovered, which makes the thing go small again and return to it's old place. This periodic sequence produces a flickering perception of the second device.
This problem also only occures on the basic zoom-level where the two devices fill the available space close to perfectly. When zoomed which gives the devices more room, no flickering occures.

https://github.com/watching

Idk if it's something that needs fixing. Maybe it's not worth packaging effectively useless stuff inside the npm package to save space.

I think it's like this after #28

might need some conversion from png/jpg to ico, to use the fact that browsers look for favicon.ico
If that would work we don't need to inject any header html tags, which might be more complicated, but on the other hand then we could probably save the format conversion step?

hi @faassen, can you create a new release on npm?

When a webxdc instance is opened on a port, there is sometimes a flash of contents. This happens to clear the local state (localstorage, etc) of the previous instance so we start with a fresh slate, and then the application is reloaded. After this, the setUpdateListener is registered for serial 0 and the state is loaded anew.

How to avoid this flash of content? The trouble is that we don't know whether clear is going to come in. A normal reload shouldn't wipe local state, only the initial opening does.

I considered turning off the UI (by setting document.style.display = 'none') in the window.load event but:

• this may already be too late to prevent a flash of content

• we want to reenable the display sometime, and when to do that? We can't wait for an update or clear, as it may not arrive.

I considered loading a custom index.html initially when you open a tab, and then clearing contents if a clear event comes from the server, and buffering any other updates somehow, and then reloading to the real index.html and piping in all the buffered updates. But this seems very tricky to get right.

Perhaps the simplest approach would be some kind of setTimeout, but again the reload makes things difficult...