i encountered something during the application writing: it would have been so useful to use one css pad/file for 3 different pdfs. This is a future feature wish: to be able to load and reuse css files.
> i encountered something during the application writing: it would have been so useful to use one css pad/file for 3 different pdfs. This is a future feature wish: to be able to load and reuse css files.
/cc @mb
UI/UX proposal: beside the stylesheet button, you have a drop down or something like a text input and can drop the URL of another pad in to be re-used? Then when generating, it reads that URL and uses that CSS instead.
Not sure what the stylesheet button would then do... go to the URL pointed to or open an empty pad? I can imagine if you forget, you edit CSS which isn't loaded... there may some visual cues to add to show we're loading from URL...
UI/UX proposal: beside the `stylesheet` button, you have a drop down or something like a text input and can drop the URL of another pad in to be re-used? Then when generating, it reads that URL and uses that CSS instead.
Not sure what the `stylesheet` button would then do... go to the URL pointed to or open an empty pad? I can imagine if you forget, you edit CSS which isn't loaded... there may some visual cues to add to show we're loading from URL...
/cc @mb
UI/UX proposal: beside the
stylesheetbutton, you have a drop down or something like a text input and can drop the URL of another pad in to be re-used? Then when generating, it reads that URL and uses that CSS instead.Not sure what the
stylesheetbutton would then do... go to the URL pointed to or open an empty pad? I can imagine if you forget, you edit CSS which isn't loaded... there may some visual cues to add to show we're loading from URL...