3 Mar 2013 4:00 AM #21
Yep, the cramming issue goes away if you recompile sass files using new SDK.
That's not actually backwards-compatible, but that's Sencha's fault, not mine
Gonna dig into mask issue now...
3 Mar 2013 4:02 AM #22
I am sure everyone will appreciate it...
3 Mar 2013 4:19 AM #23
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?
3 Mar 2013 4:40 AM #24
well; you can @#$!@#$# $%##
[content removed cause I trashed toorshia for not being nice and helpful]
3 Mar 2013 5:04 AM #25
Wooooow, there goes the bomb
Man, you tipped over so fast Why?
Look, I've got no use of thinking whatever you think I am thinking.
I am just a regular guy, you know.
So pull yourself together, and let's get some s#it done, okay?
I've fixed the transparency issue. It's Sencha's fault, again. They changed quite a lot of things. So my mask class was not working the way it should.
If you want a quick fix, just open mainContainer.js (controller), and comment out line 90.
I am struggling to make new Sencha CMD work with existing app structure, but it seems to me I'll have to rearrange everything from scratch according to 2.1 standards.
Can you help me with this, please?
3 Mar 2013 8:41 AM #26
SDK-2.1.1 version is pushed to Github repo.
Drop sdk contents into "touch" folder to get it working.
Please report issues, if any.
Ask away if you have trouble starting it up.
3 Mar 2013 10:06 AM #27
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.
3 Mar 2013 12:45 PM #28
Well, that's really weird
I just tested again. Made a test folder, dropped source from git, and sdk to touch folder.
No sign of 404.
I am using sdk extracted from sencha-touch-2.1.1-gpl.zip
Maybe you should try to generate fresh app using CMD, and then copy files there and try.
In the end, here's zipped sdk straight from the project that works on my machine, so you can test that to http://bit.ly/100oVG3
6 Mar 2013 6:00 AM #29
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:
7 Mar 2013 12:17 AM #30
I didn't do custom build, just unzipped GPL version.
I'm gonna try to repeat your scenario (download fresh 2.1.1 and try with it) and see what happens...
Thanks for patience.