-
-
Good news first,
- efeu is updated to latest release and latest edge.
Bad news, - its not done automatically
- there are changes for ESP8266 in EspruinoBuild, but there is nothing new in provision.sh (?)
@MaBe, could you please tell me, what to do ? Right now efeu uses v2.2.1
- efeu is updated to latest release and latest edge.
-
-
I created videos with https://camstudio.org/ some time ago and would agree to Gordon (it can be a bit of pain, unless .....). Talking and using the mouse at same time, often results in different speed of both, and use of bad words ......
-
Sorry, I just spend vacations in Alberta, wait for next month please.
On long term, there will be an automatic update.
There are some minor changes in 2 py files, which need to be pushed to github.
Right now I've to these changes manually.
Next step will be to blacklist jswrapper files, an idea brought up by Gordon.
But once again, this will be next month. -
Lets start a discussion ;-)
blacklisting C files looks dangerous to me.
I could imagine to blacklist jswrap*.c files, but even that, at least for me, is like a mine field.
May be we could add some more defines to remove blocks of software, like waveformMy idea was to use wildcard to remove idle/init/kill which belong to a class
We could add class to wrapper with type idle
It could be set for waveform, and would be empty for pipe.Going through your list, I tried to get an overview what init idle and kill are used for
- init looks mainly important for some boards and for net, bluetooth. There is no need to blacklist them, we already have defines for that
- idle is used for waveform, serial and pipe. IMHO serial and pipe should never be blacklisted, waveform could be blacklisted
- kill usage is a mix, blacklist it for waveform should cause no problem
- init looks mainly important for some boards and for net, bluetooth. There is no need to blacklist them, we already have defines for that
-
-
-
@TomWS
Replacing exisiting code like jshardware.c with other code from unknown source would open a possible backdoor for virus etc. @Gordon gave me some examples for that.
Therefore the decision is to use c-sources from repositiory only. There we have a good chance to refuse dangerous code.
Requiring a md file for each submission is my recommendation. But I would not make this mandatory. Feel free to write and add pull request for md file where you miss it. Good starting point is the JSON mapping for each class/function/... in c-code.@allObjects, thanks for your explanation. You brought it to the point as always.
Any change like 3SPI would cause changes which are not easy to do, at least on my best knowledge. If it is a simple change only, I would recommend to add changes to Espruino repository itself.
I've no idea, what MDBT42Q supports. This should be done by somebody with better skills -
Just added a DigitalPort extension, to above repository
Especially guys in my age will have been waiting for this ;-)
https://github.com/jumjum123/EspruinoExtensions/tree/master/General/Digital -
Gordon keeps care on quality and usability of Espruino, and he is doing a perfect job.
But sometimes somebody somewhere somehow creates his own SuperDuper functions.
Functions, that could be of interest for others
Together with EFEU, see http://forum.espruino.com/conversations/334202/newest/ a first small repository is available now with first couple of nice extensions.If you are interested and would like to add your own extensions, please create a pull request for this repository https://github.com/jumjum123/EspruinoExtensions
-
You can find EFEU here http://www.jumware.eu:88/efeu
Its an online tool which supports you to create your own customized version of Espruino firmware.Please have in mind, it is beta.
It will not be updated to changes in Espruino before July, may we see each other in Alberta during that time ;-)
If you find problems, have ideas to make things better, or whatever, please use this forum for now.
As soon as everything becomes more stable, we will find other ways. -
-
-
-
Removing is not a good solution for me.
I'm one of the guys mentioned by you, having their own idea from time to time.
And since my server is not dedicated for my tool, ...Looke like I'll need something like an "provision.sh-changed-event" and do the job manually.
I'm pretty sure, this will not happen very often.
May be https://app.github-file-watcher.com/ is a solution -
-
For some weeks now, it is best solution to use gcc-arm-none-eabi-8-2018-q4-major
I've done some testing based on actual provision.sh and looks like- If we already have an older version of gcc-arm-none-eabi installed, provision.sh will never install v8
- if v8 is installed manually using command from provision.sh, older version is used, v8 is ignored
- after changing sequence in export to export PATH=/home/nodejs/http88/Espruino/gcc-arm-none-eabi-8-2018-q4-major/bin:$PATH v8 is used
Since I'm not an expert in this area, could please someone check
- If we already have an older version of gcc-arm-none-eabi installed, provision.sh will never install v8
-
-
-
I would like to automate upload for latest release to EFEU and checked this
https://api.github.com/repos/espruino/Espruino/releases
Problem is, that github API returns an empty array
Next checked
https://api.github.com/repos/espruino/Espruino/tags
Now I get a long list, now problem is sorting of this list.Found a (strange?) description, why I don't find anything for releases
https://stackoverflow.com/questions/18506508/whats-the-difference-between-tag-and-release
Any idea what I can do to get most actual release of Espruino ? -
Take a look to
https://github.com/jumjum123/EspruinoExtensions/tree/master/Family/ESP32/LED32x64It's an driver for 32*64 LED boards, based on an example by Espressif guys.
jswrap_LED32x64.c holds main connection from Espruino to source from EspressifI would be interested to hear more from your project
-
-
Hmmm,
on one hand I don't like to scan html files to get information,
and oppsite to you I like to give information, if it already exists in md filesOn the other hand, german wording "sometimes you have to jump over your own shadow", means my dislike should not stop a better solution
And would it be possible to add md files to http://www.espruino.com/modules ?Just one more idea, how do you create modules directory?
If there is a script, similiar to common.getJsonData, I could use this directly.
Depends, on how you create firmware.
If you use Espruino Build Tools, there is a precompiled lib and sdkconfig
Otherwise you have to setup a local platform, run through make sdkconfig, etc.
AFAIK, ESP-IDF uses 2nd core for wireless tasks.