From what I’ve seen a lot of people like to make setups with an Actionbar and they use Zooper to make them, so my…
From what I’ve seen a lot of people like to make setups with an Actionbar and they use Zooper to make them, so my suggestion is to implement a basic actionbar for the homescreen that we can customize, this would be optional of course.
]]>
D5 Creation
< ![CDATA[
Hum, I don’t know… I believe that the amount of customization would go far beyond what can be found in the app drawer.
Instead, maybe the standard Android action bar could be displayed and configured through script (probably too complex to make a UI for this).
]]>
< ![CDATA[
“Instead, maybe the standard Android action bar could be displayed and configured through script”
Sounds good to me.
]]>
< ![CDATA[
My Android Rhino implementation supports loading bytecode jars now (v1.4).
]]>
< ![CDATA[
I’ve been meaning to ask you still working on your script editor?
]]>
< ![CDATA[
Jay M
No. I’ve stopped using on-device editors almost completely. Plus, my script editor was meant to do one thing better than the built in one: type-aware autocompletion. While trying to implement that I realized that it is effectively impossible, as javascript has no concept of typed variables. Not even the biggest IDEs attempt to do that, and for good reason.
]]>
< ![CDATA[
Yes in theory it should be possible to configure the action bar through script. Does it work if you try to display it using:
LL.getContext().getActionBar().show();
or with the alpha
getActiveScreen().getContext().getActionBar().show();
]]>
< ![CDATA[
I couldnt get either of them to work. Says cannot find function getContext in object on line 3.
bindClass(“android.app.ActionBar“);
var ab = getActiveScreen().getContext().getActionBar().show();
return ab;
I’m probably using it wrong I’m a programming/scripting noob remember 🙂 What I did was add a custom view that runs this^ script
I also tried with just.
LL.getContext().getActionBar().show();
and
getActiveScreen().getContext().getActionBar().show();
]]>
< ![CDATA[
Yeah, it seems the action bar is not created at all because of the selected theme.
]]>
< ![CDATA[
Nevermind it was worth a try 🙂
]]>