-
-
-
-
Well,
I usually prefer a construction like
var Interval = 1000; setTimeout(()=>{ draw(); }, Interval - (Date.now() % Interval));
if
- (calculation and) drawing may take longer than 1000ms (should be
rare) or - the
Interval
may change dynamically (e.g. depending on screen lock)
But, most often, a simple
setInterval
should be sufficient. - (calculation and) drawing may take longer than 1000ms (should be
-
Well,
I don't think you should judge your user's opinions just by the posts in this topic.
To use myself as an example: being critical (e.g., in terms of privacy and GDPR compliance) does not necessarily means "dissent" - it's just that I want to avoid running into troubles by not having looked at the consequences of this switch.
On the other side: since I am participating in a GitHub discussion (on the new GitHub "achievement" badges), I definitely prefer the existing forum!
-
Well,
that's indeed an interesting finding, but I doubt that it would have a significant effect on performance:
computeDiffusion
does a lot of computations and rounds in the end only - replacing it by+ 0.5
and relying on internal truncation and clamping would probably not be faster but less intuitive. However, rounding (of small values) is important for the final display any may therefore not just be omitted completelycomputeHeating
does not have any noticeable effect on the overall speed (it deals with 16 pixels only, not 256)prepareDisplay
rounds indices into an array only - and this cannot be omitted as you may easily test yourselfvar Test = [0,1]; print(Test[0.5]);
outputs
undefined
rather than0
or1
.Anyway, thanks for your effort!
-
@Gordon @ChrisS I don't want to discuss any GDPR issues of Windows or other Microsoft products here - the question should instead be: will the migration to GitHub discussions (which should lower the load on Gordon's shoulders) be safe for users (and Gordon himself!)?
Right now, it seems so (from the viewpoint of a non-lawyer, of course)
Yes, GitHub was bought by Microsoft (sigh!) but they officially(!) claim to be GDPR-compliant (and seem to offer the data processor contracts Gordon may need to be safe himself). For me as an end-user, this claim is sufficient - any further inspection should be left to lawyers.
As a consequence, I'd now welcome the migration to GitHub discussions (although I still don't really like the idea that anybody would need to register with GitHub just in order to join a discussion about Espruino - at least, "foreigners" should be able to read what was written in the forum)
-
From GitHub's Data Protection Agreement, the following excerpt seems promising to me
To the extent GitHub uses or otherwise processes Personal Data subject to the GDPR for GitHub’s legitimate business operations incident to delivery of the Online Services to Customer, GitHub will comply with the obligations of an independent data controller under GDPR for such use. GitHub is accepting the added responsibilities of a data “controller” under the GDPR for processing in connection with its legitimate business operations to: (a) act consistent with regulatory requirements, to the extent required under the GDPR; and (b) provide increased transparency to Customers and confirm GitHub’s accountability for such processing. GitHub employs safeguards to protect Personal Data in processing, including those identified in this DPA and those contemplated in Article 6(4) of the GDPR.
-
@Gordon may https://rewind.com/blog/top-github-compliance-concerns/ help you with your questions around GDPR compliance?
StackExchange may also have some valuable information in that context
-
I'm not a lawyer, but GitHub has published a lengthy data protection statement which mentions the GDPR several times. For the moment, this looks somewhat promising.
@Gordon I don't know the current regulations in the UK - but in the EU one would have to prove GDPR compliance of all used (sub)services as well (by proper data protection statements and subcontracts)
-
-
-
-
I always had the idea to bring the OneDollar.js recognizer to the Bangle.js - but I won't find the time in the near future. It is extremely compact and could fit into this small system.
With $1, solutions such as the brilliant Palm Graffiti could become possible!
-
-
Today I recognized that clicking in the "Clocks" tab in the official Bangle App Loader no longer restricts the display to just clocks.
The URL shown in the browser includes a "#clock" fragment and the display flickers briefly - but both the "Default" tab remains highlighted and the list of shown apps remains the same.
The other category tabs ("Games", "Tools" etc.) are affected as well, but the sorting tabs "New" and "Updated" still work as usual.
Opening developer tools does not reveal any error messages.
I tested with Chrome 96.0.4664.93 on macOS 10.13.6 and with Chrome 97.0.4692.99 under macOS 11.6
-
just for the records: version 1.0 of AC-AC is now available on the official Bangle App Loader
-
-
-
-
-
Yesterday, a new version of my App (AC-AC) was merged into the master branch of espruino/BangleApps.
But now, more than 16 hours ago, it is still the old version which is available through the Bangle.js App Loader.
And, yes
- I checked that
metadata.json
contains the new version number and that the new file was committed - I definitely reloaded the App Loader web page (using Chrome with the Developer Tools Window open)
How long will I have to wait for the update?
[Edit] I just found one potential problem: the
ChangeLog
file had a.txt
suffix - may that be the reason for not being shown? Anyway I just updated the file name and started a new pull request - I checked that
-
Just to let you know: I took the opportunity of a bug fix to raise the version of AC-AC to 1.0 - you should soon be able to find the new version in the official Bangle.js 2 app loader.
Many thanks to nxdefiant who reported the bug and to johan-m-o who found the underlying typo before I even became aware of the issue!
-
Thank you very much, @Gordon!
Well,
as someone who "runs with the hare and hunts with the hounds", I came in contact with many discussion forums in the past few months. My personal conclusion - from a user's point of view(!):
On the other hand, "discourse" looks like a noteworthy alternative as it provides a clear user interface not unlike this forum.
With greetings from Germany,
Andreas Rozek