-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge of my local changes #64
Comments
@cymplecy , @jsccjj ,
The problem with the environment block, is that you are only allowed to get the value of an environment variable. You are not allowed to set it. So we need to prevent somehow that this new block cannot be dropped e.g. in the node-set block. It is too long ago that I worked with Blockly, so I don't know anymore how to accomplish that. If you guys have an idea, please let me know! P.S. I got a little surprise at work that I have to work tomorrow on sunday. So not much time left to continue on this release this weekend :-( |
Hi @cymplecy , @jsccjj ,
So we specify the minimal required version and with "^" the latest minor release will automatically be downloaded if available. And if we want to switch to a new major Blockly version, we only need to adjust the version number to the new major version number. This allows us to keep our node easier up-to-date with future Blockly releases from Google. P.S. the |
Going to power up a test instance tonight and get my brain back into Blocky
Dev mode :)
…On Sat, 29 May 2021, 15:16 bartbutenaers, ***@***.***> wrote:
Hi @cymplecy <https://github.com/cymplecy> , @jsccjj
<https://github.com/jsccjj> ,
I had to wait 30 minutes while waiting for my son to help him with his
statistics exam...
So to avoid wasting this time interval, I have tested my old local changes
for "2" and "3" in the 1.1.0 branch version of this node ;-)
And I was lucky since it seemed to be still working....
- I have removed the Blockly library clone that we had copied locally
to our project.
- All the files Blockly files required by the frontend are now served
by the backend endpoint, which will get all the required files from the
downloaded NPM module directories (see next step).
- I have added Blockly NPM dependencies
<https://github.com/bartbutenaers/node-red-contrib-blockly/blob/release-1.1.0/package.json#L5>
to our package.json file:
"dependencies": {
"blockly": "^5.20210325.1",
***@***.***/field-date": "^4.2.14"
},
So we specify the minimal required version and with "^" the latest minor
release will automatically be downloaded if available. And if we want to
switch to a new major Blockly version, we only need to adjust the version
number to the new major version number.
This allows us to keep our node easier up-to-date with future Blockly
releases from Google.
P.S. the @blockly/field-date NPM package allows us now to implement a
Date picker block (see here
<#36>).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#64 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAR7RNFIQCBKMNEEFU4H5JLTQDZM7ANCNFSM45VBDYZA>
.
|
Same here. I will start looking into the code tonight |
@cymplecy, |
All seem OK |
I have an old local version of the blockly node at home. Due to the pull request of @jsccjj those changes will have to be reviewed and tested, because they probably won't work anymore.
These are the major changes:
The text was updated successfully, but these errors were encountered: