On Sunday 23 Aug 2009 4:18:06 pm Roshan Mathews wrote: > KG: The beauty of the code (and of the site) is of primary importance > if you actually want people to work on it.
it is not. You have not answered my question - does the site work? > But then I can understand > if you look at this from the other end. I'd reduce all my complaints > to not being able to run it on my machine. I don't have the 'media' > files. If they are part of the repo, and doing a `manage.py > runserver' actually brings up the site as it is on localhost:8000 ... > then it would be easy to start working on it. The other issues are > trivial and can be fixed in an hour. please look at the installation notes and download the media files. The media is dependent on jquery, jquery-ui, tiny_mce and blueprint. These are all css/js files maintained by third parties and should not be bundled with the app. I have several apps on the server dependent on these - they are all checked out from svn/hg heads and suitably symlinked to sitemedia/css and sitemedia/js as the case may be. Surely you do not expect me to bundle these with the app? that would be needless duplication and a nightmare to maintain. The paths can be seen in addreport.html, addevent.html and base.html. All you need to do is to check them out and symlink them to the css/js directories. Same for postgres/sqllite - I use postgres in production (and in testing) but you are not compelled to so - modify your settings.py to use sqllite. please note that django is platform neutral - and third party neutral. The platform, css and jscript frameworks, the database and webserver are not built in into django - it is up to the person running it to choose these components, install them and fit django and the application to them. That said, it is a given that the most difficult part of getting a django app to run is the media. Most people find it difficult to get the paths right. This is intentional. It means that the app is actually media agnostic, and one can plug in one's favourite js, css, sql engines at will and run the app. It also means that one can keep site wide library files - and keep them up to date without going to each and every application and updating the dependencies there. I could, of course, make a tarball (or a live cd) bundling all these things, and also linux. postgresql, python, PIL, reportlab and a million other things in the application to make it run 'out of the box' - but I have other things to do. People in my lab have succeeded in checking out the app and getting it to run on runserver without too much fuss - all it needs is the proper attitude - when things do not work, is the author of the application an idiot? or am I not doing things correctly? judicious use of firebug in your browser will help you to debug your media woes. As I said above, install the media and check your symlinks and your paths. btw, you do not even need to call the database 'ilugc' or the database user 'lawgon'. I appreciate your effort in trying to contribute to the code, but am less than happy with the request for spoonfeeding in setting up the app for testing/development. And if you find this messy, please look at the code for the conference app for inpycon. And if you find *that* messy and difficult to install, go look at dougn's code for pycon website itself ... the first commandment for code is that it should work, the second commandment is that it should do what is expected of it - all other things are secondary. There is always time to tidy up and make the output pretty. But before doing that, ask whether it works. Then optimise and factorise to your hearts content. -- regards kg http://lawgon.livejournal.com _______________________________________________ To unsubscribe, email [email protected] with "unsubscribe <password> <address>" in the subject or body of the message. http://www.ae.iitm.ac.in/mailman/listinfo/ilugc
