We are working a scheduling system for employees we achieved good results using a hacked version of fullcalendar that has a resource view , but we were constrained to put the whole FullCalendar init code in an autoRun block , since there was no working function that allows yuo to refetch resources or just add it programmaticaly , resources could only be added in the init Code , thus we destroy every time the calendar and recreate one on every change rerunning autoRun.
this resulted in bad performing scheduler .
now we are studuying the alternatives to revamp it .
the scheduler should support resource view and also should be used in a 2 weeks view .
what are the solutions available to avoid a from scratsh dev?
Your assumptions are incorrect. You can use FullCalendar to do every thing that you mentioned.
You can see how to re-fetch in the documentations.
Also you can add events programmaticaly with the addResource function - see documentation here.
If you initialize every time of course it will cause bad performing, but you are using it wrong. This whole plugin works with ajax and the performance suppose to be depended only on your server handling.
Last thing, you said "hacked version" of full calendar.
FullCalendar is an open source project, so there is no "hacked", only the latest version... You can download it here.
Related
As I always need to login to execute the tests and every time I need to re-do the log-in steps making it hard to maintain
I found out that on testcafe.js is possible to use hooks as a workaround but that is not the kind of optimal way
I need to save a constant login/password and alter them one time only as needed, just like a code but on the testcafe studio
We are planning to release a new version of TestCafe Studio this or next month. This version will contain the hooks feature, which would be built over TestCafe hooks (https://devexpress.github.io/testcafe/documentation/test-api/test-code-structure.html#initialization-and-clean-up)
Thus, you'll be able to use your login steps only once in hook without copying.
In addition, a bit later, we are planning to release the support of custom nodejs code inside a test, which will allow using the Roles mechanism.
Until now I have been using the standard "assets.version" configuration directive for the versioning of my assets. I am releasing a new production quite frequently (once a week or more). So if I change a single asset (e.g. javascript file), I increment my "version counter".
Here is my problem with this system: Changing a single line in an asset causes the invalidation of all assets of the whole application! This means that every weeks, users connecting to my application will re-download all assets! This appear to be quite inefficient to me...
My Question: is there a smarter system? for example we could imagine a console command to execute before each release that would track changes of every assets (using e.g. md5) and save the version to be used for every single asset? This way, only modified assets would be re-downloaded...
I know I can develop my own service and use assets.version_strategy like in this example But, before re-inventing the wheel, I would like to know if nothing similar already exists? It seams to me that every one should be using such a solution...
Thank you!
Vincent
Im using Iron:router and meteor-node-csv, after uploading a file i want to read each row of it and insert it on a collection, but when i process the file the whole web freeze (buttons dont respond). Time ago this same code worked 100% fine, after some upgrades it started working like this.
So, after a lot of testing a partner found that the waitOn is a flag here.
If i process the file and try to navigate to a route having a subscription to any other collections it freeze.
If i process the file and try to navigate to a route without a subscription it works perfect
If your file is big, then reactivity is causing this issue. There are variations of that on stackoverflow in a few questions. My recommendation, described here, is to disable reactivity while processing data. You can do that using a "guard" around reactive elements, e.g., using a session variable as described in the linked answer.
I started this little project where I would do real time collaboration on code using CodeMirror.
I have a msgs system setup such its easy to pass objects from one user to another. My problem is getting it integrated with CodeMirror. I found out that it have events for onchange and a replaceRange(string, from, to).
I pass the onchange objects to the other users and uses the replaceRange to update the view. Problem is then when using replaceRange, it triggers an new onchange and it sends msgs back and forward. Anyone know if there are some way of updating the local view without it triggering an onchange. Or suggestings for other paths to take. (the msgs system is already set up and its easy to pass javascript objects to other clients).
You Can Use Firepad
FirePad is an open-source (on GitHub) realtime collaborative plug-in to codemirror. You can get it setup with codemirror in 4 extra lines of code and a few minutes. It's uses Firebase for the backend.
To get this to work properly, you'll have to merge changes as well. See http://ot.substance.io/ for a demo of an open-source solution (also using CodeMirror).
I have a situation in which i am fetching top row from a temporary table and doing a functionality using that details. The temporary table will be updated with the new uploaded file details. I do have an aspx page which does this functionality. The web page is triggered using a task scheduler at some interval of time. My problem is that when the page is triggered
during a schedule if the functionality is not finished before the next trigger the task scheduler gets stuck and won't work unless a new schedule is created.
I have heard that executing the functionality using asp.net threading can solve my problem. Is that possible for my situation? If so any one please help me with code how i can proceed..
Now i just fetch only one top row to do the process. If i can implement this for top few rows (say top 5 rows) then i can increase the speed of my application. Please suggest a solution to implement this as well..
increase the time scheduler time a little bit to it can get completed before another starts.
Improve the update query, so it can save time.
Threading is good idea. But...
Each scheduler should check if the previous one is already running or not, you can put a status of (running/ completed) somewhere in table.
Log scheduler activity (start, end, elapsed time etc), it will help a lot.