Re: future of OM frontend

2021-10-18 Thread Maxim Solodovnik
On Mon, 18 Oct 2021 at 03:13, seba.wag...@gmail.com wrote: > If it's just JS + CSS changes you an update the files in a running > openmeetings server using those scripts: > > https://openmeetings.apache.org/BuildInstructions.html#update-javascript-and-css-at-runtime > > This will take ~10seconds

Re: future of OM frontend

2021-10-17 Thread seba.wag...@gmail.com
If it's just JS + CSS changes you an update the files in a running openmeetings server using those scripts: https://openmeetings.apache.org/BuildInstructions.html#update-javascript-and-css-at-runtime This will take ~10seconds + refresh the browser. Compared to 2-3 minutes to do a rebuild and then

Re: future of OM frontend

2021-10-17 Thread Maxim Solodovnik
On Sun, 17 Oct 2021 at 05:04, seba.wag...@gmail.com wrote: > > > > At my 5-7 years old laptop > > "unpacked" build tooks 7-9 minutes > > "quick" build tooks 01:01 minute > > You are missing that it's not only the build time. You also need to restart > the server. Which is another 1-2mins. And

Re: future of OM frontend

2021-10-16 Thread seba.wag...@gmail.com
> > At my 5-7 years old laptop > "unpacked" build tooks 7-9 minutes > "quick" build tooks 01:01 minute You are missing that it's not only the build time. You also need to restart the server. Which is another 1-2mins. And you need to re-login + navigate to the place where you were before. Which

Re: future of OM frontend

2021-10-15 Thread Maxim Solodovnik
On Wed, 13 Oct 2021 at 04:49, seba.wag...@gmail.com wrote: > OFFTOPIC: I don't really like webpack-and-friends, it's output is often > unpredictable and hard to debug. > Additionally I have difficulties to set it up to do what I need > This is why I'm trying to find something that "just works"

Re: future of OM frontend

2021-10-12 Thread seba.wag...@gmail.com
OFFTOPIC: I don't really like webpack-and-friends, it's output is often unpredictable and hard to debug. Additionally I have difficulties to set it up to do what I need This is why I'm trying to find something that "just works" and produces no damage :) Your offtopic sounds more like a rant :)

Re: future of OM frontend

2021-10-12 Thread Maxim Solodovnik
On Tue, 12 Oct 2021 at 03:41, seba.wag...@gmail.com wrote: > > > > The project is responsible for the 3rd party components/libraries it uses > > I try to check the license of JS components (but not their trees) > > Re license checking, we could explore using: >

Re: future of OM frontend

2021-10-11 Thread seba.wag...@gmail.com
> > The project is responsible for the 3rd party components/libraries it uses > I try to check the license of JS components (but not their trees) Re license checking, we could explore using: https://www.npmjs.com/package/license-checker => to automate license checks. That might be quite useful,

Re: future of OM frontend

2021-10-07 Thread Maxim Solodovnik
sorry for double post Maybe I'll check this tool https://www.snowpack.dev/ for out build not sure yet if this will be useful or not On Thu, 7 Oct 2021 at 23:29, Maxim Solodovnik wrote: > (moving to dev@) > > On Thu, 7 Oct 2021 at 03:59, seba.wag...@gmail.com > wrote: > >> +1 >> >> In the long

future of OM frontend

2021-10-07 Thread Maxim Solodovnik
(moving to dev@) On Thu, 7 Oct 2021 at 03:59, seba.wag...@gmail.com wrote: > +1 > > In the long run I am interested in how NPM fits with the Apache Foundation. > But maybe that is something to raise with @legal and @infra: > - Current vetting of licenses is based heavily on maven (e.g.