A lightweight, very flexible QuickBase API for Node.js
A lightweight, very flexible QuickBase API for PHP
JavaScript implementation of RFC4122: A Universally Unique IDentifier (UUID) URN Namespace
Clean up a freshly converted XML-to-JSON object in a sensible way
A lightweight GoCanvas SDK
Full-sized drag & drop event calendar
tflanagan/fullcalendar-scheduler 0
FullCalendar add-on for displaying events and resources
pull request commenttflanagan/php-quickbase
Hey, thanks for the PR.
I'm away from a computer for the next week or so, but there is room for improvement here.
This is how I dealt with it in JS: https://github.com/tflanagan/node-quickbase/blob/v2.x/quickbase.js#L314
I guess I missed it in the port to PHP.
comment created time in 10 days
push eventtflanagan/node-qb-table
commit sha 122ca1c4906fc74bb8ba0b5521996c046731596f
update quickbase
push time in 17 days
created tagtflanagan/node-quickbase
A lightweight, very flexible QuickBase API for Node.js
created time in 17 days
push eventtflanagan/node-quickbase
commit sha 00677869ace445a093f41d26705c9ee3268989b9
js: fix for when import does not return rids
push time in 17 days
issue closedtflanagan/node-e-trade
JSON URL returned from ETrade for Lots
First off, awesome library, has been immensely helpful, thank you!
To get specific lots, it looks like etrade provides them, accessible through returned URLs in the responses:
E.g.
{ lotsDetails: 'https://api.etrade.com/v1/accounts/<some id>/portfolio/<some id>.json' }
What would be the easiest way to sign this URL and execute it using this library?
And/or know of getting the lots for specific executed orders an easier way? I've been through the order, instrument and transaction details, but never found any info on lots.
Thanks!
closed time in 18 days
nickjag
issue commenttflanagan/node-e-trade
JSON URL returned from ETrade for Lots
Added in f124aa3 and is available in v0.2.0
comment created time in 18 days
push eventtflanagan/node-e-trade
commit sha 541b3711133c331d73aeefb9909a2471410a27eb
ignore build.js
push time in 18 days
push eventtflanagan/node-e-trade
commit sha f124aa3e57dbacea8e13450f446784d803b202de
src: added viewLotsDetails method
commit sha f9eee2f2f1ebb2c2fff4bd16ff2980127ae5546b
src: sort methods
commit sha b86ddf6ef7231d3097c2c9123412711454f0cac9
src,deps,meta: update build process, update dependencies
commit sha 7937968c5015946606da5eb6715bb5ccb849d371
Merge branch 'master' of github.com:tflanagan/node-e-trade
push time in 18 days
issue commenttflanagan/node-e-trade
JSON URL returned from ETrade for Lots
@nickjag
I can't seem to find any documentation on lotsDetails or lots either.
I'll add the method to the library at some point today.
getBasicRequest, signRequest, and request are all private methods, you wouldn't be able to access them directly (well... js) but in essence:
async viewLotsDetails({ accountIdKey, positionId }: ViewLotsDetails){
const requestOptions = this.getBasicRequest({
url: `accounts/${accountIdKey}/portfolio/${positionId}.json`
});
this.signRequest(requestOptions);
return this.request<any>(requestOptions); // TODO: find documentation for lots for more specific typing
}
comment created time in 18 days
pull request commentjitsi/jitsi-meet
feat: introduce green screen effect
@hmharshit
What was the fix to webpack.config.js?
comment created time in 20 days
push eventtflanagan/node-quickbase
commit sha 1c898ae378236977d47e17bafef6cd94713171b5
docs: update docs
push time in 23 days
push eventtflanagan/node-quickbase
commit sha 907457234521d2a8de0e160346cb58e98214ae7e
src: replace dbid terminology
push time in 23 days
push eventtflanagan/node-quickbase
commit sha 312c51e11a0075f0c4fcd581e1256c062fff8a38
src: enhance error reporting
push time in 23 days
push eventtflanagan/node-quickbase
commit sha 7d4a6988268d86a953790a85baa0eea9e8ef77af
src: fix field typings
push time in 24 days
created tagtflanagan/node-quickbase
A lightweight, very flexible QuickBase API for Node.js
created time in a month
push eventtflanagan/node-quickbase
commit sha 859b23e163cb53eec604378fd7475465ae7fe0cc
src: add CLASS_NAME property
commit sha a549e6f5c9db4342ad2bb0a81b9d0322b89cf23b
docs: update docs
push time in a month
created tagtflanagan/node-quickbase
A lightweight, very flexible QuickBase API for Node.js
created time in a month
push eventtflanagan/node-quickbase
commit sha c67bac7634fe5a2d0a5a633f49ebf8120b34c63d
src: added CLASS_NAME property
commit sha 73e60cb2a60c8269e6d637b669e97309e92b04bd
docs: updated docs
push time in a month
push eventtflanagan/node-quickbase
commit sha 2137ce8533dd7bdfddde49a8cba0230810ab162a
docs: update docs
push time in a month
push eventtflanagan/node-quickbase
commit sha 917b057de55e51a008da461551abf2136278f922
deps: update dependencies
push time in a month
push eventtflanagan/node-quickbase
commit sha ef65d6fa5fdfce732c6632040879210eda9b6aed
update build process
push time in a month
push eventtflanagan/node-quickbase
commit sha 70fc8a22ce98795e23395e087d09a376bfe1ad67
update build process
push time in a month
created tagtflanagan/node-quickbase
A lightweight, very flexible QuickBase API for Node.js
created time in a month
push eventtflanagan/node-quickbase
commit sha a2b945f613a75e3e3e283c51964c297251fe6313
docs: update docs
push time in a month
push eventtflanagan/node-quickbase
commit sha 91d4f44fdad11b4f2ed9e94f9d71f7d9c637494f
assets: added openapi json documentation for tracking purposes
commit sha 2a7eff530972c2d7823c2a8988d9dfa90542f7e9
assets: update oas spec
commit sha 2db830d0993b2dc5c06e26a63325158267e58cbb
src: added relationship and file related methods
commit sha 6c881e9ee6cd13bbcfac463ebee1563505b5e68a
src: removed return await
push time in a month
pull request commentjitsi/jitsi-meet
feat: introduce green screen effect
@jallamsetty1, if you could try going to https://meet.quickbase.dev/ and testing it there. I'm curious what would happen. (This is my personal testing environment)
comment created time in a month
pull request commentjitsi/jitsi-meet
feat: introduce green screen effect
I'm not able to reproduce the issue in my test environment. My test environment also was missing the analytic function, however, that was not preventing the feature from working.
As I do not think the webworker vs requestAnimationFrame concept is what's at fault, I'm curious about your environment and what's going on.
comment created time in a month
push eventtflanagan/jitsi-meet
commit sha 64c9f9bad1f37c4b891070870c7cf4fca8b16c79
green-screen: added missing createVideoGreenScreenEvent analytics event
commit sha ba4f797cf1077456cc70f1615bc7b781e5e0d995
Merge branch 'green-screen' of github.com:tflanagan/jitsi-meet into green-screen
push time in a month
pull request commentjitsi/jitsi-meet
feat: introduce green screen effect
Thanks for your comments. I apologize for the errors, could you elaborate?
I'll do more testing with the WW approach and try to find the missing commit from my side to resolve your errors.
comment created time in 2 months
issue commenttflanagan/node-quickbase
Hey @jtorrence1,
Correct, when you are using a user token you do not need an app token. However, if you are using a ticket, you must supply an app token if the Quick Base application is setup to require it.
Glad you were able to figure it out on your own.
comment created time in 2 months
issue commenttflanagan/node-quickbase
Quick Base's documentation is incomplete.
Please refer to the README for how to include an app token (it is commented out).
const quickbase = new QuickBase({
realm: 'demo',
appToken: '<app token>'
});
This is only required for "client-side" work, where you want to consume to currently logged in users session. Keep in mind you must call getTempToken first.
comment created time in 2 months
issue commenttflanagan/node-quickbase
bluebird inclusion leads to large memory usage increase
@BryceBarbara bluebird removal has been finalized with the release of v4 - 95ca006
comment created time in 2 months
created tagtflanagan/node-quickbase
A lightweight, very flexible QuickBase API for Node.js
created time in 2 months
push eventtflanagan/node-quickbase
commit sha 0797f03650feb68d231ebe3a97de99bf46ea50dc
docs: update docs
push time in 2 months
push eventtflanagan/node-quickbase
commit sha 95ca0061f689ee79e8b6e9432406d0b0f1b10601
meta,src,deps: update dependencies, finalize removal of bluebird
push time in 2 months
created tagtflanagan/generic-throttle
A lightweight, flexible promise based throttle class perfect for any rate or concurrency limiting need
created time in 2 months
push eventtflanagan/generic-throttle
commit sha 8b335d8b3c37d90776547a5ee356dd31c8519bf1
docs: update docs
push time in 2 months
push eventtflanagan/generic-throttle
commit sha 7fca90a4064607704d5c6db13a598b116c8f464d
src: update return type
push time in 2 months
push eventtflanagan/generic-throttle
commit sha eb07dbd2d338b04b0d5359788000976694ee036e
meta: npmignore bower.json
push time in 2 months
created tagtflanagan/generic-throttle
A lightweight, flexible promise based throttle class perfect for any rate or concurrency limiting need
created time in 2 months
push eventtflanagan/generic-throttle
commit sha f91c92a60e6083640f9650d946ea7ecef1d68a02
docs: update docs
commit sha 3eedc78d799fd832f245b726fda1036df134e5c0
meta: remove prepublish script
push time in 2 months
push eventtflanagan/generic-throttle
commit sha 5c2028dc1affc5998e94cdc101a2315beb8ef942
meta,src: finalize removal of bluebird
push time in 2 months
push eventtflanagan/generic-throttle
commit sha f0e568940bdbc19d04a97b15abb60105e60f8ef9
deps,src: remove the bluebird dependency (#2) * Remove the bluebird dependancy * Include updated package-lock and dist file
push time in 2 months
PR merged tflanagan/generic-throttle
I'm like 10% sure I did this properly however the tests pass so 🤷♂️
This is a breaking change and I'm not sure how that is normally handled in open source projects. I'm creating this PR but I don't expect it to get accepted without some additional work so please just let me know what needs to happen.
pr closed time in 2 months
pull request commenttflanagan/generic-throttle
Remove the bluebird dependency
@BryceBarbara No worries about versioning, I will handle that.
Thanks for the PR!
comment created time in 2 months
issue commenttflanagan/node-quickbase
bluebird inclusion leads to large memory usage increase
@BryceBarbara 😰yikes.. forgot about that one.
I'll work on finding a path to replace it.
comment created time in 2 months
created tagtflanagan/node-quickbase
A lightweight, very flexible QuickBase API for Node.js
created time in 2 months
push eventtflanagan/node-quickbase
commit sha 9a7a611231e29ac4a7f18925e58e5af847c87155
version bump
commit sha eb417a270b9c36b476e24e47537cfef71db3fb76
docs: update docs
push time in 2 months
issue commenttflanagan/node-quickbase
bluebird inclusion leads to large memory usage increase
@BryceBarbara That's an interesting concept. I'll take a look at it.
For API_ImportFromCSV, you'll want to use upsertRecords operation. upsertRecords is a combination of API_AddRecord, API_EditRecord, and API_ImportFromCSV: https://developer.quickbase.com/operation/upsert
comment created time in 2 months
issue commenttflanagan/node-quickbase
bluebird inclusion leads to large memory usage increase
Hey @BryceBarbara, thanks for the report.
You aren't using an out of date version, v2 targets the XML API, v3 targets Quick Base's new API.
Yes, when this library was first developed, Promise wasn't as globally supported as it is now in browsers and this library targets both Node.js and browsers.
Unfortunately, the Promise API that bluebird provides has many more methods than the native Promise object, so removing bluebird would be a major version change for v2 as the promises returned by the library wouldn't have the same methods available.
I'd first recommend trying v3 of this library which targets the new RESTful API Quick Base took out of beta over Empower2020.
You can use both v2 and v3 at the same time (requires npm >= 6.9.0)
$ npm install --save quickbase-old@npm:quickbase@2 quickbase-new@npm:quickbase@3
const QuickBaseOld = require('quickbase-old');
const { QuickBaseNew } = require('quickbase-new');
If that's not possible, I understand the desire to remove bluebird, it has crossed my mind a number of times as well, but I'll have to come up with some versioning solution to provide that.
Let me know if v3 resolves the issue for you.
comment created time in 2 months
push eventtflanagan/jitsi-meet
commit sha f2c3401a79842bbfe0aab4a31e6390a7fffe985d
chore: Update lib-jitsi-meet.
commit sha 4687187cca751b518c06c8da626ba3c00915819a
Merge pull request #7358 from bgrozev/update-lib-jitsi-meet chore: Update lib-jitsi-meet.
commit sha e39c8d8ed61e31ee65b397826b1f349ec01e64fa
rn,tile-view: render a larger avatar in tile view mode
commit sha 76e4929add6efc288b3867588182e5e14b5c033f
rn,tile-view: render display name on top of participant view Makes the tiles consistent as the participant view is equally sized and the avatar is always centered in the tile.
commit sha 0751c6ab48d9e691f866da52446fb0b64ee02c4b
ios: fix uploading dSYMs to Crashlytics Use Fastlane to get them from Apple after processing, them upload them. Also make sure WebRTC dSYMs are included when uploading.
commit sha ddaaeccafa81e92ad47c3b4497dd1df09f8e9e1e
android: disable PiP on Android Go devices Despite running Android 8.1, they don't support Picture-in-Picture.
commit sha 3cbadc72a1aaebb65e0b5973872ace9c319749f6
analytics: only import required constant
commit sha 46b444c498d8477c48f741be07fcc638b4bec7eb
settings: only import required action Fixes crash on mobile due to chained imports.
commit sha fde7cf4ab83fde7e2053184f63e102fe7ea51212
chat: fix crash on mobile
commit sha eaa715879a9168f794bb790a7ebf85976626004b
rn: update versions
commit sha eb1ef0fa9c0755c85665336b5a84814476a4ffed
Update JitsiStreamPresenterEffect.js (#7362) * Update JitsiStreamPresenterEffect.js Create/terminate the Web Worker on effect start/stop so that we don't leak them.
commit sha 48a58f8dae4bbe35956ae7aa7c9a9b0e4bfcbf1e
ios: specify the correct keyboard type and content This way autocomplete and keyboards work correctly.
commit sha 9d6e21b77bf948f4a2d932d03931a9f3daa4e234
security-dialog: restore digit-only password functionality
commit sha 1e3e15fc72eb3dde5bea0f6947628c35e5826785
fix: use consistent moderator semantics Use the same moderator semantics when adding items into the remote video menu as when showing/hiding the items themselves.
commit sha 16547b91a5aaa1709ba2f80fc2238228bf4607fc
rn: fix overriding user-selected server URL Fixes: https://github.com/jitsi/jitsi-meet/issues/7373
commit sha b831bb8350184c89a1cef094e460ccddf5a70a7c
config: add roomPasswordNumberOfDigits to whitelist
commit sha 0fc748dc4490d3da51c2d45c61ec38904ae910b5
ui: create reusable copy button
commit sha 93160ea346c0131cb717b6a1c0957da9ea4eb07c
Merge branch 'master' into green-screen
push time in 2 months
push eventtflanagan/jitsi-meet
commit sha f93f177b764dc35a976674ebf5495c73062d8d90
feat(blur): attempt to fix linting errors
push time in 2 months
pull request commentjitsi/jitsi-meet
feat(blur): terminate blur web worker when disabled
@saghul
Thanks for the suggestion, but it doesn't appear to be working.
I suppose there isn't too much danger to not setting it as undefined and checking if it is defined before use. From the code paths, it doesn't appear that this could happen.
Thoughts?
comment created time in 2 months
push eventtflanagan/jitsi-meet
commit sha 291409fd4bbce0f718b34d795495d3af1de02c02
feat(blur): attempt to fix linting errors
push time in 2 months
push eventtflanagan/node-quickbase
commit sha 0305f1a554d4a27d465c658f980d8af57e7697cb
src: move required and unique flags from create to updateField
push time in 2 months
push eventtflanagan/node-quickbase
commit sha ebbe451ad6582beee7b8a3327d0ca09a16599baf
src: test for individual deleteField errors
push time in 2 months
pull request commentjitsi/jitsi-meet
feat(blur): terminate blur web worker when disabled
I'm unsure how to overcome these lint errors. Any suggestions?
comment created time in 2 months
push eventtflanagan/jitsi-meet
commit sha 0d85d8b06f8c91569a7ca9ff54e6acb5b7d11e09
feat(blur): attempt to fix linting errors
push time in 2 months
push eventtflanagan/jitsi-meet
commit sha 8b5a56039b1beb6c8b35dde110bee5977e60de55
feat(blur): attempt to fix linting errors
push time in 2 months
PR opened jitsi/jitsi-meet
Resolve a potential leak. Terminate the blur web worker when the effect is disabled.
pr created time in 2 months
push eventtflanagan/jitsi-meet
commit sha 6b6e0c9867cc398cab5db1b1c74e8638158375bb
green-screen: attempt to fix linting errors
push time in 2 months
push eventtflanagan/jitsi-meet
commit sha 6b89492654b19cfa708bec3ffb8a4cb75990cac0
green-screen: attempt to fix linting errors
push time in 2 months
push eventtflanagan/jitsi-meet
commit sha 56f2368df27a50d363585c0838e1c15de523287e
green-screen: attempt to fix linting errors
push time in 2 months
push eventtflanagan/jitsi-meet
commit sha aca00adc5a17b179ec7e01bd6bca48057bc08807
green-screen: attempt to fix linting errors
push time in 2 months
push eventtflanagan/jitsi-meet
commit sha 6445f2e1412798cd676acdc23969c2a6e19117ae
green-screen: attempt to fix linting errors
push time in 2 months
PR opened jitsi/jitsi-meet
First off, Jitsi is a wonderful tool, thank you for all of your hard work.
In looking for alternative conference tools, Jitsi is at the top of the list, but one of the key features that prevents it from becoming the chosen solution is the lack of a "green screen" effect.
In an effort to fast track this much needed feature, I went ahead and made a rough introduction.
React and your environment in general are pretty foreign to me, so I'm sure there are some things you would've done differently. Please don't hesitate to point them out.
That said, I used the blur effect as a starting point, including the beta tag, and went from there. Overall, it works pretty well.
One of the key differences is that I noticed the blur effect introduces a potential leak in regards to the web worker. When you disable the effect, the worker persists. Granted, if you re-enable it, the same worker is consumed, but when it is disabled and never reactivated, the worker persists. Looking into the functionality of the worker, it seemed pretty strange. It looks like a manual FPS-esque/animation timer, so I removed that concept and switched to using requestAnimationFrame. I'm unsure of the original development conversation and the reasons these decisions were made, but I believe the blur effect should switch to this method as well and will open a separate PR if desired.
This PR introduces the "green screen" effect in a few different ways. There is the typical chroma key effect, then two implementations of the bodyPix library, MobileNet and ResNet.
Most parameters are configurable in a new "Green Screen" settings tab, including the color via a color picker widget for the chroma key effect, the chroma key threshold, all the various bodyPix parameters via dropdowns and range sliders, and the ultimate rendering FPS. Making these configuration options available was an effort to give users with lower tiered computers the ability to use the functionality.
Testing has been pretty minimal. I've used my 5 year old desktop, 10 year old laptop, 3 year old android and ios phones. Without too much resource usage, all were able to use at least the Chroma Key and MobileNet settings, with only the desktop being able to use the ResNet setting.
Possible additions/changes:
- Support (short?) video clips as a green screen
- More configuration (segmentationThreshold, maxDetections)
- Automatically restart the effect when enabled and settings have changed
- Preview of rendered green screen effect instead of just the selected image in the settings tab
- Different euclidean distance equation for the chroma key effect
References: #5860
pr created time in 2 months
fork tflanagan/jitsi-meet
Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
fork in 2 months
push eventtflanagan/node-jitsi-external-auth-quickbase
commit sha 5d13afd10a89205984a7da5ef6bd2e1ad14a2fbf
src: minor improvements
push time in 3 months
push eventtflanagan/node-jitsi-external-auth-quickbase
commit sha d5850feac27b6baa12a76a8bf9941959c02c72c0
src: fix logging
push time in 3 months
push eventtflanagan/node-jitsi-external-auth-quickbase
commit sha fe94a045b8ad620d696ab1c75ce7c188390bce05
src,config: added domain, logging
push time in 3 months
push eventtflanagan/node-jitsi-external-auth-quickbase
commit sha 2aadfe580a73e6289c7d2dfd6db4a3b80a045679
src: fix username and register
push time in 3 months
push eventtflanagan/node-jitsi-external-auth-quickbase
commit sha 12493a167270e532ea6e98158ec578a5148aecc5
src: fix username and register
push time in 3 months
push eventtflanagan/node-jitsi-external-auth-quickbase
commit sha 7f00990e0cbb4a380ed9e388504ef97674ebf2a8
src: added register query
push time in 3 months
fork tflanagan/jitsi-meet-electron
Jitsi Meet desktop application powered by :electron:
fork in 3 months
fork tflanagan/jitsi-meet
Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.
fork in 3 months
push eventtflanagan/php-quickbase
commit sha 70f7887518d328ba8e1ea8947ecc7c35c6ac74d0
Remove final flags in methods Trying to make something like ORM for Quickbase but final flags destruct all of my idea for example count queries when i create proxy quickbase class because i can't extend methods.
commit sha 92e52ead895d4698b10d890ea6da68803ee4d2e6
Merge pull request #12 from eskrano/patch-1 Remove final flags in methods
push time in 3 months
PR merged tflanagan/php-quickbase
Trying to make something like ORM for Quickbase but final flags destruct all of my idea for example count queries when i create proxy quickbase class because i can't extend methods.
pr closed time in 3 months
create barnchtflanagan/node-jitsi-external-auth-quickbase
created branch time in 3 months