locked
WPF/E Ready for RIA? RRS feed

  • Question

  • Is the plan for the 1.0 version of WPF/E to support RIA or is the plan to support flashy animations only?

    Put another way do we have access (in version 1.0):

    1. To standard controls (text box list box tree view list view buttons etc.)

    2. Http socket of some sort (support GET, POST and nulti-part form data enc type) to get/send data /assets from a remote server. Or is this part done through the existing browser's http socket available via JavaScript?

    Thanks

    Wednesday, March 7, 2007 10:24 PM

Answers

  • To answer the original questions:

    1) Yes, we are working on standard controls and will begin to phase these into the product.  Our initial focus has been on graphics, static text and media as this is the foundation for the rest of our stack.  The current functionality is only the first step with plenty more to come.

     

    2) The Feb CTP supports a downloader component that does HTTP GET requests back to the domain of origin and this is done through the browsers HTTP stack.  We are looking at opening this up to allow secure HTTP GETS to non-same domain servers.

     

    Joe

    Sunday, March 11, 2007 12:21 AM

All replies

  • There is an interesting discussion of this topic here:

    http://donburnett.wordpress.com/2007/03/07/poor-maligned-and-misunderstood-by-many-wpfe/

    I tend to agree to some extent that you can already build most of what you want with the current CTP. There are definately things that fall into the "nice to have" category, but WPF/E on top of ASP.NET and AJAX is a pretty complete RIA platform. Of course there is room for improvement especially in the area of z-indexes and performance, but you can do quite a bit with the technology now.

    Just my $.02...

    Wednesday, March 7, 2007 10:47 PM
  • Building "RIA" with WPF/e is pretty hard right now, but it is very possible (i would know). Most issues people bring up on this forum can be solved right now with a bit of extra coding. Unfortunatly WPF/e got couple holes in functionality that next to impossible to fill with javascript.
    Saturday, March 10, 2007 5:01 AM
  • Thanks for the link.

    Saddly I don't agree with the guys point of view and if there are more folks like him out there then we can simply kiss good bye to WPF/E ever getting to Flex and Appollo at least not for a long time. Demand for more will make this product better, agreeing with everything that's there simply kills it.

     

    Saturday, March 10, 2007 6:20 AM
  • Pray tell how do you know :)
    Saturday, March 10, 2007 6:21 AM
  • To answer the original questions:

    1) Yes, we are working on standard controls and will begin to phase these into the product.  Our initial focus has been on graphics, static text and media as this is the foundation for the rest of our stack.  The current functionality is only the first step with plenty more to come.

     

    2) The Feb CTP supports a downloader component that does HTTP GET requests back to the domain of origin and this is done through the browsers HTTP stack.  We are looking at opening this up to allow secure HTTP GETS to non-same domain servers.

     

    Joe

    Sunday, March 11, 2007 12:21 AM
  • Joe,

    Thank you for your answers.

    So the version 1.0 product will have standard data input controls?

    And the version 1.0 product will have http get/post functionality (same domain is what I'm more interested in, other domains is a plus)?

    The way I understand it, one should be able to access the the browser's http socket for get/post today, correct?

    Sunday, March 11, 2007 5:54 PM