Teasing the developer experience stuff a bit, I'd like to see a lot of the client-side communication code factored into a shared library that can be published to npm, so that new devs can play around with "hello world" client side apps using the same well-tested code as the main UI.
sent from phone On Mon, Jun 24, 2019, 1:54 PM Eric Drechsel <[email protected]> wrote: > I'd get behind and contribute to consolidating the UI around react. TBH > the gopherjs stuff scared me away (and I know go). Long term I'd like to > work on app developer experience, and getting the core client side code > more consistent/well maintained shape is an important step I think. > > I'll try to find some time to review the current state of UI code and come > up with some initial priorities (for myself) > > sent from phone > > On Sat, Jun 15, 2019, 4:31 PM Mathieu Lonjaret <[email protected]> > wrote: > >> Hi, >> >> Thank you for your interest in the project. >> As I see it, there are at least 3 different interesting axes you could >> work on: >> 1) Any bug/feature request (among the many we have in the bug tracker, >> or another one that itches you in particular) >> 2) Make the "environment" easier to work with for frontend devs. The >> current design we have is a mix of custom stuff, Closure, gopherJS, >> and React, which is a mess. Imho, the React approach is pretty nice, >> and if we could consolide the whole codebase around it, it would make >> it more maintainable, hopefully at least for most frontend devs. >> 3) Make the environment easier to work with for everyone else. We went >> with GopherJS because obviously it allowed us to write some frontend >> code "just" by writing Go. It was an attractive concept, and it kindof >> worked, but the maintenance cost was pretty high, and also GopherJS is >> sort of dying. We're considering trying a similar approach with >> Go->WASM, but we probably want to be more cautious about it than we >> were with GopherJS, so I think we're waiting to see how WASM evolves >> for now. Anyway, it would be nice to find a way for us to write >> frontend code in an easier way. >> >> hth, >> Mathieu >> >> On Sat, 15 Jun 2019 at 02:38, Omar Chehab <[email protected]> wrote: >> > >> > Hello 🏻 >> > >> > I'm interested in working on Perkeep's web user interface. >> Specifically, I have been thinking about skinning the UI using Google's >> Material Design principles. >> > >> > What would you guys like to see change with Perkeep's UI? >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "Perkeep" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/perkeep/d1cba96d-207b-4093-942f-14725b31a51e%40googlegroups.com >> . >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Perkeep" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/perkeep/CAHcDtnmNABZz7e%3Dwn7B-PgaH%2BexO1Y_gWj0mjLijSnOR%2Bp_Qig%40mail.gmail.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/perkeep/CAGTxtWg6_NoOdB_KZ2kki%2B1wrf-JPtmNu%3DxU47MyQhf%2BBfS04g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
