Related
This Qur'an Viewer was developed for my own use and will be invaluable to anyone who has memorised the Quran and wants to view two-pages at once so that it looks very similar to the mushaf.
Two types of Indo-Pak script are available, as well as two types of Uthmani script.
WVGA (800x480) resolution is an absolute necessity to run this application, any higher or lower resolution will probably not work properly and has not been tested.
You may find the size of the script is a little small, but as a Hafiz I find it invaluable as a quick reference when out and about.
You can click the page to move next/previous. You can also click the upper part of the page to go next/previous juz or surah.
You can choose from three bookmark positions, which will automatically remember your page position on each of the three virtual bookmarks.
Download it here. Unzip and see readme.txt for full installation instructions:
http://www.acclaimit.co.uk/downloads/HolyQuranWVGA_Release_20091001.zip
*** Please completely uninstall the previous Quran13Line application if you installed it before. This new application uses all new script images and a different folder structure. ***
Screenshots attached.
Jazzak Allah Khair
Could you please tell me which screen resolutions are compatible ?
qvga,vga,wqvga,wvga ???
Thank you
I'm sorry, WVGA (800x480) resolution is an absolute necessity to run this application, any higher or lower resolution will not work and has not been tested.
Thank you very much
DOWNLOADED AND INSTALLED
It is wonderful !
But could we get better Pictures ? with better script ?
Jazak-Allah, I'm glad it works. I tried my best to make the pictures look good using the 480 pixels page height so that we can fit two pages on-screen at a time. It's not going to be possible to make it any better unless we have more pixels to play with, or do you have any alternative ideas?
What do you mean by better script? Which part of the script are you having difficulty with exactly?
Thanx for your reply
I meant a different set of pictures, even the 15 line ones
attached are two samples (Zipped with WinZip)
and if you like, I can guide you to the link where you will be able to download the whole set of the first or the second sample.
Thanx again
I see. You forgot the attachments.
Please let me know the link to the whole sets of any other images you know of and I'll see what I can do... 15 or other lined ones, but I will have to rename the application too
I've resized the sample images to 480-pixel height. See attached.
I think the script on these images is much finer than the 13-line ones and is unreadable with two pages on-screen at a time. It would make more sense to show a full page at a time for the 15-line ones, which does not quite fit with the original design goal of this application.
I guess the answer would be to create a new application called "Quran15Line" showing one page at a time, but I am not sure how many people would be interested in this. Poll?
So? have you checked the samples ?
I guess the images without the frames can be visualised better especially when two of them are joined together on a horizontal WVGA screen, right ?
waiting for your reply
Well, as I have mentioned in my previous post, ( sorry just seen ur answer ), the ones without the frame are better.
Regarding your suggestion of the "Single Page", I don't think too many people will be interested in it since the images are originally taken from a software with a single page, full screen style.
These are the links to the 'non frame images' try them and give me your feedback ( Horizontal and Vertical )
http://www.4shared.com/file/96364556/390c2fa6/v_wvga.html
http://www.4shared.com/file/97539687/b3476020/h_wvga.html
Thanx again
Ahh, about your attachment, in fact they both seem readable ! and do not forget that this software is intended for a 'two page style' which means that it is obviously with smaller pages.
I am so interested in the new images !
hope you can make them.
and regarding the software, you can change the options in the TOOLS key, to 13 lines ( your old images ) and 15 lines ( my suggested images ) !
What do you think ???
Jazakhallah Khair Brother Ashiq
Inshallah you will receive Sadqah Jariya every time i use it
this is what i have been looking for for ages
if you do update it can you consider a transalation in english which corresponds to same
13 line quran if possible,maybe i am asking too much
but thanks anyway
Salaams
I was already considering English translation which should correspond with the script. However, it will take a while to do this because there are so many English translations and because we have tell the application which aayaat are on each page so that they can be matched up to the translation. It may take a few weeks, but Insha-Allah I will work on it during any spare time I have.
jaguaralani said:
These are the links to the 'non frame images' try them and give me your feedback ( Horizontal and Vertical )
http://www.4shared.com/file/96364556/390c2fa6/v_wvga.html
http://www.4shared.com/file/97539687/b3476020/h_wvga.html
Click to expand...
Click to collapse
bro what difference with this?
Code:
http://www.4shared.com/file/134351630/60362269/h_wvga-800x480-medina2.html
http://www.4shared.com/file/134114828/f2fe41e9/v_wvga-480x800-medina2.html
thanks bro
we need another resolutions plz
thanks alot
there is a collection of indopak script at pdaquran .com
which is clearer to read as it is a page per screen
wonder if you you could use the images in you excellent software
ibrahimh said:
there is a collection of indopak script at pdaquran .com
which is clearer to read as it is a page per screen
wonder if you you could use the images in you excellent software
Click to expand...
Click to collapse
This application is designed for WVGA to show two pages per screen, so unfortunately I cannot use the pdaquran images. I would urge you to contact pdaquran and ask them to provide you with a Windows Mobile application (they already provide an iPhone one). In any case, couldn't you just download the PDF and view it using Adobe Reader one page at a time?
Dear monzoyt and all - thank you for the various uthmani images you sent - I am currently preparing the Uthmani/Madinah images and will release a new application within a few days InshaAllah.
It takes a while because I have cropped the images to maintain high quality after resizing and need to also match up the bookmarks to the page numbers, and also need to render the page numbers in arabic on the page sides due to the fact that the images do not have enough space to render the page numbers at the top.
monyozt said:
bro what difference with this?
Code:
http://www.4shared.com/file/134351630/60362269/h_wvga-800x480-medina2.html
http://www.4shared.com/file/134114828/f2fe41e9/v_wvga- -medina2.html
Click to expand...
Click to collapse
800x480 and 480x800, landscape and portrait screen mode!
Beta Version is HERE (Beta1).
looking for developer to write an Album Application (OpenGlEs?) and utilize the SDK to enable pinch-to-zoom on resistive screens.
Greetings,
Wow right!
finally i was able to perform a dual touch on our resistive screens and you can find the dll in the attachements along with a demo app!
NOTE TO EVERYONE :
Please don't report the 1 finger bug, it's well known and it will be eliminated (BTW, Zoom in is possible with 1 finger but zoom out is not)
this demo app is simply a demo app and only to show that the SDK is functional, it WILL NOT zoom to focus the pinched area! if you can develop a demo application and you have a graphics development experience please be my guest and i will help you with the SDK. the current demo only resizes the image and doesn't relocate it. i can do a proper one but this will mean taking time from the real project.
thank you
documentation will NOT be available as this is a preAlpha and it's just to get you excited
here is the demo
Video
http://www.youtube.com/watch?v=ld_kIpLWa3Y
Notice :
i'm not responsible for anything might happen to your phone (Even though i'm sure there is nothing to go wrong but just in case).
This is just a pre-alpha, and there is no garantee to go beyond this version. i'm doing this for the community for free and as a proof of concept only. i will continue to work on this on my free time but please don't rush!
you are not allowed to to ask people to pay for this SDK.
you are not allowed to disassemble the SDK or reverse engineer it.
you are not allowed to post the attachement(s) below to any other website. you can always link to this tread.
if you are going to use it in your application, you MUST put a link in your application/offical website that reffers to this XDA thread.
i reserve the right to make this a paid SDK at any point of time.
i reserve the right to relocate this SDK to another website or even take it offline.
that was long right?!
ok, let's go to business!
Demo Attached
To Use the demo, place 1st finger on the image, then place the 2nd finger also on the image and slide your second finger in or out!
Requres .Net Compat Framework 3.5,
Tested on
- Touch Pro 2 (HTC Rhodium)
- Touch HD (HTC Blackstone)
- Xperia X1
Regards,
Adel R. Al Zubeir (Anaadoul)
Documentation
How to use the SDK!
create an instanse of the class,
the object wich will detect the mouse clicks MUST have mouse down, up and move.
for example in the demo above the code is as following and i use picturebox
publicpartialclassForm1 : Form
{
DualTouchSDK.DualTouchSDK SDK = new DualTouchSDK.DualTouchSDK();
privatevoid Form1_Load(object sender, EventArgs e)
{
SDK.Zooming += new DualTouchSDK.DualTouchSDK.MultiTouchEventHandler(SDK_Zooming);
}
void SDK_Zooming(DualTouchSDK.MultiTouchEventArgument e)
{
// Do the zooming here e.ZoomRatio returns a value which is the % of the zoom < 1 = zoom in, > 1 zoom out.
}
privatevoid pictureBox1_MouseDown(object sender, MouseEventArgs e)
{
SDK.SetMouseDown(e.X, e.Y);
}
privatevoid pictureBox1_MouseMove(object sender, MouseEventArgs e)
{
SDK.SetMouseMove(e.X, e.Y);
}
privatevoid pictureBox1_MouseUp(object sender, MouseEventArgs e)
{
SDK.MouseUp();
}
}
Known Bugs (V0.0)
- Single Finger sliding causes zoom IN (notice that you CANNOT zoom OUT).
First of all, nice try. As developer I kind of (think to) know the technique involved processing this and for most part this could work. However since WinMo 6.5.x has it's own overlay I must admit it's not working properly on build 28008 (and 28002).
Actually it does work if you don't release the screen, but once you do, it's completely useless. You can't do anything but scroll, this probably because of the kinetic scrolling overlay. (This only happends if the image is larger than the screen ofcourse, everything else works as advertised!)
Second, may I add a suggestion (something I once tried in an application but never finished)? If you place your finger on the photo and then place the second finger the application imediately zooms in to like 400% (depending on the place your finger is placed), This makes it hard to pinch-to-zoom out, since you actually have to place the two fingers on the same position.
My idea is this. Whenever your first finger is placed down (and the coordinates are stored) and you place the second finger on the screen, the app would recognize this as a movement of the first finger but in 0 milliseconds. It might be possible to make a sort of minimum time required to move from 'a' to 'b', so the initial position of the two fingers can be 'stored'.
I hope I made myself clear enough for you to understand, as I do not have too much time to explain it better. If you like I can explain it better, but that would be later tonight, for now got to run!
Maybe this is due to the kenetic scrooling, i hope you can watch the video, the zoom will take effect only when you move your 2nd finger not after placing it!
anyway this requires alot of testing and alot of improvements as it's still pre pre pre alpha.
i tested it and it's working good enough on my TP2 and a WM6.5.0 ROMs
Agreed the video is what I had in mind, I'm sorry I should have watched it (though it wasn't up yet when I started replying). Anyway (still being here) this is not what I get, probably due to my build being different. As soon as I place my second finger on the screen it zooms in about 400% or 500%. I actually can pinch to zoom out if I place my fingers in de top-left and bottom-right corner, and move inwards... since the distance is larger than the amount of zooming done initially I can zoom out. Fact remains that everything only works as long as the image isn't larger than the screen, but all this is rather a Windows Mobile error than yours!
Good work, hope to include it into my projects some day!
Stil forgot to mention some required debuggin information (so you can keep track of things if you want)! I use a Touch HD (BlackStone) T8282 (Original Model). I use homecooked ROMs and now running WinMo 6.5.3 build 28008. Besides the regular HTC stuff I have no applications installed (as most is cooked in). I have no Manila 2.5 running and ... that's it.
anaadoul said:
Maybe this is due to the kenetic scrooling, i hope you can watch the video, the zoom will take effect only when you move your 2nd finger not after placing it!
anyway this requires alot of testing and alot of improvements as it's still pre pre pre alpha.
i tested it and it's working good enough on my TP2 and a WM6.5.0 ROMs
Click to expand...
Click to collapse
pocketnow.com is paying attention - congrats, and I can't wait to see more
http://pocketnow.com/tweaks-hacks/multitouch-coming-to-resistive-screens
Val
Anyone know how to make opera Zoom through an external app?
maybe sendmessage API or something similar?
It probably has a lot to do with sensitivity.
For me, resting one finger and using the other to do the gesture works the best. The key is to make sure the resting finger doesn't jitter much.
gotta try this!!!
Wow it's just awesome!
you can just use 1 finger and move it over the image. it works almost the same
pensoffsky said:
you can just use 1 finger and move it over the image. it works almost the same
Click to expand...
Click to collapse
it seems it registers a second press when you drag! but it works in an unpredictable way!
anyway i will look into it and eliminate this bug!
This is awesome so far! I love the progress. If you need any help with testing at all, let me know.
Nice, had this idea for a while but never felt like doing much work with it.
Demo app works fine on Fuze
I have a Verizon Samsung Omnia i910. It works for the most part here, only complaint is the "dragging" zoom issue that has already been reported. This is a great breakthrough, I'm really impressed! I will be following this thread for updates!
excellent work! i really hope you and the other devs pursue this. this way we can have some basic multitouch apps, defeat the last stronghold of the iphone, and claim victory lol.
Wow, this is an amazing piece of work you've created! I'd love to see this further developed, to either support existing apps (like google maps, Opera Mobile, Pocket Internet Explorer, photo viewers, other apps with zooming, etc.). Also, I'd love to see this refined further to support full pinching to zoom instead of only one finger moving, if that's possible. Regardless, I'd like to say thanks for all your hard work, and thanks for sharing this groundbreaking development with us!
great work...
بارك الله فيك و جزاك خيرا...
God bless you brother !!! Thanks a lot
Dear developers,
As we develop more and more apps, and as the Windows Phone marketplace hit 10,000 apps, I noticed an increasingly annoying trend: Abuse of panoramic hubs.
Yes, I understand that our latest greatest app may be our first important app, but as a user, the app is only one of my many tools in my toolbox, not the center of the universe.
And I understand that a lot of us want our app to be the hub above all other apps, however, let's face it - it's unlikely any third party hubs will be as important as Microsoft's hubs.
While the 6 major hubs in Windows Phone 7 presents some sort of extensibility, a lot of 3rd party hubs don't really do much except the function it is confined to.
A panoramic hub lets developers put different types of list controls in the same page, often for the purpose of showcasing the many depths of the app. However, some apps don't really have much depth, and the usage of panorama in this case feels like 40 pages for table of contents for a 20 page book.
If the app only displays one type of data, a pivot suits a lot better.
And panorama views usually come with a gigantic title, which takes up lots of precious screen space.
Sometimes I noticed that some developers will try to use a background in an app. However, if the app does not have a strong reason to have a background, e.g. dynamic content, I think it's a lot better to let users decide their background colors in their own theme settings. This can save us a lot of Photoshop time, and save users from a lot of text legibility problems.
Just something I'd like to share as both an app developer/designer and a user. Thanks for reading. Peace.
I agree with the fact that the panorama is overused where the pivot is in 99% of cases more appropriate.
I definitely don't agree with the background image thing. Two simple points: Brand Image and Individuality. From a developer standpoint you need something that sticks in users' brains - nothing does so more than product branding. And images are an integral part of that. Since a mobile device doesn't have room for giant logos, the best thing to do is move it to the background and let the text sit on top of it.
I agree that the developer should always offer a choice of background and ensure the text is fully legible in all - but Marketplace rules forbid text not to be legible anyway.
Second, for every application in the Marketplace there are 10 more identical in functionality. So why get the user to use your app over the other 10? Make it look better. And you can't make it look better when it's using the same colour scheme and layout.
pakkei said:
And panorama views usually come with a gigantic title, which takes up lots of precious screen space.
Click to expand...
Click to collapse
Modifying panorama's header template u can do whatever you want with the title (even delete!). Also, most important feature of panorama control is a nice looking slightly scrolling background image (that, I believe so, MS borrowed from Android's home screen).
Panorama != Hub
There is currently no way for a third-party developer to create a hub. Just because an app has a panorama view does not make it a hub.
I do agree though, the panorama view is overused.
I'd be interested if you could give an example of an app over using it as I really enjoy it when used well.
Purely from a developers perspective, I'm slightly worried that I may fall in the category of overuse.
emigrating said:
I do agree though, the panorama view is overused.
Click to expand...
Click to collapse
I disagree.
I think panorama apps are great. Instead of clicking and then having to go back you just swipe.
Best example for me was 1800pocketpc app which was a panorama/hub.
And then apps like facebook that are purely panorama are much easier to navigate cause you never need to reach for the back key
I love the panorama apps i have , its unique to our phones and what makes it great!
evolutionqy7 said:
I disagree.
I think panorama apps are great. Instead of clicking and then having to go back you just swipe.
Best example for me was 1800pocketpc app which was a panorama/hub.
And then apps like facebook that are purely panorama are much easier to navigate cause you never need to reach for the back key
Click to expand...
Click to collapse
I mean that the Panorama is overused because the Pivot is a much neater way of displaying data imo. I think it separates it out nicely.(Pivot being the Outlook-style swiping to sections)
However, some apps do the panorama justice. Faebook, IMDb, etc. However 3rd party developers rarely use it right.
Sent from my OMNIA7 using Board Express
Don't get me wrong - I love the Panorama view, but some [a lot] apps do misuse it.
I have seen plenty of apps which rather than having a "settings" button to open a new view will create their settings page (and about page) as part of the panorama. That is, IMO, not how you should utilize Panorama.
The same goes for apps where you may search for something to add to your "library", placing the search page on your panorama is wrong. It doesn't belong there.
A panorama should, again IMO, be used to display information that belongs together.
Example. You have a DVD collection app; The app is more than welcome to use a panorama as the main page, perhaps it can display "all", "new" and "favorites" on different pages of the panorama. That's all fine. However, adding more pages to display settings, about, search, changelogs etc just gives an awful UX. Add settings/about/changelog as a pivot on it's own page, accessible by a settings button. Add search as a button, either opening a completely new page or an popping up an overlay on the panorama.
Interesting point, and am inclined to agree Panarama views shouldn't be padded with search and settings screens. After all, doesn't the phone sport a physical search button that would be more consistent and allow you to combine your app settings within the phones' main settings for added convenience?
Sent from my HD7 T9292 using XDA Windows Phone 7 App
emigrating said:
A panorama should, again IMO, be used to display information that belongs together.
Example. You have a DVD collection app; The app is more than welcome to use a panorama as the main page, perhaps it can display "all", "new" and "favorites" on different pages of the panorama. That's all fine. However, adding more pages to display settings, about, search, changelogs etc just gives an awful UX. Add settings/about/changelog as a pivot on it's own page, accessible by a settings button. Add search as a button, either opening a completely new page or an popping up an overlay on the panorama.
Click to expand...
Click to collapse
The above is actually incorrect. A pivot should be used when the data of all screens are based on the same underlying data source. Outlook is the perfecet example, as you have all, new, unread which is just filters or views based on the same source: your inbox. The above where you have DVDs should be a pivot as well, since all, new and favorite are based on the single source of your DVD collection.
This is actually where people are making common mistakes with the use of a Panorama control, when it should really be a pivot control. Most users really won't know the difference between the two controls, but developers should to keep the user experience consistent across applications.
The use of a Panorama for a main screen to offer different sections of you applications is a good idea. Be careful to not have too many though. Once you have more than 4-5 sections in a Panorama, the user has the ability to get lost. And remember unlike pivots, the header of each Panorama is seperate from the others (a pivot combines them giving a better hint of the other pages).
Some things to ponder would be in a multi-page settings setup should you use a pivot or a panorama? Since its really not based on data, it should be a Panorama, but a pivot might give a better user experience.
spokanedj said:
The above is actually incorrect. A pivot should be used when the data of all screens are based on the same underlying data source. Outlook is the perfecet example, as you have all, new, unread which is just filters or views based on the same source: your inbox. The above where you have DVDs should be a pivot as well, since all, new and favorite are based on the single source of your DVD collection.
Click to expand...
Click to collapse
I wouldn't say it's incorrect. A pivot may have been a better choice, but it was based on an existing app I have installed where the panorama view isn't completely wrong.
I also believe your argument falls when we step into movie details - this should clearly be displayed as a panorama even though it's based on the same data.
spokanedj said:
Some things to ponder would be in a multi-page settings setup should you use a pivot or a panorama? Since its really not based on data, it should be a Panorama, but a pivot might give a better user experience.
Click to expand...
Click to collapse
A settings page should, IMO, always be a pivot (if more than one screen is really necessary - often it is better to have a scrollable listview instead). That said, if you manage to keep your settings on a single page, using a panorama view would still work to display the about/support/etc screens.
emigrating said:
I wouldn't say it's incorrect. A pivot may have been a better choice, but it was based on an existing app I have installed where the panorama view isn't completely wrong.
I also believe your argument falls when we step into movie details - this should clearly be displayed as a panorama even though it's based on the same data.
Click to expand...
Click to collapse
Here is a video from MS that clarifies this. Pivots should be used when displaying different views or filters or data. For the Movie details if you look at the "bad pano" example, around 11:00 it explains why you woulnd't want to do that. Just because another app is using it, doesn't mean you should.
http://channel9.msdn.com/blogs/jaime+rodriguez/windows-phone-design-days-pivot-and-pano
spokanedj said:
Here is a video from MS that clarifies this. Pivots should be used when displaying different views or filters or data. For the Movie details if you look at the "bad pano" example, around 11:00 it explains why you woulnd't want to do that. Just because another app is using it, doesn't mean you should.
http://channel9.msdn.com/blogs/jaime+rodriguez/windows-phone-design-days-pivot-and-pano
Click to expand...
Click to collapse
?
I pretty much agreed with you that it I presented a bad example. That said, it still works and was nowhere near as bad as many of the apps in the marketplace today.
As for movie details, let's just agree to disagree. Displaying movie details (as opposed to movie listings as discussed above) in a pivot is somewhat counter intuitive and gives a far worse UX than a panorama - I know, I've tried (and had it useability tested by the actual target audience).
Hi everyone!
We're looking for testers for our photo processing app named Pho.to Lab. It's a collection of more than 500 photo effects. These are mostly photo frames and photo montages. All the effects are applied automatically, so the app works more like Instagram filters rather than Photoshop. Warning: it needs Internet connection to process photos. If you're going to use cellphone data, you better not.
Pho.to Lab has been on the market since 2011, but we have completely redesigned the new version. I've attached some screenshots to compare the versions so you can see how different they are. And this difference is the reason why we are looking for testers.
View attachment 2168443View attachment 2168444
We're looking for feedback on two things. The first one is, obviously, any kind of bugs. Weird fonts, erratic shadows, stuff like that. You know,he app redesign can work bad on devices with extremely small or large resolutions or ppi. The second thing you could tell us is if you ike the app design. Was it obvious how to use it? Did the app do what you expected?
To get access to the app, join XDA Android App testers community or Pho.to Lab Beta community. Then follow this link and, pretty please, read what Play Market says you. Just in case you don't feel like reading it: opt-in first, then click the link below, then click 'Install' button.
Feel free to ping me anywhere. This thread, PMs, comments in one of the communities, and G+ messages are welcome. And please remember that I live in Eastern Europe. If you're from America and you're posting your comment in evening, I might very well be sleeping. So don't worry if I don't answer your questions or comments immediately, I'll definitely get back to you a little later.
Please check out Pho.to Lab and thank you!
Hi, I wanna ask is there any of you here know any hack, Interop app tools tweaks or any settings, even on when you’re only Interop Unlocked or jailbroken your Windows phone to disable that pesky “Adding finishing details” which is basically post processing the images, not just ruins it but also slows the process of taking pictures. Because of that, you’ll end up with “Saving…” message on your Windows 10 Camera app on 10 pictures straight you taken, you can’t take unlimited pictures.
Here's some pictures to tell you how it really ruins the pictures. The first every photo is what after the photo is taken, the post processing is still loaded, but basically a screenshot of the screen. It’s almost as good as what really the camera is seeing. The second ones are after the post processing.
Btw. I’m using a Lumia 830 and the very latest build available for it. Yes I got the most recent and latest Camera app update on mine, I dunno but I really think an app update after are what starts ruining the images here, I’m really sure this “Finishing details” aint here before Microsoft implemented this half bakedly, my phone aint shooting pictures this bad. The camera aint that really bad, it’s just the post processing that ruins it. It’s annoying and unacceptable. I can’t file this on Feedback Hub and ask for a fix, since I can’t get any newer updates since Insider Preview ditched my model already on Insider Preview. So please help me fix this the hard way.
Please help me remove this pesky process if it’s possible. I don’t’ want to use a third party app since no other 3rd party camera app has integration with Photos app, aint got Panorama feature, and I don’t want to screenshot every other photo I’ve taken after just to preserve that details.
i had this too on my lumia 830(same issue, was having nice pictures until the final postprocessing). you will need to tweak the camera on interop tools, im on latest stable build(not insider) and it works no prob on mine, so i guess it should be fine on yours too.
once you get ur lumia rooted,access local machine->software->oem->nokia->camera->barc->isenabled
just set the reg value to 0. this will disable postprocessing after you took your pic, will also save your file faster.
if you want the postprocessing back for some reason, just revert the value to 1.