Hi,
I would recommend that choosing a Calendar is less important than choosing a web UI/datasource framework (which would include a Calendar solution) and using it whenever you have a choice. Picking and choosing libraries for specific UI problems makes development more difficult and inefficient. In some specific cases, like charting, it makes sense, but for a Calendar, that’s less likely. Perhaps you have a really specific need that narrows what you can use, but its more likely that you can use any of the better UI frameworks for your solution. I’d go shopping for a web UI toolkit and stick with it. I’ve been using Kendo UI more recently and really like the Calendar functionality, and more importantly the whole framework is great to work with. As for how to get data into and get data out of a web area, it is very straightforward: From 4D code to call javascript in the Web Area - WA EXECUTE JAVASCRIPT FUNCTION: http://doc.4d.com/4Dv16/4D/16.3/WA-EXECUTE-JAVASCRIPT-FUNCTION.301-3652382.en.html <http://doc.4d.com/4Dv16/4D/16.3/WA-EXECUTE-JAVASCRIPT-FUNCTION.301-3652382.en.html> From the Web Area, to call 4D methods using javascript code, look for using the $4d object in the middle of the page below: http://doc.4d.com/4Dv16/4D/16.3/Programmed-management-of-Web-Areas.300-3652400.en.html <http://doc.4d.com/4Dv16/4D/16.3/Programmed-management-of-Web-Areas.300-3652400.en.html> Tom ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
