[Feedback needed] Atlas, the next version of Neowin


Recommended Posts

Overall, it's looking very nice! Much more efficient use of the available space...

One thing bothering me though - the rounded corners are only supported by Firefox, whereas IE users will get the non-rounded corners? Argh! Neowin making me switch to IE for browsing purposes? I suppose there's no need to be too dramatic, as long as it's not too difficult to revert to the non-rounded through some simple CSS tweaks!

Apologies if this was mentioned already, but I might've missed it when quickly skimming through the 9 pages.

You can always use Stylish to apply any tweaks you'd like. I'm sure the devs wouldn't mind telling you what to change to remove the rounded corners.

All in all, it's kind of ironic they haven't recognized that technology has moved forward and everyone either has a widescreen monitor or a high res 4:3 monitor, you know since they're doing a solo crusade to force some browser to ugprade to a work in progress standard.

after all the people who don't use a high res 4:3 monitor or wide screen monitor could use one of the low res device(i.e. mobile) layouts.

Not everyone that has a wide screen monitor browses with the browser maximized; I don't. I have Fx open about 3/4 of the way; the remaining portion is either for messenger or yahoo widgets. To me, it seems like a waste of screen real estate to browse maximized.

We're not denying anyone the option of increasing the width of the site via Stylish or a custom CSS file of any sort. What we are saying is that the site does not operate as designed if we offer it.

We don't want to offer options that make the site work in ways we did not intend. If users want to have the width increased, they can do a simple CSS file with the contents #container { width: 100%; }, and be done with it. Otherwise, we have to put the code in to offer a feature which, in our opinion, breaks the site, and requires a lot more support because of it.

Personally, I think that's perfectly reasonable.

I don't understand tho, you guys tried this with the last refresh and got a ton of bad feedback about it. It doesn't make any sense for force it again especially as your *still* getting a ton of bad feedback about it. I think those giving feedback understand *why* you want to do it, but at the same time it's kinda fail to just shun off the feedback in favour of the "vision"

I don't understand tho, you guys tried this with the last refresh and got a ton of bad feedback about it. It doesn't make any sense for force it again especially as your *still* getting a ton of bad feedback about it. I think those giving feedback understand *why* you want to do it, but at the same time it's kinda fail to just shun off the feedback in favour of the "vision"

You do know the current site is a fixed width by default. You have to know WHAT button to click to make it semi fluid/larger width.

(though I agree about the white bg helping it feel wider...)

cnn.com

bbc.co.uk

= Fixed width,

Also, here is the site at a fluid width.

http://qkpic.com/e1e9e

Edited by Timan
you do know the current site is a fixed width by default. You have to know WHAT button to click to make it semi fluid/larger width.

yes... you put that it after the feedback last time and it's worked fine so far. Removing it leads to the dislike seen in this thread.

I don't understand tho, you guys tried this with the last refresh and got a ton of bad feedback about it. It doesn't make any sense for force it again especially as your *still* getting a ton of bad feedback about it. I think those giving feedback understand *why* you want to do it, but at the same time it's kinda fail to just shun off the feedback in favour of the "vision"

Don't forget the views of the silent majority.

Design looks great! Can't wait to use it.

The font in the screen shot that Timan posted (fluid width) seems to work much better than the font in the original screen shot. I actually like the squared design better than the rounded (on Fx) and will use stylish to make it so. I also don't have any problems with the fixed design as i used Fx in a windowed mode.

Awesome work guys!

All in all, it's kind of ironic they haven't recognized that technology has moved forward and everyone either has a widescreen monitor or a high res 4:3 monitor, you know since they're doing a solo crusade to force some browser to ugprade to a work in progress standard.

after all the people who don't use a high res 4:3 monitor or widescreen monitor could use one of the low res device(i.e. mobile) layouts.

So you complain that Neowin disadvantage one type of user by giving them exactly the same experience as all other types of user, but you then suggest that they actually disadvantage a type of user by giving them a worse experience (the mobile skin). I see your logic... I see it, but it's not logical. At least with this fixed-width layout all users are getting the same Neowin experience - no one is getting discriminated against and no one is becoming disadvantaged (you can't call 'extra space at the sides' disadvantaging users when you suggested that some users be given the mobile skin just because they can't afford or do not want a larger monitor...)

It's obvious that you just can't please everyone. Just because larger monitors are now fairly popular amongst the technology enthusiasts, it doesn't mean everybody wishes to maximise their browser window and have it cover the whole screen. I actually see no point in that, especially when most sites tend to be the same sort of width (the width of the current Neowin front page), so surely Neowin can't be the only website that annoys you people by not being fluid? You must get annoyed by a lot of websites... I'm going to get a much larger monitor soon and I am extremely happy that the Neowin developers have designed this new theme with this width in mind because it means I will not have to have my browser window too big and I can have my buddy list, Facebook widget and Zune software (in mini-mode) showing at all times.

