js-widget | Template for building JavaScript widgets | Widget library

There are three distinct (but quite similar) cases:

• web components
  They are supposed to be an encapsulated web fragment. If you want, it's a smarter alternative to </code>s. Its main use case (and what it was designed for) is to display ads in a page and guarantee the host can't mess with its internal logic and rendering.</p> </li> <li><p><a href="https://html.spec.whatwg.org/multipage/custom-elements.html#custom-elements" rel="nofollow noreferrer"><strong><code>custom elements</code></strong></a><br /> These are, simply put, declared and registered custom HTML tags. The advantage of using them is being able to mark them as <em>off-limits</em> in any outer framework, stating: <em>"this custom element is not one of your custom components, treat it as an HTML tag"</em>.</p> </li> <li><p><strong><code>framework components</code></strong><br /> By default, modern JS frameworks (Angular, React, Vue) use this pattern internally: their internal components look like custom elements (case 2). <strong>But they are not.</strong> They are just internal conventions, without ever making it into the HTML markup output of the app.<br /> Here's what happens internally: when the template is parsed, if an unknown HTML element is met, the framework assumes it's one of its registered components. If it is, the tag is not rendered. A new instance of that component is created and the tag is replaced with the contents of the component's template (or the result of its render function).<br /> All of the above frameworks, when running into an unknown html tag that is not a registered custom component will issue a warning along the lines of <em>"hey, did you forget to register this component?"</em>. Unless it's registered as a custom element (case 2) - in which case they treat it as as such: an HTML tag.</p> </li> </ul> <p>Vue handles all of the above with grace. What you choose for your widgets largely depends on context and desired end result.</p> <p>Here are the answers to your questions:</p> <blockquote> <ol> <li><em>Do I need to be thinking Web Components here or can the widgets be actual Vue applications that we embed somehow?</em></li> </ol> </blockquote> <p>You shouldn't go with Web Components if you want to be able to style them from the context.</p> <blockquote> <ol start="2"> <li><em>If the widgets should be created as Web Components is there any difference between using the <code>@vue/web-component-wrapper</code> or the <code>vue-custom-element</code> library?</em></li> </ol> </blockquote> <p>Yes, there is. <code>@vue/web-component-wrapper</code> produces web components (encapsulated DOM framents).<br /> <code>vue-custom-elements</code> declares and uses custom elements (custom HTML tags). Their content is HTML markup (not encapsulated). The advantage of using custom elements is being able to inform outer frameworks: don't treat this custom element as one of your own components, it's handled by something else (Vue, in our case). Treat it as HTML markup.</p> <blockquote> <ol start="3"> <li><em>Whichever option we choose can we make full use of features that you would use in any normal Vue application - Vue router, Vuex for state management etc (and can state be shared across those widgets)?</em></li> </ol> </blockquote> <p>Yes. Whichever option you choose, you're still using JavaScript (every widget/app has unrestricted access to the entire context). You can also inject dependencies into your widgets, allowing them to communicate (by modifying the same external dependency - a router, a state management module, etc...). This is pretty much the standard mode in which every Vue instance normally operates. In simpler words, a Vue (sub-)component can function without a parent component and is, essentially, a Vue app. (or, if you prefer, every Vue app is a Vue instance and all of its sub-components are also Vue instances).</p> <blockquote> <ol start="4"> <li><em>Would the widgets need to be fully styled or would it be best practice to leave all the styling of the components to the parent app (or a combination of the two)?</em></li> </ol> </blockquote> <p>It's entirely your code design choice. It's easy to <a href="https://vue-loader.vuejs.org/guide/scoped-css.html" rel="nofollow noreferrer">scope CSS</a> in Vue. But there are great advantages in styling from above (DRY-er code). Also, having styles coming from context means less CSS rules applying, although that hardly qualifies as a performance issue. Obviously, take into consideration the answer to the first question.</p>

I found the answer here, in an open issue on Github

I ran the following in Anaconda prompt:

Its because you are not escaping the quotes correctly you need to escape the single quotes in the statement

The following code is bound on load of the page. When #adform-outstream is scrolled to, we add a class to it and visually reveal it. I used CSS for the transition, but you can handle it however you see fit. One important detail is to remove the scroll listener once the scroll trigger has been reached. Otherwise, it will continue to fire and slow things down.

It might be easier for you to have a single widget file (generated by you with the default configuration) and use the user-provided information as parameters.

domainName: www.google.com vastUrl: www.vast.xx.com position: Bottom right

I had the same problem, and following this vvk2001github https://github.com/jupyter/notebook/issues/4399 fixed it for me.

Uninstall tornado 6 and reinstall tornado 5.

Basically the composer update was not generated the extension.php properly. There was the alias issue which worked after delet the vendor folder on server and update the composer again.

I used to do it like this:

From http://ipywidgets.readthedocs.io/en/latest/user_install.html :

Question: When I display a widget or interact, I just see some text, such as IntSlider(value=0) or interactive(children=(IntSlider(value=0, description='x', max=1), Output()), _dom_classes=('widget-interact',)). What is wrong?

Answer: A text representation of the widget is printed if the widget control is not available. It may mean the widget JavaScript is still loading. If the message persists in the Jupyter Notebook or JupyterLab, it likely means that the widgets JavaScript library is either not installed or not enabled. See the installation instructions above for setup instructions.

Page refresh fixed issue for me. I think installs referred to in my question were still required.