Looking for recommendations on a programming language for a web application.

[Paul]

I am soliciting recommendations on a programming language for a web
application described below. Actually, it is not real, just an example
of what the real application would do. I do not want to stimulate any
debates between respondents. Everyone is entitled to their opinion.
Let me be the one to privately decide on the validity of the comments.
All options are open: ASP.NET, PHP, Cold Fusion, Oracle, AJAX, XML, and
so forth. Yes some of you are better programmers with one of these
languages, but I hope you can be objective enough to provide insights
to possible shortcomings with your specialty as well as its strengths.
You thoughts on languages you are not so familiar with are acceptable
as well.

The web application will run similar to a custom manufacturing job shop
where a product is built from pre-determined parts or new parts with
multiple levels of sub-assemblies each with its ability to build from
the parts inventory. For example, the customer wants to build an
automobile. Then they choose from such things as engine, body type,
and tires. Then under engine, they can choose such things as V-8,
transmission type, fuel type, or define a new part (that will be added
to the inventory).

Expected database tables would be the parts inventory, and then tables
for each level that contains the links between tables so when, in this
example, this car is selected again, all components will be listed as
originally designed.

This is pretty simplistic but a fairly good example. I would like all
of this to be viewable on a single page. Items at the lower level
cannot be selected until the items of the higher level have been
specified. As one progresses down through the levels, the number of
total items at that level would normally become more numerous. For
example, let's say the body type had three parts, and the tires had
three parts; you can see that we started with one main unit built from
three sub-elements, with each of those sub-elements being built from
three parts for a total of nine parts at that level. Elements from the
inventory may be used at any level. For example, we could list a type
of machine screw to be used to build the body type and to build the
V-8.

We also need to be able to attach to each part a reference to something
like a page from a manual, a web site, or an image.

We also want to ability to provide spelling and grammar checking.

When building or adding parts; we want to be able to search the parts
inventory.

When finished, we need to be able output this completed "job" to
Microsoft Word and PowerPoint.

I would expect a database handling 1000s of users, each with it own log
in to access it own data, and maybe an average of 250 users in the
database at a time.

[Mike]

"Paul" <pm*******@neb.rr.comwrote in message
news:11**********************@l53g2000cwa.googlegr oups.com...

>I am soliciting recommendations on a programming language for a web
application described below. Actually, it is not real, just an example
of what the real application would do. I do not want to stimulate any
debates between respondents. Everyone is entitled to their opinion.
Let me be the one to privately decide on the validity of the comments.
All options are open: ASP.NET, PHP, Cold Fusion, Oracle, AJAX, XML, and
so forth. Yes some of you are better programmers with one of these
languages,

ASP.NET, Oracle, Ajax and XML are not "programming languages". As far as
the "best" one is concerned, the answer to that is whichever you feel most
comfortable with. As far as the detail in the rest of your post is
concerned, it's irrelevant to your question, except to confirm that you
should be looking at a technology that provides for database access (but
then you already know that).

Mike

PS. If people respond to your post, and others want to debate with them,
that's their business. Nothing you can do to stop them. And why would you
want to?

[Tim Mackey]

hi paul,
for a start, you could use all of Asp.Net, AJAX, and XML, they are not
mutually exclusive, each is designed for a very different purpose.
personally i would recommend Asp.Net 2 as the main development platform,
based on workforce availability, the popularity of the platform, and its
acceptance in the industry (e.g. trusted by government, education, etc.
plenty of exceptions to this for sure, but asp.net has certianly broken
through to these sectors as 'a' main player). there is a wealth of sample
code, tutorials, community sites etc. these exist for php and CF as well
obviously. i have found asp.net to be a great platform with a fantastic IDE
(visual studio 2005). you also get a great surrounding set of tools and
technologies.
the natural choice for a database with asp.net is Sql 2005.

good luck
tim
"Paul" <pm*******@neb.rr.comwrote in message
news:11**********************@l53g2000cwa.googlegr oups.com...

>I am soliciting recommendations on a programming language for a web
application described below. Actually, it is not real, just an example
of what the real application would do. I do not want to stimulate any
debates between respondents. Everyone is entitled to their opinion.
Let me be the one to privately decide on the validity of the comments.
All options are open: ASP.NET, PHP, Cold Fusion, Oracle, AJAX, XML, and
so forth. Yes some of you are better programmers with one of these
languages, but I hope you can be objective enough to provide insights
to possible shortcomings with your specialty as well as its strengths.
You thoughts on languages you are not so familiar with are acceptable
as well.

