What is everyone using for thier presentation layer?
-
http://www.hanselman.com/blog/SurveyRESULTSWhatNETFrameworkFeaturesDoYouUse.aspx This was an interesting, fairly big survey of the .NET space at least.
rjempo
That's sort of what I was interested in. Thanks for posting that.
I didn't get any requirements for the signature
-
So where do you perform validation and where do you implement business rules? In the flex UI???
Both IMO. Flex has validation components built in. We also do some in the biz logic layer.
-
Flex is the way to GO. am trying it out ...and yes great WOW factor indeed...thousand pounds of respect :)
That's right, "WOW factor" that's a good phrase for it! :-D
-
Flex is the way to GO. am trying it out ...and yes great WOW factor indeed...thousand pounds of respect :)
My vote is also for Flex, although now that Silverlight is at version 2 there's a lot of great things to say about it as well. RIAs are, in my opinion, the way to go though. Better separation of concerns, better security, real application development environment and languages, incredibly easy deployment, clients are always up-to-date without any effort, the list goes on and on.
-
No, no issues of that sort. I guess I'm not familiar with the terms object graphs and object trees either. Our WCF service just gets LINQ objects, serializes them to an xml string, and hands them to Flex, and then the reverse. It works tremendously well.
-
passing LINQ objects? ;) Is is any different than "array of objects being passed between client and service" (just adding some well known buzzwords WCF, LINQ to impress someone, IMO). How this affects topic about presentation layer :)?
Not I'm not trying to impress anyone. :laugh: :laugh: We're all programmers here right? At least that is what I thought. If a programmer is impressed by a couple of acronyms,. I feel sorry for that guy. If you look at my first post in this thread, I was responding to the thread starter. Then other's proceeded to ask questions so I obliged. :-D
-
The DOS command prompt.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001Good choice! Reliable, consistent, and everyone knows what to expect of it. Three necessary features in any user interface. :-D
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
Good choice! Reliable, consistent, and everyone knows what to expect of it. Three necessary features in any user interface. :-D
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
Roger Wright wrote:
Good choice! Reliable, consistent, and everyone
over the age of 20knows what to expect of it. Three necessary features in any user interface.Fixed that for you. Anyone much younger than that's probably been introduced to the MS world vs win95 or later and unless they have power user tendencies is likely to've never seen the command prompt more than once or twice.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
Yeah, to do any kind of object graphs, also circular references should be possible. The neatest thing that just works without any issues: plain old .NET serialization. I was just curious how to handle it properly in the web services world.
Wout
WCF supports circular references in the object graph that it serializes. However, this option is not on by default. You need to specifically configure the DataContractSerializer to keep track of object references. (I don't recall the exact setting off hand.)
-
WCF supports circular references in the object graph that it serializes. However, this option is not on by default. You need to specifically configure the DataContractSerializer to keep track of object references. (I don't recall the exact setting off hand.)
Does that also generate some special WSDL? That would be nifty.
Wout
-
I have been doing asp.net (and ajax) for a while. While I have taken the time to learn 3.5, WCF and LINQ. I have not invested any energy in learning the new presentation tools. I am just curious if the rest of you have and if so what you are using. Anyone think I am missing out and that I should move away from ASP.Net? Do you use any of the following? ASP.Net (including AJAX) Win Forms WPF SilverLight Other.
I didn't get any requirements for the signature
... how about console? I use that most of the time.
-
I have been doing asp.net (and ajax) for a while. While I have taken the time to learn 3.5, WCF and LINQ. I have not invested any energy in learning the new presentation tools. I am just curious if the rest of you have and if so what you are using. Anyone think I am missing out and that I should move away from ASP.Net? Do you use any of the following? ASP.Net (including AJAX) Win Forms WPF SilverLight Other.
I didn't get any requirements for the signature
PHP + HTML + JavaScript + CSS + Flash + Actionscript I do use asp.net, but I find PHP more versatile for the web, and I am far more productive with it. But what I use depends on what the app is for (and might require in the future). Had a look at silverlight and the expression suite and was quite impressed. I noticed a lot of similarities with flash (although the designer/developer interfaces are, of course, very different). XAML is very promising, but the designer interfaces, of Microsoft Expression Blend, aren't very intuitive. If you would like to look at an alternative to microsoft, I would suggest the following as a starting point: Developing Server: Xampp (Linux) http://www.apachefriends.org/en/index.html[^] Interface Design: The Adobe Suite (especially flash, photoshop and dreamweaver) http://www.adobe.com/products/creativesuite/[^]
-
I feel sorry for you. The last time I had to work with that I wanted to quit my job.
Mike Lasseter
I used to work for DataMax/RFGen, so it comes easier to me now than perhaps for you. It's very much a tool which lends itself to designing apps using machine state logic.