is there any plan to support html template and normal css files?

[Mohammad Shamsi]

Hi All,

As far as I can see from the documentation, Kotlin DSL is the only way to create html pages and stylesheets.

how about html templates? is there any plan to implement a template engine for Kara? 

Thanks.

[Andy Selvig]

I'm not specifically opposed to adding a separate html template engine, but there are no specific plans at the moment. Frankly, the Kotlin DSLs are the reason that Kara was created. You get to write concise, statically-typed html and css. 

I suppose if you were really interested in having the angle brackets (for designers and such) it would be pretty easy to wrap one of the existing text templating engines like Velocity into a Kara View provider.

--
You received this message because you are subscribed to the Google Groups "Kara Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to karaframewor...@googlegroups.com.
To post to this group, send email to karafr...@googlegroups.com.
Visit this group at http://groups.google.com/group/karaframework.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Mohammad Shamsi]

Handling everything with Kotlin DSLs, sounds interesting and revolutionary. but things are different in the real world. web developers prefer to play with html and css files, rather than kotlin code.

anyway, I'm not trying to say what is wrong or right, but it will be very difficult to change web developers mindset. 

thanks again.

[Andy Selvig]

There's probably some truth to that, yes. However, I think that the popularity of non-angle bracket markup languages like HAML and Jade shows that there's some market out there.

[David Vydra]

I agree that this can become very religious. One way to play it is to support html/css providers for prototyping, but 'production' code must be in DSL. I am not saying the tool has to enforce it -- it can be a team decision. I am used to using static DSL's in Gosu on very large projects -- this is where they really reduce the risk of introducing a bug.

-d

http://www.linkedin.com/in/dvydra
http://www.testdriven.com
http://twitter.com/vydra