-
So, I was requesting the other day, whether I could do some tests in here... I'm afraid it's not ready for testing yet, though.
Here's what I'm, hmm, trying to do...
See the Google+ or Facebook apps on mobile? They both have (and aren't the only ones) the 'navigation drawer' feature, which is something Google standardized for Android apps, where you swipe the screen to show a sidebar, and swipe it again to hide it.
Thing is, this is something that makes sense on mobile, and it reminded me that the original sidebar for Wedge was very similar to that... If you'll remember, if you didn't have enough room on the screen, it moved your sidebar to the extreme left, only showing a small portion of it, and when hovering that portion, it would bring it into view (position: absolute), with a nice animation and all.
Honestly, I can't for the life of me remember why I gave up on it, but here we are.
The main advantage of the current responsive sidebar, is that you can easily see its contents by just scrolling your mouse wheel, so it doesn't require much action on your part; that is its advantage, and really, its only one...
I've been doing LOTS of tests trying to get it right, started with a few lines of CSS, then added a few lines of JS, then expanded it even more, added more goodies, etc, the usual stuff, and now my current code is, like, 200 gzipped bytes added to the script file... Hmm. It's a lot to me, but I know I shouldn't be too worried about this kind of increase, especially since we still have 7.5KB for the entire script file, and it can easily go up to 10KB without me getting too worried, so... Whatever.
Here's what it's been doing until today... Hovering the left portion of the screen (about 30px wide) would bring the sidebar into view, position: fixed, with a scrollbar if too long, and a subtle but nice animation effect (basically, on mobile you get the bare animation, but on desktop you also get a parallax scroll effect on the whole page, which is nice really.)
There are two points where I'm currently stuck.
1/ The convenience. Of course, none of the sidebar information is vital, but still... it's a bit annoying, having to hover something so far on the left... Would like opinions on whether this is important, or not...
2/ The main menu. Up until today, I didn't touch it, but then I suddenly decided that it would be nice, at least on mobile, to automatically move the main menu to the sidebar. I got it working, but it's really hard.
(a) All items are developed, as intended, but I realized that as an admin, I have way too many entries, and it forces me to scroll wayyyy down just to be able to view the actual sidebar content...
(b) It's probably best to collapse them, then, but it suddenly implies an extra tap for mobile users. Swipe left to open sidebar, tap the menu item you want, then tap the option you want. The only advantage, I guess, is that since we're in the sidebar, I can easily control the menu item sizes, and thus you'll never have to zoom in to ensure you're tapping the right item, I guess... Opinions..?
(c) It also occurred to me that I could open *two* sidebars, eh... For instance, have the sidebar show up on the left, but at the same time, have the main menu unfold in a new sidebar on the right. This implies, however, that the sidebar can never fill more than half (or 60%) of the screen, otherwise you can only have one, or the other. I like the idea, though...
(d) Any .note classes will be hidden from view, obviously, if the menu is hidden by default... I mean, you won't get to see the number of admin errors, or PM number, or unseen media number. I could shove these up somewhere in the visible UI, but it doesn't make a lot of sense, or it might be more work than deserved, I don't know...
Okay, I'll end this long post here, given how my previous long post asking for feedback scared the hell out of everyone, I suppose it's for the best, eheh... :P
I'll post screenshots once I'm satisfied with the layout, but it certainly won't be today, and perhaps not tomorrow either, that's how much I'm NOT happy with it, but you know how much of a perfectionist I can be, so...
PS: in case you missed these, there are two uncommitted features that made their way into wedge.org last week: (1) infinite scroll now works on mobile, (2) previewing a notification will now mark it as read automatically, yay.
-
So I find myself surfing around more on my phone of late. In portrait mode I'd have to scroll all the way to the bottom to see the sidebar anyway so I'd be fine with it hidden to the left and shown on tap or swipe.
As for the menu in the sidebar, I'd probably have to see a screenie or see it in use case to form a real opinion there. For now I cant say I like it, not because of the extra taps or swipes but simply the menu seems fine as it is now to me.
The idea of 2 sidebars is also something I'd probably have to see or use to get a feel for it and then give some real feedback. My current take on it is it will make an already small screen even smaller. On second thought I'm assuming the double sidebar would only be visible when interacting with the menu so it probably wouldnt matter as far as screen size goes.
-
I finally decided against doing the sidebar menu on non-mobile devices, I added the rules to the screen density media query, rather than the screen width media query. The latter applies to any device with a small screen, including a resized desktop browser window, while the former only applies to devices with a screen that has more pixels than visible, i.e. not a regular monitor. (Mac & iPads have a high density, too, but I can't test these...)
-
What do you want me to test? (iPad 3 here)
-
Well, I guess you'll get to see it when I upload at some point...
Basically, ensuring that the menu stays in the header, and isn't moved to the sidebar.
-
I'm still not satisfied with the friggin' sidebar...
I fixed most of my problems, but for performance reasons, I decided to give up the parallax scrolling thing, and it suddenly makes the whole thing very dull, hmmm....
It's still better, on mobile, than whatever is currently available in Wedge, but when it comes to desktop, it's really no good. If I tried to implement some kind of trick to make it as easy to open the sidebar (i.e. an emulated swipe with the right button clicked, or something), I might interfere with mouse gestures, which isn't good...
I'll probably upload *everything* I have in store for now, i.e. all the notification stuff and this sidebar, for a couple of days, so you guys can tell me whether you like them or not, although I might go ahead and commit the notification stuff, already.
-
Fixed sidebar to actually show up... (I was focusing on my notification work, sorry.)
So, guys..? What do you think..?
It's not as sexy as I'd have liked to upload, but at least it should be okay, performance wise.
I don't know how to "point out" the sidebar to people when it's hidden, though... I added a diamond shape as a made-up arrow, but it needs some love, because it's only correctly positioned in Chrome, ah ah... (And only Desktop...)
-
me likey!
-
Okay, good to know!
Anyone else..?
-
Why not add a physical button as well instead of solely relying on a swipe gesture (I'm thinking jQuery mobile's panels here, they can help you with this)? Otherwise the menu's font is too big but the idea is pretty cool!
-
Why not add a physical button as well instead of solely relying on a swipe gesture (I'm thinking jQuery mobile's panels here, they can help you with this)?
Otherwise the menu's font is too big but the idea is pretty cool!
I take it you tested on iOS, right..?
Also, the iOS version is WAY too eager to open the panel, as a very, very small swipe (even an accidental slow swipe) triggers it, while on my S3, you have to do a conscious swipe, hmm... This, I guess, also needs a quick fix...
Oh, and I finally found a nice way to make it work on desktops...! I can't believe it!
- The problem was that the drop zone for the mouse was too small (about 30 pixels wide, 100% height), and I couldn't decide between a 100ms or 200ms delay before triggering the popup.
- All of this means, you need to make a proper effort to take your mouse to the extreme left of the window (which, at this point, is almost guaranteed NOT to be stuck to the left side of the screen, meaning you need to correctly position it), and then wait for a tenth of a second, then move the mouse... Really, really painful, compared to moving the wheel to the bottom of the page, and then reading there...
Then I thought... Wheel..? Mouse wheel....? Can't I hook something into that..?!
And it occurred to me, clear as ever: even though I never did it, I can certainly hook into the friggin' wheel *button*...!
So, I did JUST THAT. I added a mousedown event, and if e.which is 2, trigger the panel, to open it or close it.
You can try it now... :)
What do you think..? Is it good material, or is there any good reason why I shouldn't cancel the usual wheel button, which in 99% of all cases would simply trigger a mode that allows you to scroll the window with a mouse move, something I'm pretty sure most people would never do consciously, thus meaning a waste of time, having to re-click the button to untrigger this mode..?
Posted: June 29th, 2013, 04:06 PM
Note I also ensured that a middle-click on a link wouldn't trigger the panel, because usually you'd do that to open the link in a new tab, of course...
-
I like it ad well
Just want to point out on windows phone 8 IE 10, while viewing a topic if I try to access the sidebar it does not stay in view it slides away on its own. If I'm viewing the homepage wedge.org The sidebar slides out and stays out until i decided to swipe it away.
-
Swipe manual:
- Swipe from left to right
- Opens sidebar
- Swipe from right to left
- Closes sidebar
- Swipe in any other direction
- Does nothing, except the default (scrolls sidebar or screen)
- Swipe in any other direction
- Does nothing, except the default (scrolls screen)
There are limitations, though... Scrolling the sidebar will work, and when you reach the end, it'll start scrolling the rest of the screen, instead. It's the default behavior, and also occurs in select boxes, for instance. I tried to 'block' that, but it didn't work, and to ensure it'd work, I'd probably have to add more code, which I'm reluctant to do at this point, as it's already heavy enough, and melikes short code better, as it's easier to maintain, of course...
-
Actually clearing the cache fixed it, should have thought of that sooner. Works as intended everywhere. Nice job.
-
Well, the icon is not obvious enough (but I think we already knew that), the swipe works nicely on iPad but the text is a bit big on iPad 3.
Interesting direction, I like it... though I thought you were going to keep the menu in the top of the page rather than the sidebar?
-
Ah, it's too big on iPad 3 too..? Then it means I have to change my media query, indeed...
And the menu position is tied to the screen resolution, too (CSS resolution, i.e. pixel density), so I'm not surprised the menu disappears on a Retina screen, of course...
I guess I'll have to do some new media query that checks for a resolution below 500px, or something...! It should catch pretty much all of the mobile devices while leaving tablets in peace, right..? :-/
As for the middle button click, I'm guessing no one is bothered by it, since I got no complaints..?
-
As for the middle button click, I'm guessing no one is bothered by it, since I got no complaints..?
-
Yeah, text is huge in iPad 3, I can always upload a screenshot?
As for middle clicking, that's something I *never* do unless I have to for the simple reason that middle clicking on a mouse where the middle click *is* the scrollwheel is just not going to happen.
-
I use it to open links in new tabs all the time. So much easier than Ctrl+Click...
-
On iPhone 5 is unusable (triggers unexpectedly and text is enormous)..
-
Better now..?
Posted: June 30th, 2013, 03:53 PM
I use it to open links in new tabs all the time. So much easier than Ctrl+Click...
-
Yep :)
I wonder though if that position can be "uncomfortable" on iOS 7, given that a swipe from left to right (on left side) would open the left tab (if multiple tabs are open).
-
I don't know anything about iOS 7...
All I know is that Chrome has this, but for the swipe to be taken into account, you'd have to start it on the edge of the page, while Wedge takes any swipe into account, and for what it's worth, my iOS 5 tests were satisfying, although I'm still not happy with the jerkiness of the animation, hmm...
-
iOS 7 is very pretty, has some Android and Palm OS influence and is rather buggy right now... and yes, the swiping in the general UI starts from the left side too...
-
Even when not at the edge..?
Great... Means they're gonna break a lot of web apps... ::)
Oh well, I suppose I could change it to a right-to-left swipe. If it doesn't also take over this..???!!!
-
Right to left would switch to right tab :P
-
What about a single tap?
-
Single tap would be crazy, eh... ;)
Okay, so I read a bit about iOS 7, and from what I gathered, they simply copied Chrome's behavior for Safari, i.e. you have to swipe from a side, it won't trigger if you swipe from the middle, for instance. So, it should be okay... Just as I thought -- they wouldn't dare break thousands of websites that implemented code specifically to work on their OS...!
Also, I rewrote (again) my code tonight, and ended up getting a faster animation on Android, but it's extremely broken (apart from the sidebar font size finally being fine), and the animation doesn't work on iOS (at least older versions), will fix later.. Also, the opening/closing triggers stop working after the first time, so you'll have to reload your page. I'll fix all of these, tomorrow... For now, bed time is upon me. Ah, well... Maybe if I manage to steal a few extra minutes, eheh...
Posted: June 30th, 2013, 11:17 PM
Okay, fixed the triggers to happen all the time, fixed font color, didn't fix the stuff in iOS though, I couldn't care less... :niark:
What do you think of this new animation..? It could be seen as bothersome if you're currently writing a post or something and then accidentally triggering the thing, but it's no biggie.
-
What do you think of this new animation..?
-
I see it was worth the effort... :lol:
I spent another 24 hours on this, even unearthed bugs by Chrome that I tried hard to fix (such as hardware-accelerated fixed-position items being treated as absolute-positioned), but it's definitely not worth the hassle.
See. Only Pete's new features seem to create any kind of excitement in users here. Whenever I have something new to show, I have to wait until Pete says it's "nice" for everyone else to agree with him. Whenever he's on project leave, everyone decides that they'll take their leave too...
I see that not many people share my quest for perfection.
In the meantime, projects like 'Ghost', with 10 times less innovative features than Wedge, raise £200.000 (!!) on Kickstarter and get talked about in magazines. Me? All I'm asking for is feedback (negative or positive, whatever) when I post about a feature idea.
Oh, well...
I'll just call it quits, then, and always settle for the shittiest possible solutions that require the less support time to me. Perhaps one day, someone will find my shit 'revolutionary'. I'll be long gone to another project, though... Perhaps "Slice", a fork of "Wedge" geared towards making blogs. (Yeah, it'll be exactly the same, but apparently, posts + replies aren't as exciting as blog posts + comments, even though they're the same thing...)
-
That's one of the curses of changing something that isn't directly a 'feature'. I add stuff that is very blatantly, even transparently obviously, 'new features', it's stuff people can see themselves using, it's stuff that people can directly relate to. They see what I add and think, 'hmm, I can see how I can make use of that', or 'that would have been useful for <situation I had in the past>'
Something that is not clearly 'a feature' is hard for people to grasp in order to comment on it. It's a usability thing not a 'feature' thing, and as a result people need to see it, interact with it and get a feel for it to be able to figure out whether they like it or not. It's much the same with some of the WeCSS stuff, actually... same symptom under a different situation - most people are not in a position to see it or interact with it to be able to figure out if they're going to like it or not, and most people won't use it anyway because most people are only going to do minimal colour changes based on themes other people made.
I have a similar problem in terms of getting feedback when it comes to some of the stuff I've worked on with Wedge, e.g. when I asked about permissions. Everyone seems to grasp the nature of the problems that I see with what SMF had, but no-one's really quite sure how it should be fixed, and even when I tried bumping it via Facebook, the additional views didn't really help. It's frustrating in a way because I specifically wanted feedback but came to understand why I wasn't going to get very much on it.
The quest for perfection is a lonely enough road as it is, and when taking into account usability and aesthetics, it's even lonelier. Good design doesn't shout at you to tell you how good it is. It lets you do what you want to do without being in your face, in a way that feedback generally seems redundant. But bad design will generally get met with feedback along the way. The lack of feedback, generally, is a good thing where design is concerned.
I'm not sure how I feel about the sidebar at present. The idea of it sliding out is a cool one, but I'm concerned that it isn't obvious enough and it seems a bit twitchy to me - I go by the front page an awful lot and more than once I've ended up bringing the sidebar into view when going to click on the 'Wedge' in the linktree.
-
Something that is not clearly 'a feature' is hard for people to grasp in order to comment on it. It's a usability thing not a 'feature' thing, and as a result people need to see it, interact with it and get a feel for it to be able to figure out whether they like it or not.
It's much the same with some of the WeCSS stuff, actually...
I have a similar problem in terms of getting feedback when it comes to some of the stuff I've worked on with Wedge, e.g. when I asked about permissions. Everyone seems to grasp the nature of the problems that I see with what SMF had, but no-one's really quite sure how it should be fixed, and even when I tried bumping it via Facebook, the additional views didn't really help. It's frustrating in a way because I specifically wanted feedback but came to understand why I wasn't going to get very much on it.
(Although later, I made a suggestion about moving everything to use hover dropdowns, which I still think is going to work great, but I'm always postponing my 'generic hover dropdown' thing, because I have other things to deal with... Currently, notifications, sidebar and infinite scroll, all three of which have taken their toll on me...)Good design doesn't shout at you to tell you how good it is. It lets you do what you want to do without being in your face, in a way that feedback generally seems redundant.
I'm not sure how I feel about the sidebar at present. The idea of it sliding out is a cool one, but I'm concerned that it isn't obvious enough and it seems a bit twitchy to me - I go by the front page an awful lot and more than once I've ended up bringing the sidebar into view when going to click on the 'Wedge' in the linktree.
I was actually considering dropping the hover act for this, and going for a Menu button in both mobile and desktop. Both will have an additional trigger technique, of course: middle click for desktop, and right swipe for mobile. (The version I'm working on currently is much more conservative when it comes to the swipe length, and I'm hoping to be able to make it work the same on all mobile devices, whatever their way of calculating said length, which can be annoying.)
PS: I still think that, maybe, just maybe, we should consider saying Wedge is a 'blog' platform, or at least remove references to 'forum', and use 'community' everywhere...
-
Maybe there could be 2 different sidebars for phones and tablets. The one for phones should have less items and should be smaller (and less intrusive). :)
-
There are two different sidebars...
I take it you haven't followed this topic at all... Anyway...
-
I can't open it on chrome beta on my nexus 4. O tend to switch tabs, plus I'm not even able to scroll sideways.
-
Works great for me on Chrome Beta... :-/
-
Fun crap of the day...
Chrome: $(document).mousedown(e) -> e.which returns 1 for left button click, 2 for middle, 3 for right.
Firefox: e.which returns 1 for left button click, and isn't caught at all in middle and right clicks... To trigger 2, you have to first press the right mouse button, then the middle button, then release the right button.
This is totally stupid..!
Posted: July 2nd, 2013, 11:39 PM
Also, doing it on click() (which isn't in the jQuery docs), right button works, but middle button still doesn't... -_-
Posted: July 2nd, 2013, 11:41 PM
I'm starting to seriously consider doing two different sidebar animations...
- desktop: sidebar shows from the left; screen remains static.
- mobile: sidebar is stuck to the left of the screen; entire screen scrolls, or 'pans' to the right.
The reason why I need to do it that way in mobile, is that it's the only way to trigger hardware acceleration; as a counterpart (?), the sidebar position can only be 'absolute', instead of 'fixed' (this is a W3C-induced limitation related to stacking contexts). It doesn't matter much anyway, because scrolling a position: fixed element on mobile is an... absolute PITA. Believe me, I've tried HARD... Doing it in a native app is easy as hell, but in a web app, it's really hard to get it right.
Desktop browsers don't need the extra boost from hardware acceleration anyway, so we can do without it... Although the animation isn't as cool, but since it's done by jQuery, it's compatible with all browsers, including oldIE. Normally...
I don't know... Should I do the hardware accelerated animation on both..?
-
Just a note some of us are moving so have not had time to really reply last week or so.
-
Middle mouse button would be interesting and so extremely flawed. Aside from the technical issues you've found, there are two very, very large objections to middle clicking.
1. A lot of mice have a scrollwheel instead of or even as well as the middle button. The mouse I'm currently borrowing has two principle buttons and a scrollwheel and I can depress the scrollwheel to middle click. Normally this also results in my scrolling the page somewhat meaning that I usually miss the thing I was trying to click on.
2. My laptop doesn't HAVE a middle button. It doesn't even technically have a right mouse button. Right clicking on the MacBook Pro trackpad is a two finger single tap to the entire trackpad, middle clicking is the Command key plus a tap to the trackpad. Yes, that's right: I have to physically use the keyboard, even though it's right next to the trackpad, to do that. Needless to say, it isn't happening any time soon. And most laptops I've seen have a similar issue: there's often only two buttons, which means if middle click is supported at all, which is not that likely, it's implemented as pressing both buttons together.
There is a wider issue here: outside of reasonably specialist activities - CAD, modelling and the like - and some games, middle click is *just not used* anywhere. For years I had my old mouse set up so that middle click didn't actually middle click at all, but instead issued a double click, to push less wear on to the left mouse button's switch. During that time I never found a single application that ever used the middle button for anything at all. That was a few years ago but generally speaking things haven't actually changed that much.
Hell, on my Logitech M500 mouse - the one with the back/forward buttons in easy reach of the thumb - of the games that did use middle mouse button for something, I just reset that to the back button because it was so much easier than actually using the middle mouse button. But even those were the minority in the first place.
Then, add in the fact that it's a feature NO-ONE is going to notice unless they're told about it - there is absolutely zero UI hinting in any current desktop operating system for middle clicking - and the fact that not everyone reads every post all the time (except possibly me, and even then I do gloss over the details of some of them though I try to pick up on what I think is important) and it all combines to a point where there is a feature that is potentially very cool but that no-one would ever find it except by accident and then they might not realise what they actually did about it. There is no way that is good design.
Show me one other website where middle clicking is a common and recognised aspect of the site. And then show me what they did to explain to users about it.
Of the people that actually do use middle click, they use it for a given operation and not the one you wanted to indicate (as stated, it's frequently used to open tabs in a new space). It works for me in Chrome, in that it does as described. But there is precisely no chance I'd ever know it was there unless you mentioned it. And if you have to explain to people that it's there and what it does, it's probably not the best choice for a UI element no matter how cool it is.
PS, yes I'm on hiatus, though I'm actually able to check in more than I previously thought (though Chrome seems to have trouble handling JavaScript, so I'm reduced to using Safari while I'm on OS X because I can't be bothered to either boot my Boot Camp partition or install Firefox *shrug*)
PPS, I stopped thinking of Wedge as just a forum a long time ago. But to call it a blog is a great disservice, it lowers it to the level of WordPress.
-
That's a long post, for an issue that really never was... ;)
Okay, I've updated the site to my latest local version, with:
- hover removed, so, no more accidental triggering,
- replaced with a 'standard' menu button, located in the top left of the screen, which you can click to toggle the sidebar,
- button has a title attr, explaining what it does, and that you can also middle-click,
- IE < 10 compatibility.
Hopefully, this time you'll think it's more usable. Haven't tested much with mobile devices, though...
I'm also considering turning the #top section into a fixed element, sort of a frame, and put all of the useful stuff into it, as icons. (Except for the search bar, which is okay as an input bar.. For now!)
I haven't tested yet, and I'm not even sure I'll do it, because on most sites, I tend to dislike fixed top bars, but on some sites I find it isn't too bothersome, so... I don't know, I'll have to see.
-
The hair trigger is gone on my iPad 2 with iOS 6 and I like the icon as its something I see on other responsive designs. Not tested on a pc yet.
-
Testing on PC.
1. Whereas the hair trigger was kind of annoying, being forced to use middle click to see the sidebar means I'm never going to see the sidebar.
2. The closing behaviour feels inconsistent, even though it's not. The point of moving the mouse from inside to outside the sidebar area... the first time I saw it, I thought it was broken because it just happened to open and then immediately close afterwards. Cool, but feels weird.That's a long post, for an issue that really never was...
-
On my windows 8 system on chrom my middle click brings forth a useful scrolling tool (well for large images anyway) so I am thankful there is a button. that said clicking the button again does not close said sidebar.
-
What's a hair trigger?
Removed the hover entirely now... To close the sidebar, just click outside of it.
Also made the Menu icon a bit bigger, so that you should be able to open a sidebar more easily, Pete... :P
And as always, middle-clicking also works!
-
Chrome 27.0.1453.116 m doesn't close when clicking outside the sidebar.
-
Works as expected on Chrome 28.
The icon is not clear as to what it is (but the exact same argument should be levied at Chrome when it changed the wrench icon to a 3-bar icon...) but I don't really know what can be done to make it more useful.
I still think capturing the middle button is a bad idea for anyone who has it set up for other uses (plenty of users do use it to open things into a new tab and the above example)
But hey, you know best about this.
-
I can't get the damn thing to open on my new MacBook with Chrome 28
-
There's always time to fix stuff.
Pete. Since day one, middle click isn't hooked by the sidebar when it's done over a link. Are you sure you didn't miss the early talk..?
PS: fixed a bug added today where it was impossible to post in mobile mode... Thankfully, drafts were still saved. -_-
-
Thanks for fixing that bug though it was a cache issue on my end
-
Yeah, was a CSS issue really. Button was still there, but hidden... Oops!
-
Are you doing some test against HDPI displays or something? I can't have a look at source now but the sidebar absolutely doesn't work for me.
-
Both methods...?
Posted: July 4th, 2013, 05:25 PM
And how I am supposed to test in a device I don't own..?
-
With the recent changes, the sidebar no longer shows on windows phone 8, ie10.
When i click the 3 bars, the screen slides as expected but the sidebar does show, just the blank white area. When I click anywhere outside that area the screen retracts as expected.
-
Hmm... -_-
Well, anyway my current local version has seen a lot of extra changes... Which I don't even know if I should commit... :-/
Considering that Warm has a 'special' layout, I started to scroll only the main content area, i.e. not the header, and now the top bar is at a fixed position, so you see it permanently on the screen (in mobile mode, at the very least...), but it breaks heavily in Warm too, and it's starting to really, really piss me off...
It sounds to me like infinite scrolling and responsive sidebars are voodoo tricks that will never behave consistently on all setups (browser + server + skin + plugins), and I shouldn't even bother with them... But what good is Wedge, if I only settle for the easy road, and give up on the bells and whistles which I've enjoyed adding over the years...?!
-
Maybe only add IS and responsive sidebar to Weaving? *Shrugs* Either way it it fun to test on Wedge.org :)
-
Hmm, PMs should probably issue a notifier, users on mobile including iPad will not see the sidebar by default and may not know they have messages.
-
Moved sidebar to the right (by default) in responsive mode, as well as the menu button.
Reasons:
- most people are right-handed. On a mobile device, it makes more sense to make the button easily accessible to their right hand if it's controlling the device, I guess...
- top-right corner is the least important corner, so it also makes sense to put the fixed button there, and if a fixed button is there, then we might as well put the non-fixed version there as well, just a matter of logic...
Also modified the non-hardware scrolling, to very simply emulate the hardware scroll. It's all about logic, tonight...
Please post feedback, bugs, etc...
PS: also, I'm considering getting rid of left/right swipes in mobile mode, reason being that the fixed button should be more than enough to get the sidebar to show, and swipes always mean giving something away, in terms of UX.
-
Seems to be working as intended here, no issues found so far
-
Hmmn, don't know what I am doing wrong. I downsize my browser viewport to test responsiveness, click the sidebar toggle icon in the upper right and the page stretches without horizontal scrollbars. I can't see the sidebar anywhere. Clicking on the webpage proper returns everything back to normal.
-
Browser and os..?
-
It's only if you resize the window after the page load that size is messed up; it's only calculating based on the size of the original window, so the described behaviour is entirely correct.
Take a window, resize it to make it smaller, then open the sidebar and boom, you get part of the sidebar instead of the whole sidebar.
Trouble with all this is, those people who have the screen large enough to see the sidebar normally will suddenly go 'WTH did my sidebar go' because it's now not obvious where that content is, especially that they have to press something to open it, and an icon that isn't immediately synonymous with 'sidebar' but a very general 'more things' button that isn't even that obvious (first time I saw it on Chrome, I was like "why did they replace the wrench with that?", I see YouTube uses it now but that isn't immediately clear)... if anything I'm beginning to wonder if this isn't cool but ultimately a step back in usability for desktop users. (For mobile users I can see the advantages, sure, but even then I wonder about the usability aspect.)
Interesting sidenote: responsive design caught up with XenForo and there were, in the aftermath, some questions like "Why isn't there a variable for the server to detect if responsive or not" which makes me question the understanding that some of these people have with respect to what responsive design even means, but the more pressing question that arose out of it: how do we indicate whether to use narrow/wide to ad blocks? It's going to come up, people are going to ask us how to use ads in the system and yes, there's going to be an ad management tool but there's only so much that can actually be done with that. Something to ponder, anyway.
-
In iOS safari doesnt work
-
To add, iOS 6.1.3 / iPad 3 (with dev stuff, but nothing that would apply here), button opens sidebar, does not close it again.
-
- iOS: for me, it works... It opens the sidebar. It doesn't close it, though, and I'll have to understand why. (My code isn't exactly THAT complicated..!) I've done plenty of testing, but nothing comes out of it. Only thing I can guess: maybe, maybe, that stupid browser engine can't figure out that $(...).removeAttr('style') should actually remove the 3D animation... Which is silly, since doing it the other way around does add the animation..?!
- iPad: why does it still hide the sidebar on this..?
- I have absolutely no problems with the sidebar being empty when resizing the window..?
- In terms of usability, this icon is actually the number one recommended way to open a sidebar... Believe me, I tried everything before I settled on that. I actually removed the swipe effect, even though it's also "natural" on mobile devices, because it was getting in the way of usability. So... There you go.
- Is XenForo the only platform around..? You do realize I feel absolutely no attraction to their way of doing things, right..? That if I do something that's similar to them, it's not thanks to them, but simply because it's the logical way to do it..?
-
- Is XenForo the only platform around..? You do realize I feel absolutely no attraction to their way of doing things, right..? That if I do something that's similar to them, it's not thanks to them, but simply because it's the logical way to do it..?
-
It isn't the only platform around, however as the pay-to-play crowd goes, it is by far the sane benchmark (i.e. if you want to go paid, they're the people to look at) and they basically do what Wedge used to do with respect to the sidebar, i.e. in responsive mode, push it under the content (though not nearly as elegantly as Wedge did)
I'm no design guru but I look around and see what everyone else is doing because I've learned that sitting in a vacuum is not necessarily the way to go; I have to consider what users want not just what I want. So I look at what other platforms are doing and how well they're listening to their users... and XenForo is doing a pretty good job of that all in all.
-
Sorry about that, Firefox 22 and Windows 8.
-
Must be a bug in FF 22, because I tested in FF 24 + Windows 7, and it's working just fine... (?)
Re: iOS, it should be fixed now... It's what I thought: if I do .removeAttr('style') on it, it doesn't actually remove the style, I have to manually reset the translation to 0, which sucks...
Please everyone, test again..!
I also added some code to prevent zooming into input boxes and textareas. I've always hated that, TBH... I'll appreciate feedback on whether text is readable -- if it isn't, please indicate the device and browser.
-
iPad 3 / iOS 6.1.3: Sidebar does not disappear entirely, something like 13 pixels remains on the right hand side of the screen.
In other news, the size of the 'Users Online Today' entry text is significantly smaller than the normal Users Online entry text (i.e. the names) and the plugin does also need updating for the icons used for online/contacts changes, just haven't gotten around to it.
-
iPad 3 / iOS 6.1.3: Sidebar does not disappear entirely, something like 13 pixels remains on the right hand side of the screen.
Did I say how much I hate iOS and XF these days...? :whistle:
-
Now it's kinda screwed up on iPad, where the main page content s wider than the actual page... It's weird and annoying.
-
Must be a bug in FF 22, because I tested in FF 24 + Windows 7, and it's working just fine... (?)
-
Screenshot Pete..?
-
Apologies for size, it's direct from iPad 3. (iOS 6 allows upload from Safari, yay!)
-
This should be fixed now... I figured out it was a problem with extra.ios.css, and indeed, a lot of this file was deprecated because of the new responsive rules... Meh!
Perhaps I should just drop the file entirely, it seems to work overall without it...
-
So... Anything left hanging?? Or is it commit-time for me, at last...?
Posted: July 10th, 2013, 11:46 PM
(I'll take it that the complete lack of comments following my iPad fix is the current equivalent of thinking "oh yes it works now" and clicking the "Like" button...? :^^;:)
-
Yes it all appears to be working properly. I'm sorry that we didn't manage to reply within a reasonable feedback timeframe but yes it is working properly on both desktop and iPad as far as I can tell with the few minutes of testing I've given it.
Also, side bug discovered with infinite scroll on a not-so-huge window, see attached.
-
Working on iOS 6.whatever I said last time :P Good work. I am okay with the icon used on most responsive designs for menus. I like Weaving on iPad more than ever :) I almost wish there was a persistent bar with notifications, search, and the sidebar. Scrolling to the top for all those neat features is a pity. I am liking the direction thats for sure :)
-
On iOS 6 if I'm at the bottom of a long page and press the button to open the sidebar, it's blank. I need to go to the top of the page to view the sidebar content. It should be set as position fixed I think.
-
We should add this as a rule, that all suggestions must have feedback within an hour and if no feedback is received, just proceed. Same with bug fixes, if no-one says it's got issues inside an hour, assume it's fixed.
Also, side bug discovered with infinite scroll on a not-so-huge window, see attached.
-
I almost wish there was a persistent bar with notifications, search, and the sidebar. Scrolling to the top for all those neat features is a pity. I am liking the direction thats for sure :)
- it's mostly useful on mobile devices, *and* mobile devices are the ones where saving space is a most important matter, so I couldn't make it too big, but if it was too small, it started losing its 'practicality'...
- this one is more technical, but having a persistent bar at the top, takes about 30 to 50px height, and there's no way to tell the browser that this space shouldn't be used, so it actually still keeps showing stuff behind this... For instance, doing "html { margin-top: 50px }" will only add 50px at the top, so... Whatever... And I don't think doing a position fixed would help either, ah ah... Anyway, because the browser still uses that extra space behind the top bar, when you click on a topic link for instance, you're taken to a specific post, right..? Well, this post anchor is shown right behind the top bar... In order to be able to see who wrote the post, you'd have to scroll up. So, I started implementing various ideas, such as using JS to fix that (it sucked), and then using pure CSS to do it -- there was a solution that worked very well, but... Only if the anchor was linked to an empty div or a tag. Or a simple one, but linking it to a <div style="display: table"> would break the table layout, which absolutely SUCKS, even more than the JS solution....
I spent about half a day on this one, and the persistent top-right menu button is the only leftover of this. This *is* the top bar... Yes, the only solution I found to 'fix' the anchor, was to simply not care about it, and show a button that doesn't hide anything. (As it is, in fact, it hides the "expand" button in the header, but I'm assuming it's not a big issue...)
So, if you can find a solution for this, you're welcome to suggest one...!
-
On iOS 6 if I'm at the bottom of a long page and press the button to open the sidebar, it's blank. I need to go to the top of the page to view the sidebar content. It should be set as position fixed I think.
position: fixed is all I did in the beginning, and for several days, until I gave up on it.
It was (position-) absolute hell.
- Earlier versions of iOS don't support it correctly at all. Not that I care, but...
- Mobile devices only implement it half-heartedly, meaning that if you scroll the main screen, you can clearly see the sidebar struggling to keep up, probably because mobile devices implement position: fixed with some kind of JavaScript hack, or at least they refresh the position with a low priority, lower than the main screen's scroll thread, if you know what I mean...
- Scrolling within a fixed-position sidebar with overflow-hidden, while possible (and very much necessary, given that it also holds the main menu), is excruciatingly slow and unresponsive on my Galaxy S3... I can't even begin to imagine how slow it might be on older devices.
- When you reach the end of the sidebar, the browser will then bubble up the scrolling request to the main screen, meaning you find yourself with a static fixed sidebar and a scrolling screen, even though you're attempting to scroll the sidebar itself... It's really unintuitive, and I wrote some code to prevent that, which worked perfectly in desktop browsers, but failed on my S3. I couldn't get it to work, and I tried hard. I actually committed that piece of code to the attic, at the end of the "Unused-swipe.js" file, if anyone wants to look into it, but I'd hold my horses, if I were you...
So, yeah, for all these reasons, I started looking into using position: absolute, and it simply worked better for me... Yes, of course, you end up with empty space if you're at the end of a topic, but I can't help it. I could do something more convoluted, believe me I've thought about it, all I could think of is to reset the top position of the sidebar to whatever is your current scrollTop position, it's a cop-out, but it might work. It also means that if you accidentally close the sidebar and re-open it, its scroll position will be reset, but... Whatever. Is this something that most people would be interested in, or not..?
Or am I just trying too hard..? I mean, I guess everyone but me was happy with having the sidebar at the bottom, uh..? I just couldn't take the pressure of properly positioning the elements horizontally, sometimes it just looked so fucking ugly, I wanted an alternative, but I didn't expect it'd take me so long, and for that, I'm not grateful to my own quest for perfection... :-/
-
all I could think of is to reset the top position of the sidebar to whatever is your current scrollTop position, it's a cop-out, but it might work. It also means that if you accidentally close the sidebar and re-open it, its scroll position will be reset, but... Whatever. Is this something that most people would be interested in, or not..?
It's working, though... And it seems 'usable' enough, but I'm having issues with the sidebar when the container page is shorter than it.
Then again, the exact same problem already exists in the current version (just click my user name in mobile mode, and open the sidebar... It'll systematically be shown on top of the footer...), so really, it's not that big a deal.
I'll probably end up reverting a couple of things in the implementation, e.g. the table-to-block override for the sidebar div, hopefully this will help keep the sidebar visible at all times, although people might start wondering why there's empty space in profile pages... (Said empty space being there to prevent the sidebar from overflowing when opened, of course.)
What's best, then..?
-
I read no solutions at the moment, still thinking net being off all day killed productivity.
-
On my Samsung Note 10.1 (Android 4.1.2) I get different results depending on which browser I use. With the 'standard' browser, the skin changes to Wireless and there's no button to control the sidebar's appearance. However, if I use Firefox (v22), the default skin is Weaving and I do have that button.
Rather oddly, when viewing this site (and only this site has this affect), the 'standard' browser is forced into landscape mode and will not switch to portrait. The Firefox browser works in either screen orientation as one would expect.
-
I'm currently seeing 4 menu buttons for the sidebar.
1 each before and after the the language flags
1 each before and after search field and button
Windows Phone8 IE10
-
am i correct that the sidebar is an option for anyone with a page width of less then 985px? give or take?
there are some users that have a widescreen desktop and dont have the browser full screen, on my current setup my opera window is about 973px wide... i get the option for the sidebar but when i click on it nothing shows up but a blank space on the left side
i am not resizing the window either. also without having a middle click i find this menu will be used very little as it would require scrolling all the way back up to the top of the page each and every time i would want to see the menu.
-
@spoogs, I'm not sure how I missed that, eh eh... It was a precedence problem, fixed in the latest commit.
@icari> the trigger is 1000px width, not including the scrollbar. Generally, a maximized window in 1024x768 won't trigger it, but if it does, it's not really a problem, considering a ~700px window (sidebar not included) is too narrow to really enjoy a forum, I think.
Anyway, any bugs in Wedge.org should be accompanied with: OS used, browser used (+ version if relevant), and skin used.
Ideally, if you could debug visual issues by yourself, and indicate what went wrong for you, it'd be obviously even better, because I can't access some of the platform combinations...
-
@Nao yep only seeing one now and seems to be working. I see only the one before the search field, is that accurate?
-
windows 7 opera 12.16
with dragonfly up (http://imageshack.us/a/img694/9461/fl8q.png)
but there is no scroll bar on the bottom of the window to show the menu, also anytime i right or left click when the menu is up it closes the menu, so if i want to right click and copy for example it causes issues. [or even use dragonfly]
-
looks like now i can view the sidebar, but still right or left clicking causes the bar to go away automatically, which causes issues when you want to lets say... click on a message to view or click on a button to do an action.
-
Yes, I fixed some additional issues with the sidebar. Opera < 15 still doesn't do great, mostly because it has the same problem as Firefox (middle-click -> can't cancel the default behavior for it, but it'll still toggle the sidebar.)
I don't really care about Opera < 15 to be honest, because it's outdated now, and eventually Presto will be used by a tiny, tiny fraction of web users. Opera Blink is still very far from Opera Presto's coolness, and it'll be a long time before I use it by default on my computer, but at least it works when it comes to the sidebar, so... No need to bother too much, just like I decided not to bother with IE6/7 and not give them a responsive sidebar. (Makes things much easier, ah ah...)
As for the extra click -- it's irrelevant. Most implementations of a toggable sidebar do the same, i.e. if you click OUTSIDE of the sidebar, the software assumes you want to get away from it, and thus it hides it. Showing it again, is just a click away.
If you click INSIDE the sidebar, of course it's not going to go away. Actually, I even added some code to ensure that clicking outside the sidebar, but inside a scrollbar, will not close it either.
Posted: July 15th, 2013, 03:40 PM
(Edited.)
-
Okay, did some extra modifications... Tested in oldOpera, oldIE, and Chrome. Tested with all skins. Now the skins should all be working great, *and* hardware acceleration is enabled even on Warm and Wine, which is nice. And finally --- the best part is that I'm no longer doing browser sniffing to determine if you can have hardware acceleration, so it should be working 100% for everyone, at last...
-
So, here we are in a hotel room with decent wifi and we thought we'd check out the sidebar. We have an iPad 2 and an iPad 3 (so, one 1024x768 and one 2048x1536 retina display) both running Safari with iOS 6.1.3, neither has been modified or running dev code at this time.
Here's where it gets funky. On the iPad 3 (retina one), I don't see a sidebar displayed, even in landscape. It's hidden and I have to unhide it, which is fine. The iPad 2 on the other hand, shows the sidebar all the time, even in portrait mode, even after refreshing the page. Both iPads are using wedge.org while logged in so it's not a guest account vs member account. Admittedly the other account is not a beta tester or admin but I fail to see why that would make a difference.
Also, I assume the sidebar button is positioned at the top of the viewport when going to a page? I don't entirely know what is intended but here's what I'm seeing on iPad 3: the button appears at the top of the page for wherever I go to. So for this page for example, I came here from other navigation and arrived at #new, so looking at the last post and the sidebar button is aligned with the last post.
Now, aligning it with the top of the page when the user lands somewhere is neat - provided it follows them. Otherwise they could easily jump to the mid point of a page and then not be able to find the sidebar again because the button is somewhere on the page. Now, if it is supposed to follow my movements, it's not doing that. I did, while writing a long post, see the sidebar button manifest itself on the far right of the page just above the quick reply area, but only for a short while before it disappeared to who knows where - I was writing a long post and didn't see where it went.
Wait, if I'm in the editor and delete a line of text, such that I force the content to come back down to me (e.g. long post, I double-hit enter to make new lines then delete those lines) the button will appear on the far right of the page but will move if I cause the editor to scroll in any direction.
It's interesting but it seems unreliable to me :( (it's a shame because I can see how hard you've worked but I keep finding things that cause it to break)
-
So, here we are in a hotel room with decent wifi and we thought we'd check out the sidebar.
(I must say, it's interesting that I was finally able to see you 'live' after 3 years working together and only knowing you from a single picture, and yet you're 20 times further away from me than you usually are... :^^;:)We have an iPad 2 and an iPad 3 (so, one 1024x768 and one 2048x1536 retina display) both running Safari with iOS 6.1.3, neither has been modified or running dev code at this time.
- Windows 7, main dev browser has been Chrome Canary for 6+ months, usual test browsers are Opera 15, IE10, and sometimes Firefox Aurora. These days, also Opera 12.16 (cf. comments in the thoughts.)
- S3 smartphone with Android 4.1.2, rooted, using the regular Chrome, with Firefox Beta as my occasional test browser, and very rarely, the stock browser (which I think sucks.)
- iPod 4 with iOS 5.1.x (probably just 5.1), rooted, using the regular Chrome. The only reason I've re-charged it these days, is to play Ron Gilbert's Scurvy Scallywags (very nice game, albeit a bit hard, so reliant on (bad) luck that it can get troublesome...), and Safari used to crash on me, but apparently, these days it doesn't, so I just tried on it...
It looks like the current Safari + iPod version gives me a different result... Instead of having the fixed button on the top right, it shows it on the top left (?!), and only a very small portion of the button, uh... Yeah, sure, great devs at Apple...Here's where it gets funky. On the iPad 3 (retina one), I don't see a sidebar displayed, even in landscape. It's hidden and I have to unhide it, which is fine.
You definitely should try remote debugging Wedge from your Mac. You have a Mac, I believe..? Since I don't, and don't plan to ever buy one, I can't debug their stupid Safari, and thus, can't see which media queries are triggered, etc...
The media queries are as such, IIRC ($response = max-width: 1000px):
- "$responsive" hides the sidebar, and shows the sidebar button in the top_bar, where it sits next to the Upshrink icon and Search form.
- "$responsive and min-resolution: 1.5dppx" additionally makes the sidebar button a fixed button, and moves it to the top right corner.
And, that's all there is to it...
The first query should run everywhere (including iPads), if the windows is shrunk. The second query specifically targets smartphones, by ensuring we're both in a low res, AND we have a Retina screen or better. Of course, I could simply test against the OS, or the 'mobile' variable, or both, as it would thus take bad screens into account... But, well. I'm not sure about this.
Normally, an iPad 2 shouldn't trigger the second query, but an iPad 3 and iPhone/iPod 4+ should. As I said, my iPod 4 doesn't show the button entirely, but that's probably down to a change I made yesterday, which I'm bound to cancel at some point, i.e. I changed the button width to use vw units (percentile of viewport width), which is great, but messes up the button in desktop mode, ah ah... (I even had to add an @if mobile test, to ensure it wouldn't screw up.)The iPad 2 on the other hand, shows the sidebar all the time, even in portrait mode, even after refreshing the page.
Also, I assume the sidebar button is positioned at the top of the viewport when going to a page? I don't entirely know what is intended but here's what I'm seeing on iPad 3: the button appears at the top of the page for wherever I go to. So for this page for example, I came here from other navigation and arrived at #new, so looking at the last post and the sidebar button is aligned with the last post.
Now, aligning it with the top of the page when the user lands somewhere is neat - provided it follows them. Otherwise they could easily jump to the mid point of a page and then not be able to find the sidebar again because the button is somewhere on the page. Now, if it is supposed to follow my movements, it's not doing that.
iOS didn't support position: fixed at all, years ago, but now it's supposed to... In fact, it does support it on my iPod+Safari, if you don't take the button size into account.I did, while writing a long post, see the sidebar button manifest itself on the far right of the page just above the quick reply area, but only for a short while before it disappeared to who knows where - I was writing a long post and didn't see where it went.
Wait, if I'm in the editor and delete a line of text, such that I force the content to come back down to me (e.g. long post, I double-hit enter to make new lines then delete those lines) the button will appear on the far right of the page but will move if I cause the editor to scroll in any direction.
It's interesting but it seems unreliable to me :( (it's a shame because I can see how hard you've worked but I keep finding things that cause it to break)
So, I'm definitely not going to give up on this, but I'm guessing I'll have to rely on someone with a Mac to do the debugging for me, because I'm not buying a friggin' Apple computer just for the sake of ensuring they didn't screw up with my code, eh...
-
iPad 1: 1024 x 768
Browser: Safari
Portrait: sidebar visible
Landscape: sidebar invisible, must scroll horizontally to see, no sidebar button
Samsung Galaxy S3
Browser: Stock
Portrait: no sidebar, part of button upper right but not selectable
Landscape: no sidebar, part of button upper right but not selectable
No sidebar, no menu on top so not even possible to login etc.
Ps
You could, for test purposes, run Apple OS X in a virtual machine on your Windows computer.
Enough info on the internet. With some searching even complete images for virtual machines.
-
Regarding the PS... running OS X on virtual machines is tricky at best. VirtualBox just sits there and complains if you try to run OS X as a guest VM when you're not already on OS X (I tried this before)
-
I tried OS X 10.8 Mountain Lion in VMware workstation. It should also work in VMware Player.
Works good as far as I can tell.
Maybe a bit slow, but I don't mind for test purposes.
OS X can officially only run on VMWare Fusion.
Some guys made work arounds to run in other virtual machines including Virtual Box.
I used a VMWare image (complete with Darwin.iso) I found on the internet.
So I downloaded the image, fired up VMWare and started OS X.
-
Yay for doing it illegally. (The licence actually states it can only be used on Apple equipment. It is also unlikely it will work properly for users who have AMD processors.)
-
Whether it's legal or not, I don't really care... Apple doesn't like Windows users, and wants to force them into using OS X to debug websites running under Safari Mobile. Good for them. But it doesn't mean I have to fork out $1K for a crappy machine that's going to make me miserable, just like their mobile OS made me miserable over the years. Mind you, I'm not a pro-Google either -- I just installed their new Maps update, and it sucks -- but they're still the ones who innovated on the mobile front in the last few years, and with terms that were far more user-centric...
Anyway, all I need to say is:
- I don't have an iPad, nor do I have plans to buy one. (Maybe an iPad Mini, in the far future, if Google starts trailing iOS...)
- Wedge.org runs okay on my iPod 4 + Safari Mobile.
- Thus, I have no reason to install OS X and debug something that doesn't happen to me...
- Unless they provide an iPad emulator over there, of course.
Do they..?
-
Hmm, my AltGr key decided to drop dead or something, hopefully it's only temporary, but I can no longer enter brackets like [ (only doing it through a copy'n'paste...), so it's not cool, definitely not cool...
iPad 1: 1024 x 768
Browser: Safari
Portrait: sidebar visible
Landscape: sidebar invisible, must scroll horizontally to see, no sidebar button
What iOS version..?Samsung Galaxy S3
Browser: Stock
Portrait: no sidebar, part of button upper right but not selectable
Landscape: no sidebar, part of button upper right but not selectable
No sidebar, no menu on top so not even possible to login etc.
-
My iPad 1 is running the latest IOS version which is 5.1.1
Because your remark I decided to retest on my S3.
Every time I wanted to click the (small) sidebar button, the arrow which opens and closes the top window (sorry but I am not very familiar with the English names of all the screen parts) got selected.
After trying and trying it would work ± 1 out of 15 times. I have very thick fingers :eheh:
Finally I discovered that if I would scroll a bit so that the arrow would be out of sight I still had the sidebar button which by then was free and easy clickable.
-
Okay, I fixed:
- the arrow problem (added some extra margin when the button is fixed),
- the button not showing up entirely in the stock browser; I chickened out, and simply turned my 'mobile' test into 'mobile && chrome', which should work more efficiently, I guess... I mean, mobile browsers can live with a hardcoded px width, rather than a viewport-dependent width, so... No need to bother, I suppose...
Everything all right, for you..?
-
iPad 3 still doesn't show the sidebar in either portrait mode or landscape until I press the button. It's also smaller than it was yesterday, but it's still big enough to be usable.
Regarding the legality of OS X... I know some people are bothered by that, and I know that the way OS X is built, it just doesn't work properly on non stock hardware (which can have issues with virtualised machines) because they just don't have the drivers. I will be able to help debugging when I'm not on the road (and right now using an iPad connected to an iPhone for its 3G connection!)
There is an iPad emulator of sorts with Xcode but I don't really know how it's geared to browsing.
-
It's working perfect now on the S3 stock browser.
Thanks.
I ran the OS X image running in VMWare to find out if a Apple computer with OS X would be something for me, before spending a lot of money.
It's ok, just not for me. I stick to Windows.
Sorry Apple.
-
The only theme the sidebar shows on my iPad 2 is wireless and I think that is as designed. I personally like weaving and wine best on my iPad 2 everything is to small on wireless. JMI thanks for all the hard work.