Skip to content

docs: add Blaze (Meteor) to the framework list - #3434

Open
dupontbertrand wants to merge 1 commit into
gridstack:masterfrom
dupontbertrand:docs/blaze-meteor-framework
Open

dupontbertrand wants to merge 1 commit into
gridstack:masterfrom
dupontbertrand:docs/blaze-meteor-framework

Conversation

@dupontbertrand

Copy link
Copy Markdown

Description

Adds a Blaze (Meteor) entry to the "Specific frameworks" section of the README.

Context. Meteor (GitHub) is a full-stack JavaScript app platform, and Blaze (GitHub) is its library for live-updating user interfaces, one of the UI options of Meteor apps alongside React, Vue and Svelte. Blaze 3 runs on Meteor 3, and the upcoming Blaze 3.1 makes jQuery optional. There was no gridstack integration for Blaze so far, so Blaze apps had to wire gridstack by hand.

The package. dupontbertrand:gridstack on Atmosphere, Meteor's package registry. Source: dupontbertrand/blaze-gridstack, MIT.

{{> gridStack items=widgets itemTemplate="card" options=gridOptions onChange=onLayoutChange}}

gridstack is not bundled: the app installs it from npm (meteor npm install gridstack) and the package checks the installed version at startup, so updates and security fixes come straight from npm. Supported and tested: gridstack 12, 13 and 14, on Blaze 3.1 without jQuery, Blaze 3.1 with jQuery, and Blaze 3.0.

The component takes a reactive array of items and keeps the grid in line with it: items are added, removed and moved as the data changes, a Blaze template is rendered inside each item, and user moves and resizes are reported through onChange. gridstack owns the item elements and Blaze only renders inside each item's content element, so the two never fight over the same DOM nodes.

Docs only: one line added to README.md.

Checklist

  • Created tests which fail without the change (if possible): not applicable, docs only
  • All tests passing (yarn test): no code change
  • Extended the README / documentation, if necessary

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant