I would like to have a recent version of full calendar, but that requires a recent version of jQuery, and a new jQueryUI and it needs moment.js and once you update jQuery there are a ton of plugins we might have to update.
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
If we touch the JS libraries in anyway, wouldn't it make sense to start using a proper javascript package management like bower or npm with browserify?
true, first I want to figure out what the heck is in there and where does it come from. Currently struggling to find an unminified version of jquery.class.min.js
DoneJS is the successor to JavaScriptMVC. If your project chose JavaScriptMVC in 2007, you would have made a wise decision, giving your team an upgrade path to a modern application for the past 8 years.
I think we are using something that has died a long time ago... and evolved into something very different. Looks like vtiger 6 should already have dropped that library... Maybe we can think about it now at least.
maybe, but it isn't a huge file, and doesn't seem to be terrible. The main thing was getting the unminified version, I want to ensure we have the full version of everything so that we can actually fix bugs if there are any - or at least analyse what it is doing. Being able to maintain stuff that is dropped by the original developer is a core strength of free software, so it might not be something we need to drop in a hurry - it is used by a lot of vtiger code.
there is some css styling for handsontable, but I agree, I can't see it being used anywhere, I am preparing a branch with just stuff that I know is used, I took out everything and pulled a fresh upstream library for every error on the console and fixed things where they broke http://code.vtiger.com/alanbell/vtigercrm/commits/javascript_library_updates not quite ready to merge yet
Your branch makes a lot of sense!
I really would like to start managing this with a proper package management sometime, otherwise you will start doing this over again very soon. I have read around a little and seems like npm in combination with browserify outruns bower and co. I don't find enough time at the moment, but sooner than later I will give https://github.com/substack/browserify-handbook a go. Alans branch could then be the starting point. Using browserify looks relatively easy, but it might be a challenge to insert this into the existing project base. I hope to find some time real soon to start a branch with this and add an example, like I did for the composer issue.