You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it will be very useful if CSS_PATH could be usable in Widget instances also, like it is already available in e.g App or Screen.
You could use live css to create advanced widgets. And I think it would be consistent in general.
This also allows you to make a choice. For example, in our application we try to separate the entire CSS into files - so we have created an appropriate function for this, which is simple and with the oneliner call it searches for a specific CSS file, reads its content and allows it to be inserted into DEFAULT_CSS like DEFAULT_CSS = get_relative_css(__file__). But this means that we are not able to use live reloading for such widgets (could be still workaround by working on the CSS file given in the Screen CSS_PATH).
The text was updated successfully, but these errors were encountered:
I think it will be very useful if CSS_PATH could be usable in Widget instances also, like it is already available in e.g App or Screen.
You could use live css to create advanced widgets. And I think it would be consistent in general.
This also allows you to make a choice. For example, in our application we try to separate the entire CSS into files - so we have created an appropriate function for this, which is simple and with the oneliner call it searches for a specific CSS file, reads its content and allows it to be inserted into DEFAULT_CSS like
DEFAULT_CSS = get_relative_css(__file__)
. But this means that we are not able to use live reloading for such widgets (could be still workaround by working on the CSS file given in the Screen CSS_PATH).The text was updated successfully, but these errors were encountered: