|
163 | 163 |
|
164 | 164 |
|
165 | 165 |
|
166 | | - <div style="margin-bottom: 20px;"> |
167 | | - i include here a standard example of web components, which i feel went some way as to introducing the ability to include complex functionality |
168 | | - into web pages, i feel however it fell short on a number of issues i have solved with my component.js library, these are |
169 | | - <ul> |
170 | | - <li> |
171 | | - elements were scoped to the global namespace, always a problem when functionality gets ever more complex its only a matter |
172 | | - of time before clashes occur |
173 | | - </li> |
174 | | - <li> |
175 | | - methods and properties associated with the component were added to the host node of the element, again thats ok for simple |
176 | | - components, but when components get ever more complex its going to be a problem |
177 | | - </li> |
178 | | - </ul> |
179 | | - </div> |
180 | | - |
181 | 166 | <div> |
182 | 167 | <p> |
183 | 168 | to me a component / module should have a standard lifecycle that is |
|
236 | 221 | <div class=hr2></div> |
237 | 222 |
|
238 | 223 |
|
239 | | - <div style="margin-bottom: 20px;"> |
240 | | - users are able to supply their own components and therefore build up a rich selection of components |
241 | | - </div> |
242 | | - <div style="margin-bottom: 20px;"> |
243 | | - to get the whole thing started and supply and example, i have created the first, simple, example |
244 | | - </div> |
245 | | - |
246 | | - <div style="margin-bottom: 20px;"> |
247 | | - <a href="select/select.html"> |
248 | | - custom select |
249 | | - </a> |
250 | | - </div> |
251 | | - |
252 | | - <div style="margin-bottom: 20px;"> |
253 | | - <a href="checkbox-one/checkbox-one.html"> |
254 | | - checkbox-one |
255 | | - </a> |
256 | | - </div> |
257 | | - |
258 | | - <div style="margin-bottom: 20px;"> |
259 | | - <a href="log/log.html"> |
260 | | - log |
261 | | - </a> |
262 | | - </div> |
263 | | - |
264 | | - <div style="margin-bottom: 20px;"> |
265 | | - keep checking back for more examples and an interface for user supplied examples |
266 | | - </div> |
267 | | - |
268 | | - |
269 | 224 |
|
270 | 225 |
|
271 | 226 |
|
272 | 227 |
|
| 228 | + <div style="margin-bottom: 20px;"> |
| 229 | + i include here a standard example of web components, which i feel went some way as to introducing the ability to include complex functionality |
| 230 | + into web pages, i feel however it fell short on a number of issues i have solved with my component.js library, these are |
| 231 | + <ul> |
| 232 | + <li> |
| 233 | + elements were scoped to the global namespace, always a problem when functionality gets ever more complex its only a matter |
| 234 | + of time before clashes occur |
| 235 | + </li> |
| 236 | + <li> |
| 237 | + methods and properties associated with the component were added to the host node of the element, again thats ok for simple |
| 238 | + components, but when components get ever more complex its going to be a problem |
| 239 | + </li> |
| 240 | + </ul> |
| 241 | + </div> |
273 | 242 |
|
274 | 243 |
|
275 | | - <code class=code> |
| 244 | + <web-editor id=ex3 component fullsize> |
276 | 245 |
|
277 | 246 | class newElement extends HTMLElement { |
278 | 247 |
|
|
307 | 276 |
|
308 | 277 | }//class |
309 | 278 |
|
310 | | - </code> |
| 279 | + </web-editor> |
311 | 280 |
|
312 | 281 | <br> |
313 | 282 |
|
|
0 commit comments