Recommended Posts

I think his point was that OpenOffice can do most of what Office 2007, for infinitely less price wise. For opening documents, it'll do just fine. For hardcore business people who make documents for a living, Office 2007 would be much better, but it's a few hundred dollars more than OOo.

yes i really digg openoffice 3 over office 2007. it's faster, does pretty much everything and it's free. office 2007 seemed pretty slow to me.

You're dead on right.

The good news is DirectWrite will solve this and finally bring great Asian font rendering to Windows. (see the demos in Neowin's PDC coverage for examples, or pop on the Engineering Windows 7 blog)

The bad news is almost 90% of today's apps which use GDI will still continue to have crappy arse fonts. :/

Even on Linux, the font rendering is a bit sketchy for Western fonts, but Asian fonts look damn good.

(side note: I can't write in Chinese, though that's my background. But there's a handful of people on my contact list who do use Asian fonts, and they look ugly.)

edit: Here's an example. Take a look at the font rendering on the icon's previews.

post-99705-1228871807_thumb.jpg

That is how it should look all the time, is there a timeframe on Directwrite? I'd assume it'll take quite some time to implement into Windows?

The good news is DirectWrite will solve this and finally bring great Asian font rendering to Windows. (see the demos in Neowin's PDC coverage for examples, or pop on the Engineering Windows 7 blog)

Why do we need DirectWrite and Direct2D API? I thought WPF was already vector, hardware accelerated and able to define pixel tight lines (so a line doesn't look blurry if it is 1,5 pixels wide).

wpf_apps_are_vector_based_and_can_be_zoomed.jpg

Why do we need DirectWrite and Direct2D API? I thought WPF was already vector, hardware accelerated and able to define pixel tight lines (so a line doesn't look blurry if it is 1,5 pixels wide).

wpf_apps_are_vector_based_and_can_be_zoomed.jpg

Because not everybody can or wants to write managed code.

Why do we need DirectWrite and Direct2D API? I thought WPF was already vector, hardware accelerated and able to define pixel tight lines (so a line doesn't look blurry if it is 1,5 pixels wide).

wpf_apps_are_vector_based_and_can_be_zoomed.jpg

Full screen zoom in Windows 7 gives pixellated output even for WPF apps. I hope they'll consider adding in a billinear filter to make the zoom as smooth as those found on OS X/Compiz Fusion.

yes i really digg openoffice 3 over office 2007. it's faster, does pretty much everything and it's free. office 2007 seemed pretty slow to me.

Problem with Office 2007 is MS attempt to do everything with it. When you create email message it gets created in html format. For simple text you get such crappy html code...pages of crap ms puts in there.

Here's something I personally would love to see done with WMP12 - make the mousewheel functional. Right now, in almost all other media players (Media Player Classic/Home Cinema, VLC, etc) scrolling the mousewheel changes the volume, which might not seem like a big thing to a lot of people, but it's so tremendously useful sometimes. Instead of giving an app focus and then having to go cursor to volume control, you'd save the last step just giving the app focus and rolling the wheel up or down as required.

Yes, I do have a keyboard with volume controls on it, but but but... the mousewheel is there for a reason, and other media players put it to very good use, so why not WMP this time out...?

Heres something that I would love to see implemented.

The "BRAND" New UAC Dialog.

When you launch a new program, that needs privileges, there is a tick box saying []Would you like to save this configuration

If you tick it, and press yes then it always launches in Elevated under the .exe . BUT. I know your thinking, viruses could manipulate this program and make it so it launches the virus code.

If microsoft implemented some kind of check (etc. MD5) every time it ran, if it matched the original dialogs MD5 then it will run without the prompt and if it doesnt then it will launch the UAC prompt. It also needs to be in the exact place for it to pass.

Heres something that I would love to see implemented.

The "BRAND" New UAC Dialog.

When you launch a new program, that needs privileges, there is a tick box saying []Would you like to save this configuration

If you tick it, and press yes then it always launches in Elevated under the .exe . BUT. I know your thinking, viruses could manipulate this program and make it so it launches the virus code.

If microsoft implemented some kind of check (etc. MD5) every time it ran, if it matched the original dialogs MD5 then it will run without the prompt and if it doesnt then it will launch the UAC prompt. It also needs to be in the exact place for it to pass.

As bulletproof as that sounds, it wouldn't be that hard to get past those security measures.. MD5's can be faked fairly easily.

Is it just me, or does the Start Button look completely unimportant?

It doesn't look completely unimportant, but I sort of agree. In terms of appearance, the Start button has been pushed a bit into the background, starting with Vista, and now Windows 7.

I like how it looks in Vista. It's not as prominent as it used to be with the huge word, "Start", but how it sort of sticks out a little bit over the taskbar makes sure it isn't completely lost.

For new computer users, it's definitely less discoverable, since there's no longer a completely obvious place to, "Start" using the computer, and this is probably going to carry over into Windows 7 as well, but I think it isn't any harder to become familiar with than any other interface.

Here's something I personally would love to see done with WMP12 - make the mousewheel functional. Right now, in almost all other media players (Media Player Classic/Home Cinema, VLC, etc) scrolling the mousewheel changes the volume, which might not seem like a big thing to a lot of people, but it's so tremendously useful sometimes. Instead of giving an app focus and then having to go cursor to volume control, you'd save the last step just giving the app focus and rolling the wheel up or down as required.

Yes, I do have a keyboard with volume controls on it, but but but... the mousewheel is there for a reason, and other media players put it to very good use, so why not WMP this time out...?

As opposed to how the mousewheel already is functionally used for scrolling the library?

You named two library-less players as comparison. "Scroll in view" is the default logic for what a scrollwheel does. If you somehow decided that the mousewheel should *not* activate those slider bars, you'd rightly leave people very confused about the noncohesive design.

It doesn't look completely unimportant, but I sort of agree. In terms of appearance, the Start button has been pushed a bit into the background, starting with Vista, and now Windows 7.

I like how it looks in Vista. It's not as prominent as it used to be with the huge word, "Start", but how it sort of sticks out a little bit over the taskbar makes sure it isn't completely lost.

For new computer users, it's definitely less discoverable, since there's no longer a completely obvious place to, "Start" using the computer, and this is probably going to carry over into Windows 7 as well, but I think it isn't any harder to become familiar with than any other interface.

When I say "completely unimportant" I mean in context with other Taskbar items. Everything has been made bigger and bolder, but the Start Orb has just been left. Nothing about it says "Click here to start" - the only visual clue that it's special comes when you hover over it, by which time it's already been clicked on. In Vista, it sticks out and has a kind of glass bubble look, but in Win7 it just looks dull (and squashed) compared to the rest of the Start Menu.

When I say "completely unimportant" I mean in context with other Taskbar items. Everything has been made bigger and bolder, but the Start Orb has just been left. Nothing about it says "Click here to start" - the only visual clue that it's special comes when you hover over it, by which time it's already been clicked on. In Vista, it sticks out and has a kind of glass bubble look, but in Win7 it just looks dull (and squashed) compared to the rest of the Start Menu.

The position of it, still indicates it's importance. Fitt's Law assures us of that.

However, with the this new taskbar and quick launch system, the importance of the start menu is decreased.

How so (I'm not arguing, but would actually like to know!)?

http://www.xvsxp.com/interface/fittslaw.php

Screen corners guarantee an 'infinite' target with almost no precision or dexterity required. Just move your mouse mindlessly in one direction and click.

Nope, you can't move the icons to the middle or far right of the task bar and lock them there. :)

You can if you fill the taskbar with icons, can't you? ;)

I know what you are saying though, it might make more sense to let us move the icons to the middle (or right) if we wanted. It would make the taskbar tidier to have the icons centre aligned, I reckon :)

Nope, you can't move the icons to the middle or far right of the task bar and lock them there. :)

Woops, that was a mistake. I meant that you can move icons into the taskbar, but, you're right, you can't lock them anywhere.

If the items were locked to the center of the taskbar, then in terms of appearance if really would be something like a dock. :laugh: .

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

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!