This is just my opinion by the way, but I feel strongly about this - I'm getting a bigger monitor so I can do more at once and fit more on the screen, not so I can pointlessly maximise my browser window when I can currently do that just fine, and view all websites perfectly, on my 17" laptop screen...

See I like how InsanelyMac does it. They have the option up top of doing fixed or fullscreen. I am lost as to how a "tech site" wouldn't allow for widescreen monitors.

Here is InsanelyMac.

http://www.insanelymac.com/

See I like how InsanelyMac does it. They have the option up top of doing fixed or fullscreen. I am lost as to how a "tech site" wouldn't allow for widescreen monitors.

Here is InsanelyMac.

http://www.insanelymac.com/

In my opinion that looks awful when using the "full screen" version on my 22" monitor at work (so much white space, logos/search bar positioned horribly), but looks very nice when using the "fixed width" version, on this 22" monitor, with space at the sides. Yes, it's nice they offer that choice because, in my opinion, choice is always a benefit, however, that's because it seems to work for their site (to some extent... it still looks horrible in my opinion). Looking at Timan's screenshot in one of his latest posts, it looks like it wouldn't work for Atlas - loads of white space, the promo image changer only covering half of that section etc.

I'm not speaking for any developers here, but I doubt Timan's screenshot is how the developers would like Neowin to look.

So you complain that Neowin disadvantage one type of user by giving them exactly the same experience as all other types of user, but you then suggest that they actually disadvantage a type of user by giving them a worse experience (the mobile skin). I see your logic... I see it, but it's not logical. At least with this fixed-width layout all users are getting the same Neowin experience - no one is getting discriminated against and no one is becoming disadvantaged (you can't call 'extra space at the sides' disadvantaging users when you suggested that some users be given the mobile skin just because they can't afford or do not want a larger monitor...)

It's obvious that you just can't please everyone. Just because larger monitors are now fairly popular amongst the technology enthusiasts, it doesn't mean everybody wishes to maximise their browser window and have it cover the whole screen. I actually see no point in that, especially when most sites tend to be the same sort of width (the width of the current Neowin front page), so surely Neowin can't be the only website that annoys you people by not being fluid? You must get annoyed by a lot of websites... I'm going to get a much larger monitor soon and I am extremely happy that the Neowin developers have designed this new theme with this width in mind because it means I will not have to have my browser window too big and I can have my buddy list, Facebook widget and Zune software (in mini-mode) showing at all times.

This is just my opinion by the way, but I feel strongly about this - I'm getting a bigger monitor so I can do more at once and fit more on the screen, not so I can pointlessly maximise my browser window when I can currently do that just fine, and view all websites perfectly, on my 17" laptop screen...

Just include a button for it like there is now and everyone is happy.

Noooooooooooooooo! Why do people insist on having all that wasted space on the left and right hand sides? I have a widescreen monitor, I dare say quite a few people here do as well, so let us use that space!

Remember, people read websites in an "F" shape, not a "T" shape =\

I understand the reasonings behind making it easier for the developers, but what about the users? They should be your primary focus.

Just include a button for it like there is now and everyone is happy.

As I have said, choice is always a benefit, but I'm not a Neowin developer so I don't know the ins and outs of the design :p I doubt they would deny users the choice if Atlas looked decent in a fluid manner, but as The_Decryptor pointed out, the design just doesn't lend itself to that, judging by Timan's screenshot. This might not be the reason, but if you'd worked hard designing something which looks really nice, would you like to see it used in a way which, in your opinion, breaks it? :/

but if you'd worked hard designing something which looks really nice, would you like to see it used in a way which, in your opinion, breaks it? :/

