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've used ASP.NET MVC before and now I'm looking into Backbone.js.
How a project should be structured? That is in ASP.NET MVC you can create separate files for Model, View and Controller code and there is true code separation. How do I achieve that with Backbone.js, do I just create a series of JS includes and position these in my home page index.html file?
Backbone does not impose any specific organizational hierarchy on your application structure.
So yes, you are free to set up your application structure in whatever way you want. As far as separate files are concerned, you can definitely have (and I'd recommend you to do so) your models, views etc. in separate files. If your application is getting large with several files checkout a javascript dependency managemer/module loader eg. Require.js
If you are looking for something more structured and opinionated you might take a look at one of the meta frameworks built on top of Backbone eg. Chaplin : http://chaplinjs.org/
Quoting from the Chaplin site :
Chaplin is an architecture for JavaScript applications using the
Backbone.js library. Chaplin addresses Backbone’s limitations by
providing a lightweight and flexible structure that features
well-profen design patterns and best practises.
Another popular alternative is : Backbone.marionette
Quoting from the README.md
Backbone.Marionette is a composite application library for Backbone.js
that aims to simplify the construction of large scale JavaScript
applications. It is a collection of common design and implementation
patterns found in the applications that I (Derick Bailey) have been
building with Backbone, and includes various pieces inspired by
composite application architectures, such as Microsoft's "Prism"
framework.
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.
I'm starting a project and I'm not sure about what technology to use on the back-end and front-end sides. The project needs to generate charts and a lot of statistics so I have been surfing on the site and I think that the best way to front-end is Backbone.js or Ember.js, is it?
On the other hand I've to decide the server part. I'm an old school developer...Php. I need to develope an API that reads de ddbb and provide the information to the front-end side. I don't know what is the best way to develope a system that let final user to choose a date interval to view their statistics (like Google Analytics, Square, etc.). Maybe Ruby? Symfony as well?
Thx! =)
I was in your same situation months ago and I decided to go for Backbone. The main reason is that it's more used and so it's easier to get help and find good tutorials, plus it's not much opinionated so I think you can learn more while develping and also you can shape your app to fit better your needs. Anyway I didn't tried in deep Ember or Angular so take my opinion with care. For the server side part I've always worked with PHP too, I tried Ruby and I think it's a better support for a webapp but I ended use PHP anyway cause of my company's needs. You can do a good job with PHP too, but I suggest to use frameworks like Silex, Slim or Laravel that are better suited to put up a REST api which you will need if you want to use Backbone.
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.
At work we have an application that we need to update. It is a fat client that is largely written in Windows Forms with newer parts of it being in WPF. The main section of this application is a form designer that is implemented with a Web Browser control using HTML.
We need to redesign a large portion of the application and need to generally improve the user experience. There's a good chance that I will be the one working on this project and I am very familiar with WPF and feel like it would be a very suitable technology to use. I would plan to remove the old windows forms portions and largely rewrite the application.
However, there has been some discussion of migrating this application to be a web application in a future release. My coworker was tossing around the idea of trying to redesign the dialogs and application using HTML while still being a fat client.
Does this seem like a reasonable idea? Is there any kind of design similar to this approach that would support this kind of hybrid application? Would we be able to realistically create the same kind of user experience using HTML5 / JS that WPF would offer?
The idea of making portable code is enticing, but I have serious concerns about the feasibility of this suggestion. I know that windows 8 apps support a variety of design options, but this application would be targeted for xp / windows 7.
This really depends on the application audience but I'd say go with Web if it's easy enough and it should be since you're starting from scratch.
I was faced with the same question 3 years ago and I still regret sticking to WPF because the app could have been deployed on tablets if it was a web app.
If your app contains abundant business logic make sure you split that out well, business logic in JS doesn't work well - crappy to debug, difficult to manage over the entire life of the app. Generally expect more difficult development when compared do WPF but with much larger potential audience.
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.
Are there any open source framkework to help with management of content for language translation? Like users can select their language of choice, system will pull in all untranslated text for that language, user can enter their translations, wait for 3-4 other people to verify it then push it live. Similar to facebook translation application. Looking for something I can implement with PHP. IF nothing is out there I will need to build one tool in-house for this. Any suggestions on the basic schema design to store languages in then?
Have you checked out Pootle? It's
an online translation management tool
with translation interface. It is
written in the Python programming
language using the Django framework
and is free software
...
It can play various roles in the
translation process. The simplest
displays statistics for the body of
translations hosted by the server. Its
suggestion mode allows users to make
translation suggestions and
corrections for later review, thus it
can act as a translation specific bug
reporting system. It allows online
translation with the assignment of
work to various translators and lastly
it can operate as a management system
where translators translate using an
offline tool and use Pootle to manage
the workflow of the translation.
Might be what you're looking for.
I've been working on this question for the last couple months since we've decided to adapt a PHP CMS to a more multilingual project. If you need some kind of backend translation workflow system, Poodle with the Translate Toolkit looks like the strongest solution, but it requires learning Django/Python framework. This screencast from Mozilla was helpful for me. Depending on your level of commitment and time constraints, this is not a quick solution.
Google translate has a php api
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 tried Unity and MEF and plain old new. And I am a bit confused as to when exactly you need to use any of these "patterns". Why would I choose to use MEF or Unity if using new is simpler and satisfies my needs.
In other words, what needs justify the use of MEF or Unity?
MEF allows for isolation of subsystems within an application. This isolation is useful if you need to change subsystem implementations often, or even at runtime. MEF takes care of the details of loading the subsystems and wiring up all the providers to the appropriate consumers. It's a giant step forward toward the ideal of building an application by concatenating a set of self-contained modules that know nothing about each other.
A significant portion of the code in a traditional application is dedicated to simply gluing things together - glue code. MEF drastically reduces the need for glue code.
If you're just constructing an object so you can open a file or show a dialog, that's not what MEF is for. If you're wanting to write code that uses a generic xyz service but don't want to hard-code a dependency on vendor a or vendor b implementations, that might be a MEF candidate.
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.
We are starting a big LOB application using Silverlight.
I was wondering if you have any experience with Testing Silverlight apps, what are the best solutions you found and if you encountered any pitfalls.
A stalwart individual named Jeff Wilcox has developed a unit test framework targeting Silverlight 2 specifically. It works well.
http://code.msdn.microsoft.com/silverlightut/
I also use Rhino Mocks 3.5 For Silverlight as my mocking framework, developed by Oren Eini. Rhino Mocks is free and excellent. It also offers Silverlight support:
http://ayende.com/projects/rhino-mocks.aspx
I use Prism 2.0, and Unity IoC, which help facilitate the MVVM pattern. This makes testing a breeze. One pitfall that I find, is that Silverlight unit tests run inside a web browser, which hampers continuous integration.
ib.
A "must have" debugging tool for SIlverlight is Silverlight Spy, available as a free download.
Probably not exactly what you're after, but I subscribe to Netflix and they use the following url
http://www.tinyurl.com/netflixsl
...to send subscribers to when they've got a problem. This is of course, at the end of things, and I'm assuming you're after something to test while you're actually developing. But, this might be something you could copy once you're product is released.
I use SilverUnit to unit test Silverlight, it is an open source tool that sits on top of Typemock Isolator