Gelmiş geçmiş en büyük porno sitemiz olan 2pe de her zaman en kaliteli pornoları sunmayı hedefledik. Diğer video sitemiz olan vuam da ise hd porno ağırlıklı çalışmalara başladık.

  1. #171
    Sencha User
    Join Date
    Jan 2008
    Location
    Toronto, Canada
    Posts
    480
    Vote Rating
    4
    elishnevsky is on a distinguished road

      0  

    Default


    Quote Originally Posted by mkidder View Post
    Eugene,

    I stumbled onto your project after a long hiatus from ExtJS. Absolutely wonderful work.

    Do you have a timeline for MVC2 release, I saw you mention that it will be coming soon?
    Thank you! No, I don't have a specific timeline for MVC 2.0 yet. I have started looking into converting the project, but it can take some time, because I am extremely busy at work lately.

  2. #172
    Sencha Premium Member
    Join Date
    Sep 2008
    Posts
    710
    Vote Rating
    6
    Bucs is on a distinguished road

      0  

    Default


    From what I understand, the newer features of MVC2 relate more to the View and rendering controls than anything else. So if you're using the 1 page app model and having the UI rendered from ExtJS files, then you don't really need most of that imho and MVC 1.x should be plenty. Unless of course you are using the View to generate the JS/HTML, then maybe it would be useful. Other than that, what is in the 2.0 version that you would really need? I'm curious as I haven't looked in depth at it.

    Thanks...

  3. #173
    Sencha User
    Join Date
    Jan 2008
    Location
    Toronto, Canada
    Posts
    480
    Vote Rating
    4
    elishnevsky is on a distinguished road

      0  

    Default


    I agree with you almost 100%. When the client-side is written entirely in Ext JS, there is nothing new and revolutionary in ASP.NET MVC 2.0, that you can benefit from. We are using MVC 1.0 at work and not planning to move to 2.0 even after it is released. However, people have a choice and should be able to use Ext.Direct with MVC 2.0 if they want to. I was working on the changes required for it last night and I am happy to say, that I am nearly done. I will let you all know, once I am finished.

  4. #174
    Sencha User
    Join Date
    Jan 2008
    Location
    Toronto, Canada
    Posts
    480
    Vote Rating
    4
    elishnevsky is on a distinguished road

      0  

    Default


    Released v0.9.0 - Major update!

    Latest changes:
    * Changed configuration requirements. Made it much easier to configure. Setting apiUrl and routerUrl config options is no longer required and should be deleted from Web.config of your web project. The API path is now hardcoded to "/Direct/Api" and Router path is "/Direct/Router", and cannot be changed.
    * Removed DirectHttpModule class, it is not needed anymore. So the related lines in Web.config file of your web project where you register this module should also be deleted.
    * Removed DirectMvcRouteHandler.cs and DirectMvcHandler.cs - they are no longer needed either.
    * Support for ASP.NET MVC 2.0 RC
    Ext.Direct.Mvc Homepage

    Please read the documentation about how to configure and use Ext.Direct.Mvc.

  5. #175
    Ext JS Premium Member
    Join Date
    Mar 2007
    Location
    NL
    Posts
    607
    Vote Rating
    1
    mdissel is on a distinguished road

      0  

    Default


    Thanks for the update!
    Two remarks:
    - new /Direct/Api url...that's only possible if you configure asp.net to handle all requests.. why not /Direct.ashx/Api?
    - debug is optional, but why not remove it completely and follow the system.web/@debug entry.

  6. #176
    Ext User mkidder's Avatar
    Join Date
    Mar 2007
    Posts
    27
    Vote Rating
    0
    mkidder is on a distinguished road

      0  

    Default


    Eugene, WOW that was quick!! And a very nice refactoring as well.

    Quote Originally Posted by mdissel View Post
    Thanks for the update!
    Two remarks:
    - new /Direct/Api url...that's only possible if you configure asp.net to handle all requests.. why not /Direct.ashx/Api?
    - debug is optional, but why not remove it completely and follow the system.web/@debug entry.
    @mdissel - The addition of DirectController makes use of the MVC framework, negating the need for a separate HttpHandler, does it not?

  7. #177
    Sencha User
    Join Date
    Jan 2008
    Location
    Toronto, Canada
    Posts
    480
    Vote Rating
    4
    elishnevsky is on a distinguished road

      0  

    Default


    Quote Originally Posted by mkidder View Post
    Eugene, WOW that was quick!! And a very nice refactoring as well.
    @mdissel - The addition of DirectController makes use of the MVC framework, negating the need for a separate HttpHandler, does it not?
    That is correct.

  8. #178
    Sencha User
    Join Date
    Jan 2008
    Location
    Toronto, Canada
    Posts
    480
    Vote Rating
    4
    elishnevsky is on a distinguished road

      0  

    Default


    Quote Originally Posted by mdissel View Post
    Thanks for the update!
    - debug is optional, but why not remove it completely and follow the system.web/@debug entry.
    Some people have asked for ability to return full exception even in release mode.

  9. #179
    Ext User
    Join Date
    Feb 2010
    Posts
    3
    Vote Rating
    0
    pnrrth is on a distinguished road

      0  

    Default Override for Router URL

    Override for Router URL


    Thanks for providing a great library. It has saved me a lot of time and it works great.

    I have a simple feature request: the ability to change the url for the Router. Currently it is hard-coded to generate Direct/Router. I am deploying an app in an environment that is forcing me to use Classic Mode in IIS. Because of this, I am having to append .mvc to all the controller names in order to get IIS to route these requests to ASP.Net as opposed to trying to serve up static content.

    I was able to modify my main site page to include ~/Direct.mvc/Api, however subsequent calls to retrieve data still go to /Direct/Router, as opposed to /Direct.mvc/Router

    I rebuilt the source code to include an additional parameter in the web.config that will allow an alternate url for the router. If you could include something like this in a future release, that would be great, then I wouldn't have to rebuild the solution each time

    Here is a reference for getting MVC to work in Classic mode (thus requiring the .mvc extension on controllers)

    http://www.asp.net/LEARN/mvc/tutorial-08-cs.aspx

  10. #180
    Sencha User
    Join Date
    Jan 2008
    Location
    Toronto, Canada
    Posts
    480
    Vote Rating
    4
    elishnevsky is on a distinguished road

      0  

    Default


    pnrrth

    I don't have much time to look into this. Can you please post your fix here? I'll see if I can add it to the library.
    Thanks.