- stuff
- things
- cool
- important is a java keyword. This declares the class that you are creating so it can then be used else where in your code.
- It is Vanilla
- I think that this is what puts what ever your created through the different parts of code and pushs it to show up in the field below.
- I believe that this isn't vanilla as it is something that was created through the code.
- This constructor is laying out how you need to set up the information.
I don't need to read slides and bring everything togeter for you, you can do that on your own time. In my 30 minutes, I will be showing what the solution is, how it works and trying to make something ridiculous, quickly.
This is your take home sheet for when you are trying to convince your co-worker that they need to try this out and help us go further together.
Imagine this is a fraction of what we've been building.
Welcome to HAX - https://open.spotify.com/track/4hD4nwWtkqTmf5U8FY3SsE?si=40f8b07857004916
Want to learn more about front end web development? Web components | |
let you create framework-agnostic components by creating new valid HTML | |
tags that work anywhere! Looking to share components across React, | |
Angular, Vue or in your CMS project? Need to learn tooling, bundling, | |
SEO, OpenWC, Lit or even just where to start? Whether you're a HAX core | |
maintainer, a Lit pro, an educator, or someone looking to learn how | |
web components can benefit them, we're all here to learn and share | |
valuable knowledge about web components at < hax-camp >! |
<!DOCTYPE html>
<html>
<head>
<meta charset="UTF-8">
<title>Page Title</title>
<link rel="stylesheet" href="styles.css">
</head>
<body>
import { html } from 'lit'; | |
import { fixture, expect } from '@open-wc/testing'; | |
import '../src/app.js'; | |
describe('A Science card', () => { | |
let element; | |
beforeEach(async () => { | |
element = await fixture(html`<learning-card class="two" type="science"></learning-card>`); |
- make an account on npmjs.com
- verify your email address
- make an organization that's the same name as your github but lowercase (do this on npm)
- Add the other team members to the organization (1 person leads in doing this while the others get added in, like github)
- type
npm login
and login with your credentials / email address you entered - Edit the
package.json
file and make the following changes: "version"
set this to somethin like"0.0.1"
as this will be your 1st version / a test
/** | |
* Wrapper to leverage curl when possible to avoid potential socket connection | |
* issues with certain SSL connections | |
*/ | |
function _cis_connector_make_request($url, $options){ | |
// support developers overloading the request method, specifically curl | |
// as some systems can have issues with SSL configuration and socket connections | |
if (function_exists('curl_init')) { | |
$headers = array(); | |
foreach ($options['headers'] as $property => $value) { |
I am not on the WHATWG / W3C, I'm just someone who implements and tracks low level JS/HTML APIs. The current direction and discussions around this topic are interesting yet seem to revolve around the concept of anonymous class instances of element definitions that ship with other elements.
The advantages of this methodology involve being able to ship completely containerized code that
is not going to suffer issues with cool-stuff
tag being registered globally when trying to
download and implement whatever-tag
which happens to ship with a competing reference to cool-stuff
.
The scoped proposal can be found here: https://github.com/WICG/webcomponents/blob/gh-pages/proposals/Scoped-Custom-Element-Registries.md
pandora’s vox: on community in cyberspace
by humdog (1994)
when i went into cyberspace i went into it thinking that it was a place like any other place and that it would be a human interaction like any other human interaction. i was wrong when i thought that. it was a terrible mistake.
the very first understanding that i had that it was not a place like any place and that the interaction would be different was when people began to talk to me as though i were a man. when they wrote about me in the third person, they would say “he.” it interested me to have people think i was “he” instead of “she” and so at first i did not say anything. i grinned and let them think i was “he.” this went on for a little while and it was fun but after a while i was uncomfortable. finally i said unto them that i, humdog, was a woman and not a man. this surprised them. at that moment i realized that the dissolution of gender-category was something that was happening everywhere, and perhaps it was only just very obvious on the ne