I have a upload page done with classic asp and I want a progressbar.
Could be with jquery, ajax?
Does anyone know where I can find a solution, thanks.
You cannot upload files using AJAX nor report the progress with javascript. There's a jquery upload plugin which supports this functionality and uses Flash behind the scenes to perform the upload and progress report.
Try looking at http://valums.com/ajax-upload/ It doesn't use flash (it is all based on DOM and javascript) and the upload script part can be adapted to any language (classic asp as well).
Old post, but maybe still interesting:
http://www.motobit.com/help/scptutl/upload.asp
Is using a com component, works with classic asp. But this costs a few bucks (so it is commercial) and no, me are not related to this company, just a pleased customer.
Related
I have to develop a phone application on every platform so I thought of using phonegap. Seems pretty nice.
I have a web application coded in classic Asp and it's this webApplication that I need to strip down to be a phone app.
At first I thought it will be simple, my classic Asp render some html so phonegap is able to put it as an app.
But it's not that simple, because in my asp I have some code that is rendered server side, I've talked to some who tell me that some html could call the asp pages and this html could be used in phonegap. Don't think it's possible ...
Well if someone could help me here, maybe i've said something wrong in my little text don't hesitate to correct me :)
My solution (I think) : code some webServices in asp.net that will use the same database as my asp classic web application. And some html and jquery will call the webservices and those html and jquery will go trough phoneGap
What is the best way to transfer and asp classic web app to a multiplatform phone app ?
EDIT : After looking everywhere, effectively phonegap can't use asp pages. So I'm questionning myself should I do a mobile website or a mobile app with webservices?
EDIT 2: I'm going for an asp.net mobile website, someone have a great way to do this, I've seen the answer proposing mvc... more details?
You are on the correct path in wanting to use PhoneGap to create a multi-platform phone app via HTML5, and some mobile framework like jQuery Mobile.
Yes, you can leverage the power of ASP.NET to serve up your data but I wouldn't create an asmx web service. A SOAP-based service serving up XML may be too fat/overkill for your mobile web app. Instead, you may want to investigate using JSON which is more lightweight (remember, bandwidth is a concern with mobile apps). One can rapidly create an API to serve up your JSON data via the new ASP.NET Web API. With your API exposed, you can make an ajax call from your html page to retrieve the JSON and bind it using jQuery.
The bonus to using the ASP.NET Web API would be when it's time to upgrade that classic ASP web site you have there, you could leverage the API you already created.
I'd really consider rewriting the website using Mvc.Net. You may want to consider using the iUI for the views.
It will be much cheaper long-term to use modern technology than trying to shoe-horn legacy code into new usage areas.
It looks like you've made up your mind to go with a webapp instead of native apps via PhoneGap. I would recommend that you pick up this book by Jonathan Stark. It's very short - shorter than it should be when it gets into using PhoneGap - and although it focuses on iPhone development, much of the content is applicable to most mobile devices. The first few chapters give a great introduction on developing attractive, responsive, highly usable web apps for mobile devices. If you familiarize yourself with jQuery and jQTouch you can get some really great looking apps with relatively little effort, regardless of the server side technology you go with.
So i'm questionning myself should I do a mobile website or a mobile app with webservices ?
The answer to that question is always mobile website... given an outdated website that the client is wanting duplicate functionality in an app.
Do the work to convert the website or at least the portions that you need to use ajax and webservices. Once you have that in place pulling the same data to place in a mobile app will be easy... you've already done it once.
So my approach would be to convert this dataview into two separate elements Data and View.
You can probably even keep the current asp pages without a lot of modification to the code since you can still call these web-service functions the same way as before in your asp code.
Well, if you really want to reuse your existing webpage you can do the following.
Create a index.html and the body.onload event, redirect to your webpage.
Then build this index.html with phonegapbuild, and you will get your "native" application that simply loads your existing webpage.
If you want to serve mobile users, you have 2 main options:
Create a mobile website. You can render html on the server all you want, no javascript programming needed. Maybe look into jQuery mobile, it can be a cheap and easy way to make the website better for mobile users.
Create a html web app (and package it inside PhoneGap if you want). This is basically a html page which loads just the data from the server in json format and updates the page contents dynamically with javascript. You need good js skills to implement this, you're server is just a REST api that server json - technology can be anything, at least asp.net mvc makes it easy. On the client side you'll want to use some good structuring frameworks, backbone.js ( http://documentcloud.github.com/backbone/ ) is a good option. Check out http://m.linkedin.com for an example of what a mobile web app can be.
3rd hidden option: just create a native app for each platform, that'll get you the best user experience.
Does someone can help me to understand WHERE to collocate Gwt compared to (for exmaple): asp.net or jquery ?
Does it only a toolkit client side, server side or... ?
I'd like the "final product" written with GWT but i'm an asp.net developer.. can i integrate asp.net with GWT ?
AS you can see.. i'm little confused about it!
I believe that the idea is that with Google Web Toolkit (GWT) you write in Java, but the output is JavaScript, therefore you would just need to include the JavaScript output in whatever project you are using in order to have the "deployed" version of your GWT code available.
I'm not sure why you'd use GWT with asp.net rather than crank some jQuery to sit alongside your asp.net pages. That's more of a subjective subject.
Since GWT is able to retrieve JSON data, you are free to integrate it with ASP.NET web site. But GWT is all about Java, I can't see any reason for ASP.NET developer to use it.
In case if you want to utilize it's UI widgets, you can try jQuery-UI, ExtJS or Yahoo UI client-side libraries.
Check out Morfik, it allows to build ajax apps with C#
The title pretty much says it all. I have a project that for political reasons cannot be moved to a later version of .Net and would love to have a drop-in control for uploading files better than the old FileUpload control.
I'd like to use the AsyncFileUpload control, but it's not in the latest version of the toolkit that is supported in the 2.0 framework.
I've looked at some of the flash based controls, but integrating them would trigger a full regression test of the project I'm on (multiple weeks).
We've lived with the FileUpload control because our files are small, but the error handling when a file gets larger won't be unacceptable much longer.
-- EDIT --
I just found Uploadify. At first I didn't think it would work, but I checked out the forums any way. I found this link http://www.uploadify.com/forum/viewtopic.php?f=7&t=142&p=8620&hilit=asp.net#p8620 It works great. I can do whatever I want to in the upload handler.
I'm adding this as an answer for whoever follows:
I just found Uploadify. At first I didn't think it would work, but I checked out the forums any way. I found this link http://www.uploadify.com/forum/viewtopic.php?f=7&t=142&p=8620&hilit=asp.net#p8620 It works great. I can do whatever I want to in the upload handler.
Ok so we have an upcoming development that will involve a level of off line processing of dynamic forms. Here's what we have to do:
Create a asp.net web application whereby users can download dynamic forms, fill them in then upload them to be published.
We also have a windows mobile application that will do something similar.
The forms will requires images to be selected for uploading when publishing.
Upon publishing the completed form certain server side validation needs to occur which may trigger additional work to be done i.e. send out emails or update a database etc.
From what I know of InfoPoint (which is next to nothing) it seems like it may be a nice fit. I know its quite highly tied to SharePoint (which again I know nothing about), but can it be used without a SharePoint instance?
Either way, I am just firstly looking for validation that InfoPath is a good fit for what I describe. If it is the I am also after some good online resources.
Thanks in advance, Chris.
I don't think that there is an InfoPath client for mobile devices. What you would want to do is use Forms Server (comes with SharePoint 2007 Enterprise edition) to render InfoPath forms as aspx to the mobile device.
Everything else you describe could be done with straight ASP.NET and the InfoPath client. The mobile piece sounds like it will require SharePoint (for rendering the InfoPath forms as aspx).
See this blog post on using Infopath forms on mobile devices: http://blogs.technet.com/vik/archive/2008/02/25/filling-out-infopath-forms-on-windows-mobile-devices.aspx
Also the Formotus solution may work for you: http://www.formotus.com/
Before delving into whether or not InfoPath (+ SharePoint) is the right solution, what's the reason for not using ASP.NET with which I assume you are familiar? While InfoPath + SharePoint is sexy and hot right now, the learning curve is very high.
Back to InfoPath, I don't believe InfoPath supports uploading files. At least not out of the box. So if having your users upload images is a requirement, I'll say infoPath is out. Apart from that, InfoPath, with the addition of SharePoint Forms Services and workflow, can be used to accomplish what you want. I just wonder what the cost would be versus using straight up ASP.NET.
I have been rather successful in promoting JQuery within my organization. No small feat on it's own. However, one of the ideas being kicked around here to make it part of our app is to create an ASP.net server side control. (We are going to be sticking with WebForms for the foreseeable future.)
I'm not too wild about this approach as it seems like overkill when a couple of script tags will do the job. We found an article on the web, and the amount of code involved really doesn't seem to justify itself. However, I do hear that there is some benefit in the script caching or generating that happens with the server controls.
My questions:
Has anyone else written an ASP.net server control to serve up the JQuery js code?
Does anyone else think that this is a crazy idea to just avoid writing JQuery or Javascript code?
I know Microsoft (along with Nokia) is "mainstreaming" jQuery and will be integrating it with future versions of Visual Studio. You may want to explore how they'll be officially using it so you can tailor your setup now, and hopefully ease your transition to "official MS jQuery" down the road.
I agree with you. It is not worth the time to create and overhead to create a control to make to add a JQuery script location.
A better solution would be to have 1 .js file that has all the links required to load on the page. That could eliminate allot of .js links, if that is the issue with the team.
The only time I would excuse creating a custom control to just link JavaScript would be for whatever reason you did not want to copy the JavaScript to the server and want to be embed it into the .dll. However you will not stop people from seeing the JavaScript on the page because if you embed the files in the .dll you must register them in the header as the full script file.
One reason for using a server control for injecting the JavaScript reference is that it is easier to control which JavaScript files get added to a page. Imagine a scenario where you use jQuery core, plus jQuery UI and a handful of other plugins. Depending on how you coded this control, you could allow a developer to easily choose which features were needed for a specific page without worrying about the specific scripts needed. This approach would allow you lots of flexibility for segmenting your application: for example the server control might be used by a master pages, a child page, user controls or another server control. If the master page registered a requirement for one jQuery library, but the child page or one of the user controls requires additional libraries, then having a unified API makes this simple. Personally, I believe this is best handled by a helper library rather than a server control.
The bottom line is how much you want each developer re-inventing the wheel or using a common, simple to use API which enforces uniformity across your apps.
I found Scott Hanselman's blog post with a sample app that has ASP.net AJAX + JQuery. It's a simple app, but it includes all the javascript with script tags. I don't see any advisement to use a server control to serve up the scripts.