The web application will run similar to a custom manufacturing job shop
where a product is built from pre-determined parts or new parts with
multiple levels of sub-assemblies each with its ability to build from
the parts inventory. For example, the customer wants to build an
automobile. Then they choose from such things as engine, body type,
and tires. Then under engine, they can choose such things as V-8,
transmission type, fuel type, or define a new part (that will be added
to the inventory).

Expected database tables would be the parts inventory, and then tables
for each level that contains the links between tables so when, in this
example, this car is selected again, all components will be listed as
originally designed.

This is pretty simplistic but a fairly good example. I would like all
of this to be viewable on a single page. Items at the lower level
cannot be selected until the items of the higher level have been
specified. As one progresses down through the levels, the number of
total items at that level would normally become more numerous. For
example, let's say the body type had three parts, and the tires had
three parts; you can see that we started with one main unit built from
three sub-elements, with each of those sub-elements being built from
three parts for a total of nine parts at that level. Elements from the
inventory may be used at any level. For example, we could list a type
of machine screw to be used to build the body type and to build the
V-8.

We also need to be able to attach to each part a reference to something
like a page from a manual, a web site, or an image.

We also want to ability to provide spelling and grammar checking.

When building or adding parts; we want to be able to search the parts
inventory.

When finished, we need to be able output this completed "job" to
Microsoft Word and PowerPoint.

I would expect a database handling 1000s of users, each with it own log
in to access it own data, and maybe an average of 250 users in the
database at a time.

[clintonG]

ASP.NET 3.0 includes support for Windows Workflow which is also supported in
Vista. ASP.NET 3.0 WorkFlow is uniquely suited to job shop process
management hence ASP.NET 3.0 would be the best development framework.
Especially with regard to intgration with Microsoft Word and PowerPoint.
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/
MAP http://wikimapia.org/#y=43038073&x=-...8&z=17&l=0&m=h

"Paul" <pm*******@neb.rr.comwrote in message
news:11**********************@l53g2000cwa.googlegr oups.com...

>I am soliciting recommendations on a programming language for a web
application described below. Actually, it is not real, just an example
of what the real application would do. I do not want to stimulate any
debates between respondents. Everyone is entitled to their opinion.
Let me be the one to privately decide on the validity of the comments.
All options are open: ASP.NET, PHP, Cold Fusion, Oracle, AJAX, XML, and
so forth. Yes some of you are better programmers with one of these
languages, but I hope you can be objective enough to provide insights
to possible shortcomings with your specialty as well as its strengths.
You thoughts on languages you are not so familiar with are acceptable
as well.

The web application will run similar to a custom manufacturing job shop
where a product is built from pre-determined parts or new parts with
multiple levels of sub-assemblies each with its ability to build from
the parts inventory. For example, the customer wants to build an
automobile. Then they choose from such things as engine, body type,
and tires. Then under engine, they can choose such things as V-8,
transmission type, fuel type, or define a new part (that will be added
to the inventory).

Expected database tables would be the parts inventory, and then tables
for each level that contains the links between tables so when, in this
example, this car is selected again, all components will be listed as
originally designed.

This is pretty simplistic but a fairly good example. I would like all
of this to be viewable on a single page. Items at the lower level
cannot be selected until the items of the higher level have been
specified. As one progresses down through the levels, the number of
total items at that level would normally become more numerous. For
example, let's say the body type had three parts, and the tires had
three parts; you can see that we started with one main unit built from
three sub-elements, with each of those sub-elements being built from
three parts for a total of nine parts at that level. Elements from the
inventory may be used at any level. For example, we could list a type
of machine screw to be used to build the body type and to build the
V-8.

We also need to be able to attach to each part a reference to something
like a page from a manual, a web site, or an image.

We also want to ability to provide spelling and grammar checking.

When building or adding parts; we want to be able to search the parts
inventory.

When finished, we need to be able output this completed "job" to
Microsoft Word and PowerPoint.

I would expect a database handling 1000s of users, each with it own log
in to access it own data, and maybe an average of 250 users in the
database at a time.