Discussions

Sourcecode: In my honest opinion, I'd take Flash/Flex over Sparkle anyday. Why? Cross-platform compatability. Flash applications run anywhere, from OS X, Linux, to Windows. That's my major reason for sticking with Flash. I tried the Sparkle CTP, and I wasn't really impressed.

Some of the UI elements are neat, like skewing, resizing, and otherwise manipulating shapes by clicking on them and dragging around their outline. I also thought it was a step in the right direction for replacing GDI+, and a great way of making Windows (desktop) applications. Am I ever going to design a site with it? Hell no, nor will I ever recommend it to anyone, unless it becomes as extensible and as cross-platform as Flash. That's why Flash Player has such a high market penetration level, it runs anywhere.

Besides, Flash can do everything Sparkle can, with the exception of Direct X powered 3D. Given that most of our users don't have a GeForce 7800, I don't think this will be a big problem.

In Sparkle's defense, the UI is a tad bit more intuitive than Flash. I say "a tad" because I got used to working with Flash's (authoring) UI, so when it comes to the UI, I'm "a tad" biased.

Well, that's my two clams!

manojT: I'm positive Visual Studio doesn't read the SWF (or FLA) and read dependencies. I normally keep all dependant files in the same directory as the master FLA.

As for getting dependencies using .NET code, I believe that won't be very easy either. You'd have to (1) understand how FLA files are structured, and (2) the only way of talking to a SWF in WinForms is using the Flash Active X control, and that'll surely get you nowhere.

Another way of checking for dependant files is to create a Flash Project file (.FLP file), then adding all the dependant files inside of the FLP. That way, if one is deleted or moved, Flash will notify you.

I like their language. I can't even begin to guess what they're saying!

Woo! Nice set o' screens. I used to have two monitors until I got my Zonet KVM switch! I have one Windows workstation and a Linux (Novell SuSE) testing server. Making sure stuff runs in both worlds is a big thing for me!

If your development team consists largely of .NET developers, then MSDN Pro would be very helpful. You'll get the newest versions of Visual Studio, get to test software before it's released, etc. If you don't need all those fancy servers, then go with MSDN Professional.

arunpv wrote:

What do they trying to prove... Google stick to your Ad---Sense and Search leave the rest to seasoned players(M$), let Microsoft figure out the WINFX or WEBFX File System with tons and tons of bugs in it and release Service pack 1,2,3,4..........

I would rather have my data with me but i am ok if the Software which i want to use are on a GFileSystem.

Are you saying that Microsoft's filesystems are prone to bugs, while Google's may be more ironed-out? (I had a hard time understanding you, sorry! )

If so, I would agree. Microsoft's new filesystems will probably have its share of bugs, and there might be people who would preferr not to use them.

What I would really love is that Microsoft implement support for other filesystems into Windows, such as ReiserFS, EXT3, or even FTPFS. Now don't get me wrong, I know those filesystems have their own issues, but it would just add more "freedom" to Windows.

But the big question for me is: Can I trust a 3rd party with my data?

I use Google Desktop, and I feel thats as far as I want to go with trusting my data with Google. For website hosting, the infrastructure Google has would be neat.

I'm sure he means RSS vs. HTML, eh?

Coolzor.

Tensor wrote:

WinFX = avalon.
ATLAS = AJAX-like things for ASP.NET.
LINQ = Language Integrated Queries. You should find a vid on this if you are a c# / vb developer. Its sweet.

Ah, thanks! I new wat WinFX was though; I should've been more specific. [Edited. I just remembered what the CTPs are. I'm a dork, excuse me whilst I go drool on myself.]

(Maybe I should just go hunt around for videos! )