What programming language would best fit my kind of problem?

[Giku Promitt]

We received a task @ school to create a project for our winter session. My task is to make a program that would automize the ticket booking process in a cinema. Assuming that:

• I want a friendly graphical interface for my program (meaning that I want to view the plan of audience room instead of the list of seats)
• My data will be kept in an .mdb or .accdb database

what programming language would best fit my kind of problem? I think I could learn this p.l. in less than 3 weeks to keep the rhythm with my colleagues that do not need any graphical interface and therefore work in Borland C++ Builder or C# under Visual Studio. I first thought abt Adobe Premiere Pro, but I'm doubtful abt its ability to manage databases.

Thanks for any feedback.
Giku Promitt.

[Frinavale]

The first question that comes to my mind is: Is this an Online Application (web application/website) or is it a desktop application?

Does your application have to run on multiple platforms, or just the Windows operating systems?

If I were you I would stick with a language that I was comfortable with...if you know C# then use it to write your application.

If you're looking for a rich user interface, and you are comfortable with C#, consider using WPF (windows presentation foundation) for a desktop application...o r SilverLight for a web/desktop application.

-Frinny

[Giku Promitt]

@Frinny

I'm actually planning to make the desktop application first (enough to run on cinema booking man's computer [sry 4 my engl.]), and later (after our session) to implement the project on a website.

I think I'll pay attention to WPF. I have enough time to get initiated...

[Frinavale]

Maybe you'll be interested in creating a Web Service then. That way both the Desktop and the web application can use the same service to do things (everything is centralized).

-Frinny

[Giku Promitt]

@Frinny

Web Service is quite a general term for me. Could you please be more explicit?

[Frinavale]

You should probably look them up.

It lets you write methods that are exposed over the network which you can call from multiple applications.


In your case, you are creating a ticket-booking application and people will be able to interact with your system through a desktop application and a website (web application).

It makes sense, in this case, to write your logic for ticket-booking in a web-service so that both applications can simply call (consume) the logic in the web-service. As opposed to writing the same logic in both applications... which would be double the work to maintain in the log run.

For example, your web service would expose methods that do things like BookTicket, or GetNumTicketsAv ailable, or HoldSeat....the se methods would be called by your desktop application and your website. If the logic in BookTicket were to change, all you'd have to do is change it in one place: the web service...

Look up web services :)

You may not choose to use them but it is a viable option in this type of system.

-Frinny

[Giku Promitt]

Ok, I've got it.

It's true that a Web Service would be the best solution from the studied ones here, but I'm @ the beginning of Web programming and for now I'll remain on what I definitely know I can.

Whatever my choice would be, I'm thankful to you for assistance ;)

Giku Promitt