You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Two is a single window application. Once #1 is accomplished we can decide if we want to have multiples or stick to the single window route.
I am tempted to say tabbed is the way to go if we want to allow testing of more than one site at a time, but I also like the simplicity and focus of restricting the app to one site at a time.
The text was updated successfully, but these errors were encountered:
I also like the idea of focusing on just one site at a time, but I could see it being a bit of a problem if you need to take a quick glance at something on a different page or being able to compare different sites to look at them side-by-side. Personally, I would think that have the option to at least have new windows would be helpful.
I'm curious how does memory management fair with some of the higher end sites in this format? Would that be a factor when working with multiple tabs? I'm asking more because I don't know anything about memory management and it seems to me like you're essentially just loading the same site twice in the same window.
Yes, that is exactly what I am thinking, and although ARC is pretty smart, it isn't prescient. My main concern with all of this is taking to much of a chunk of memory when running it. Going to have to do a lot of testing.
Currently Two is a single window application. Once #1 is accomplished we can decide if we want to have multiples or stick to the single window route.
I am tempted to say tabbed is the way to go if we want to allow testing of more than one site at a time, but I also like the simplicity and focus of restricting the app to one site at a time.
The text was updated successfully, but these errors were encountered: