[Feedback needed] Atlas, the next version of Neowin


Recommended Posts

DO WANT THIS THEME!

==============

On a less.. lolcat note, the tags bit should probably be below the story (a la wordpress style), having the tags under the title next to the author name isn't entirely intuitive IMO. Even if you don't move the tags, you should probably put "Tags: Tag1, Tag2, Tag3" instead of just "Tag1, Tag2, Tag3".

I think a public beta is definitely in order :yes:

They should use the standards that ALL browsers support so that EVERYONE gets the same experience when browsing Neowin, segmenting the site users by using elements that not all browsers can render smacks of using iframes back in the 90s that only ever worked properly in IE.

I can't tell if you're being sarcastic here. At what point do you stop supporting everything? IE6? IE5.5? Firefox 1? There's obviously a limit.

In any case, it might be wise to withhold judgement of the skin with non-rounded corners until you've seen the skin with non-rounded corners.

I can't tell if you're being sarcastic here. At what point do you stop supporting everything? IE6? IE5.5? Firefox 1? There's obviously a limit.

In any case, it might be wise to withhold judgement of the skin with non-rounded corners until you've seen the skin with non-rounded corners.

Well you could decide it by what are part of the current finalized web standards, and not the work in progress ones.

as I believe the rounded corners are part of the still not finished CSS3.

That or at least stick to making a site that looks the same in the latest version of all major browsers. if you can't make it looks the same, then your design and/or code is bad.

The CSS3 Backgrounds and Borders module is pretty much finished, it's coming up to last call status and then it's a recommendation.

No spec is ever really "finalised", so waiting for that means you'll be waiting forever (CSS2.1 is still being updated)

The CSS3 Backgrounds and Borders module is pretty much finished, it's coming up to last call status and then it's a recommendation.

No spec is ever really "finalised", so waiting for that means you'll be waiting forever (CSS2.1 is still being updated)

How come below at the footer, it shows Powered by Ignition?

Anyways I love the new theme, I can't wait.

How come below at the footer, it shows Powered by Ignition?

Anyways I love the new theme, I can't wait.

Nah, Ignition is the backend, Atlas is the front end (layout designy stuff)

Hope that helps :yes:

Can we Please stop the ***ching about how it looks in whatever browser?

Why don't you try to open a webpage from South Korea in any browser other than IE and see what happens, then you can direct your lame attitude towards SK for not making their websites work for other browsers outside of IE

:p :p :p :p :p :p :p

Certain Opera and IE users feel oppressed/discriminated I suppose.

Personally I support the developers' opinion on this. As a leading technology site Neowin should be among the first to support web standards instead of resorting to browser-specific hacks.

It's not like the IE/Opera version of the site looks totally horrible (see also Neobond's screenshot above).

What I can't beleive is people are having a cry over something that unless you really payed attention to it, wouldnt even bother you in the first place.

How many of you are going to spend your time on Neowin looking at the corners in IE instead of looking at what the site has to offer in terms of news, articles and/or interviews?

The site could look horrible like it did when it was first conceived (sorry Steve, but it did :p ) but did anyone care? NO - we came because of the content.

Seriously guys, grow up. Corners or not, Neowin is the best tech site on the internet. It's free, it has the best community on the internet as well. If you guys are going to squabble over something that is so remotely not even half interesting, then you have to ask yourself, why are you using a browser that doesn't support web standards anyway on a tech news site?

We all love IE, or at least used to. But now, we have Firefox, Chrome, Safari, and other browsers on the market now which DO support the latest web standards. So I say this to everyone complaining to the devs to make rounded corners work in IE and Opera...

"TOO BAD"

For the devs, awesome work. Everything looks great, even in IE and Opera.

For the complainers, time to complain to MS and the makers of Opera and get them to get with the times and implement a update that does support the latest web standards.

My two cents

:)

I agree with the devs. As a web developer myself, I know it's infuriating to have to put in all the extra markup and CSS hacks just to get something as simple as a drop shadow or rounded corner working in IE or Opera.

Simpler markup also makes the website more accessible for the disabled because screen readers have a much easier time with it. Just look at the way the iPhone 3GS does screen reading: it goes element by element, so if there are links inside of divs inside of unordered lists, it's going to take a very long time to get to the important information in that hierarchy, where as the new markup would go right along the list with ease.

Is it viewable like we can choose our neowin home page style?

No, only that you can choose different colors like Midnight and Green. The other (older/current) themes won't be supported

A while back I thought they confirmed that the new Neowin would have Facebook connect.

It's planned. There are issues with IPB3's implementation of Connect at the moment that are to be resolved, but we're hoping that their bug fixes should get things to the stability level we require.

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!