Comments (2)
Possible problem of manual context control is:
- no destructor - not clear how to detach effect
- async fx figures out current aspect via callstack
yes, that's the problem. Since calling spect
is not limited to current scope, we have to push and pop context, that is manual control over context, that can possibly come along with scope-bound control.
- very similar to incremental-dom. That's actually a high-level extension of it.
So what would that be?
// attach aspect per fn-scope
spect(target, el => {
})
// manual control over scope
groupStart(target)
groupEnd()
What about setting state on manual context? How should that trigger redraw?
Maybe we should provide scope(el)
, scopeEnd()
methods, but only as low-level machinery. state
should be able to call defined scope at any moment. For that purpose tiny scoping functionscope(el, () => {})
is the most natural choice.
Whatever good the idea is, that's just a round-walk path: scopeStart is nice, but we have to rerender scope. Defining scope from inside is impossible, must be scope(target, () => {})
, which is essentially the same as spect(target, () => {})
.
To make spect compatible with jquery, we can make it a default export, so that user would just import $, {} from 'spect'
, so that if want to rename $ to something different - just import spect from 'spect'
from spect.
Ok, so the initial issues are addressed:
- to resolve jquery conflict -
import $, { fx } from 'spect'
to resolve conflict - to resolve naming inconsistency - see prev.
- selector usefulness - it is shortcut.
from spect.
Related Issues (20)
- h: cache element by stack instead of creating anew HOT 1
- h: drop parser, use htm HOT 2
- v β f, v. Shaving off API, v as proxy HOT 6
- operators HOT 1
- 0b HOT 1
- v ~~as proxy~~ as observable HOT 1
- v: access multiarg values as [0], [1] etc. HOT 1
- $ β selector-collection HOT 2
- h: keyed. Why not morphing? HOT 3
- v(v0, v1, v2) - observables as args HOT 1
- $: pseudos? HOT 1
- h/$ - a nice way to convert data to template? HOT 2
- add Github Corner to spect.ly and fix typo HOT 2
- v23: animevents-only $ HOT 1
- 23.0: API reconsiderations, half-a-year later
- $: stop infinite recursion HOT 1
- $: first run flickers
- $(parent, β> childβ)
- h: lists; diff algo is underused. Possible syntax HOT 1
- spect@24 breaks integration tests with subscribable-things HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from spect.