When kranium will support Ti Mobile 1.8?

[milescui]

Hi

I think kranium is great. I want to use kranium on my project. But i have a few question.

When kranium will support Ti Mobile 1.8?
Kranium will be long-term support?

thanks

[krawaller]

Thanks for the kind words, and sorry for the late reply!

I hope to have a 0.2beta release out the door next week which will work beautifully with 1.8.

Kranium is an open source project primarily run by me, mostly in my spare time, so I cannot vouch for the long-term support. But as Kranium will always be open source, you're not totally screwed even if I get run over by a bus.

Also, Kranium is used heavily in my day-job at Logica, where our team use it for most Titanium Mobile apps, so I do believe it will get some love in the future too.

Cheers
/Jacob

[nvdnkpr]

very good news :)

I appreciate the time and energy you're putting into kranium. I'm eager to see 0.2beta. As I'm currently integrating Kranium into our own development environment (at http://www.eyeworkers.de), I'm sure to be able to contribute a bunch of self written components or help with the documentation to provide some real life experience.

Is their any other way to communicate than github ? IRC, skype ?

thanks
Navid

[krawaller]

Ant that's very good news to me :-) Contributors are more than welcome, and I'd certainly like to make it much easier to understand Kranium and commit fixes and demos.

For public communication Github is great since everyone can follow the conversation, but I'm also available for swifter discussion on jacob at krawaller dot se or as litenjacob on Skype.

[milescui]

very good news

I'm looking forward to 0.2beta.

thanks
/Miles

[milescui]

I very much hope for kranium contribution some things, but my english is very bad.
I think i can translation English document into Chinese document.
I think the current document transfer to github wiki on more conducive to cooperation.

/Miles

[krawaller]

Hi!

I promised to push a version for Ti SDK 1.8 no later than today. I'm happy to tell you I've pushed a 0.2 branch both to this repo, and to kranium-demo. However, this is more of an alpha than a beta.

I'm experimenting with autoloading of modules, while stile trying to stay mostly backwards compatible. One of the big changes are that elements aren't queryable by default - you'll have to give the elements you want to reach through the selector engine the queryable property set to true. Also, if you use kui-components, you'll have to change the syntax of all these slightly:

exports.Class = Window.extend({

becomes

var K = require('kranium/init').K;
exports.Class = K.UI.Window.extend({

This is related to the enforced private scope of CommonJS modules.

Please note that some parts are missing in this 0.2 release - the custom tabgroup for Android doesn't work properly, backbone isn't integrated, Livetanium isn't working, and some tiny bits and pieces are just completely off or missing. If you find something that doesn't work properly, please let me know through an issue.

Also, I'd love your input on Kranium and it's feature. For example, I'm seriously considering making Kranium a compiled javascript module distributed mainly through the Titanium Marketplace. What do you think of that?

[nvdnkpr]

Hey Jacob,
that sounds great, I'll take a look into it tomorrow. I wrote a small Gist for explaining some best practices how to create own components, however I would like to ask you to take a short look into it: https://gist.github.com/1657255

I used the inst-property to access the self created components methods to provide loose coupling via events.
And I used el in the self defined component to access the Ti-Object.

Problem is that I can't tell if that was your initial intention for that properties. So take a look into my Gist and tell me if that's okay with you.

I got another two points ;)

• Building a Kranium Plugin/Module sounds great, but it would be perfect if you would present a base repository with it with dependency management via command line NPM
• I would really like to help with Code (needs perhaps a small howto), Documentation (some basic examples for Tabgroup or NavigationGroup Contexts), Bugs (...). So perhaps we should write via skype to delegate some of the smaller works ;)

Greetings Navid