-thread removed- - JAM, MDA Compact, S100 Software Upgrading

The newest version was released on Development forum,so this thread removed.

Very nice
Very nice application, tried previous version, many thanks. Just a thought, is that possible to make it smaller in size and keep it as a today's plug-in? Something like one inch in height and rolling through-out the width of today's screen?
This helps to keep our favorite test always on top and rolling , what do you say?
Laso personally interested in how you developed! what tools you used?

VS2005 with WM5/6 SDK and CompactFramework2.0
My apps usually written in VB.Net or C.

Related

Spb New Pocket Plus 4.0 - is worth a look

<< Plug Alert >> (I am not affiliated with Spb in any way.) (But if they give me free products, I wouldn't mind. )
I didn't see a thread about this announcement, so I thought I mention that Spb Software House has a new version of Pocket Plus. It is smaller, faster and has some really cool new features. I personally like the IE7-like tabs in PIE and the 'touch-like scrolling of Contacts and PIE. (Interestingly, if you use Spb Contacts, I can't seem to get it to scroll.)
http://www.spbsoftwarehouse.com/products/pocketplus/?en
I have been a big fan of Spb. I know now that I've been on the XDA forum for a while that some of the features of the Spb products are available for free, but I think they do a great job of putting it all together.
I loaded this yesterday and I've been busy with work, so it is a little early to review. Has anyone else looked that this. Post your comments here.
I love the new "Smart Scrolling" feature... You can scroll your contacts and web sites like on TouchFLO.. Great stuff..
I have been using SPB Plus for the past two years. Downloaded this new version and in just one hour I was convinced to purchase the licence key.
I am specially impressed by the reduction in memory usage over the previous version and also the large tabs fit for finger operation and finally the way it handles third party today screen plug-ins.
Tried the trial version:
good point - doesn't take too much memory to run.
Bad point - occupies 2.9 meg of device memory.
good point - runs other plugins within tabs.
bad point - no need for Ilauncher anymore.
good point - tabs in IE.
bad point - smart scrolling doesn't work very well ( I do have touchflo rom so maybe this is interfering with it).
bad point - only lets you put 6 tabs on today screen.
good point - you could run Ilauncher in a tab and have more tabs to launch things.
good point - skinable.
overall I like it, i'm going to run the trial version for as long as possible but on first impression I may switch to this it is fast and flexible enough and integrates well with other programs.
I would recommend you try it. (I;m not affiliated in any way either).

Jbed WinMo screen problem

I've got this problem ever since I switched to Windows Mobile 6.5 builds. Java applications executed by Jbed begin to resize themselves after some time. It's almost as WinMo is losing focus of this app - suddenly top and bottom bar of WinMo appears, screen is a little bit resized.
Anyone had an issue like this one?
Do u check all version from here:
http://forum.xda-developers.com/showthread.php?t=407667
??
Yes. I already tried them all.
Here is my thoughts.
You indicate that the size reduces over time. which implies its fine at first.
I suspect that your running a java app that is setting the java parameters and hence reducing them in the process.
Try 1 new java app at a time, then see which one could be causing that!
I know that some apps are made for QVGA screens or smaller (like for Nokia phones) and those will always display small if its built for one of those devices specifically.
Alternatively check this thread and see if it helps with the settings.http://forum.xda-developers.com/showthread.php?t=439989

Interest for WisBar Advance Desktop

I'm interested to know how many people would like to see a WisBar Advance Desktop build for Android. Just let me know. Thanks!
+1
I think WAD was a very cool launcher in WMobile
Fantastic loved it on win mob
Sent from my Pulse Mini using Tapatalk
I loved wisbar!
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Well, so far it's looking like there's at least a little interest. I'll get started.
Count me in a interested. Never ran wm without it!
Sent from my PC36100 using Tapatalk
Its funny that you mention it. I just visited the wisbar forums thinking there may be something about it coming to android. Before switching to android I had purchased and used Wisbar and WAD. As good as WAD for WM was, it just never really worked perfectly. And thats only because of the limitation of WM and the hardware not WAD itself.
I think android is the perfect platform that would be ready to embrace WAD. I will be looking forward to using it in the future I think WAD for android will be what the long term goals of WAD for WM had striven for.
I'm glad that you finally decide to make an android version of WAD2(I've ask for that a long time ago in your forum).
I hope that this best wm UI will come on android devices very soon.
-----------------------------------------------------------------------------
I use WAD (now 2) since a long time. I could not do without it. It is the only reason to stay at WM6.x.
If there would bei WAD2 for Android, it would be great and I think I would change over to Android too
Interestng...I also used WAD when I had a PPC device. I would be interested too.
I would be interested too... On WinMo Wisbar Advanced Desktop was amazing!
Thank you everyone for your interest. I've been doing some thinking about this as it will be a major step for me as I've been a long-time supporter of Windows Mobile (I've been around since PPC2000).
Given how powerful Android is, I can only think of one UI limitation at the moment: since there's no taskbar with an ever-present start menu, I'll have to make the app-drawer/launcher available on every page. At least, that's probably the best way to go right now unless someone has a different opinion/preference.
Another thing I was thinkg about: do you want a variable number of pages (being added through Menu > Add Page) or should I add a preference like some other launchers have to specify the number of pages?
These are very good news.
I can't wait to be able to use WAD again. I just hope that HTC Tattoo will be supported.
As for pages, I prefer the way of wm WAD2(pages added via menu).
So, I'm thinking about approaching this from a different direction than I did with Windows Mobile.
The first major change is I'm thinking about using a scripting language to describe how things are laid out and how they behave rather than just dragging and dropping items. The reason is two-fold:
1) This will give the script designer more control about how things look and how they work.
2) We won't run into the problem of shortcuts that open apps and widgets that are not installed on someone else's device (a major shortcoming of WAD2's).
So, the language would say something like: create a folder at x, y. This "button" will open it and this button will close it. You would also be able to specify an area where shortcuts could be added, such as "create a shortcut grid at x, y", but you would not be able to specify the shortcuts (this would be left up to the user who is using your theme).
One downside of this is that the layouts would have to be created on the desktop and then uploaded to your phone.
The other downside is that this would severely hamper the ability to launch specific apps using scripts. But, this is really a limitation of Android itself as, unlike Windows Mobile, not every device comes with the same core set of apps. And, for the apps that are included in most devices (such as the calendar), the intents to launch them may vary depending on the OS version (i.e. the calendar changed in between Eclair and Froyo).
I'm just brainstorming here. If anyone has any suggestions, please feel free to let me know. Right now I'm in the planning stages to see how close I can keep it to Windows Mobile, but at the same time implement new technologies in order to make it the most robust launcher around.
hells yeah man!!! i used it on my tilt for a while.....i think its ironic how similar android really is to winmo...just more refined but very similar in the idea
I found this thread quite late but i can just say +1. =)
I would really like to see Wisbar Adv Desktop on Android. Hope you are making good progress
I just finished asking your to offer support for android on your forums.
Feel free to plus one over too, guys.
http://forum.lakeridgesoftware.com/showthread.php?p=106717#post106717
See it for the first time. +100000
I used to love making themes!!
Sent from my X10i
Awesome. Back in the days WAD was one of the best applications for WM, I've always been impressed by how much one could do with it.
I like the idea of creating themes on the desktop and then uploading them to the phone, because creating themes has always been kind of difficult and work-intensive.
You can map the app drawer to the home button or you might even be able to implement the ability to create shortcuts that open the app drawer.
Concerning the number of homescreens, I think Menu > Add Page is a bit more convenient and less likely to mess things up (since removing non-empty home screens could create issues, as it did with some launchers).
chmckay said:
Thank you everyone for your interest. I've been doing some thinking about this as it will be a major step for me as I've been a long-time supporter of Windows Mobile (I've been around since PPC2000).
Given how powerful Android is, I can only think of one UI limitation at the moment: since there's no taskbar with an ever-present start menu, I'll have to make the app-drawer/launcher available on every page. At least, that's probably the best way to go right now unless someone has a different opinion/preference.
Another thing I was thinkg about: do you want a variable number of pages (being added through Menu > Add Page) or should I add a preference like some other launchers have to specify the number of pages?
Click to expand...
Click to collapse
I just stumbled over this.... is it for real?
WAS with all the functionality will be ported over to Android? This will be the killer app taking all other launchers / home screen apps out of biz.
I am here to betatest!
chmckay said:
So, I'm thinking about approaching this from a different direction than I did with Windows Mobile.
The first major change is I'm thinking about using a scripting language to describe how things are laid out and how they behave rather than just dragging and dropping items. The reason is two-fold:
1) This will give the script designer more control about how things look and how they work.
2) We won't run into the problem of shortcuts that open apps and widgets that are not installed on someone else's device (a major shortcoming of WAD2's).
Click to expand...
Click to collapse
Hopefully you can get the HTC Sense Widgets to work as well at least on HTC devices where this should not be a violation of copyright laws. I will gladly offer to borrow you a european HTC Desire for testing purposes if that is of any help.
I second your notiong of requiring a script language, but of course it would take one that is not laid out for programmers but also still understandable for regular designers. Search around here in the Forum for SlickUI and KiteUI, both which are still deep in the "maybe wel will do this stage" for some decent ideas on how people imagine their ideal design, and therefore gfgiving you an idea how much flexibility your framework needs.
Things that should really be in the to-do-list: radial icon menus. That means you assign say 6-8 icons to a WAD icon placed on the homescreen, upon tapping this the home screen blurs and the assigned icons circle around the pushed icon. This is a terrific way to organize similar apps IMO, much better looking than the folder blocks we have gotten used to.
WAD actually was one reason I found it very hard to aprt with my WM phone. Thie level of adustability had not been reached before. People who do not know what the heck I am creaming my pants about should use google image search for "wisbar advance desktop". It was a pure naked framework, allowing beasically every freedom any designer could wish / hope for.
Anotherr important thing to note is the touch features which have come quite a long way since WM6.5. You would need to extend the framework in order to allow rotating dials for menu control, swipe movements for changing screen left to right and vice versa.
If you could actually manage to pull the old stunt where you made an app run constantly on a "homescreen" it would be awesome. Imagine 3-5-7-whatnot screen with widgets laid out side by side, but a simple upward stroke brings you into the already preloaded browser (from which you return with the back key into the regular homescreen).
God, I am bursting with ideas.
As I said, I will beat test all days long if you need someone.
So, the language would say something like: create a folder at x, y. This "button" will open it and this button will close it. You would also be able to specify an area where shortcuts could be added, such as "create a shortcut grid at x, y", but you would not be able to specify the shortcuts (this would be left up to the user who is using your theme).
One downside of this is that the layouts would have to be created on the desktop and then uploaded to your phone.
The other downside is that this would severely hamper the ability to launch specific apps using scripts. But, this is really a limitation of Android itself as, unlike Windows Mobile, not every device comes with the same core set of apps. And, for the apps that are included in most devices (such as the calendar), the intents to launch them may vary depending on the OS version (i.e. the calendar changed in between Eclair and Froyo).
Click to expand...
Click to collapse
I'm just brainstorming here. If anyone has any suggestions, please feel free to let me know. Right now I'm in the planning stages to see how close I can keep it to Windows Mobile, but at the same time implement new technologies in order to make it the most robust launcher around.[/QUOTE]
#Pinch to zoom and similar gestures will go a long way in allowing to extend the possibilites and ways the users can interact with the interface. Instead of an always visible appdrawer you could just use a gesture predefined that will launch the app drawer
Should we make a thread where all former WAD users and upcoming UI design freaks post their wishlists?

[Q] any way to view Sketchup (google) files on Android dev?

I already STFA and did not find what I was looking for. I was wondering if there is an application that will allow viewing of existing Google Sketchup files, editing/creating files - no - not so much, think that would be best done on a full blown desktop, One earlier post was asking about running a fully functional Sketchup, and I tend to agree that it would be too much of a tax on the processor and memory to be feasible for a mobile device. I also found the SketchBook program from AutoDesk which is designed for mobile devices but from what it says it is more like Paint in Microsoft Os's not a CAD type program.
Anybody know if there is anything like that available out there to be able to view Google Sketchup files? Thanks in advance for any information on the subject.
Sorry to wake up an old topic (very old) but I too am looking for such an app.....being a kitchen builder in my spare time I was asked a few times if I had any models on hand to show. And since I do all my sketches in Sketchup, well you guessed it....I can't show them on my tab....
Would be kinda cool to show potential customers how their kitchen might look like if I could just drop existing cabinets in place etc...
If you've already found something would you mind sharing with me? Very much appreciated...

Milkdrop/androp amazing music visualization live wallpaper

AerialX said:
Alright, thanks for the results everyone. I asked because I wanted to decide which framebuffer method would be selected as the default... I decided on the "slow" version - 8bdefb7e - as it's the most compatible option. The "fast" version can be chosen as a preference for those who prefer the speed. It may not work on all devices, and seems to produce artifacts and some tearing, though it probably is preferable for most simply due to the speed.
So, here you go, latest version: Download
Built for ARM and ARMv7, does not include the NEON extensions. You may want to uninstall the old one before installing this.
EDIT: Fine, have a NEON build too: Download
Hint: the main change is the inclusion of settings. I consider this build to be very close to the initial release for the application on the Android Market. Just a few things remain...
What's Left
In order of priority...
Filtering of non-white-screen presets. The app will include the projectM preset library by default, excluding any that just result in a white screen. I don't believe I will be able to distribute any of the Winamp/MilkDrop library itself, as awesome as it is.
Stability enhancements. It's probably still somewhat crashy. I'm not sure how much, though. I'd love to get some detailed reports on how stable/crashy it is for you guys.
snoop() support, otherwise the wallpaper requires 2.3... I don't have anything older though. Would anyone be able to test on an older OS for me if I supplied a build?
x86 support. Means writing a few missing STL pieces.
NEON detection, and the loading of an appropriate optimized library. I get the feeling that this is just a placebo, but will try to get it in.
Optimizations. Would be nice if it didn't essentially restart every time you visit your home screen. I'm probably leaving this for a 1.1 release though.
Localizations. If anyone wants to help translate the settings page into their native tongue, I'll happily include them.
Anything else I forgot...
What I Need
It would be great if anyone who tries it can comment on its stability. Whether it often dies, reverts to some other wallpaper, completely kills your system, or whatever. Just give me your overall experience with the wallpaper. I'm not necessarily interested in hearing about its performance at this point - if it runs slowly on your phone, I suggest switching to the "fast" render method and only using presets that run speedily. Of course, miscellaneous suggestions / comments / criticism are welcome as well!
Another thing I was hoping someone could do is go through all the presets and filter out the bad "white" ones. The new settings page makes it easy to test a single preset at will. So if anyone is willing to do this, I could really use two zips: one containing all working presets from the projectM set, one containing all from the MilkDrop set.
As a base for the projectM set, please use this: Download
For the base MilkDrop set, find the attachment from a few pages ago.
You may also want to note any that run particularly slow, but please don't exclude them from these packages.
EDIT: As a test, feel free to try the exact same preset on both the non-NEON and NEON builds and see if there's any noticeable improvement there.
Click to expand...
Click to collapse
Hands down best app ever
Sent from my LG-P999 using XDA App
Any screenshots?
Um seems to be a few post missing in this thread... Usually when something starts like this:
Alright, thanks for the results everyone. I asked because I wanted to decide which framebuffer method would be selected as the default...
Click to expand...
Click to collapse
What results are we talking about here? What is this exactly? Kinda like writing a book that starts:
But when the baby came out looking like death on a hot tin roof, Jim finally found the nerve to call her out and say, "Devil wench, I will not accept that thing as my my spawn! I know you have been sleeping with your brother!"

Categories

Resources