....if you put a component out and expect others to fix it up I think you are taking the wrong path.
also, it does not really matter what benefits 2.1.1 has over 2.0.1. its the principle of being able to use whatever build we developers choose...
just my 2 cents.
First, speak for yourself, don't say "we developers"
Second, this doesn't sound like it's coming from a developer. I don't know you, all right.
But it sounds like it's coming from WYSIWYG user. Someone who simply wants turn-key solution.
This is open source community. I expect from you to make something better from whatever building blocks I gave you. And vice versa.
Just my 2 cents.
Now, let's not take this down the wrong path, OK?
Tell me, when you say "It doesn't work" what do you exactly mean by it?
Because it worked for me unpacked, packed, packaged into APK, and now it works on 2.1.1 with only a single css issue (active component becomes transparent when menu is open).
The only way for me to help you further is to include the goddamn 100MB sdk in the github repo to show you it works
I'll include 2.1.1 release soon enough.
If you decide to use it and it proves useful, then you can buy me a coffee, OK?
still it seems like something small is missing?
I get a http://localhost:8080/jam/touch/src/List.js404 (Not Found) wierd thing is List.js is actually not under src, its under stc/dataview so i am not sure why the framework looks for it.
maybe I am missing something but I am having trouble only with your component.
here's what I am experiencing: I still get the 404 code I talked about above.
If I use your touch folder everything works. however, if I use a 2.1.1 download and just drop it it does not work.
the 2.1.1 GPL version folder content looks different than yours, file sizes are sometimes also different (is this because you build it?)
so the question remains, why can't I just DL 2.1.1 GPL and drop its contents to make your app work?
attached are screen shots of the differences in folders between your touch and 2.1.1 'stock' touch: