liavt / Scheduler

Scheduler for school.
https://liavt.github.io/Scheduler
MIT License
1 stars 1 forks source link

Triggers #8

Closed liavt closed 8 years ago

PoisonNinja commented 8 years ago

I think we can merge firstRun with init. In init, we can do a simple check for whether a trigger exists. This also means that we only need one button. I think the update was pushed too early.

liavt commented 8 years ago

The trigger is for firstRun now. So when you open the document, it will do firstRun. However, I don't like making everyone redownload now. But the live update thing works.

liavt commented 8 years ago

SO what we can do is pretty simple:

liavt commented 8 years ago

along with being able to edit colors and values of cells, I think you can also create images and assign scripts to it in code. We can update the code to do that once for everyone.

liavt commented 8 years ago

NVM we can't assign scripts to the image after it's made.

liavt commented 8 years ago

Just leave it. It works fine. It may be a bit redundant, but it's useless to make everyone update an hour after its made. I don't want to make everyone redownload anymore at all

liavt commented 8 years ago

I will move the triggers in firstRun() to init(). Then when firstRun() is called, a prompt will appear telling the user that the button is outdated.

PoisonNinja commented 8 years ago

No need. Leave firstRun as a wrapper for init. In the next update (a month away, perhaps?), we can remove the first run button.

liavt commented 8 years ago

Nope. Try clicking the first launch button. I already moved firstRun() to init().

PoisonNinja commented 8 years ago

Commit it to Github