Mortscript
{
"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"
}
View attachment MortScript.zip
IreView attachment IRE.zip
Why not? Whenever app doesn't use HWND APIs, it will run. If it does, it just won't show HWND.
Absent functions is still a problem for some (if not most) of apps.
Please more information
About how to use and benefit from the advantages
AhmedElsharkawy said:
Please more information
About how to use and benefit from the advantages
Click to expand...
Click to collapse
There is explorer.exe (started usually by HKLM/Init/Launch50, it is replaced by simply TellShell.exe TaskBar started by HKLM/Init/Launch40) and some shell missing on WP7 relative to full WEC7, especially screen UI functions and parameters. There are possibilities to include missing APIs by using Platform Builder sources, but it is too much work for deprecated system, because all necessary changes will related to big amout of dependent places. The same answer is to USB Host/OTG/HID support etc. All is possible, but too few experienced native coders is available. May be simple debugging API using application can start most of WCE/WEC applications with simplified UI. There is security hole posssible due to different data and shared code segments between kernel and user mode (callbacks are valid with marshalled parameters), which offers to us all processes memory and code controlling access too. The most simpliest way is to add visual page creating and registering to original WM/WCE/WEC source code, which cause application main window visibility, but it could not solve problem of any missing needed API functions and parameters (scrollbars, start menu, low level support etc.).
Related
Inspired by the zoombar projects (link below), I thought that it could be possible to convert the hard button area of the touch HD to a more useful thing: a touch pad.
I think we have enough room for left-right and also up-down movement. Also a double click could be considered as pressing the Enter button.
I believe we have skilled enough developers who can make this dream a reality (like XaKing and namuk).
-------------------------------------------------------------------------
Links to the zoombar projects mentioned above:
XaKing's (works flawlessly on many ROMs): http://forum.xda-developers.com/showthread.php?t=518367&highlight=zoombar
{
"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"
}
namuk's (on-going project): http://forum.xda-developers.com/showthread.php?t=515701
Although im no developer, i'd love to see this!
Although, would it only enable in certain applications? Because i want to answer a call when one comes in and not be zooming! lol
Also, if i get a call in camera mode, will it detect this and revert the buttons?
It all comes down to the limits of our imagination. Maybe we could have a blacklist/whitelist approach, where we could define the applications for which this touch pad should be enabled. This could be in some conf file or registry.
But we need the real thing first, these nice little touches could come later.
vizier said:
It all comes down to the limits of our imagination. Maybe we could have a blacklist/whitelist approach, where we could define the applications for which this touch pad should be enabled. This could be in some conf file or registry.
But we need the real thing first, these nice little touches could come later.
Click to expand...
Click to collapse
you are a wise person
I am trying to set up some NFC tag actions using my Galaxy Nexus running stock ICS 4.02. I am using the pro version of NFC Task Launcher. Right now I can create a shortcut to launch a program via NFC, but I want to do more. For example, I want to create an NFC tag in my living room that will execute a Wake On LAN command. Right now, I have the option to launch the WOL program, but then I have to click a button on the screen, which is such a pain. I think I can do what I want using the Custom command line option which should "open a specific activity within an app", but I don't know how to figure out the custom activity command. This command would be formatted like "com.google.android.talk.BuddyListCombo", which I found in reference to Google Talk. How can I figure out custom commands for different programs? Thanks.
I beleive that you will have two choices.
1. Contact the application developer.
2. Launch application from Eclipse, then you will see the intent.
Or is there anybody else that has a better solution?
dsnis said:
I beleive that you will have two choices.
1. Contact the application developer.
2. Launch application from Eclipse, then you will see the intent.
Or is there anybody else that has a better solution?
Click to expand...
Click to collapse
That would be my suggestions too.
Did you solve this, even setting profiles app picker
{
"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"
}
could not help me
Ian
What is Flash-Transfer?
It is an app which provides a file-sharing functionality to your smartphone using Wi-Fi tethering. It can be used to easily connect to another android smartphone and then transfer apps,
images or any other files you may want to. We all have to agree that it is indeed a clever way to transfer data faster, given the slow speed at which Bluetooth works. This doesn’t even use your data plan, just connects to the other device over Wi-Fi.
{
"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"
}
Why Flash-Transfer?
Though similar apps already exist in the market, what defines Flash Transfer is its unique style of sharing files, aptly termed as Swipe & Share. It allows swipe like gestures to share photos, that seems more like magic rather than a useful feature. As illustrated, the photos being swiped out simultaneously comes into view in the receiving device, which is really a fun thing to watch. There is also a shake and share feature.
Its simple enough to configure and use, that once you open the Flash Transfer app on your phone or use the Swipe & Share option from the Gallery or File Manager, you can invite someone to share with. This invite appears in the form of a QR code which need to be scanned by the receiving party on their device to get connected. Once done, both phones can simply share any number files or apps that you want without any data charges.
IF I HELPED YOU IN ANYWAY
DO PRESS
RESERVED
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I made an app for my school, it is currently on google play. I need help on designing the dashboard as there is another data to be added onto it.
Currently the dashboard has 2 parts, academic requirements (plain text) and schedule (tabbed). On the next update there is another plain text to show which is academic interventions much like requirements, just plain text. I'm thinking of redesigning it because if I add the academic interventions below the requirements, it would push the tabs below and would not look great for small phones as they could only scroll a little of the tabs.
{
"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"
}
Here is the website version of it:
Hey ,man, what kind of feedback or help are you looking for? Give me a shout on here or email. [email protected]
I think you are right, the "header" (academic requirements) is way to big and the scrollable part gets to small. You could do different things:
1.) Put the academic requierement in different activity and let them open it via the menu.
2.) You could just popup a small info message if requirements are available and give the user the possibility to click on the message so the requirements will open in a different activity/popup
3.) Remove the title "Requirements for Clearence" (because it is actually very big - and it is only a title, isn't it?).
These are my thoughts so far
I kinda agree with spcialx I think you're wasting a lot of space with the title "Requirements for clearance" and even more space by saying "No pending requirements posted", you could just add a : 0 in front of the first title so that you save some space (for example, Pending Requirements for Clearance: 0 ; Pending Academic Interventions : 0 ) and if there is 1 or more, maybe make it clickable so that it shows what they are.
Hello everybody,
we are looking for alpha tester for a new app that we’ve been working on for a long time: Contextual App Folder (C.A.F.)
{
"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"
}
C.A.F. like the name suggest allows you to create contextual folder on your homescreen and access to the right apps and shortcuts just when you need them. The app offers 9 different trigger (e.g. Headset, Bluetooth, GEO Location) to create your custom scenarios and it should also work with Tasker for more advanced stuff. Custom folder styles and color options are also available.
If that sounds interesting for you and you’re willing to accept minor flaws which come with a early access release then join our Google+ Community to get access to the app on Google Play:
https://plus.google.com/communities/114562739170140440710
It’s currently a closed group (some components are not ready for a public release) so you need “ask to join” but we’ll try to give you access soon as possible. A open Beta through the Play Store beta program is also planned in the next weeks.
Things to note:
The App requires Android 5.0+
You may have to adjust the folder size if your device is not in our database or you are using a custom launcher
Looking forward hearing your feedback!
*Edit*: The app is now in beta and can be downloaded directly from the Play Store. Thanks to everyone who participated our alpha test!