Is elm/browser still maintained?

k-bx · March 14, 2023, 11:14am

Elm debugger crashes when you’re working with large lists. PR has been up for more than two years now.

Is elm/browser still maintained? Who can I ping to merge this in?

lydell · March 14, 2023, 11:26am

None of the elm/* packages are maintained. There is nobody to ping. (Note, since there is no clear definition of “maintained”, you’ll get different answers depending on who you ask.)

I patch the Elm JS output at work, including the PR you linked to. Note that it makes the debugger not crash anymore, but it still gets really slow with very large lists.

There is an effort called elm-janitor that explores how to get fixes for the core packages: GitHub - elm-janitor/manifesto: Meta repository for elm-janitor organization documentation.

k-bx · March 14, 2023, 12:01pm

I see. @evancz , are you still around to comment on this? Elm is still the best thing to use in 2023, it’s a pity to see the maintenance problems like this.

kanishka · March 14, 2023, 1:08pm

I would focus your energy on elm-janitor. The elm leadership has it’s approach to the language development. At most, it would be nice if they consider choosing some trusted delegates to move maintenance forward, but that may not happen. It seems like slow experimentation aimed at hobbyist users is the priority of elm proper.

Mark · March 20, 2023, 11:33pm

Any idea why the PR to fix elm/browser has not been applied to the elm-janitor/browser repo? The person who submitted that patch is the same person who wrote the elm-janitor manifesto. Am I not looking at the right branch in elm-janitor/browser?

rupert · March 21, 2023, 10:14am

That would be me, and I was kinda wondering the same thing. Turns out I had misclassified that PR as a “Doc Fix”, rather than as a runtime bug fix. So I will change its category and apply it too.

We have a bunch of patches reviewed now, just need to apply them all, write some release notes and tag some releases.

Mark · March 24, 2023, 3:50pm

Got it. Sounds like a lot of work!

tlentz · March 27, 2023, 9:09am

I was running into an issue that might require a change to elm/browser to have the elm debugger able to be opened and used in a tauri app.

github.com

elm/browser/blob/1d28cd625b3ce07be6dfad51660bea6de2c905f2/src/Elm/Kernel/Debugger.js#L190


      
          	});
          }
          
          
function _Debugger_openWindow(popout)
          {
          	var w = __Main_initialWindowWidth,
          		h = __Main_initialWindowHeight,
          	 	x = screen.width - w,
          		y = screen.height - h;
          
          
	var debuggerWindow = window.open('', '', 'width=' + w + ',height=' + h + ',left=' + x + ',top=' + y);
          	var doc = debuggerWindow.document;
          	doc.title = 'Elm Debugger';
          
          
	// handle arrow keys
          	doc.addEventListener('keydown', function(event) {
          		event.metaKey && event.which === 82 && window.location.reload();
          		event.key === 'ArrowUp'   && (popout.__sendToApp(__Main_Up  ), event.preventDefault());
          		event.key === 'ArrowDown' && (popout.__sendToApp(__Main_Down), event.preventDefault());
          	});

github.com/tauri-apps/tauri

[feat] WebViewWindow should provide access to the `document` property

opened 04:51AM - 19 Jul 22 UTC

closed 06:16PM - 02 Aug 22 UTC

miniBill

type: feature request

### Describe the problem Elm uses `window.open` for its debugger. Critically, I… cannot simply replace the call to `window.open` with the `WebviewWindow` API because it doesn't allow access to the `document` property of the opened windows. ### Describe the solution you'd like Either a. `WebviewWindow` provides a `document` property compatible with what browsers offer or, even better, b. the `window.open` API is implemented exposing types compatible with browser ones. ### Alternatives considered I've considered mocking all the properties and calls using a `Proxy`, but it's actually calling nontrivial JS functions on the document itself, and I think it would be a huge undertaking for something that can be done more efficiently by tauri. ### Additional context _No response_

github.com/tauri-apps/wry

Implement `window.open`

opened 09:13AM - 04 Aug 22 UTC

closed 05:05PM - 29 Sep 22 UTC

miniBill

**Is your feature request related to a problem? Please describe.** A "library" …I'm using (Elm's built-in debugger), uses `window.open` to pop up the debugger in a new window. **Describe the solution you'd like** An implementation of `window.open` that works similarly to the browser. **Describe alternatives you've considered** Using tauri APIs to open the new window wouldn't work because the code is in a library. Critically, the code also accesses the `window` object of the newly opened window. **Would you assign yourself to implement this feature?** - [ ] Yes - [X] No

see the source here that uses window.open and the issue in the linked github issues. the way the debugger is currently implemented, it doesn’t seem possible to use it within a tauri window.

perty · March 30, 2023, 7:53am

Looking forward to see some releases from elm-janitor!

rupert · March 30, 2023, 3:45pm

I’ve gotten a bit busy with work, and also spent the last 3 weekends planting trees, so have not had time to pull it all together.

However, no reason at all why someone else cannot do it, if they happen to be keen? I made the repos under a github group, precisely so that other people can join that group and be empowered to do things? I guess PM me if that happens to be you.

perty · March 30, 2023, 9:26pm

Way over my skills to change anything in core of Elm. But I’d like to be able to recommend it because it is actually maintained.

system · April 9, 2023, 9:26pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.