Re: [Architecture] Shareable Common JS

2014-11-20 Thread Ruchira Wageesha
Is this library a client-side JavaScript file or a *.js file with server side JavaScript(Jaggery)? If it is a Jaggery code, then best option would be to make it a Jaggery module[1]. So, you can version it, share it etc. If it is a clientside static *.js file, in the current caramel model, we keep

Re: [Architecture] Shareable Common JS

2014-11-20 Thread Sumedha Rubasinghe
Ruchira/Sameera/Manu, AFAIK we do not have a specific folder to keep JS libraries related to BE functionality in the current Jaggery App Structure. Only libraries I have seen (could be wrong) are in themes/{theme name}/lib. But these libraries are mostly related to UI presentation. If I am corr

[Architecture] Shareable Common JS

2014-11-20 Thread Lahiru Cooray
Hi, *Please refer the mail thread : "[Architecture] [AF] Capturing BAM events with an objective of understanding user activity"* Currently I'm working on implementing a common JS library modifying the above mentioned JS to make it more generic. User can give the below inputs to this Javascript a