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
My application is one page contract. I would like users to be able to sign the contract by clicking on a button. The contract is not a resource; it's plain HTML.
Every solution I have found so far relies on having a model that acts as votable. How can I implement a simple button that users may only click once, and display the number of users who have clicked it?
It's not possible to do this with static pages, at least not in a way that is clean and secure.
Think about it this way: every user is looking at a copy of the contract, which is being displayed to them on their browser (the client). If you want users to be able to cast votes that persist and be aware of votes cast by other users, then you need a server that keeps track of it centrally. That's why the solutions you have found so far rely on having a model, presumably backed with a table.
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
I'm a bit new in rails development I'm modeling a website with few resources and so far so good. But here is my question:
I would like to allow the admin users to manage information show in most of the pages: Application name, telephone number, address, default email and this kind of things.
My current idea is make a model Property with name and value, but somehow I'm not convinced about this approach because I'll need to access the database to get this values for every request.
Thanks everyone for your time! :D
This seems like an OK approach. If you implement caching, it no longer will hit the db with every request, and honestly it probably isn't really that big of a deal even without the caching. Build it the way you need, and optimize afterward, if necessary.
With all this being said, it may be worth considering how much things like the phone number are going to change, and balance the cost of developing a dynamic solution against the time it would take to change once, 3 years from now (if the number ever does change), in a partial.
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 7 years ago.
Improve this question
I am currently building an app and would like the option of having users view other users playlists. Is this possible?
Of course this is possible. All this data would be in a database, and you would write stored procedures that would fall in a REST API that you would call from your app. You would need to do the filtering of said stored procedure to show users any kind of data you want (if you only want to show 'friends' playlists, or 'people around you'..etc). Remember, it's just all data. Nothing more. You format the data to look nice, but it's still just data.
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 have an app that is already fully built, the only thing I'd like to add is real-time rendering of one of my pages.
Suppose it is a page with all the pizzas. When pizza is added to the database, I'd like page to show it without refreshing.
I know you can do it with websockets, but is there any easier way? Could, eg, AngularJS help here (as I understand it refreshes the page contents as soon as model is changed)?
Well you could make a small service in Angular that asks the server like every 15 secons or so, to see if there are new pizzas added to the database. (Say the last time you took the pizzas from the server you had 15 of them returned. Now you send that number 15 back with the check request and compare it with the database)
If so, it will call the query method in the pizza Angular service to fetch the new pizzas.
If this is a small table with often changing info then I would also suggest to migrate this model into Redis instead. Asking info repeteadly from Redis is a lot cheaper than it is to ask like this from a database.
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 usually use drop down lists in many scenarios, such as selecting predefined types, parent record, etc.
But currently I am working on a system where a drop down list might have more than 200 records . and I want users to see more info about each record to be able to choose. So drop downs might not be user-friendly and usable in my case.
So what are other components or packages I can use with asp.net mvc , something like displaying a dialog box which allow users to search , filter , view more details about the record before selecting it?
BR
I've used select2 in these scenarios before with good results. It allows you to see the whole list if you need to (just like a regular dropdown) and it also gives you a way to filter the list if you know what you're looking for.
Have you thought about using autocomplete; http://jqueryui.com/autocomplete/ this would solve the problem.
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
What is the best practice for having globally (e.g. from all view controllers) accessible current User object?
I am using core Data.
EDIT:
I just realized I should elaborate a bit (and immediately received a comment regarding that)..
current User means the user who is the owner of the phone and is associated with an entry in the remote database. User enters login/password (or registers) and then can access the remote server, get data etc..
Object visibility is a major part of app architecture. It is up to you to make your objects visible to the other objects that may need a reference to it. No simple rule can be given. I have tips in my book on how to make objects visible in an absolutely global way:
http://www.apeth.com/iOSBook/ch13.html#_global_visibility
For example, store a reference in the app delegate, which every other object can easily get a reference to. But there are lots of other solutions and approaches (which that chapter also talks about). It's a matter of planning ahead.