The Big Programming Thread - Page 426

On January 14 2014 10:09 WarSame wrote:

Thanks for the feedback. For MVC I thought that View = user display, Model = data, Control = controlling logic. As I saw it the Model was PongData, the View was PongPanel and the Control was PongFrame. I guess I really misunderstood what MVC is. Looking at Wikipedia this seems like it might be an example of a passive model, though, where the view is updated from the model by polling(by running the heartbeat cycle with sleep lengths). Maybe not, and honestly this is confusing me quite a bit by this point. Could you point out what you believe would make this into an MVC project?

As for making a class for each component of the project, I'm not really sure what you mean by that. Do you mean I should make one for Ball(with an X and Y value/speed), one for Paddle, and so on like that? If so, you are definitely right and I regret not doing that. If not could you please clarify it? And thanks for the feedback throughout, I definitely appreciate it. This project was a lot easier to handle organization-wise than the last one for Tic Tac Toe.

On January 14 2014 10:30 sob3k wrote:
If I want to add H1-H6 headers to a previously made page for SEO purposes, if there any way for me to remove all formatting from them? I just want to stick them on as SEO markers and not have them effect the site visibly at all. Right now they break all kinds of stuff. I tried some resets but none of them reduce the headings to just tags.

On January 14 2014 11:39 sluggaslamoo wrote:


Yep basically what you said and not much more than that if at all. Those classes will basically serve as "models".

Controllers handle inputs. For example in a website it will handle the URL's, in your case its the game controller inputs. There should be minimal logic in the controller. Think about how much logic is in an actual game controller, it takes a signal, and converts it into an instruction to the game, that's all your controller should do as well. As a rule of thumb, light controllers, fat models.

Pretty much all the logic should be in your models. Anything code that has anything to do with a model, should be in the model itself. For example, "moving a Paddle", there should be a move method on the Paddle itself, don't write the logic in the controller or anywhere else. In the controller you would handle the mouse movement, and delegate all logic to the Paddle by passing in the mouse event or minimal information necessary.

You could also do it declaratively, by adding in a listener to the paddle in the beginning and firing it off with the controller.

When I was saying that your last example was MVC, I was more or less being tongue in cheek about MVC not being the issue there. When you do things properly your program will naturally become MVC of sorts. Even when you do implement what I said, it won't be MVC really.

MVC normally has an ORM associated with it, and you declare Models as an abstraction for saveable/stateful components in your application.

I only pointed it out because you specifically wanted your app to be MVC. I don't think its necessary to think of it like that though. MVC is much more useful for applications where you need to save state. This is more or less focused on doing Responsibility Driven Design.

On January 14 2014 11:41 phar wrote:

I'm gonna avoid commenting on whether or not you should be doing that for SEO purposes, but have you looked at the page's css at all? That should be controlling the way stuff looks, not so much your html.

On January 14 2014 12:39 sob3k wrote:


yes, the issue is that H tags come with some sort of (hidden) default styling

On January 14 2014 18:59 obesechicken13 wrote:
Hey guys. Long time since I've posted here I think.

I'm having trouble connecting the front end to the back end of a .net website. I'm not sure how you do it. I guess if I were doing PHP I would first connect to the db then have some in line <?php tags to get the data from the db and echo out what I need from the db.

How does .net handle this?
What if I wanted a table of data?

c# code:

public JsonResult GetUserNameAsJson()
        {
            var userContext = new UsersContext();
            User user = userContext.GetUser(User.Identity.Name);

            return Json(user, JsonRequestBehavior.AllowGet);
        }

This might be what the function above spits out if I call it directly.
{"UserID":1,"UserName":"booger","Password":"5f4dcc3b5aa765d61d8327deb882cf99","Email":"booger@gmail.com"}

Now what if I wanted the html file to call the function?

On January 14 2014 19:17 obesechicken13 wrote:
I'm using MVC and I've tried lots of javascript and in particular ajax calls. But I'm not sure what to do after I have the javascript to test if its actually working.

For instance I might have this code:

$(function () {
        $.ajax({
            type: 'POST',
            contentType: 'application/json',
            dataType: 'json',
            url: 'UserController.cs/GetUserNameAsJson',
            data: '{ FirstName: "Dave", LastName: "Ward" }'
        });
    });

Great. Now what does it do?

By itself this returns nothing visible on the client side.

On January 15 2014 07:34 darkness wrote:
I remember having studied some term that represents an empty while loop but I can't remember how it was used exactly and why. I suppose it was like this:

while (mailbox.isEmpty()) {} // <--- I am talking about such loop

// now the mailbox isn't empty, so execute something?
mailbox.processLetters();

Does anyone remember something like this? If yes, what is a possible application? Threading?

while(DoSomething) {}

On January 15 2014 07:49 Shikada wrote:


Like this it only serves to waste computer resources. You drive a thread to 100% use for no reason.

If it was:

while(DoSomething) {}

It would do something in that method, and the method would return false to indicate that the work is complete and the loop should stop. That at least make sense, but it's still bad programming (maybe for something really low level). What you would do instead is some well established pattern of asynchronous concurrency, like event driven programming.

while (mailbox.isEmpty()) {} // <--- I am talking about such loop

// now the mailbox isn't empty, so execute something?
mailbox.processLetters();