1. NewD's Avatar
    It's not an easy convert. It's almost a complete rewrite. Just look at uniaw 6.2 vs 6.3 (accuweather)
    Yeah. I was afraid of that. And I have that Mac Software called 'Diverge'.. which lets me compare files. I think Dacal posted the main code changes about 4 pages ago.. It looked like the WHOLE location.js file was different (that's an easy swap out) and the 'main' bottom portion of the UniAW.js (or main.js) - that he also posted. But when I just replaced those portions on the UniAW6.21_LS it broke the widget. My guess is that there are differences in the Config.js too that Dacal didn't post. I'm okay if it's a 'complete rewrite' - i just need to know what 'stays and goes' in the 'older code'. If the Accuweather calls are deeply intertwined into all aspects of the widget running then we leave it only to the pros. But Dacal's post with the Accuweather location.js and portion of UniAW8.js redone looked pretty user friendly to me.
    2013-05-30 01:07 AM
  2. Dacal's Avatar
    I have this request in to Dacal as well. I want to convert all my favorite widgets to Accuweather. But I fear it may be pretty complex - like when many of us were wanting to convert Native Weather or Woeid-only widgets to GPS. It just wasn't "that easy". I'm getting better with code now so I'm hoping the learning curve isn't too steep!

    Ah! So that's how they do it! I wasn't too far off. So mostly sunny = fair; partly sunny = partly cloudy.. Makes sense..

    Thanks Dacal!
    Like MJ said, not so easy. Not very hard now the code is done, but need to adjust some minor things. And there is so much widgets now, with different codes, there will be never an only way to adjust all.

    Not the time tonight, i will try to explain a step by step conversion in the next days.

    Yeah. I was afraid of that. And I have that Mac Software called 'Diverge'.. which lets me compare files. I think Dacal posted the main code changes about 4 pages ago.. It looked like the WHOLE location.js file was different (that's an easy swap out) and the 'main' bottom portion of the UniAW.js (or main.js) - that he also posted. But when I just replaced those portions on the UniAW6.21_LS it broke the widget. My guess is that there are differences in the Config.js too that Dacal didn't post. I'm okay if it's a 'complete rewrite' - i just need to know what 'stays and goes' in the 'older code'. If the Accuweather calls are deeply intertwined into all aspects of the widget running then we leave it only to the pros. But Dacal's post with the Accuweather location.js and portion of UniAW8.js redone looked pretty user friendly to me.
    It doesn't work because i have add a lot more things than accuweather in 6.3, like all the cookie stuff. To have an universal thing, need to remove all of that and just keep the necessary. But your right, the main important thing is the location.js and the fetchweather function.
    Last edited by Dacal; 2013-05-30 at 01:17 AM.


    My themes : Jade HD, Silex HD, BaSalt HD,ToPaz
    All are on Cydia and/or Theme It.
    2013-05-30 01:12 AM
  3. King_O_Hill's Avatar
    This is not the case with my early tests with Accuweather. So glad to be done with Yahoo forever.
    You better get your stuff converted now bro. There is a new method that uses neither and it is getting closer everyday. I really don't foresee maintaining 3 sources of data and 3 methods to obtain that data in parallel. It's just too much to keep track of and too much to troubleshoot for everyone.

    Check out WW3 for iOS 9/10 - Widget-Weather 3.0
    2013-05-30 01:29 AM
  4. siemprelisto's Avatar
    Ian, Dacal, et al.

    Here is a side by side comparison of AccuWeather and Yahoo Weather for Houston, Texas. Memorial is a neighborhood in Houston. Shots made within 20 seconds of one another

    I'm just providing these so Ian and Dacal can see how they both report and differ for a large city in the US... information only. If and When King has his in Beta I can do a 3 sided comparison if you want.



    AccuWeather....................................... .......YahooWeather

    Temperatures at time of Native; AccuWeather 81 and YahooWeather 82
    Attached Thumbnails UniAW6.0 for iph4 & iph5-accuweather1.png   UniAW6.0 for iph4 & iph5-yahooweather1.png   UniAW6.0 for iph4 & iph5-nativeweather.png  
    Last edited by siemprelisto; 2013-05-30 at 02:43 AM.
    2013-05-30 02:01 AM
  5. Simon's Avatar
    Loving the new reload button. Make changes on the fly and simply reload instead of having to respring everytime.
    2013-05-30 02:20 AM
  6. NewD's Avatar
    Like MJ said, not so easy. Not very hard now the code is done, but need to adjust some minor things. And there is so much widgets now, with different codes, there will be never an only way to adjust all.

    Not the time tonight, i will try to explain a step by step conversion in the next days.
    --------
    It doesn't work because i have add a lot more things than accuweather in 6.3, like all the cookie stuff. To have an universal thing, need to remove all of that and just keep the necessary. But your right, the main important thing is the location.js and the fetchweather function.
    Thanks, Dacal. No rush at all. You can even PM me if you don't want to field endless questions about the conversions. If you teach me then I can do some of the converting for you for people requesting conversions..
    2013-05-30 02:21 AM
  7. The.Drifter's Avatar
    Question to the thread concerning iWidget version.

    I'm starting to run into a issue concerning the iWidgets widget.plist boundary.

    The widget.plist boundary helps to define the iWidgets display and touch areas on your springboard.

    Thanks to Durben, we can "display" things outside of the widget.plist boundaries.

    That became helpful because we could then code iwidgets to display out of the widget.plist boundaries and still be able to touch your springboard icons.

    The issue now is the touch area which is also defined within the widget.plists boundaries.

    If I set the widget.plist boundary to cover the screen height, you wouldn't be able to touch your icons within that defined boundary space. Even if there was no weather wall and you could see your icons.

    Currently for a iwidget touch forecast, I have to lower the widget.plists height value low enough for you to touch the actual forecast, but not too low as to make the last few rows of visible icons untouchable.

    Now that Dacal has implemented a "Magic Daisy/Balloon" pop up menu, I would need to lower the widget.plists height value even further down the screen to be able to "touch" all the menu options.

    If I do that, you will not be able to touch your icons in the last few rows when the pop up menu disappears.

    I cannot dynamically adjust the widget.plist values, so I have to either set it to where you can tap your icons below the Main UniAW main display, or set it low enough for you to be able to use all the menu pop up options rendering your icons untouchable.

    You can see the dilemma now.

    So my question to the thread is how would you like to use your iWidget version of UniAW, do you:

    1) use it on the first page without icons so you can enjoy all the timed backgrounds, weather walls, Slideshow and magic popup menu and not worry about touching icons.

    2) use it on any page using just the main display without weather walls and place icons below that are touchable.

    With the first option, that would be the easiest to code because I could just cover the whole screen area with a touchable area and place the magic button anywhere and allow for a whole page worth of popup menu options.

    With the second option, setting the widget.plist boundary to just the bottom of the 5 day forecast and allowing for touchable icons on the last few rows of icon, would render the pop up menu to only be touchable half way down the screen. So I would have to edit the number of pop up menu options to only fill the space on the screen where the forecast touch line ends if you want to touch icons when the menu disappears.

    I wish it was as easy as saying adjust the widget.plist height value to how your gonna use it, but with the advent of the pop up menu, changing the values too small to allow touching of icons would render half of the pop up menu options untouchable.

    Options I thought of.

    1). No popup menu, just a refresh button and all selectable configs would be handled through the iWidgets options menu on first launch.

    2) Reduce the number of popup menu options to only fill the area used by the main display with forecast showing. ( about 1/2 the screen)

    3) Make 2 iWidget versions, one for full screen SB use with all the features of the LS version including full screen pop up menu options, and another for basic use without weather walls, and pop up menus to allow for touching icons below the display area.

    So I guess I need some direction in how you all would like to use your iWidget version.

    Any thoughts, ideas or suggestions are greatly appreciated, I'm converting the iWidget versions for YOU, and your input matters in how I'm gonna proceed
    Last edited by The.Drifter; 2013-05-30 at 02:48 AM.
    2013-05-30 02:22 AM
  8. Darrenrooster's Avatar
    In the Javascript/Main folder, replace (or just rename it) the touchmove.js file with the one attached to this post.
    Hi Ian,
    Thanks for this.
    I replaced this file which works but found when I unlocked and then locked again, the slide show remained but got the animations?
    I have downloaded your very latest version.
    2013-05-30 02:25 AM
  9. Marty McFly's Avatar
    Hi all,

    I like to have neighbourhood AND city displayed on my LS. Dacal once again comes through with some amazing instructions for Accuweather that I thought I would share. Works like a charm! Dacal, thank you once again.

    ---------------------------------------------------------

    At beginning of the location.js :

    var neighborhood;

    And below :

    $.getJSON(url, function(data) {
    found = data.query.count; // Check if coordinates return a valid location.
    if ( found == 1) {
    var woeid = data.query.results.Result.woeid;
    city = data.query.results.Result.city;
    neighborhood = data.query.results.Result.neighborhood;


    Now, need to add a #neighborhood section in CSS and in uniaw6.js, dealwithweather function, something like that :

    if ($.cookie('jsonCookie').neighborhood != null) { document.getElementById("neighborhood").innerHTML= $.cookie('jsonCookie').neighborhood ; }

    And at the end of the file, in fetchweatherdata :

    if (gps == false) {
    obj.city = $(data).find('location').attr('city');
    obj.coordinates = "[ZIP : "+zip+"]";
    } else {
    obj.city = city;
    obj.neighborhood = neighborhood ;
    obj.coordinates = "["+ $.cookie('locationCookie').textLat + " " + $.cookie('locationCookie').textLong + "]";
    }
    Last edited by Marty McFly; 2013-05-31 at 12:10 AM.
    2013-05-30 02:25 AM
  10. King_O_Hill's Avatar
    Ian, Dacal, et al.

    Here is a side by side comparison of AccuWeather and Yahoo Weather for Houston, Texas. Memorial is a neighborhood in Houston. Shots made within 20 seconds of one another

    I'm just providing these so Ian and Dacal can see how they both report and differ for a large city in the US... information only. If and When King has his in Beta I can do a 3 sided comparison if you want.
    Just send us a pic of your stock weather app too. It will be the same data.

    Check out WW3 for iOS 9/10 - Widget-Weather 3.0
    2013-05-30 02:26 AM
  11. NewD's Avatar
    You better get your stuff converted now bro. There is a new method that uses neither and it is getting closer everyday. I really don't foresee maintaining 3 sources of data and 3 methods to obtain that data in parallel. It's just too much to keep track of and too much to troubleshoot for everyone.
    I will be the first to stand up and applaud you and Derrick, Brian, when I see Native W auto-updating as well as MyLocation app did and when I see it reporting my small town's weather the same as Accuweather's accuracy. I suppose I can just look at Native weather on my phone now to compare that. If Native Weather pulls from Yahoo I will not be saluting and will be almost as big a pain in the azz as when I first came here trying to talk modders out of using the new Native method.. Consider yourself warned! ...
    2013-05-30 02:26 AM
  12. <Ian Nicoll/>'s Avatar
    Question to the thread concerning iWidget version.

    I'm starting to run into a issue concerning the iWidgets widget.plist boundary.

    The widget.plist boundary helps to define the iWidgets display and touch areas on your springboard.

    Thanks to Durben, we can "display" things outside of the widget.plist boundaries.

    That became helpful because we could then code iwidgets to display out of the widget.plist boundaries and still be able to touch your springboard icons.

    The issue now is the touch area which is also defined within the widget.plists boundaries.

    If I set the widget.plist boundary to cover the screen height, you wouldn't be able to touch your icons within that defined boundary space. Even if there was no weather wall and you could see your icons.

    Currently for a iwidget touch forecast, I have to lower the widget.plists height value low enough for you to touch the actual forecast, but not too low as to make the last few rows of visible icons untouchable.

    Now that Dacal has implemented a "Magic Daisy/Balloon" pop up menu, I would need to lower the widget.plists height value even further down the screen to be able to "touch" all the menu options.

    If I do that, you will not be able to touch your icons in the last few rows when the pop up menu disappears.

    I cannot dynamically adjust the widget.plist values, so I have to either set it to where you can tap your icons below the Main UniAW main display, or set it low enough for you to be able to use all the menu pop up options rendering your icons untouchable.

    You can see the dilemma now.

    So my question to the thread is how would you like to use your iWidget version of UniAW, do you:

    1) use it on the first page without icons so you can enjoy all the timed backgrounds, weather walls, Slideshow and magic popup menu and not worry about touching icons.

    2) use it on any page using just the main display without weather walls and place icons below that are touchable.

    With the first option, that would be the easiest to code because I could just cover the whole screen area with a touchable area and place the magic button anywhere and allow for a whole page worth of popup menu options.

    With the second option, setting the widget.plist boundary to just the bottom of the 5 day forecast and allowing for touchable icons on the last few rows of icon, would render the pop up menu to only be touchable half way down the screen. So I would have to edit the number of pop up menu options to only fill the space on the screen where the forecast touch line ends if you want to touch icons when the menu disappears.

    I wish it was as easy as saying adjust the widget.plist height value to how your gonna use it, but with the advent of the pop up menu, changing the values too small to allow touching of icons would render half of the pop up menu options untouchable.

    Options I thought of.

    1). No popup menu, just a refresh button and all selectable configs would be handled through the iWidgets options menu on first launch.

    2) Reduce the number of popup menu options to only fill the area used by the main display with forecast showing. ( about 1/2 the screen)

    3) Make 2 iWidget versions, one for full screen SB use with all the features of the LS version including full screen pop up menu options, and another for basic use without weather walls, and pop up menus to allow for touching icons below the display area.

    So I guess I need some direction in how you all would like to use your iWidget version.

    Any thoughts, ideas or suggestions are greatly appreciated, I'm making this for YOU, and your input matters in how I'm gonna proceed with any iWidget versions
    I know your situation M8, but I think we have enough resources here to redo the touch menu, we could make it a lot smaller (in height) and just scroll through the options.

    I am already late for work so got to fly but I think iWidget needs scroll, plus this will come in handy later for adding new options.
    2013-05-30 02:37 AM
  13. NewD's Avatar
    Weather reporting service wars aside - I just have to say how much I am loving 6.3's design Ian & Dacal!!!!! The options daisy is - wow! The whole concept / no respring.. I'm blown away!! The Timed Walls or personal slideshow potential. Of course the amazing UniAW consolidated Ian/Dacal animations styles. Ooo! I too am getting muscle pain in my upper body that my chiropractor told me today is partly from me staring at my phone all day!!!!

    2013-05-30 02:40 AM
  14. siemprelisto's Avatar
    Just send us a pic of your stock weather app too. It will be the same data.
    Done... added Stock/Native weather app to above post.
    2013-05-30 02:44 AM
  15. MamaJaay's Avatar
    FUUUUUUUUUUUUUUUUUUUKKKKCCCC

    I am now the newest victim



    2013-05-30 03:41 AM
  16. <Ian Nicoll/>'s Avatar
    Sorry, I messed up the 6.21 iWidget in post 1, fixed now.
    2013-05-30 03:41 AM
  17. NewD's Avatar
    FUUUUUUUUUUUUUUUUUUUKKKKCCCC

    I am now the newest victim
    From what pray tell???? What could possibly kill this jailbreak, girl??! So sorry! ILex RAT had a rescue from disaster mode in it - didn't you have that installed? Damn.. so sorry, MJ..
    2013-05-30 03:44 AM
  18. VOLTAGExDT's Avatar
    hey what is ilex rat? gonna google...

    Question to the thread concerning iWidget version.

    I'm starting to run into a issue concerning the iWidgets widget.plist boundary.

    The widget.plist boundary helps to define the iWidgets display and touch areas on your springboard.

    Thanks to Durben, we can "display" things outside of the widget.plist boundaries.

    That became helpful because we could then code iwidgets to display out of the widget.plist boundaries and still be able to touch your springboard icons.

    The issue now is the touch area which is also defined within the widget.plists boundaries.

    If I set the widget.plist boundary to cover the screen height, you wouldn't be able to touch your icons within that defined boundary space. Even if there was no weather wall and you could see your icons.

    Currently for a iwidget touch forecast, I have to lower the widget.plists height value low enough for you to touch the actual forecast, but not too low as to make the last few rows of visible icons untouchable.

    Now that Dacal has implemented a "Magic Daisy/Balloon" pop up menu, I would need to lower the widget.plists height value even further down the screen to be able to "touch" all the menu options.

    If I do that, you will not be able to touch your icons in the last few rows when the pop up menu disappears.

    I cannot dynamically adjust the widget.plist values, so I have to either set it to where you can tap your icons below the Main UniAW main display, or set it low enough for you to be able to use all the menu pop up options rendering your icons untouchable.

    You can see the dilemma now.

    So my question to the thread is how would you like to use your iWidget version of UniAW, do you:

    1) use it on the first page without icons so you can enjoy all the timed backgrounds, weather walls, Slideshow and magic popup menu and not worry about touching icons.

    2) use it on any page using just the main display without weather walls and place icons below that are touchable.

    With the first option, that would be the easiest to code because I could just cover the whole screen area with a touchable area and place the magic button anywhere and allow for a whole page worth of popup menu options.

    With the second option, setting the widget.plist boundary to just the bottom of the 5 day forecast and allowing for touchable icons on the last few rows of icon, would render the pop up menu to only be touchable half way down the screen. So I would have to edit the number of pop up menu options to only fill the space on the screen where the forecast touch line ends if you want to touch icons when the menu disappears.

    I wish it was as easy as saying adjust the widget.plist height value to how your gonna use it, but with the advent of the pop up menu, changing the values too small to allow touching of icons would render half of the pop up menu options untouchable.

    Options I thought of.

    1). No popup menu, just a refresh button and all selectable configs would be handled through the iWidgets options menu on first launch.

    2) Reduce the number of popup menu options to only fill the area used by the main display with forecast showing. ( about 1/2 the screen)

    3) Make 2 iWidget versions, one for full screen SB use with all the features of the LS version including full screen pop up menu options, and another for basic use without weather walls, and pop up menus to allow for touching icons below the display area.

    So I guess I need some direction in how you all would like to use your iWidget version.

    Any thoughts, ideas or suggestions are greatly appreciated, I'm converting the iWidget versions for YOU, and your input matters in how I'm gonna proceed
    drifter...now finally I can help.. well idea wise.. the pop up is nice.. but can you not do such a thing as this..

    UniAW6.0 for iph4 &amp; iph5-unisbs.png

    yes I know ugly... but with html tables, you could do an image menu of sorts.. hell call it UNISettings. like sbs..

    if I were coding this, the daisy or whatever would call a menu file.
    Last edited by VOLTAGExDT; 2013-05-30 at 04:04 AM.
    2013-05-30 03:58 AM
  19. MamaJaay's Avatar
    Nothing new installed today..

    at approximately 7pm EST my phone decided that it would no longer pick up cell service. Only wifi. And what good is a phone if you can't make calls....

    Reboot, reset all, reset network, hard reset, ilex rat, nothing.

    Restore only option. Cell service back up and running.

    On the plus side, I'm sure my battery will last longer... Not from the lack of tweaks, but from checking the threads a lot less often...
    2013-05-30 04:09 AM
  20. bliken's Avatar
    That Stinks.....

    Nothing new installed today..

    at approximately 7pm EST my phone decided that it would no longer pick up cell service. Only wifi. And what good is a phone if you can't make calls....

    Reboot, reset all, reset network, hard reset, ilex rat, nothing.

    Restore only option. Cell service back up and running.

    On the plus side, I'm sure my battery will last longer... Not from the lack of tweaks, but from checking the threads a lot less often...
    2013-05-30 04:15 AM
LINK TO POST COPIED TO CLIPBOARD