Anyone interested in reviewing updated code? Now the search functionality is working. I have added comments and a link with screenshots of working functionality. Also refactoring done in the Javascript to make code easier to read. I think the functionality should be clearer by the changed code now. I have added a partial for rendering as was suggested.
There are some parts of code which can be improved but I don't know exactly how to implement the changes.
Like the Javascript needs the static URL for addition of categories on screen. It can be done in a much better way if I can use a partial here. But I am not sure how to render a partial by the html() function of a javascript. Any ideas?
On Tuesday, May 27, 2014 8:26:20 PM UTC+5:30, Aseem Bansal wrote:
Background? I have some experience(a few months only) with Java 6/Struts 1.2 for web development. Started working on Python May 2013. Not continuously but as a hobby for scripting purposes and some automation. I guess my github and stackoverflow account can give you a better ideahttp://stackoverflow.com/users/2235567/aseem-bansal
On Tuesday, May 27, 2014 7:09:47 PM UTC+5:30, shmengie wrote:Partials/sub-templates are the same.
For a small one pager, includes aren't very useful. As for the logic in using them, that's more difficult to elaborate since it depends a lot on the layout and design of the site.
There are a couple of different types of "sub sections" you can implement. html fragments, which are useful in larger sites. Then there are fragments of css/js which even tho it's all html, I refer to html as presentation code and css/js as links/includes. For a larger site this is more useful, but since you're using this as a learning tool, why not implement concepts that are useful in larger sites.
I referenced the custom tags, because you can dynamically include CSS & Javascript (partials) based on rules with them. Which is a nifty concept, though I've seen it used, Ive not implemented them myself.... I don't wish to push too much on your plate, w/out knowing your background, but this might be a good concept for you to tackle at this point.
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/b766787d-1d44-4c70-98e2-037c7258ede8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment