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 am evaluating Rails3 or Sinatra to build a new site. Both of them look interesting and not sure which one is better for new developer to Ruby. I heard Rails3 is used to build a website with complicated business logic, but Sinatra is more suitable for simple web. I want to build a website could be used in production, the initial business logic may be simple, but then I may add more features with more complex business logic later on. So, I'd appreciate if someone may help me out on my case. Thanks.
You also might consider building out your initial version in Sinatra, where you can really get your head around the various objects you'll be working with. Then, once you've gotten a prototype built, you could port it over to Rails relatively easily.
That being said, I think daddz's recommendation to use Padrino's a good one. I've really been enjoying Sinatra lately, and plan to build something with Padrino soon.
You should also take a look at Padrino. It is built on top of Sinatra and not as "complex" as Rails.
See the new slides for a quick overview: Padrino Slides
My advice is to go with rails3. And here are my reasons.
You may start with a small app but you will eventually add other functionalities later.
It has a large community and excellent screencasts at http://railscasts.com/
Since you are new to Ruby rails will get you interested in learning ruby and it will introduce you to the topics of DRY, TDD, MVC and Rest. It is little harder to grasp but it worth every minute you spend.
Now dont get me wrong. Sinatra is a great micro framework and specially for a good Ruby developer since it has a small base of code (about 1000 lines) so you can check out the code and learn few tricks. But like a said go with Rails and you wont be sorry.
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 10 years ago.
I'm new with Google Web Toolkit and i have some questions about the tool.
First of all, what i have to know to correctly program for GWT? It's ok if i use the GWT Designer to make the GUI?
Second, how i persists all the data i want to store? Use JPA/Hibernate + SQL Database? Or it's better to use AppEngine?
I'm with a great doubt how i get the data from Database to populate fields and tables on client-side.
and Last, i know a bit of Swing, so, GWT is the same? (Except Client - Server concept) ?
That's my questions. Well, thanks in advance.
First of all, what i have to know to correctly program for GWT? It's ok if i use the GWT Designer to make the GUI?
Ok.
Second, how i persists all the data i want to store? Use JPA/Hibernate + SQL Database? Or it's better to use AppEngine?
It's your choice. AppEngine has it's limitations. For example, it scales but may not be the best choice for multi-player games if you need data updated very often and quickly. It really depends on your need/design.
If you do go with AppEngine, my experience with JPA was a headache. Objectify is much easier and the way I would go.
Last, i know a bit of Swing, so, GWT is the same? (Except Client - Server concept) ?
I guess they share the concept of using listeners/handlers for events. They are not the same though.
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.
MonoTouch is great for cross-platform app development. This makes a very strong business argument and I am on verge of developing using MonoTouch with prospects of branching into Android and WinMo. Before starting commercial development in MonoTouch I want to ask one last question, just in case I've missed something critical in my research so far:
What do you think is the biggest drawback of MonoTouch as compared to Objective C?
Barring games development, use whatever context comes to your mind.
Thanks
Steph
UPDATE: Following link probably best answers the question: http://docs.xamarin.com/ios/about/limitations. Conflict of interest is that it comes from Xamarin. Thanks to everyone who contributed!
In my opinion MonoTouch is just great, if you are an c#-developer. You can use almost everything from the full .net-framework and it works like a charm.
Your app gets a bit bigger in a meaning of filesize and you are at the mercy of Xamarin. The only real drawback I have found until now is that you have to change a lot between xcode and monodevelop IF you use the interface-builder. As I don't use the IB that wasn't a big dealbreaker for me (I don't use the visual studio designer either...)
If you know c# and would have to learn Objective-C -> go for MonoTouch!
If you don't know both, it might be a good choice to learn the "real way" to code native apps. Btw. you need some knowledge of Objective-C or iOS-development in general. So you know how to use Views and ViewControllers, what's the names of the methods and so on.
UPDATE: To answer your questions in the comment. The farest I have gone by now, was kinda migrating an existing opensource Objective-C-GUI-Library (kind of popoverControl) to an MonoTouch project. That was rather straightforward and easy. Direct using of Objective-C-Libraries wasn't in my needs by now. But you can read about it in the Xamarin-Docs.
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'm always hearing that RoR is good for Agile implementation. Could someone plaese summarize this statement and explain me why with some examples.P.S I can't read "Agile Web Development with Rails" yet.
Tools are never agile in the matter of software engineering. Tools support in being agile. Ruby on rails is a framework to rapidly build basic functionalities with ease and Agile in most minds is a way to build your system without having the knowledge of every requirement needed by your system.
So tools which support the developers to rapidly bootstrap a software or change functionalities rapidly help you in being agile. Because most of the times the understanding of "How things work" differs between the customer and the developer perspective.
Aligning those perspectives is a success factor on every project and most of the times it is better to show something for a common understanding than painting some flow charts, uml charts or whatever which imply domain knowledge.
Another thing is if you may bootstrap a project rapidly you may react on reordering of priorities more flexible.
For the nitpickers.: Agile is a buzzword. There are lots of definitions and different understandings whats agile is and it may always be that my view on being agile or developing agile differs from some other definitions.
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 want to ask about the best resources to know how cucumber, capybara works. I know how to use them, but sometimes things go wrong I just don't know why, I thought about reading the capybara and cucumber source code, but It's a bit complicated without having a general idea about their work, so here's my question. How do you learn this things enough to understand whats happening behind and things doesn't seem like magic with tools like this?
Greetings
Cucumber and Capybara are fairly independent, so you should try to learn about each one of them individually.
I haven't used Cucumber, but I assume the web site with its wiki, examples and tutorials (see the navigation bar at the top) should be a great resource.
Regarding Capybara: Since the time you asked your question I've expanded the Capybara README a bit, so I recommend you check it out again. You should be able to get going just by reading the README top to bottom (and perhaps following its pointers into the rdoc reference). Capybara is not a very complex beast, really.
For cucumber I would recommend reading either "The RSpec Book" from pragmatic press, or find the free download of a work in progress called "the secret ninja cucumber scrolls" http://cuke4ninja.com/
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'm not talking about bug tracking software (like Bugzilla or Jira). I'm looking for something that:
Stores test specifications in text format
Combines test specs into test coverage scenarios
Keeps track of the progress through testing scenarios
Links test specs with bug reports stored in Bugzilla
Generates progress reports
Is centrally managed on its own (i.e. is not a hack/extension on top of something else)
TestLink is a pretty nice open source test tracking tool with the features you need, and is still under active development. Take a look at http://testlink.org/
I haven't used this (yet), but Testopia seems to meet all your requirements, especially the one about Bugzilla.
I'm biased since I'm the primary author, but I think Cuanto is pretty good. It allows you to track historical results for multiple test projects and you can store your analysis with the test results.
RTH is another open source test management tool
I have personally used Trac (http://trac.edgewall.org/) which combines a simple issue tracker with Wiki functionality. Solved the need I had on my project.
A while back I briefly looked at the free version of QaTraq. Although I left the team I was considering it for before we every got very far with the project, it was the frontrunner of the options I looked at at the time.
It's got quite a nice interface, and what seemed to me to be a very sensible test planning structure. I think one of the big downsides was the the open source version didn't have table support in the WYSIWYG test case editor - Not a showstopper, and could be fixed with a little development effort or by spending some money on the professional version.