On 12/14/06, T. Size <[EMAIL PROTECTED]> wrote: > > I would appreaciate any comments about if Django is a good framework of > developing an application like is described below. If it is a good > framework for this I would appreciate pointers to applicable > documentation or examples. > > In the near future I will be developing an application that will be > used as a tool for doing the electrical engineering for making > electrical power transformers. Individuals from other parts of the > company will have to access parts but not all of system. > > Anyway here are the details > 1. An electrical engineer will log into the system, access one of > several design programs and after completing a few forms submit for the > program to perform iterations. Output will be saved to a database and > portions of the output will be published to other parts of the company. > I have libraries in python for doing most of the engineering part of > this work right now. It could take several minutes for each > transformer design to run making the iterations. > 2. Managers will login the system to run reports. Few items if any > can be changed by management but they will do a number of reports. > Django's CRUD system looks very promising to me for this part. > 3. Purchasing agents will update prices for components and get reports > of requirements for recently released jobs. > 4. Authentication by person and role will be very important. > 5. The deployment will be on an intranet initially but web access in > the future would be a great asset thus my interest in using a web > framework. > > Most of the examples I have seen for Django seem to focus on custom CMS > type applications. Atleast the engineering function described above is > more of a servlet (although a big one) type application. >
Well, I've done something that sounds reasonably similar. In-house intranet app for an engineering company. We had some in-house Python tools that were used pretty heavily, but each user had to run their own version of it, and we couldn't place any controls on how it was used. So, I created a Django app. Engineers would log in, fill in the necessary info into the forms, and hit Submit. Processing would fire stuff off to another dedicated server, a process that could take up to a minute. Eventually, it'd finish, and send the data back to the Django app, presenting the user with the final results (done with a little AJAX). Certain admins could then log in and track what different people had done, as well as grant and remove permissions for individual users to perform certain actions. So essentially, it was a big Django app wrapped around tens of thousands of lines of Python code that was previously used in the end-user tool. Worked like a charm, everyone seemed pretty happy with the system. Hope that helps. I know I didn't offer too much in the way of details, but essentially, it sounds like I did what you plan on doing. The only problem I ran into was getting the AJAX stuff going, but that's only because this was both my first ever Django app, and my first time trying out AJAX. I simply used the AJAX so the "Submit" button would immediately bring the engineer to a new page, and I could keep them up to date on the status as the separate server did its processing. Jay P. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