I wouldn't care how people use it as long as they are happy. And the users do want the choice myself included. Just add the button there and the discussion is over. And its not impossible to do.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • No, size is not the only selling point. I did not even remotely say that. Your claim was that "building your own will be faster and cheaper". This is false. You cannot build something close to that form factor with off-the-shelf parts. You can build a Mini-ITX PC and pay more, or something larger and pay less. But these are different market segments. It's apples and oranges.
    • There is a default resolution setting in Settings > Display that can be changed with a click. You can also change the settings on a per-game basis. No CLI needed. Also, Steam has countless games that are not "[perpetual] alpha/beta games", so no need for the straw man. Plus you can use other stores as well. And console games (e.g. PS5) cost a fortune, which itself more than negates the price subsidy on the system, unless you plan on exclusively playing 1 or 2 games. It's true that you shouldn't buy a system that doesn't support the game(s) you want to play, but I think that's kinda obvious, and applies to every console as well as PC. I don't game in the living room and have no need of a Steam Machine, but there is a clear market segment that would find it useful.
    • RSS Guard 5.2.0 by Razvan Serea RSS Guard is a simple (yet powerful) feed reader. It is able to fetch the most known feed formats, including RSS/RDF and ATOM. It's free, it's open-source. RSS Guard currently supports Czech, Dutch, English, French, German, Italian. RSS Guard will never depend on other services - this includes online news aggregators like Feedly, The Old Reader and others. RSS Guard is developed on top of the Qt library and it supports these operating systems: Windows GNU/Linux OS/2 (eComStation) Mac OS X xBSD (possibly) Android (possibly) other platforms supported by Qt The core features of RSS Guard are: support for online feed synchronization via plugins, Tiny Tiny RSS (from RSS Guard 3.0.0). multiplatform, support for all feed formats, simplicity, import/export of feeds to/from OPML 2.0, downloader with own tab and support for up to 6 parallel downloads, message filter with regular expressions, feed metadata fetching including icons, simple Adblock functionality, customized popup notifications, Google-based auto-completion for internal web browser location bar, ability to cleanup internal message database with various options, enhanced feed auto-updating with separate time intervals, multiple data backend support, SQLite (in-memory DBs too), MySQL. is able to specify target database by its name (MySQL backend), “portable” mode support with clever auto-detection, feed categorization, drap-n-drop for feed list, automatic checking for updates, ability to discover existing feeds on websites, full support of podcasts (both RSS & ATOM), ability to backup/restore database or settings, fully-featured recycle bin, printing of messages and any web pages, can be fully controlled via keyboard, feed authentication (Digest-MD5, BASIC, NTLM-2), handles tons of messages & feeds, sweet look & feel, fully adjustable toolbars (changeable buttons and style), ability to check for updates on all platforms + self-updating on Windows, hideable main menu, toolbars and list headers, KFeanza-based default icon theme + ability to create your own icon themes, fully skinnable user interface + ability to create your own skins, “newspaper” view, plenty of skins, support for "feed://" URI scheme, ability to hide list of feeds/categories, open-source development model based on GNU GPL license, version 3, tabbed interface, integrated web browser with adjustable behavior + external browser support, internal web browser mouse gestures support, desktop integration via tray icon, localizations to some languages, Qt library is the only dependency, open-source development model and friendly author waiting for your feedback, no ads, no hidden costs. RSS Guard 5.2.0 changelog: Added: Feed auto-fetch can now also be delayed while Feral GameMode is active on Linux and startup auto-fetch is skipped when GameMode is already active. (#2265) WebEngine builds can now use RSS Guard generated proxy auto-config (PAC) rules so article/web browsing follows per-account and per-feed proxy settings more closely. (#2273) Generated PAC rules now also cover related subdomains and use Public Suffix List data, so feeds such as feeds.bbc.co.uk can also proxy resources from images.bbc.co.uk. (#2273) Standard feeds can now define extra proxy domains, useful when article images, stylesheets or other page resources are loaded from a CDN or another domain that should use the same feed proxy. (#2273) RSS Guard now asks for proxy credentials when a WebEngine page needs proxy authentication and can fill credentials from the current feed proxy when available. (#2273) Network settings again include an option to ignore all cookies, which clears stored cookies and prevents new cookies from being accepted. Standard RSS/ATOM feeds can now individually ignore cookies while downloading feed data. Stored cookies can now be deleted from the Tools menu. Custom skin colors can now override the feed list article count color separately from feed titles, including a separate highlighted color. (#2275) Settings dialog can now search across available settings and highlight matching controls. (#1754) Standard RSS/ATOM feeds can now optionally be reported as broken when they are valid but contain no articles. (#2039) Standard RSS/ATOM feeds can now override the application-wide feed connection timeout per feed. (#1023) Tray icon can now use a custom background color and unread-count text color, with an option to reuse the generated icon as the application icon. (#1973) Support for more benevolent parsing of Gemlog entries (#2295). Article list can now show when an article was received by RSS Guard. (#947) Feed deep discovery now actually scrapes all links found in the website and checks if they are feeds or not. This greatly enhances usability of the deep discovery mode and discovers many more feeds than before. (#2306) Search boxes now show a small dot when the feed or article list is hiding some items because of active filtering. (#873) Articles now have a shortcut-assignable action to open the homepage of the feed they belong to. (#2060) Fixed: Parallel feed updates no longer crash when multiple update results are processed at the same time. (64cf521) Links in WebEngine articles opened from feeds such as Kill the Newsletter now open correctly instead of being swallowed by the embedded page. (#2272) Relative article URLs resolution was kinda broken. (#2282) Clicking article URL did not work when the URL had "fragment" set. (#2293) The default proxy setting now uses Qt/system default proxy behavior instead of forcing no proxy. (e0263ad) WebEngine article loading now keeps the current feed context, so feed-specific proxy credentials remain available while the article page loads. (fdd0f00) Download: RSS Guard 5.2.0 (64-bit) | Portable | ~ 130.0 MB (Open Source) Link: RSS Guard Home Page | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • This is gonna separate the creeps from the rest of the crowd.
  • Recent Achievements

    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      461
    2. 2
      +Edouard
      161
    3. 3
      PsYcHoKiLLa
      110
    4. 4
      Michael Scrip
      83
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!