aspose file tools*
The moose likes Java in General and the fly likes A Practise application - some advice Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Java in General
Bookmark "A Practise application - some advice" Watch "A Practise application - some advice" New topic
Author

A Practise application - some advice

Wesleigh Pieters
Ranch Hand

Joined: Sep 04, 2012
Posts: 81
Hi All,

So I want to write a small useful application for practice, it will be used by the GF.

Basically it is a task management system where it will hold tasks, timestamps, responsibilities and progress in a DB. Then each user will be able to search, create and update tasks, leave notes etc. (and yes I know such things exist, I just want to use it for the practise and be able to customise it fully etc.)

In this situation what approach would be best, a server application that does all the work that clients speak to, a server application and client connect using a web browser etc?

I am fairly new to all of this so any advice will be appreciated and will take it from there, apologies I may have more questions later.

Thanks.
Maneesh Godbole
Saloon Keeper

Joined: Jul 26, 2007
Posts: 10451
    
    8

Wesleigh Pieters wrote:Hi All,

So I want to write a small useful application for practice, it will be used by the GF.

Basically it is a task management system where it will hold tasks, timestamps, responsibilities and progress in a DB. Then each user will be able to search, create and update tasks, leave notes etc. (and yes I know such things exist, I just want to use it for the practise and be able to customise it fully etc.)

In this situation what approach would be best, a server application that does all the work that clients speak to, a server application and client connect using a web browser etc?

I am fairly new to all of this so any advice will be appreciated and will take it from there, apologies I may have more questions later.

Thanks.


Start by asking yourself
1) How many users will use this application
2) Will they use it at the same time?
3) How will they use it? Over the internet? Intranet?
4) What is the client? Stand alone application? Browser? Smart phone?

In general, you should always split the application into different modules (if not different components) anyway.


[How to ask questions] [Donate a pint, save a life!] [Onff-turn it on!]
Wesleigh Pieters
Ranch Hand

Joined: Sep 04, 2012
Posts: 81

Start by asking yourself
1) How many users will use this application - up to 12 people but it should be able to handle lets say 20 for some growth
2) Will they use it at the same time? - all should be able to use concurrently
3) How will they use it? Over the internet? Intranet? - intranet mostly but want to add in that can be logged in off site using a dynamic address for this.
4) What is the client? Stand alone application? Browser? Smart phone? - windows pc, either desktop app or browser
Bob Scott
Ranch Hand

Joined: Oct 04, 2012
Posts: 40

I'm doing the same thing. I'm writing an app that is specific to keeping up with classical music collections. I asked on a classical music forum for some advice and they gave me some great tips that I had never thought of.

Good luck with your app!
Wesleigh Pieters
Ranch Hand

Joined: Sep 04, 2012
Posts: 81
Bob Scott wrote:I'm doing the same thing. I'm writing an app that is specific to keeping up with classical music collections. I asked on a classical music forum for some advice and they gave me some great tips that I had never thought of.

Good luck with your app!


thank you

I just need some advice on the direction to take and then I can ask some specific questions and away I code
Maneesh Godbole
Saloon Keeper

Joined: Jul 26, 2007
Posts: 10451
    
    8

Wesleigh Pieters wrote:
Start by asking yourself
1) How many users will use this application - up to 12 people but it should be able to handle lets say 20 for some growth
2) Will they use it at the same time? - all should be able to use concurrently
3) How will they use it? Over the internet? Intranet? - intranet mostly but want to add in that can be logged in off site using a dynamic address for this.
4) What is the client? Stand alone application? Browser? Smart phone? - windows pc, either desktop app or browser


Multiple people, accessing your application concurrently over the network.
This would indicate you have a web based distributed application design, where the client server communication uses JSON or something similar (so that you can easily switch between desktop/browser) In future you can even adapt it for mobile clients!
Wesleigh Pieters
Ranch Hand

Joined: Sep 04, 2012
Posts: 81
Maneesh Godbole wrote:
Wesleigh Pieters wrote:
Start by asking yourself
1) How many users will use this application - up to 12 people but it should be able to handle lets say 20 for some growth
2) Will they use it at the same time? - all should be able to use concurrently
3) How will they use it? Over the internet? Intranet? - intranet mostly but want to add in that can be logged in off site using a dynamic address for this.
4) What is the client? Stand alone application? Browser? Smart phone? - windows pc, either desktop app or browser


Multiple people, accessing your application concurrently over the network.
This would indicate you have a web based distributed application design, where the client server communication uses JSON or something similar (so that you can easily switch between desktop/browser) In future you can even adapt it for mobile clients!


JSON as in javascript?
Maneesh Godbole
Saloon Keeper

Joined: Jul 26, 2007
Posts: 10451
    
    8

Wesleigh Pieters wrote:
JSON as in javascript?

Recommended reading JSON
Also check out http://code.google.com/p/json-simple/ which has good examples.
Bob Scott
Ranch Hand

Joined: Oct 04, 2012
Posts: 40

Maneesh Godbole wrote:
Wesleigh Pieters wrote:
JSON as in javascript?

Recommended reading JSON
Also check out http://code.google.com/p/json-simple/ which has good examples.


Thanks for the links, Maneesh. Even though it's way overkill in my practice app, I'm going to write it in a 3-tier architecture for the experience.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
 
subject: A Practise application - some advice