[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to make a new web component
[Thread Prev] | [Thread Next]
- Subject: Re: How to make a new web component
- From: Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>
- Date: Mon, 7 Jul 2025 17:17:57 +0200
- To: user@xxxxxxxxxxxxxxxxxxxxxx
Le 07/07/2025 à 17:08, Fabien Bodard a écrit :
In case of making a leaflet-based widget in 'gb.web.gui', people take the javascript from the web, as these kind of tools are usually intended to be used that way.Just a thought: A component should probably not rely on externally retrieved sources. The sources should be downloaded and saved locally so they are always available. And, having the sources "frozen" at a certain version would prevent any unexpected surprises. Well both can have good reason - local: more stability, but need to be updated- extern: more secure update, but can lead to a end of service from the provider.In our case you are right... We want stability even if internet die.
But, of course, it's always better to base your software on local javscript.So I think the better is having a property that allows to define the javscript URL pointing at the leaflet javascript, and having a sane default when this property is not defined.
Regards, -- Benoît Minisini.
How to make a new web component | Fabien Bodard <gambas.fr@xxxxxxxxx> |
Re: How to make a new web component | Lee <t.lee.davidson@xxxxxxxxx> |
Re: How to make a new web component | Fabien Bodard <gambas.fr@xxxxxxxxx> |