Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
I would like to modify the tutorial poll that Django provided. I'm interested in varying the question displayed each time the user selects an answer. Specifically, pull questions randomly out from a .txt file, but keep the answer selection the same.
Can I use the model from the tutorial or do I have to create a new one?
Hi, welcome to SO. You may wish to check this page... How to ask
questions on SO - its best to ask a specific rather than general question here and show what you have tried to date.
Having said that this doesn't really sound like a job for django's model classes which are designed so that
Each attribute of the model represents a database field.
Source
You are best to use the existing poll tutorial model, but build a view which takes a text file and loads it into the database. For instance something like this SO post, and this one may get you started.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 4 years ago.
Improve this question
First sorry for my bad english and my unclear question.
I am trying to make my own blog that can post articles.
Using django basic form is convenient, but its form is just plain.
I want to be able to underline, change colors, and use images.
So basically I want to the feature the image below
the picture
I want to implement the thing in the black oval (I don't know its specific name... T.T).
So is there any APIs or feature implemented in django itself? Or can you tell me what it is called? I don't know what it is called in english so I can't search for it at all..
Thank you for reading my question.
You can do it bytinyMCE, quilljs.
But you should have basic understanding how django form works.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
OVERVIEW
I'd like to test some Django websites using random data on a production server using real domain names, but these websites will be simple tests with possible duplicated data (quite probable not following Google rules). I know usually for this you use a development/staging/virtual box for such a task, but I do want to use directly the production box with the real DNS.
Now, I'm kind of new on website development and SEO, and I wouldn't like to mess with SEO and Google.
What'd be the right way to proceed here? Should I try to avoid being indexed/crawled by Google somehow? Any other advices?
You can disallow the complete indexing of your page and then later (when you're done with coding) activate it again.
Thats probably the best way because google is not going to crawl "bad pages" (for example when your website still is in development) and thus you will not get a Ranking so far (called Page Ranking if you want to look it up).
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I was searching for product recommendation system in shopping carts and saw, How does the Amazon Recommendation feature work?
and in many other sites there are several complex solutions were given and each method has some disadvantage in adoptation. Instead of using complex methods, is it not very easy to get user feedback like giving options for the users to choose why they ordered a particular product. Example, if a user purchases a book, he will be given options, 1)author 2) genre 3)price 4)publisher. By this system, one can get the exact reason for the sale of the product. Are there any disadvantages in implementing this method? Thanks
Users do no want extra interactions.
There is a reason why "one click shopping" is successful.
https://en.wikipedia.org/wiki/1-Click
Most likely, they will be annoyed and not come to your site anymore, and prefer an online retailer that doesn't ask them this extra question. They may also just click random buttons to make the window go away, without caring. What is the incentive for them to answer correctly?
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I'm writing a basic ShoppingCart App as my first ember.js application. The first feature is to filter products based on a keyword. The entire product catalog is displayed first:
https://skitch.com/nicholas.henry/gw5js/online-store-all-products-active
And when a keyword is clicked the products are filtered (opacity is set to 0.2):
https://skitch.com/nicholas.henry/gw5kn/online-store-selected-products
I have this feature working, but am looking for some design advice/review. You can try it out at: http://shoppingcart-js.heroku.com/
I am doing this using a binding on a property 'isActive' on the product model, but this doesn't seem quite right to me. It feels like I'm missing another object to track this property, as this is really a view property, not a model one. The code is here:
https://github.com/nicholasjhenry/shoppingcart.js/blob/95ffd2e3eb5aaf2e9e6c44c71f19b06c29c84a93/site/javascripts/application.js
I would greatly appreciate anyone take a look and make a recommendation to help me implement this feature with a better design. Thank you.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I have a long method in my Model that generates an SVG from the model instance.
It creates a Dot graph and then renders it.
Should this code be in a view instead?
In my opinion, it should. The model is the description of the data, and holds functionality to add, delete and update records in your datastore. The view describes data that is visible to the user. As you are creating data to be presented to your users, I'd say this better fits the view. This is most in line with what the Django FAQ says. But, to quote the conclusion of the linked FAQ entry, "At the end of the day, of course, it comes down to getting stuff done".