Re: Standalone Lightning for webapps?
Philipp Kewisch <mozilla <at> kewis.ch>
2016-01-27 18:39:30 GMT
On 1/27/16 4:13 PM, CC wrote:
> On Wednesday, January 27, 2016 at 2:32:33 PM UTC, Alan Lord wrote:
>> How about using something like:
> I think - I may be wrong - that it only displays a public Google calendar. Public calendars appear in search
results and can be viewed by anybody. The calendar itself is stored at Google. If you want to change the
calendar, you have to log on at Google with a Google account. It looks nice, but has a very limited use case. I
could do pretty much the same trivially by displaying the source calendar in an iframe, and Google gives
you a link to do exactly that.
> I've looked at a lot of other options, but they all have similar limitations. Basically, the JS/jQuery
ones are, I think, all display-only, so you have to handle talking to the calendar server yourself in your
> The advantage of using the Lightning code would be that it handles both the front- and back-end: it talks to
the calendar server, *and* it creates JS for output. I think. This lets you create private calendars which
can be both read and written by a group of users.
The Lightning code is pretty much geared towards working in a client
side application. If you are implementing this from scratch I'd rather
suggest using various other libraries. You should defintiely do 1, then
you have the choice of either doing 2, 3 or 4.
This is really the best solution for calendar display in the browser.
Use a custom backend that hooks up to the remote server and maybe does