I am using EGORefreshTableHeaderView in my app.
In that I am refreshing one part of the app and showing the last updated date using egoRefreshTableHeaderDataSourceLastUpdated method. Also in another part of the app, I am refreshing some content. Also I am showing the last updated date and time, but I am unable to differentiate the last updated date and time between the two update.
How could I fix this?
I guess you need to implement EGORefreshTable separately in every view you want to update your content. You can not use same for all other part of the app. Still you can differentiate with some kind of app. It is hard to answer without knowing about your app structure and what do you meant by another part of app.
Related
I am creating an application and trying to figure out best way to deal with navigation in it. User can choose different view settings (which content to show and options to filter it). Part of settings is stored in backend in user preferences model. Another part is stored in url and managed by router. But there is more settings I want to keep. The reason: I want to be able to refresh content therefore I need to keep settings somewhere, not update content on user actions and forget how I came to this state. My question is: what is the best place for such settings? Collection object? View object? My own controller?
P.S. to make it more clear, I'm working on rss reader application. And I want, for example, to show last week posts from certain feeds which are starred etc.
Save it in the URL. Thats the only place you can really rely on. If you need more then routes use query parameter like in a classic web application and use them in the view.
I'm working on an application using Play 2.0.4 in Scala, and one of the features I was asked to implement is to build a form that remembers all of the edit history. Basically, there should be a button next to every field that shows the details of every change, because the app users may want to rollback or use the edit history information later.
The first idea pops up in my mind is to assign a hidden div to every field that appends every change, and only shows the div when users click on the corresponding button. This doesn't sound very hard, but I feel like it may make the HTML a mess (since each user has his own record, each record has many fields). Or I could make a copy of the database and store all the changes inside, with the primary keys changed to be both the id of the form, and the edit time.
Thoughts? Am I overthinking the problem? Is there a more elegant way to store all of the edit history? We estimate that there would only be around 200 people in the company using it, so I guess I can let efficiency slide a little...
Thanks in advance.
I would normalize and persist the record in the database. This would allow you to have history on changes by having a history table for each section that they with to rollback.
This would allow manageability of restorations based on sets of data and significant changes can be tracked. Managing each field separately would be very cumbersome and least pragmatic.
So some background, I am working in GWT, using MVP and activities and places. So I have all my stuff working with hyperlinks, and places are changing. I am also using a PlaceController.gotTo(Place).
Now what I want to do is be able to send the person to another place but programatically. Right now with the setup GWT manages the converting of the url into a place, and then fires the activities from that, but what I would like, is to either convert a url to a place, using the same way gwt does it or change the url, and fire a history changed type of effect onto the site.
What I don't need is an anchor to reload my whole site, I just want to feed a string into something and get the whole place change situation moving.
I want the effect of a hyperlink.
I'm not sure I understand exactly what you're trying to do, but PlaceHistoryMapper is the only tool that GWT uses: feed a String to getPlace and it gives your the corresponding place. Alternately, you could use History.newItem (note that contrary to PlaceController#goTo, if the user cancels the PlaceChangeRequestEvent, the URL would have already changed).
Let's say we have a mobile app (iPhone, Android) already deployed and being used by people.
Is it possible to change text on buttons, title bars, or even shape or colour of these things without a major update? What I mean is, do we have to deploy an update to the whole app (for example, new version) in order to change one single text on the button? Or maybe these things (settings) can be stored in some kind of database or XML?
Help me out on this one please. Thanks a million.
Is it possible to change text on buttons, title bars, or even shape or colour of these things without a major update?
No. You have to deploy a new version, even if you want to change a single thing like that.
It's possible to do changes to an existing app without deploying a new version, but in your case it's not possible. This is how it works:
You create a mechanism to check for new updates.
New updates can be new data, new settings, etc.
You make your app download and use that new data.
The problem here is that you have to have already deployed an app that do the steps above. Since your app currently does not have that implemented, there's no way to do any changes to it but updating it.
You have to update your app. I implemented the consumption of a JSON string recently to display a Message of the Day periodically. It also keeps a "low watermark" that I compare against the user's running version. If their version is too old I present them with 2 options: upgrade or quit.
You could as easily make your text work in the same way. Just be sure to keep a local cache in case they don't have network access. Will require some healthy refactoring.
you are able to store the text of buttons in values/Strings.xml and set them to the controls by text="#String/text_for_buttonxy" . This is grat for multiple languages, because you are able to put the Strings.xml in a country-code ending value folder like values-de values-en or values-fr in order to get the right String based on the phonesettungs.
Vor colors you are able to to the same thing with the colors.xml.
But you won't be able to change this xml file by synchronisation with a server, this will be a litte bit more complicated, please explain how to you want to change the settings.
I want to allow the user to enter a valid date using the iPhone’s settings application.
I have experimented with many of the PreferenceSpecifiers data node types including date.
I have two issues:
When I specify date as the type, my app within the settings app crashes. Working examples would be greatly appreciated.
Since this approach hasn’t worked for me yet, will I programmatically be able to validate the date that the user enters?
The answer to number 2 is no. The only time you can validate the data entered is the next time your app is launched. None of your app's code is run via the Settings app.
You might consider pulling this setting into your app.
Have you read this guide and this section of the App guide? They describe in detail how the settings like this work.
You won't be able to validate anything a user sets through the Settings application. Also, I don't see Date as a valid setting type anywhere, so I don't even think this is possible through the Settings application.
I would simply create a settings view within the application. That way you can control your custom logic as you see fit.