Welcome to the Lounge

Kornfeld Eliyahu Peter wrote:

I'm waiting...

Kornfeld Eliyahu Peter wrote:

I have to see in more details what we talking about

• Bootstrap. CSS framework. It's a consistent style for your whole site. Makes it easy to build responsive sites that work well across all screen sizes. It makes it easy to do things like modal dialog boxes, gives you a consistent appearance across your whole site, and gives you some nice common web components such as drop-downs and navbars[^].
• jQuery - DOM manipulation framework, helps you do HTML manipulation consistently across all browsers. It's required by Bootstrap and still quite handy when you need to manipulate HTML elements by hand.
  
  
  JavaScript

  // Manually manipulate your HTML using jQuery.
  $("#someHtmlElement").text("some new text here!");

• KnockoutJS - Databinding and MVVM pattern. It lets you do things like this:
  
  
  JavaScript

  // JS
  var myViewModel = {
     foo: 42
  };
  ko.applyBindings(myViewModel);

  
  
  XML

  <!-- HTML -->
  <label data-bind="text: foo"></label>

• ASP.NET MVC and ASP.NET WebAPI - MVC (with Razor) for server-rendering your HTML, and WebAPI for fetching data asynchronously.

Judah Himango wrote:

There are some decent ones out there, such as Telerik's Kendo UI[^], but it's not really necessary.

Judah Himango wrote:

The hot new sexy thing everyone's worked up about is Google's AngularJS[^]. I've used this now on my last 2 web projects.

Judah Himango wrote:

NodeJS is JavaScript on the server, e.g. a replacement for things like ASP.NET

Judah Himango wrote:

personally don't want JavaScript on the server.

Judah Himango wrote:

I prefer TypeScript (or even CoffeeScript[^]) over raw JS.

class MyAwesomeClass {

   constructor(firstArg: string, someOtherArg: number) {
       // ...
   }

   someFunc(answer: number): string {
      return "The answer is: " + answer;
   }

}

Marc Clifton wrote:

What ever happened to node.js

Judah Himango wrote:

The hot new sexy thing everyone's worked up about is Google's AngularJS[^]

Leo Muller Rap wrote:

it is unnecessarily complicated, and will take (me) longer to develop and maintain

Bajaja wrote:

I would use these if planning to do some apps on mobile devices.

Bajaja wrote:

one thing to decide first would be the famous discussion Code First - Model First - Database First approach.

Bajaja wrote:

Just my 20p to discussion

Fabio Franco wrote:

You will learn the delight it is to work with when you get there.

Fabio Franco wrote:

jQuery is a must,

Fabio Franco wrote:

AngularJS will be very helpful, but I think you can leave that for a later project if you feel overwhelmed.

Fabio Franco wrote:

I would definitely go for entity framework.

Fabio Franco wrote:

Do go for code first.

Marc Clifton wrote:

Found this[^], but I may be making this too complicated

Marc Clifton wrote:

Fabio Franco wrote:

Do go for code first.

 

Hmm, I have some moderately complex modeling issues to consider, such as supporting DPW's in different municipalities and states. I prefer to have a solid model in place, perhaps even with some "scenario tests" to vet out the design, before doing too much coding / UI development. However, when the model is obvious, yeah, I often end up prototyping the UI first.

Marc Clifton wrote:

Thanks for the great feedback!

Gerry Schmitz wrote:

I'd start with "designing" (wire framing) the thing first before deciding on a "technology stack".

Gerry Schmitz wrote:

Didn't see any thoughts on "hosting" either. It may be "pro bono" but at some point there's going to be a cost of ownership.