Re: Project Structure - Lots of scattered custom views
> > It had occurred to me that Django wasn't the right tool for this job - > not everything is a nail :) I am embedding these files within a template, so they are not direct static serves. But the content must be inserted within the template "as-is" from the filesystem. I suck at Javascript. Perhaps still, Django is not proper for the job, but I do know that I need some server-side logic, and I want to do it in Python. Any recommendations on another framework? There are aspects of Django that are growing on me, this one paradigm is where I am struggling, and I would not like to abandon just yet. To recap one of my original statements; I do believe what I am really looking for is a content management system, I just don't feel ready to commit (maybe I need to get over that). I want a content management system that focuses more on the "client experience" in the browser. It needs to be picky about layouts, and aware of embedded media. Any suggestions for starters? NOTE: My site layouts are not "liquid" at all. They are very absolute; from dimensions to positioning. Its not just about getting all the content on the page in a certain order. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/hLQsR_8-pOYJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Project Structure - Lots of scattered custom views
Sanjay, you were hitting things pretty close. I think that making sure slug names match up to real *static* locations is the key. I am hosting with Apache, and I thought about using some configurations to cheat a little bit, and get some of the static-files burden off of Django and let Apache resolve any requests that point to actual files on disk (with some security in mind). What about a view that can determine if it should be pointing at a file on disk, and if so, do a custom Http_Response, and read the actually binary contents from disk by hand. Im just curious on this one; it could be an alternative means of file storage and recognition. I understand this may have some performance implications, but this is not going to break Django, correct? Is this bad Django etiquette? Amirouche, a different way to describe what I am trying to achieve might be this: I would like to bypass the admin as much as possible when it comes to these "Articles". But when rendered, all of these articles do need at least a small HTML wrapper, and probably some kind of of global template that helps with navigation. If I could handle navigation without the admin, i would be very excited, but it does seem that I will need to use the admin for at least this purpose. The navigation would probably help render hierarchical "menus" for use as templates within the Articles. I would like to keep this navigation as light as possible. Thanks for the feedback. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/ja-o_pBFAT4J. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Re: Project Structure - Lots of scattered custom views
> > Tie them neatly together > There are some cases where they send me Indesign, but when I export to HTML some of the layouts break. So then I have to manually rig it until I feel its close enough (but then it turns out it wasn't, so I mod again). Some imagemaps made from sliced up Photoshops with some cute rollover effects added on. And then some of the Articles form sequential "stories", so they need linking in between to make them feel seamless. The major point is that I have small bundles of files that are very interconnected, and keeping them close and organized makes the reviewing/editing/handling process much easier. Most of my hacking has been from KomodeIDE, and then VIM/SSH (and thats even when Im doing the design work!). Im having a hard time breaking away from the direct editing. > > I think that splitting each article into it's own app sounds like a > > disaster waiting to happen. > > I agree, thats why I posted here. I am already starting to see the problems... I have started breaking the DRY principle, and its not looking much better. The good news right now, is that my repeats are within close proximity on the filesytem, so Im not rooting all over the place just yet. The only major burden is a project-wide navigation map that has to be properly updated and sequenced (still doin that one by hand). On a good note: I did find an App called django-media-tree that made me feel a little better. It should be easy enough for my guys to feed the projects in there, and maybe I implement an Article-Bundler to help the push/pull process. And then when I need to do my editing, I can set up a temporary staging directory that checks out a bundle, I edit, and then it parses it back in. But I still find myself creating bare apps with some crazy model defined that only has 1 table row. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/mMaEbFr1I4QJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Project Structure - Lots of scattered custom views
Right now my project only has 2 apps that use a database (*real* apps). The rest of the website is composed of many custom views, scattered all over the place. I am new to Django, and I havn't quite figured out how to structure my project directory just yet. I think what I should really be looking at is the beginnings of a Content Management System. But at this point, I think that is too far over my head.The other *issue* is related to my design/develop workflow. Working completely through an internet browser just isnt possible for 80% of the project cycle. We have many programs which want to work directly on the filesystem (on an offline machine), mostly coming from the Adobe Creative Suite. There are all kinds of media documents and markups forming "Articles". These Articles are passed around as bundles during design, and then when they get to me I have to tie them together very neatly and push them onto the website. The one thing I do have control over is the Url layout, and the navigation of these articles. Should I be splitting each of these "articles" into their own apps (a directory with little more than 'templates/' and 'static/'). This makes synchronization easy with the server, there is no database interaction required; the only task left after the sync is for me to update my navigation widgets (which I currently just do by hand). Am I going the right direction here? Is there some App that helps me accomplish this task a little cleaner. I think what I really want, is an App Application (hotplugging apps or something like that). -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/yJsqstRt2JIJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
Working with Django from a Shell
I do fully intend to deploy django on my web-server, but so far I havn't made it off of my development platform. Right now, I primarily use the built in test server, and do most of my composition using the template system. I know there are other systems designed with document publishing in mind, but with the direction django has been taking me, I might be ditching Adobe InDesign within a few weeks in favor of Django!!! I remember once upon a time I tried to get serious with Latex, but it just wasnt meant to be. I think it is the power of python that really draws me in, along with the automagic of Django. I want to use Django for some pretty heavy content layout and organization, but a large portion of my data feed still comes from custom python backends, and the final raw products are fed into Adobe Acrobat. What I need is to keep my Django framework, but bypass the HTTP! (only for this part of the project. Im still going to need network availability before long) The biggest problems I forsee would be with memory management, and huge request processing times. It would be much easier if I could give Django batches of requests, have it crawl over the raw data feeds at its leisure, and pipe the pretty outputs (HTML based) into structured directories, and then start feeding Acrobat for my final PDFs. With all of the other functionality I see, Im surprised that there isn't a way to feed fake "URL Requests" through django-admin.py or something like that, and have it dump the output to a file or even within the context of the python interpreter. Has anybody else tried to use Django without its *Web* interfaces? The the more raw, the better. I know its not exactly meant for it, but hell, why not. Go and automate Adobe and M$ office with ECMAscript on one side and .NET on the other... Pure python just sounds so nice. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/kTTciAEV5QkJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
