[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

    • I hope this encodes in to AV1 or AV2 as currently tiktok uses h265 and h264.
    • Qualcomm reportedly in talks to build custom video chips for TikTok parent ByteDance by Karthik Mudaliar Qualcomm is reportedly in advanced discussions to provide custom chip-design services to Chinese tech giant ByteDance, the same company behind TikTok. According to a report from Reuters, Qualcomm could be involved in designing custom silicon tailored for ByteDance's massive data-center workloads. If it goes through, the deal would make ByteDance one of Qualcomm's early anchor customers for its fastly growing custom chip-design division, For years, Qualcomm was the king of making smartphone processors and modems. The company has also been moving into the PC ecosystem and other formats such as on-device AI for Android XR headsets. However, this particular deal is about Qualcomm's custom Application-Specific Integrated Circuits (ASICs). For a platform like TikTok, ByteDance needs hardware that can help it ingest, process, and serve billions of short-form videos daily. Generalised hardware is no longer the most cost-effective and efficient route, which is why ByteDance is trying to develop custom Video Processing Units (VPUs). VPUs designed specifically for ByteDance’s algorithmic needs could drastically reduce data-center power consumption and improve encoding speeds at an unprecedented scale. The underlying tech behind these processors is actually from Qualcomm's recent acquisition of AlphaWave Semi, a high-speed connectivity specialist company. By combining AlphaWave’s high-bandwidth IP with Qualcomm’s architectural expertise, the company could begin mass production by the end of 2026, if the talks go through. All this also comes at a time when U.S.-China tech relations have dwindled. Escalating trade frictions between Washington and Beijing have severely impacted the export of high-end AI chips from U.S. firms like Nvidia, AMD, and Lam Research. Yet, the Qualcomm-ByteDance discussions show that U.S. tech companies are still actively seeking growth avenues and are open to doing business with China, where regulators still permit. Reuters notes that the outcome of this deal could be uncertain, and ByteDance might also seek partners other than Qualcomm. via Reuters | Image via DepositPhotos.com
    • Look who's back!
  • 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
      455
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      116
    4. 4
      Michael Scrip
      82
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!