Karl Guertin wrote: > On 10/19/06, John Henry <[EMAIL PROTECTED]> wrote: > > So, to all you experts, what's the simplist way to go about doing this? > > I'm not sure what you want to get out of putting your app on the web. > It seems like you're using the various office apps as a pseudo-web > site but you don't mention to what end. >
Right now, these are just static documents - but they are hyperlinked documents. Once everybody gets the CD, we get into teleconferencing, talk about things, Then comes the endless stream of emails to talk about things somemore. Well, it's still light years ahead of what people in our industry is still doing: they print them all out, bind them into room full of 5 inch books, distribute the books, fax back and forth.... I am looking at doing project management over the web down the road (like things you do with www.basecamp.com). So, if all of the information on these CDs becomes available directly over the web, I can see that it would become big help in improving collaboration among various participants. Unfortunately, most of these people are (still) slaves of Outlook and Office right now (that's why I had to use Word documents - rather then html files). I have to ease their way into what I like to see happen. > If you're trying to just put some sort of index of office docs on the > web, you can do that in just about anything and I'd actually recommend > PHP because it's simple and available on commodity hosting. Just > search through the manual to find the function that does what you want > and call it. > > If you're trying to migrate a larger portion of your functionality > onto a web site, *don't* use PHP. PHP sucks for app development. I > personally like TurboGears and Django. Which I use for a particular > project depends on how much I can get out of Django's automatic admin > interface. I use Django for stuff that looks more like an online > newspaper/blog and TurboGears for stuff where I'm doing a lot of forms > processing or working off a legacy db or heavy json calling. > > I'd possibly consider Pylons as well but I'm happy with the TG/Django > pair. I avoid the Zope/Plone due to the developer learning curve > (sorry zopistas) and the rest of the packages you've listed are pieces > rather than a whole solution. Not to reinvent the wheel, somebody must have encountered the need to "publish" their .doc and .xls files to a web site - without completely rewritting the form generation code. I tried the Google web doc/spreadsheet system but it didn't convert my Excel spreadsheets properly - and I lose all of the hyperlinks. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
