Your favorite Apple, iPhone, iPad, iOS, Jailbreak, and Cydia site.
Thread: Widget Weatheris a discussion within the
File Modsforums, a part of the
Originally Posted by Dacal Hi, Twitter request (@BrYcOu), a good idea. I have added a "home" button on forecast pages, for come back with one touch on the current weather...
03-08-2014, 06:25 PM #3081
Widget-Weather App Now Available! Also with MyLocation Support!
Check out the thread here - Widget-Weather
To install the Widget-Weather app, just go to Cydia and install. This will also remove MyLocation, as it is built in!
Want to protect your JailBreak! Add this repo http://cydia.myrepospace.com/iLEXiNFO/ & Install "iLEX R.A.T."
It will allow you to bring your phone back to a fresh jailbroken state!
03-08-2014, 06:35 PM #3082
03-08-2014, 09:51 PM #3083
Enjoying this one a lot, Dacal!!Here to help if I can. If I can't I know someone who can!
03-08-2014, 10:38 PM #3084
Beautiful work, Dacal! Thank you very much!
03-09-2014, 03:16 AM #3085
03-09-2014, 06:09 AM #3086
03-09-2014, 07:33 AM #3087
03-09-2014, 07:46 AM #3088
Me too, but i think its gone now
03-09-2014, 10:27 AM #3089
The Following User Says Thank You to NewdestinyX For This Useful Post:
03-09-2014, 10:47 AM #3090
Look back a page if on appWidgetWeather Thread
03-09-2014, 11:51 AM #3091
03-09-2014, 01:09 PM #3092
03-09-2014, 02:39 PM #3093
I really like both Widget Weather and Forecast (by Ashman) is there a chance that the conflict between the two will ever be resolved? I really want them to coexist on my home screen!
03-09-2014, 03:48 PM #3094
03-09-2014, 03:52 PM #3095
03-09-2014, 04:08 PM #3096
Hope you're enjoying your 2nd time through fatherhood. What a cool thing! I had my first grandchild the same time you had your son. LOVING IT!Here to help if I can. If I can't I know someone who can!
03-09-2014, 11:42 PM #3097
Found something that might be of interest to some of you. It's all about the accuracy of GPS from the amount of digits after in the coordinates. So if this is accurate, Id'e say we need no more than 4 decimal places (realistically 3 is plenty) as anything more requires DGPS devices.
"The tens digit gives a position to about 1,000 kilometers. It gives us useful information about what continent or ocean we are on.
The units digit (one decimal degree) gives a position up to 111 kilometers (60 nautical miles, about 69 miles). It can tell us roughly what large state or country we are in.
The first decimal place is worth up to 11.1 km: it can distinguish the position of one large city from a neighboring large city.
The second decimal place is worth up to 1.1 km: it can separate one village from the next.
The third decimal place is worth up to 110 m: it can identify a large agricultural field or institutional campus.
The fourth decimal place is worth up to 11 m: it can identify a parcel of land. It is comparable to the typical accuracy of an uncorrected GPS unit with no interference.
The fifth decimal place is worth up to 1.1 m: it distinguish trees from each other. Accuracy to this level with commercial GPS units can only be achieved with differential correction.
The sixth decimal place is worth up to 0.11 m: you can use this for laying out structures in detail, for designing landscapes, building roads. It should be more than good enough for tracking movements of glaciers and rivers. This can be achieved by taking painstaking measures with GPS, such as differentially corrected GPS.
The seventh decimal place is worth up to 11 mm: this is good for much surveying and is near the limit of what GPS-based techniques can achieve.
The eighth decimal place is worth up to 1.1 mm: this is good for charting motions of tectonic plates and movements of volcanoes. Permanent, corrected, constantly-running GPS base stations might be able to achieve this level of accuracy.
The ninth decimal place is worth up to 110 microns: we are getting into the range of microscopy. For almost any conceivable application with earth positions, this is overkill and will be more precise than the accuracy of any surveying device.
Ten or more decimal places indicates a computer or calculator was used and that no attention was paid to the fact that the extra decimals are useless. Be careful, because unless you are the one reading these numbers off the device, this can indicate low quality processing!"
I'm not sure how WW determines the accuracy & can't check this atm cause I don't have iPhone, but would like to know:
If we change the "GPS Distance Filter" and "GPS Desired Accuracy" does this effect the amount of decimal places in: "<latitude></latitude>" and "<longitude></longitude>" in our .xml file?
If not then can you make clear for me how this two settings work? (Sorry if it's been explained before) I read post 1 but would like to know how it works under the hood if possible?
I'm also curious why we have the "Neibourhood Location" and "Atmospheric Information" options, would it not make sense to just have this info all the time and have the options in the widgets? I mean we have to code it anyway so be as well having it there all the time as let the user select it in the options.plist no?
With these options, widget creators should specify to the user what settings to choose.
I'm also curious why we have the "Time" & "Temperature" options, again I feel these options should be in each widget, the reason is (now that I'm getting into coding for WW): If the user for some reason has no .xml file we still need to add "ampm" code (for example) in the .js so a clock displayed it. Yes I know this is unlikely but still I add the code just incase,
I'm not complaining by any means, WW is the greatest weather tweak period, I just feel it's options are a bit confusing to the average user, even the "Location Update" settings, they need better explanations placed in the app itself, maybe in future updates you could take this into consideration?
Again, not complaining, just trying to help, keep up the great work guys.
Last edited by Ian Nicoll; 03-09-2014 at 11:59 PM.
"If it's not broken, I'll fix it till it is"
The Following 10 Users Say Thank You to Ian Nicoll For This Useful Post:
03-10-2014, 06:27 AM #3098
Good observations! I too had to dig a little to find clearer descriptions of some of the settings in WW - but got my answers and it all makes sense to me now.
Distance Filter - is the amount of meters you must travel before WW will look and see if there's a new location you've traveled to and then update the XML. 50 meters (default) is plenty tight to leave this one in my experience.
Accuracy Filter - is the size of the "circle", if you will, that WW looks within to determine your location (amount of lat/long decimal places, as you were explaining). Larger numbers here (at bottom of list) will get you the nearest "larger city" but could never get you the address of a house let's say.. Where the Nearest 10 meters, Best (5 meters) and Best for Navigation (1 meter) settings "close the circle around your vehicle" more and more, so as to be able to get the exact address of your location if your widget uses a reverse geocode API service (like Google) that has street address functionality.
As to your other main observations:
1) Temperature type and Time type are in the widget for basically the same rationale you pointed out yourself for leaving the atmosphere and neighborhood switches just "built into" WW. A given user like myself will only ever need Fahrenheit and AM/PM in my country. Why would I want to set those items in a config.JS for every widget I own? Set it in WW and forget it. Then every widget I use, that uses WW, will be set correctly for my country for Time/Temp. Heck I'd like to see more universal switches in WW.. Like for Barometric pressure unit and mpg versus kph.
2) I agree with you that we don't need the atmosphere and neighborhood switches in the widget. They could just be built in and always on. It's not like the XML is getting glutted with data that would slow down our phones. We could do without the switches.
Thanks for the education on the decimal places in latitude longitude coordinates. Very helpful!
Last edited by NewdestinyX; 03-10-2014 at 12:26 PM.Here to help if I can. If I can't I know someone who can!
03-10-2014, 07:30 AM #3099
Thanks for your clear answer, but maybe I wasn't clear, I was asking how it's coded (it's what I meant by "under the hood").
I'm confused because how can I have a "Desired Accuracy" of 3 Kilometers with a distance filter of 1M, it doesn't add up!
So I was wondering if its coded with a maximum accuracy all the time (say 5 decimal points for 1.1M accuracy), then the distance filter must continually calculate our every movement (especially if set on constant) so how is it possible with this to also set a desired accuracy of 3Km? It's confusing as hell and I was just suggesting some clearer way thats easier to understand.
Even the default setting: how can it truly be a desired accuracy of 100M then we say update the coordinates every 50M?? (distance filter). Understand the confusion?
I'm sure there is method behind the madness here, it's just me with too much time on my hands waiting to go to airport, I'm sure KOH or Durben will clear it up.
Your point about temperature & time is good.
Glad you agree with the atmosphere & neighbourhood point, I'm guessing everybody has them both enabled all the time (but I'm sure someone will reply to this saying they don't )
Last edited by Ian Nicoll; 03-10-2014 at 07:52 AM.
"If it's not broken, I'll fix it till it is"
The Following User Says Thank You to Ian Nicoll For This Useful Post:
03-10-2014, 09:05 AM #3100