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 9 years ago.
Improve this question
I'm currently developing a game with friends. We are searching for informations about design patterns for User Interface in order to implement a simple UI including: buttons, progress bar (for health, exp, mana, ...), text, views/subviews, and scroll views.
The first goal is to have something simple but working. We are not looking for patterns about making an UI loading from XML/JSON files, we just need information about the inheritance of our classes and their relationship.
While it doesn't matter while we talk about design patterns and algorithms, we develop in C++, using SFML/OpenGL 2.x for rendering.
Any additional information about implementation in C++/OpenGL are welcome :)
EDIT: I already know about the common design patterns and the MVC architecture, but I look for a far more simple alternative since our goal is not to recreate Qt or Cocoa.
My question is more about an alternative and how to organize these patterns.
I suggest you go over this site, it has a great example from "Gang of 4" (look it up)
great web for design patterns
and there is also a great tutorial in youtube
http://www.youtube.com/user/derekbanas
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 3 years ago.
Improve this question
I'm working on a development road map for a django project. My choosen IDE is pycharm pro and mock up tool is bootstrap studio. One of my criteria is a calendar and I have discovered that none of the existing public projects will meet my needs so I will have to create one from scratch (no problem). My typical approach would have been that the UI and the django project would be done in near parallel periodically merging and diverging the two. However, given the ability of the two software tools, I'm starting to think that that a better approach may be to do the UI first in BSS, next import the templates into the django project and finally perform the django dev to meet the needs of the UI.
The specific calendar functionality is not the issue here, this is a methodology question. While I know that there is a subjective answer to this question (which is not the "answer" I'm looking for here), there also has to be an objective answer as to why this would not work, or be the incorrect approach.
Doing the UI first is fine if you already know exactly what you want it to do and can specify that. Doing the Django first lets you play around with a working rough version and get a better feel for what works best before fine tuning the look and feel. Like you suggest, working on them both together will let each inform the other.
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
I want to implement a "simple" video editor and since I'm new to the topic, I'm not sure how to start.
The editor should have the following features / components
A timeline for multiple recordings
A video player that plays the edited video in real-time (it should render all added effects and assets)
Assets that can be placed on the timeline such as text elements, arrows and so on
I'd like to start with the video player and then build the other components around it.
Which frameworks would you recommend?
For the player, I'm not sure if DirectShow is the right choice or MediaFoundation would be better. Are there other libraries to consider? FFmpeg?
My recommendation given your interests is to start with Blender
http://www.blender.org
It's written in a combination of C, C++, and Python, has a substantial user community, and has the advantage of open source code so you can see how a real large project looks.
You might end up just contributing to it, or you might lift bits of it to bootstrap your own project, etc. But if you don't know about, it's worthwhile to look at if only to help you refine what you want to work on.
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 6 years ago.
Improve this question
After creating reusable Django apps do one make an app that glue them together to create a website? Also is it correct to make each menu item and section an app itself in Django? The source code of https://www.djangoproject.com/ is probably the best example of how to correctly structure Django websites if it is available.
How you organise your project is up to you and mostly depends on the project's specific needs, but yes using a "main" app to glue the pieces together is a common and working pattern. Also you don't have to try and make your project's apps reusable - start with just what your project requires and if you find out some parts solve recurring problems it will be time to factor them out as more generic apps.
Wrt/ your menus they have to match the site features not it's implementation so the "one app one menu" thing very seldom makes sense. And since it's a "glue" part it really belongs to the project's main app (even if it usually delegates parts of the job to other apps).
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?