As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I am building a web application that have several requirements for the client:
1. It should be one page (web app).
2. Contains complex UI elements (that I need to draw/create).
3. Support client side coding (data comes from 3rd parties and needs to be rendered in the browser.
I was leaning toward Vaadin but I'm not sure it is flexible enough for #3.
I don't care too much about the server side, I have a Tomcat server with servlets that provides all the data needed to be rendered (besides the data taken from other server).
I do care about the client side, but have zero knowledge in JavaScript.
My last web client was a complex Flash application, and Vaadin simply seems the "closest" way.
To conclude Given this info should I go with a Vaadin (or Wicket) solution?
Or invest time to really learn HTML5/JavaScript/CSS and build my UI in a conventional way?
(with possible help from Backbone/Ember/jQuery and/or any other)
Thanks
I think you should get started in HTML, CSS and JavaScript. The skills are very transferable and it is easy to get started (although there is lots of depth in these areas, so you'll never stop finding new things).
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
When is it better to have multiple views in something like MVC, as opposed to a single view via something like Prototype calling a Web API? It seems like in terms of UX, the single-page app with AJAX calls will always be better.
MVC is an architecture approach that separates the view from the model and connects the two via a controller. It is used to separate concerns that may have different audience and life-cycles. It applies to Web applications and other types of user-interface applications as well such as desktop, thick client and rich client apps.
As the comment says, a single page with a Java applet, Flash movie or Javascript/AJAX is not mutually exclusive with MVC. Your view is in the page, the model will most likely be on the server if you are using AJAX, although it may be within Javascript if the AJAX is purely for persistence to a 'dumb' data store.
So, you can have full MVC within a Javascript application and most frameworks are designed that way. Maybe your question was a comparison between web page to server controllers as compared to controllers in Javascript within the page?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am trying to write applications for iPad which take advantage of web services. I know the concept of a web service and have used it in C#/.NET. I need to know how to do this on an iPad. Can anyone recommend a good book or reading material on webservices for iOS?
If you're using iOS frameworks, your solution will involve using NSURLConnection or NSRLRequest. In-depth Apple documentation can be found here. In my experience, you want to wrap those API calls in your own client request that can build data transfer objects your application logic understands.
If you're looking at 3rd party frameworks to access a RESTful web service, take a peek at this answer for a number of iOS framework options.
For SOAP services, take a look here.
As for processing the data, it depends what kind of data your web service produces. There are several frameworks and libraries that can make it easy to consume XML or JSON.
In my experience, the best book on the subject is Advanced iOS Programming.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 12 years ago.
I am starting a website and am wondering if I should go with PHP, a php framework, or ruby on rails? I want to make a website fast, easiest and without a big learning curve. I already know a little bit of php and a little ruby on rails...But which would be best?
OK so to clarify more on the topic of what my site will be, It's basically a Classified Ads website that needs to have a user login, ability to post classifieds, and categorizing, and basically anything else a classified website has.
I would put my vote in for Rails. It's easy to get started building a website that requires persistence in a database, and there are many websites that host the framework. I agree with #Squeegy that PHP is great for sprinkling dynamic content into an otherwise static page, but it sounds to me that you want something more involved, so I would go with Rails.
Start with anything you know better.
PHP is great for sprinkling bits of dynamic content into a website. Given your requirements "fast, easiest and without a big learning curve" I think PHP would be ideal.
Now a large and more complex site, that would be much better suited to a framework. But with any framework also comes steep learning curve.
Codeigniter.com, try it out, it rocks.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I need to add a real time dashboard of data to a ASP.NET MVC application. The dashboard needs to be refreshed every few minutes from SQL server 2008. I was going to use ASP.NET MVC, with jQuery and AJAX. But Silverlight 3 is a possible option (each client has Silverlight 3 installed). I know WPF, is it worth the jump to SL 3 for this?
A dashboard is an excellent use of Silverlight. You can create some terrific looking UIs and it can be used to create a very compelling visual experience. Charts and gauges will pop off the screen. Your data will look incredible.
There is a learning curve when developing your first Silverlight app so make sure that you're clear on what the final product will be. If the requirements are well defined, you'll be able to determine if you think it is something that you and your team will be able to achieve.
For a dashboard, I think a JQuery solution works best and that is the direction I would go in. I'm still a little unsold on the long term future of Silverlight compared to the AJAX/HTML 5 future.
I would only go to SL 3 under one of the 2 scenarios below.
You need a rich UI experience (ex. fancy charts, graphs, etc..) that WPF/SL will help you achieve easier. If the user interacts with the dashboard, then that makes it a good candidate
You want to learn SL 3 or want your team to learn SL 3
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I think the best part of flash is the possibility to create not squared user interfaces, so I like the idea to create desktop apps using flash. I know AIR is for that but it doesn't allow real access to OperatingSystem apis and dlls and the commercial options are kind of difficult to customize.
You can try ScreenweaverHX:
http://haxe.org/com/libs/swhx
It's the Haxe-based successor of the old Screenweaver. However, it's not as simple as the old version used to be. Most likely you need to take a look to the basics of Haxe and Neko, the 2 technologies it's based on.
There's another project on top of SWHX that it's called HippoHX. It aims to "complete" SWHX providing that extra functionality you might miss (simple ActionScript APIs and a GUI). However, it's in its early stages:
http://hippohx.com
DISCLAIMER: I'm the owner of HippoHX, so my point is obviously biased.
As far as I know SWHX is the only Open Source alternative at this point.
Try flajector. it's powerfull converter from flash to exe. You can to develop your application using AIR. And then you can convert it into desktop application .exe