I've made a stripped down fiddle, and you'll have to interact with the map to see the issue:
JSFiddle Link
You'll notice, or at least I hope you will, that if you make a quick drag, the map seems to flash completely gray for an instant. It does not happen every time, so you may have to quickly drag several times to see this. Furthermore, it seems to happen more frequently at lower zoom levels.
This is after the tiles have been cached, so it's not google maps fetching the tiles that causes this. Furthermore, I've tested the behavior on a standard google maps example and it does not cause this flicker. I think it may have something to do with $scope.$apply() being called from the directive and forcing a repaint, because I notice sometimes that the flicker happens while google is loading the tiles, i.e. the two events happen independently of one another.
While my last resort is to dig into the directive, this seems like a pretty fundamental problem from a UX standpoint, and I suspect that some of you must have run into this issue. Perhaps most importantly, the example at
http://angular-ui.github.io/angular-google-maps/#!/demo does not suffer from this issue, though they have set a minimum zoom level, and so I wonder if this is simply a cheap fix for the issue I'm describing.
Thank you for any help you can offer, I've been tearing my app apart at the seams all day trying to pinpoint what's happening, and any advice would be greatly appreciated.
why does stack overflow require a code-line for a jsfiddle link? seems totally contrary to the point of making a fiddle...
Related
The Codename One tensile scrolling is a lot worse than the native scrolling in IOS. It does not feel right - not anywhere like the IOS "rubberband" effect.
And it is buggy, too. And apparently those bugs don't get priority over the years.
I feel it is high time to fix this - do You agree?
See #2121 Native Scrolling Container
Here is the source, feel free to submit a pull request: http://github.com/codenameone/CodenameOne/
I'm suggesting this because in one of your latest issues it was clear you don't understand the mechanics involved. Explaining why your request doesn't make sense will be the equivalent of showing you the entire source code of Codename One so consider that as an explanation...
The issues you filed in the issue tracker don't help. They are complaints not issues as only some have test cases and in those cases they refer to things that aren't as common e.g.: X scrolling with snap to grid.
About priorities that's simple. We work for the people who pay our salaries: the enterprise account users. None of them complained about the current state of the tensile drag. We have limited time and resources and we have a lot of issues/requirements and priorities. If it bothers you, fix it.
As mentioned on the title, Iv'e just finished making a static website, using - CSS/JQUERY/SLICK/JQUERY/BOOTSTRAP.
And I have no idea what to do or where to start in order to make it responsive, tried google but still feeling confused not sure about where to start...
As for now minimizing the page seems to do nothing but cutting the area been minimized.
Changing the view to phone-view on chrome devtool causing the website to look the same, just extremely small which means you can't really read text or anything without zooming in.
any ideas or guidelines of how to start?... feeling lost which is weird cuz am feeling pretty comfortable with the method mentioned above.
Thanks alot for reading!
Thinking the mobile site after doing the standard one is not a good idea. But you are already at the end of that road and there is no going back now.
Responsiveness mostly works on the CSS side. You cambine media queries to specify which CSS should be used for each screen size, but it also has to do with your content structure. As mentioned in the comments, using rows and columns when designing your site helps doing the mobile site a lot.
I suggest you start reading this if you haven't: http://www.w3schools.com/css/css_rwd_intro.asp
And go through each section under the Responsive Web Design section. It should give you a good introduction to help you get started.
I started using ng-grid, and honestly seems it's not easy to tame that beast. I'm having various problems and this is one of them. I'm using ui-router and before ng-grid I was using my own implementation based on ng-repeat and haven't encountered this, so I'm assuming somehow ng-grid is responsible.
So I have a few tabs and ui-view with a grid underneath. Everytime you switch a tab, controller initiates a request and fetches data for the grid. Very first time when you open the app, everything seems to be fine, but whenever you switch to a different tab, for a few milliseconds it shows ugly, unbound content.
I tried to hide grid with ng-if, ng-hide and ng-show - (data.length <= 0), but that didn't work. I tried to place a few $timeout functions, that didn't help either.
Any ideas how to fix that?
UPD: first time when I posted this question I thought what if I make the grid transparent and then change opacity after it gets the data. So it kinda did the trick.
jQuery.animate({opacity:1})
and then I deleted the question, but soon I realized this is not very good way to solve the problem - not very anguleresque. Question remains open.
UPD: Had to abandon ng-grid and currently looking for something better. ng-grid in its current state is horrible. It's painfully slow, full of strange bugs and pretty much useless. Version 3 if far from being ready, and current version is abandoned. Very, very sad.
Actually after using ng-grid for awhile, I have to admit - it's really, really bad. Anyone who values own time and nerves should stay away from it. In its current state project is completely broken, have tons of bugs and authors won't even accept any tickets. They all working hard on a new version and honestly God knows when they ship it. So, for your own sake DON'T use it! I mean I believe in this product and that team. After all those guys gave us awesome ui-router and amazing angular-ui directives. Check the date, who knows maybe this answer already is obsolte and by the time you run across this post all the problems in ng-grid are already solved. But simple fact still remains - the product was so bad, they even decided to rename it.
For now I switched to ux-angularjs-datagrid. It may not be a complete grid solution and doesn't have a cool name and many features you're gonna have to build yourself, but it's amazingly fast and responsive.
I'm a Ui/Ux designer, and I've been asked to give some advice on the architecture of an iPhone app, the said app implies a section called 'Help and guides' for the users to know how to properly enter their data in the app. While analyzing the app, I was going to recommand that it may be interesting to put that part in the settings, and I was challenged about the reason I would do that. All I could come up with was that it was kind of a habit to put it there. But indeed, why would we put the help in the settings?
While doing some research, it appears that the help and the FAQs are often placed in the settings of the apps, and I was wondering why. Even though it seems obvisous to me that this has evolve into a known pattern to the user, I was wondering if there was a proper justification for this practice. Any ideas or clues?
From my research into this as I am currently designing Android and IOS Apps. The reason to group both these items under the one menu is to keep the screen as clutter less as possible. Due to the screen size of a mobile phone, the need for space is high so removing the buttons by grouping them under the one menu helps greatly.
I would suggest possibly making a Menu button with the options to access help & settings as subheadings personally.
I'm trying to use FluidMoveBehaviour from the Dynamic Layout and Styles presentation at MIX 2010 in combination with MVVM (Caliburn.Micro).
The Master/Detail behavior is what I'm after. It isn't working and I would like to find out what's happening behind the curtains to see why Silverlight is not picking it up.
How can I debug the FluidMoveBehaviour?
Because the FluidMoveBehavior is so encapsulated and because the source code is not available, the only recourse when it is not working as expected is trial and error. Even worse, the feature is conceptually very opaque and the implications of what will happen if you change the settings are not at all clear initially.
Your best hope of getting the master/detail scenario to work (the most complicated one) is to create a very small example, get it working, and gradually reintroduce your code until it is fully integrated.
There are other working examples besides the MIX10 demo. I recommend reading and re-reading Mike Taulty's explanation until the feature is less opaque:
Blend Bits 14: Fluid Movement
Notice how he approaches the problem gradually and with little test programs. That is how to avoid wasting time trying to use a "black box" feature.
Anyway, the promise of "effortless interactivity" might ring rather hollow right about now. It is perhaps a lesson for other behavior developers: how will the clients debug it when it isn't working? The answer: give them the tools, like configurable logging. When it's not working, the silence is unbearable.