"is pretty surreal. . ." --tell me about it =) Frankly, I think it's too many features. We've a prioritized development schedule based on user input, and I expect that we'll find that the site becomes what we want/need at around 1/3-1/2 of these features.
That's good to hear, about Django, given the prominence of user/session support in our plans. Public site design is frankly a secondary concern: I think a template system will be more than enough. But, I figured I'd throw it out there.
We've already rolled a simple CAD/drawing app via the element, and I expect that to be more than sufficient.
Thanks a bunch for your input! I'll be sure to be in contact as we proceed.
So I'm developing a web application involving "socially" networking elements created by users. But, I'm a novice [when it comes to web programming].
I'm getting to the point where I'd like to choose a language/framework. I'm OK (in fact, I prefer) trying options out and switching flexibly before settling down on a choice, but I thought I might get some feedback from some people who know what they're talking about.
Some goals (both long- and short-term) central to my plans that I think might influence my choice include:
-Lots of user/database interface and editing via gorgeous graph/node visualization
-Easy web site template authoring (read: visual/drag & drop elements, no/minimal coding required of user)
-Integration of version control (of web pages)
-Fairly sophisticated AI performed on the backend for resource matching and knowledge representation
-Enabling for public editing of HTML and site design
-Online CAD/drawing tool (probably via )
-Acute, application-level awareness of user profile/information in what/how pages and information is displayed as users browse (read: dynamically generate and display content per user)
-Web spidering/pulling and reusing content from the web
After shopping around, I've been primarily considering Python (Pylons; Django) and WebObjects/Project Wonder.
Thoughts? Recommendations? Are these goals _actually_ constraints on what language/framework I choose? What are the more generic features of the language/framework that I should paying attention to, given my goals?
That's good to hear, about Django, given the prominence of user/session support in our plans. Public site design is frankly a secondary concern: I think a template system will be more than enough. But, I figured I'd throw it out there.
We've already rolled a simple CAD/drawing app via the element, and I expect that to be more than sufficient.
Thanks a bunch for your input! I'll be sure to be in contact as we proceed.