PulseJS

A global state and logic framework for reactive Javascript apps created by @jamiepine. Used by @NotifyTeam.

[PulseJS @PulseFramework]

Coming in the next version, a solid, typesafe event system for Pulse. Events are useful for many reasons, such as alerts and small UI triggers.

Check it out!

https://t.co/GgIHLMTNsC

[PulseJS @PulseFramework]

@NotifyTeam @spacedriveapp @jamiepine lose*

[PulseJS @PulseFramework]

Can anyone recommend a decent UI framework for React Native, that is also compatible with React Native Web?

Looking for a UI framework to build fully cross platform components.

[PulseJS @PulseFramework]

@NotifyTeam @cloudz_dev @jamiepine @GoPysyk @twomad wtf

[PulseJS @PulseFramework]

@NotifyTeam @jamiepine @GoPysyk @twomad function Eeeeeeeeeeeeeeeee {
return DingDong
}

[PulseJS @PulseFramework]

Pulse 4 will be a syntax simplification, including a global instance by default, similar to React itself.

[PulseJS @PulseFramework]

Pulse 3.3 is out now, and we have our own NPM org!

See how you can upgrade here: https://t.co/zVfkMBaUoF

[PulseJS @PulseFramework]

If you're interested in the internals, this is the current implementation inside Pulse.

Learned a few handy Typescript tricks writing this too.

[PulseJS @PulseFramework]

Currently, in order to achieve this with Pulse you must use State combined with a watcher in your component and maybe a function (or action) to mimic an "emitting" syntax.

It's not a clean solution and traditional event systems do not have typesafe payloads either.

[PulseJS @PulseFramework]

Coming in the next version, a solid, typesafe event system for Pulse. Events are useful for many reasons, such as alerts and small UI triggers.

Check it out!

https://t.co/GgIHLMTNsC

[PulseJS @PulseFramework]

@DevBenno Reinventing the wheel is not the same as building on top of the wheel. If you feel like there’s something missing—make it, if it interests you.

[PulseJS @PulseFramework]

Had a little mental detour this evening and decided to imagine what a conceptual "Pulse UI" would look like.

This would compile to a home grown recipe of React, React Native and RNW.

I also learned how to write a syntax parser for VSCode with Regex, very fun to play with.

[PulseJS @PulseFramework]

@nurodev just colon* my bad

[PulseJS @PulseFramework]

@nurodev I can see why that'd be necessary. I just think the second set of semicolons are a bit much. I do like this however...

[PulseJS @PulseFramework]

@nurodev Something more like this?

[PulseJS @PulseFramework]

@nurodev I love the idea for the imports. will change to that. Not sure about the parenthesis though, trying to avoid them honestly. I also think since they wouldn’t work exactly like parameters, just bolt-on styles, it could be misleading.

[PulseJS @PulseFramework]

@nurodev don’t leave me on this cliff hanger!!! dm me ideas for tweaks

[PulseJS @PulseFramework]

IT GETS YOU THINKING

[PulseJS @PulseFramework]

Docs!!!!!

[PulseJS @PulseFramework]

Releasing Pulse 3.0 in the next 24 hours. With docs.

Here's a preview of the latest syntax, featuring the new Controller instance-a container for State, Collections, Routes and Actions.

This update fixes an annoying cyclic dependency issue in large Pulse 3 projects.

[PulseJS @PulseFramework]

Also Selectors have been added to Collection instances.

Previously, you needed to create a Computed function that returns a cached copy of an item from a Collection based on State that maintains the id of the "selected" account.

Now just use a Selector

[PulseJS @PulseFramework]

Releasing Pulse 3.0 in the next 24 hours. With docs.

Here's a preview of the latest syntax, featuring the new Controller instance-a container for State, Collections, Routes and Actions.

This update fixes an annoying cyclic dependency issue in large Pulse 3 projects.

[PulseJS @PulseFramework]

We can now call `Core()`to get all controller instances, making for less imports and no cyclic dependency issues.

Also added a built-in error handler for actions.