Library for using Crontab-like syntax in scheduling of some Kotlin Coroutines tasks to do from time to time
Go to file
InsanusMokrassar e279e6105b 0.2.0 2020-01-08 14:28:57 +06:00
gradle/wrapper 0.2.0 2020-01-08 14:28:57 +06:00
src/commonMain/kotlin/com/insanusmokrassar/krontab rewrite all onto KronScheduler 2019-10-10 16:43:52 +06:00
.gitignore updates 2019-10-08 23:42:50 +06:00
CHANGELOG.md 0.2.0 2020-01-08 14:28:57 +06:00
LICENSE Initial commit 2019-05-21 11:35:07 +08:00
README.md update README 2019-11-19 19:23:35 +06:00
build.gradle 0.2.0 2020-01-08 14:28:57 +06:00
gradle.properties 0.2.0 2020-01-08 14:28:57 +06:00
gradlew init 2019-05-21 18:14:09 +08:00
gradlew.bat init 2019-05-21 18:14:09 +08:00
maven.publish.gradle 0.2.0 2020-01-08 14:28:57 +06:00
mpp_config.json 0.2.0 2020-01-08 14:28:57 +06:00
publish.gradle 0.2.0 2020-01-08 14:28:57 +06:00
settings.gradle 0.2.0 2020-01-08 14:28:57 +06:00

README.md

krontab

Download

Library was created to give oppotunity to launch some things from time to time according to some schedule in runtime of applications.

Table of content
How to use
How to use: Including in project
How to use: Config from string
How to use: Config via builder (DSL preview)

How to use

There are several ways to configure and use this library:

  • From some string
  • From builder

Anyway, to start some action from time to time you will need to use one of extensions/functions:

val kronScheduler = /* creating of KronScheduler instance */;

kronScheuler.doWhile {
    // some action
    true // true - repeat on next time
}

Including in project

If you want to include krontab in your project, just add next line to your dependencies part:

implementation "com.insanusmokrassar:krontab:$krontab_version"

Next version is the latest currently for the library:

Download

For old version of Gradle, instead of implementation word developers must use compile.

Config from string

Developers can use more simple way to configure repeat times is string. String configuring like a crontab, but with a little bit different meanings:

/-------- Seconds
| /------ Minutes
| | /---- Hours
| | | /-- Days of months
| | | | / Months
| | | | |
* * * * *

It is different with original crontab syntax for the reason, that expected that in practice developers will use seconds and minutes with more probability than months (for example). In fact, developers will use something like:

doWhile("/5 * * * *") {
    println("Called")
    true // true - repeat on next time
}

Or more version:

doInfinity("/5 * * * *") {
    println("Called")
}

Both of examples will print Called message every five seconds.

Config via builder

Also this library currently supports DSL for creating the same goals:

val kronScheduler = buildSchedule {
    seconds {
        from (0) every 5
    }
}
kronScheduler.doWhile {
    println("Called")
    true // true - repeat on next time
}

Or

val kronScheduler = buildSchedule {
    seconds {
        0 every 5
    }
}
kronScheduler.doWhile {
    println("Called")
    true // true - repeat on next time
}

Or

val kronScheduler = buildSchedule {
    seconds {
        0 every 5
    }
}
kronScheduler.doInfinity {
    println("Called")
}

All of these examples will do the same things: print Called message every five seconds.