Instructions for Running latest Dev code on Android tablet?

(13 posts) (2 voices)

Started 1 year ago by billieblaze
Latest reply from admin

Tags:

billieblaze
Member

Greetings,
First off, GREAT APP man! i've got some really fun stuff going into max, controlling hardware (cc and nrpn) and software (via CC + ableton api) with my tablet, EFF YEH! Latest endeavor is creating a volume indicator widget which is fed from ableton api requests to the mixer_device's..

I'm trying to get the latest dev code running in the simplest, most debuggable form. Am I correct in understanding that I simply run the www/ folder off a webserver? It seems to be mostly working, just want to verify. I'm certainly NOT looking to get all up into PhoneGap in the short term, but AM trying to get at the jquery + javascript I love so much..

Third, how do you suggest expanding my debugging capabilities? For instance, apparently the template config format changes so obviously i can't load in the template I was working on, but how can I actually SEE javascript errors, et al? Extra points for explaining how to run it in Firefox (Firebug junkie)..

Posted 1 year ago #
admin
Key Master

I don't know if I can get the extra points, but weinre is definitely what you're looking for:

http://callback.github.com/callback-weinre/Home.html

It uses the webkit debugging environment as opposed to Firebug's, but, besides that it is great and has saved me many headaches.

Running from the web server is one way to do it. You can also put -most- code inside of interface files and just overwrite what comes with Control; the entire interface file just gets eval'd (I know, I know... I'm a bad person). It's a bit easier to do this in the newer version of Control as I've refactored the code, but I haven't started moving that to Android as it isn't fully functional in iOS yet.

Please keep me posted on your projects! I haven't played with the Ableton API but it's on my list of things to do as I use Live fairly regularly with Control... any sample code integrating the two would be a great help. - Charlie

Posted 1 year ago #
billieblaze
Member

yeh, i can def share some max patches.. i got control mostly working, even started updating event bindings from touchEnd to "touchend click" so i can debug on my pc. first thing i encountered was some interfaceManager issues trying to load my .js. revolving around the same eval.. i'm looking at trying to refactor "downloadInterface" into pure jquery, but it got late before i finished.. are you looking for contributions like this? I'm pretty sure I could refactor alot of the core code to jquery!

Posted 1 year ago #

Well, the one main problem is that I've completely refactored the code in the development branch of the iOS version. And there's probably already a lot more jQuery in there. For example, the createInterfaceListWithArray method is now:

createInterfaceListWithArray : function(listArray) {
        var list = $("#interfaceList");
        var count = 0;

        for(var i = 0; i < listArray.length; i++) {
            var r = listArray[i];
            var item = document.createElement('li');

            function _touchend(_key, _count) {
                return function(e) {
                    Control.interfaceManager.highlight(_count);
                    Control.interfaceManager.selectInterfaceFromList(_count);
                }
            }

            $(item).bind("tap", _touchend(r.name, count++));

            $(item).html(r.name);

            $(item).css({
                        "border-bottom" : "1px solid #666",
                        "font-weight"   : "normal"
                        });

            $(item).addClass('destinationListItem interfaceListItem');

            $(list).append(item);
        }

        $(list).listview('refresh');
    },

I don't think it's possible to get much more jQuery in there :) So, maybe take a look at what's in the www folder the root directory of the repo on the development branch before you do too much work... most patches to the main branch won't work with the development branch and vice versa. And work on the main branch has basically stopped; the development branch will become v2.0 of Control.

I'll try and integrate the Android version with the new .js files sometime soon. It would be great to have some jQuery experts contributing! - Charlie

Posted 1 year ago #

billieblaze
Member

you can ALWAYS get more jquery.. hah.. .each instead of FOR loop, `$('
<li>')` instead of createElement.. :)

so the dev/www is the current version? Thats what i was trying to run on my android last night and was going to begin by getting it debuggable and improving some of the error handling when i encountered problems..

Posted 1 year ago #
admin
Key Master

I didn't know that shortcut to create elements and had been wondering about that... thanks.

Yeah, I have to port the dev/www stuff to Android. There was one point where I had both iOS and Android using the same www folder, but it became exceedingly difficult due to the complexity of dealing with the different device sizes in Android. Maybe I'll try to get that working again... it would certainly be easier to maintain.

Posted 1 year ago #
billieblaze
Member

I started a little blog about what i've been doing.. first post is just a general overview of the interface i've got going. I'm going to expand page by page on the control and max4live sides respectively throughout the "series".. I'd love to hear from any readers!

http://diffuseaudio.com/index.cfm/content/blog/22469

so, this leads me to ask, what are the main differences b/w the android code and the ios code? is it mainly just sizing? or, are there other things (java layer, etc) that differ? I really need to get phonegap setup, it just seems daunting from the quick look I had at it (for PC / android specifically)..

One thing that I think is majorly lacking and would love to contribute, would be a way to define CSS files for the interface - maybe it'd just look at the .js file and by convention load the .css equiv if available, i don't know, but I've certainly got some wheels turning.

Posted 1 year ago #
admin
Key Master

That interface looks pretty intense... looking forward to reading about how it integrates with Max4Live!

In regards to iOS vs. Android, yes, there's the whole Java vs. Obj-C thing, but, to be honest most of the new code for v2 of Control is in JavaScript, not in the backend stuff. If I remember correctly, almost -all- of the JavaScript / HTML differences had to with the problems getting things to appear at the correct resolution on Android. And it seems like I only got it correct for about half of the devices out there (still pretty good in my book considering how many different resolutions / operating systems there are).

I did at one point add css classes to all the widgets, both so they could quickly be grabbed by jQuery (for example, $(".button") and so that style sheets could potentially be deployed. You could certainly download a style sheet from a server and have it be applied. I'm not sure how you would save it to be local on the device itself without having to recompile the app. There might be something tricky with localStorage you could do...

Posted 1 year ago #
billieblaze
Member

Just got phonegap + ADT setup - yay, more stuff in my eclipse windows..

Then copied 1.4 from dev/www/ to /Android/Control/assets/www .. seems to be working..

And man, thanks for the tip w/ weinre, great little piece!

Posted 1 year ago #
admin
Key Master

Really???

I am shocked. That is great news. There are some things which can't be working yet, like Bonjour and receiving OSC messages, but I guess the rest of it (OSC sending, interface selection, destination creation / selection) could be working. If you're interested in fixing things, the main reason Bonjour / OSC reception won't work right now is because the names have all changed in JavaScript to be inside of the Control object. So, window.oscManager is now Control.oscManager etc. Simple fixes really.

Keep me posted how it goes. - Charlie

Posted 1 year ago #
billieblaze
Member

well, by working i meant, i can load it and maneuver around a little.. i keep getting some annoying message about calling phonegap functions before deviceReady is called..

Posted 1 year ago #
billieblaze
Member

I see the reload button in index.html.. am I correct in assuming I'd have to point the src of the script tags to my webserver to be able to "reload" and check script updates in realtime?

Posted 1 year ago #
admin
Key Master

Sorry I was slow responding to this... been traveling. Yes, that's how you can reload the pages easily. It works pretty well.

Posted 1 year ago #

RSS feed for this topic