https://android-developers.googleblog.com/2017/05/here-comes-treble-modular-base-for.html
What took google so long to implement this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One problem I can see from reading your link is adding another layer to Android. The fastest way the perform any program routine is hand write it in Assembler directly for specific CPU, the slowest would be to run in multi level abstract program like Basic, so adding another layer to Android could slow it down, but I hope I'm wrong.
pete4k said:
One problem I can see from reading your link is adding another layer to Android. The fastest way the perform any program routine is hand write it in Assembler directly for specific CPU, the slowest would be to run in multi level abstract program like Basic, so adding another layer to Android could slow it down, but I hope I'm wrong.
Click to expand...
Click to collapse
Don't worry, google know's that they're doing... /s
Related
Hi All
I've updated my project and on of my concerns is the deprecation of AbsoluteLayout
look at this:
http://2.bp.blogspot.com/_NiIT7LXuBv4/SfuFe7dFn9I/AAAAAAAACKo/0neSn1Jyey8/s1600-h/device.png
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
notice the cards on the middle that are overlapping?
see the bottom cards that have some sticking up?
how am i supposed to do that without AbsoluteLayout???
any ideas will be appreciated...
You copy the AbsoluteLayout code from the master source tree and maintain it yourself... You figure out how to do this using FrameLayout or RelativeLayout. The Android Team claims you can do anything that you can do with an AbsoluteLayout with either FrameLayout or RelativeLayout, though I am skeptical. Personally, I might suggest ditching the view hierarchy and drawing your UI to the canvas or even OpenGL.
got it to work using linear layout
I did do it, but it isn't 100%...
take a look
http://developreality.blogspot.com/2009/05/overcoming-absolutelayout-deprecation.html
See if you can get some help from SweeterHome. They seem to have the layer thing down pat.
You may find that it is a memory hog, though. Because that is the main problem that SweeterHome has had developing their app... The lack of available memory on the hardware.
OK so i am wanting to make a new project but im not sure if what i have on the table right now is something worth going for. Its going to be a massive multi-tool that supports multiple phones including android, apple and possibly windows. It will be able to root your device if a way has been found for it. It will also have Semi-GUI layouts for programs such as ADB, NVFlash and so on. This will be a massive project, massive size and massive amounts of updates... almost daily as things change almost daily. But if it can be done i am thinking it would be the best tool out there and the most hated by some... hopefully not to much though. Here is a pic of something i threw together in a hour or so and has a project from december on the tf101. Please let me know what everyone thinks even if its bad or good. If you can code Visual Basic and want in let me know. I could use a hand lol.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok guys.....It has been a while since I have been on here....
So what's new...
I decided it was about time I made it a little simpler to work with AppInventor so I took up the challenge to expand on an already offline local version of AppInventor.
So what did I do?
I took the offline AppInventor and loaded it in to a simple UI......
But that's not all.....
I created a set up which will install and help configure all the things you need to start building right up to publishing your apps
The ISO currently stands at something like 1.3GB but that is only because it is packed with everything you need.
Right now I'm running short on time and will not be able to upload right now.....but.....enjoy some screenies lol
Upload will follow soon enough.
Peace guys.
Install ADK.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Install 1 of 2 Publishers.....
Configure JAVA Environment Variable Guide....
UI Loading Screen......
Main UI.....
Choose Publisher.....
Publisher......
Hi!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was struggling to create clear folder structure for maintaining reverse-engineering projects. Also doing everything manually took that much time I preferred not to compile app and read .java files of cracked application just to check that I didn't break anything while working with Smali. That's why I created this project. The code is mostly uncommented but I have made it pretty easy to read if you know basics of Ruby though I'm thinking about commenting it soon.
The software is Linux only at this moment since I'm lazy, I don't like Windows and there is no good reason to prefer Windows over Linux while reverse-engineering.
https://github.com/b10011/Android-Software-Detonator
I hope you enjoy, report bugs and contribute. And as always I'm not responsible of your acts and this shall not be used for apps that you don't have permission to reverse-engineer!
We have a decent logging inside L Speed but it can be improved. Since we strive for simplicity I have some ideas to suggest
And yeah, if someone recommend simple/advanced logging, I won't do that, it's a bit overloading.
Do you like something like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for support
Root Apps
For root applications logging should not be simplified IMO, especially since a single switch in L Speed can (and often does) trigger multiple actions. Each action should be clearly documented in a single line as is done today for many L Speed options (thank you!). However, logging for some are missing while others only indicate a switch was set w/o accompanying detail. Looking forward to improvements in future releases.
I would agree with @Davey126 .