Background

I have been playing around with Scenic to make a desktop app across multiple environments. While the Install dependencies for Ubuntu are outdated and don;t work for the latest LTS (v20) I was still able to figure out the packages and install it on Ubuntu Linux.

However ... there is nothing for Windows.

Questions

1. Does Scenic even work on Windows?
2. If so, what are the dependencies? What need I to install?

So, Scenic does not support Windows nor will it run on a Windows system. Are you aware of any alternatives to Scenic that would run on a Windows system?

flame,

take a look here: https://medium.com/@jeffborch/running-the-scenic-elixir-gui-framework-on-windows-10-using-wsl-f9c01fd276f6

Background

I have been playing around with Scenic to make a desktop app across multiple environments. While the Install dependencies for Ubuntu are outdated and don;t work for the latest LTS (v20) I was still able to figure out the packages and install it on Ubuntu Linux.

However ... there is nothing for Windows.

Questions

1. Does Scenic even work on Windows?
2. If so, what are the dependencies? What need I to install?

Upate forked repo

update

Upate forked repo

I am also interested to listen about scenic roadmap

I'd be interested in participating on a call as well (although if the participant list is getting unwieldy I'm fine sitting out). Also pinging @BWheatie since he might be interested.

Excellent. Thanks for the update. I'll go thru some issues and attempt to dig in.

Sure, just using those as examples!

@Eiji7 Fair points!

It's also true that Scenic is not 1.0 for good reason. Too many rough edges. @cretel - tiling is interesting, but comes after making sure the core model is nice and smooth. (games still aren't the design point)

@boydm I'd be down for a call.

Maybe we should put together an agenda or sketched roadmap, or maybe have everybody bring their pet concerns?

(For example, I had some questions about specifying ST and tiling a year or two ago, and I recall a bunch of discussion--without resolution--around XB360 controller support.)

Nobody is yelling at me to get these these things done tho, so that indicates it is mostly used in hobby scenarios. That will eventually change, but for now it means then pressure to do the bigger items is fairly low.

Well … nobody is yelling only because we have such an amazing community. :smiling_imp:

Actually people are interested in using scenic in serious apps. From what I know right now people see that you are trying best, but also they are worried that their effort would not be worth in long term i.e. people are looking if scenic project would die "sooner or later" or if you are going to push it forward.

I have already worked in one of my jobs on scenic-based GUI application. However because of it's current state it was like a demo/preview app to check if we can do it. We decided to start work on scenic as it was really easy to work on it and meanwhile we were updating standard web application based on our work on scenic.

Also I'm one of many EF members who are watching for progress of scenic. If you are going to do an major update this year then scenic may gain much more attention. Regarding video call it would be amazing, but for now I'm in really bad situation and simply can't promise anything. For now I'm limited to EF and github.

Hi Graham. We'll do a video chat either way... ;)

Last thought for anybody listening: Scenic has been out there for a while now. If I were to do a bigger design update on it (Not going to be this month or next... expectation setting...) Think about what you would change. I was also learning Elixir as I built it so now, I look at it and see design patterns that probably need updating.

So... I'm open to general ideas and feedback.

Boyd,

I would very much like to participate in any video call on the Scenic roadmap/design.

Graham Hay

On 11 January 2021 at 10:45 Boyd Multerer notifications@github.com wrote:

Hey guys. @Eiji7 https://github.com/Eiji7 . I've been focused on a related project (https://kry10.com/blog/kry10_secure_platform) that is WAY TOO HARD and has taken a lot of my time.

I am hoping to do a pretty major update to Scenic in 2021. But the shape of it depends on how the OS comes together. Specifically, I know I need to update the cache mechanism and the way the drivers compile render scripts for graphs.

More than happy to take bug fixes and clean up and push updates as they make sense.

Also if you, or anyone else, are interested, I'd be happy to do a video call to discuss roadmap and design.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/boydm/scenic/issues/205#issuecomment-757549123 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEMSCK4WWBDFAIETFIUFQ3SZINWNANCNFSM4V2U6WKA .

Areas I know I want to rework and may even involve breaking changes:

The cache, especially the way dynamic cache items are handled. Some of the styles. Especially image fills. The Path primitive needs to be revisited. Super powerful, but I worry not general enough. Rename Scenic.Sensors to Scenic.PubSub Input focus management and quite a bit more. Support for the Raspberry Pi 4

Nobody is yelling at me to get these these things done tho, so that indicates it is mostly used in hobby scenarios. That will eventually change, but for now it means then pressure to do the bigger items is fairly low.

Hey guys. @Eiji7. I've been focused on a related project (https://kry10.com/blog/kry10_secure_platform) that is WAY TOO HARD and has taken a lot of my time.

I am hoping to do a pretty major update to Scenic in 2021. But the shape of it depends on how the OS comes together. Specifically, I know I need to update the cache mechanism and the way the drivers compile render scripts for graphs.

More than happy to take bug fixes and clean up and push updates as they make sense.

Also if you, or anyone else, are interested, I'd be happy to do a video call to discuss roadmap and design.

I don't think so. Looks like @boydm is really busy and don't update himself this project often. Instead he mostly discuss and merges PRs.

Issues and PRs are obviously welcome. If remember correctly @boydm would be happy to discuss about improvements in C code of scenic_driver_glfw.

I don't have much time as well, but will try to help as much as possible. I would be especially interested if you want to fix resizing problem, so feel free to ping me.

Checked in to look at issues and maybe fix some, but won't if it's not moving forward.

So... What is the issue?

Bumps ini from 1.3.5 to 1.3.7. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/npm/ini/commit/c74c8af35f32b801a7e82a8309eab792a95932f6"><code>c74c8af</code></a> 1.3.7</li> <li><a href="https://github.com/npm/ini/commit/024b8b55ac1c980c6225607b007714c54eb501ba"><code>024b8b5</code></a> update deps, add linting</li> <li><a href="https://github.com/npm/ini/commit/032fbaf5f0b98fce70c8cc380e0d05177a9c9073"><code>032fbaf</code></a> Use Object.create(null) to avoid default object property hazards</li> <li><a href="https://github.com/npm/ini/commit/2da90391ef70db41d10f013e3a87f9a8c5d01a72"><code>2da9039</code></a> 1.3.6</li> <li><a href="https://github.com/npm/ini/commit/cfea636f534b5ca7550d2c28b7d1a95d936d56c6"><code>cfea636</code></a> better git push script, before publish instead of after</li> <li><a href="https://github.com/npm/ini/commit/56d2805e07ccd94e2ba0984ac9240ff02d44b6f1"><code>56d2805</code></a> do not allow invalid hazardous string as section name</li> <li>See full diff in <a href="https://github.com/isaacs/ini/compare/v1.3.5...v1.3.7">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~isaacs">isaacs</a>, a new releaser for ini since your current version.</p> </details> <br />

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>