From: Dan B. <dbe...@ph...> - 2014-01-07 18:21:24
|
On Tue, 2014-01-07 at 09:43 -0800, Sean Mathews wrote: > the glitch I saw is this. > > var mode = data.objects.mode_occupied.state; > results in undefined this causes the browser to load a bad image. > > > I am testing against my Pi and its not fully configured and I have not > set the current mode. Makes sense, does it load the other buttons/icons for the other modes? > > By moving buttons what i was referring to is this. > I see in the code that it will display the icons from left to right > but it will show the "current' mode icon first so if I am home it will > be on the left if I am at work then work will be first. It just seemed > a little odd. When I get home I will touch this tab and click on > "home" and it should highlight that I am now home. I figure It would > be easier to not change the order of the icons just show one as Active > and then I press the same part of my touch screen every day I come > home and every time I leave. > > > I see these icons as indicators as well as buttons to change the mode > and so I guess I feel that buttons should not move around the screen > as it seems they will with this code > > for (var i = 0;i < count; i++) { > if (modes[i] != mode) { > modestable += '<td align="center"><img > src="images/icons/' + modes[i] + '_mode.png" alt="' + modes[i] + ' > mode" /></td>'; > } > } I see your point in this and think it is very valid. In that case it would be nice to have icons for active and inactive states. This will be an easy change as I just have to remove the script that puts the active state in the first row and then remove the "if (modes[i] != mode) {" so it will just generate all icons in one row. Since it gets these modes from the JSON call to MH the only way that would ever change is if MH changed the way the data was returned. I did it that way too so that if MH ever added modes to "mode_occupied", all we would need to do is add an icon for that mode. > > > I have an older Archos A10 running an old version of a hacked android > 2.2.1 froyo. In firefox it looks fine and it also works with the stock > android browser. I did try this on the mobile version of chrome that I have loaded and it seemed to work on that. My main reason for wanting it to work in firefox is that there is an add-on for it that puts the browser in full screen mode as soon as the page loads. This hides the address bar and the top bar that shows the time and makes it look a bit more like a full screen app than a web page. I posed the question on stackoverflow.com http://stackoverflow.com/questions/20978101/jquery-mobile-html-not-rendering-in-firefox Maybe I will get it figured out with help from others. > > > > A simple button to reach the top "main" menu on every screen would be > a typical design or a back button on every sub page. I agree a timer > could easily be implemented to force the screen back to home after > idle. Several idle detection methods exist for jquery. If you look at some of the changes I pushed up to the git repo between last night and this morning, I removed the power button on the bottom and replaced it with a home button that takes you back to the main menu. I still think I will implement the timer since not everyone will remember to always hit the home button after they are done. > > > Re > Sean M Re Dan B. > > |