but may point to a jre depending on your installation

yes, it needs to point to a JDK

well i have to think of users who do not really care about more than writing the config and passing it into my program

but i guess some section in the readme has to be written in allcaps

The better way to define a script is to use

@KotlinScript

annotation on the base class with a configuration object, and then construct a configuration from it. And then

BasicJvmScriptingHost

now have all needed defaults. So the resulting code may look like:

object MyScriptConfiguration : ScriptCompilationConfiguration({
    defaultImports("org.apache.camel")
    jvm {
        dependenciesFromCurrentContext(wholeClasspath = true)
        javaHome(File("/opt/data/sfw/lang/java/8"))
    }
})

@KotlinScript(compilationConfiguration = MyScriptConfiguration::class)
abstract class MyScript(var name: String) {
    fun say(message : String) {
        println(name + ":" + message)
    }
}

fun main(args: Array<String>) {
    val script = """
        say("hello kts!")
    """

    val config = createJvmCompilationConfigurationFromTemplate<MyScript>()

    val evalu = ScriptEvaluationConfiguration {
        constructorArgs("injected")
    }

    val result = BasicJvmScriptingHost().eval(script.toScriptSource(), config, evalu)

    for (report in result.reports) {
        println(report)
    }
}

This way, for example, you can easily get a support from the IDEA, since the properties this configuration object could be used for completion and navigation.

As of the jdk and javaHome - I hope it will be not necessary after my fix will be released.

IDEA support in scripts works.. partially

i am working with 2 projects and deploy the script definition to mavenLocal

hmm next question.. how can i add extra kt or kts files to a script compilation ?

i will be easier to implement something like ktscript with the new scripting improvements, or to update ktscript but not quite yet https://youtrack.jetbrains.com/issue/KT-27815 is blocking

and here is a example of scripting + maven deps : https://github.com/JetBrains/kotlin/tree/master/libraries/examples/scripting/jvm-maven-deps

yes it is.. kscript does actually only do some simple regex

it just tries to emulate using annotations, but actually parsing them would take too long i guess

That's weird and took 40 minutes of my life 😛

To implement 'perfectly' may involve something very close to the full complier parser -- handle comments, quotes correctly, handle detecting the 'target' of the 'annotation' -- I can definately understand a compromise to avoid that (from a non-compiler-vendor ) -- which leaves the question only 'which compromises' 🙂

you can PR a better regex

i think all it needs is allow handling newlines between elements and such

@Nikky Indeed, I fully agree that some a slightly better regex should do the trick, since the a full parser is out of question with current preprocessing and execution model of

kscript

.

Can I use kotlin scripting to configure an object in the same way gradle does

Project

(and possibly get IDE support)? How would I go about this if possible and what are my options if not

idea gives you script highlighting as soon as you have a jar in the classpath with your script definition and the right files in META-INF

more details are in the KEEP.. its not even completely implemented yet.. but you can load textfiles and compile them into scripts

Hi, I'm happily using Kotlin script with version 1.3, and I'm wondering… why is the IDE syntax highlighting for

.kts

files not the same level as

gradle.kts

files? It highlights only reserved keywords and strings… Is there a way to make the IDE recognize it all, and also have cmd/ctrl+click go to source from stdlib instead of to compiled code? I'm using Android Studio 3.3 RC1 with IDE plugin 1.3.10

i think to recognize it all you need to use

.something.kts

and have a a jar in the classpath that provides the script definitions

that worked for me in 1.3.0

oh you meant something in the buildscript

when i need more than build.gradle.kts i use buildSrc, idea gives me full syntax highlighting there

and this is what i meant: https://github.com/Kotlin/KEEP/blob/master/proposals/scripting-support.md#how-to-implement-scripting-support

add a discovery file named after FQN of the base class to the

META-INF/kotlin/script/templates/

in the target jar

but iirc that will onlz work for kotlin script files in some src directory