here is the problem I have. I have a CoreData app with CloudKit functions. So far everything works fine.
A table with entries is displayed. About a column I rule the position of the entry. The entries in the list I can then also move them and the column is adjusted accordingly. So far so good. Now there is the shard function where I can share entries from the table with others. As soon as another user moves the entry, this entry is then also moved to me without me wanting that. I think I have a design problem here, but I don't know how to solve it differently. Do you have any ideas.
Related
I am a Django noob and have a situation that goes beyond the basic documentation, etc.
I am updating an ordering webpage that has a form structured as follows:
several text boxes, etc to gather general info (name, date, etc)
two separate tables for selecting (via checkbox) catalogs that are generated/managed using endless_pagination. Each table can have thousands of records, hence the endless_pagination. The first column in each table is a checkbox with value = catalog.id.
a textbox where the user can manually enter catalog IDs
a submit button
I am not sure how to keep track of what a user has selected in the two paginated tables since the checked boxes are lost when choosing a different page. Also, when the user flips back and forth between the pages, the previoulsy checked catalogs will need to be re-checked(since the checked state is not maintained). I am also not sure which tool(s) to use to deal with this.
My thought is to use JavaScript (with which I have minimal experience) to update a list of catalog IDs whenever a checkbox is checked/unchecked and:
- and attach that list to the form or
- update a variable in the form or
- send as a variable separate from the form, whichever is possible/makes more sense.
I'm hoping that maintaining a list of catalog IDs is possible because the next iteration of this form will likely include some sort of filtering so I'm trying to devise a solution that will not have to be reworked later.
I have reviewed a lot of posts but I believe the closest solutions are rendered useless because of the endless_pagination.
Let me know if further clarification is required. Thanks in advance for any suggestions.
UPDATE
I tried using JavaScript to store the catalog IDs in an array when a checkbox is checked. This does not work when a user selects another page in the pagination. The array of checked catalog IDs is lost when the page 'reloads'.
I'm running into this problem right now as well. I'm handling this by writing the checked items to localStorage so they carry across to page 2, 3, etc.. as well as show up as already checked when you go back to page 1. Then every time the page loads, either find and check the existing checkbox, or create a hidden input with the appropriate name and value and append it to the main form.
var selected_items = []
function add_item_to_checkbox(item) {
localStorage.setItem('selected_items', JSON.stringify(selected_items));
checkbox.on("click", add_item_to_checkbox);
bahh... Just look at my jsfiddle it's easier to read and yeah. I don't have to type JS into a textarea on stackoverflow.
Here is my javascript minus a few things that are specific to my code. I'm sure it could be improved upon but it works really well for my application.
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.
I encounter a strange error. On page-module level i´m not allowed to create new page elements. If i do the same via the list-module page-elements are created and i can edit them (even in the page-module).
Also, if i created a flexible content element - e.g. columns - (via the list module) i CAN create new elements in the flexible content element, even in page module.
New elements are always on TOP of the page, meaning the first entry, and i can´t drag and drop them. Well, i can, but changes do not come in effect. To sort the elements I have to edit the page properties, and sort content.
The user has every right(!) given by the user settings, and it is TYPO3 4.7.4
Does anyone know where i have to look for a solution? Thanks in advance!
Edit 1
This error appears in the log:
Attempt to insert record on page '[root-level]' (0) where this table, tt_content, is not allowed (msg#1.1.11)
Again: Creating Elements IS working via the List-Module.
This error is causen because the field t3ver_swapmode in the page table was removed since TYPO3 4.7 (Maybe in combination with TemplaVoila).
I dont know whats exactly going on here (didnt had the time to find that out), but the solution is of cource simple. I uploaded my fix to the TYPO repository under the key swapmodefix http://typo3.org/extensions/repository/view/swapmodefix
The extension appears in a couple of hours, good luck!
You need to select a page inside the pagetree first. You may not create content elements on the root page.
It might be that the selection is lost, but still visibel. Just click the page again.
I am new to IOS and coreData Framework..from past 2 days m reading tutors regarding coredata..I understood few concepts..but i am confused..can you all please suggest me good tutorials regarding coredata.
So my second problem..I am building a application..where my first view has a text field and a search button..and an empty table..so when the user enters a search query and hit the search button..it opens a another view which gives him a list of values in a table and again when the user cliks on a specific cell he is agian taken to page which contains some values..so on this page ,I want to have a button name (xyz) which when cliked..will save that particular value in the table which is present in the first view..and similarly the process will conitnue..
So i want to know..whether coredata is necessary for my problem or any diffrent menthods are available......
Please reply..m waiting for your respones..
Regards
RRK
Core Data manage very well sqlite database.
You can learn on the apple developer website :
http://developer.apple.com/library/ios/#documentation/DataManagement/Devpedia-CoreData/coreDataOverview.html
And there is a quite good tutorial here :
http://developer.apple.com/library/ios/#documentation/DataManagement/Conceptual/iPhoneCoreData01/Introduction/Introduction.html
I think core data is a very suitable solution for your problem.
I have one requirement that I need to mark the table item when the user has already viewed that item in the table.
It is exactly like emails in the inbox. when the user reads the mail, the font will be changed to normal. The same way I need to implement. For that I used Font for the table. Now i need to save the state for the table item. When the application restarts, the table item which the user has already viewed should be seen as viewed item. I mean normal font. Is ther any way to save the state for the table item?
Thanks
Bhanu
An alternative - if we are only talking very little data, e.g. a pointer to the last read item - you can use the view state. See IViewPart.init(IViewSite site, IMemento memento) and IViewPart.saveState(IMemento memento). This method is not very useful if you have lots of data as the storage is rather ineffective.
If your bundle activator subclasses org.eclipse.ui.plugin.AbstractUIPlugin or org.eclipse.core.runtime.Plugin you can use org.eclipse.core.runtime.Plugin.getStateLocation() to get your plugin state location. You can use java.io.File and FileReader/FileWriter to store information there across sessions. See org.eclipse.ui.plugin.AbstractUIPlugin.saveDialogSettings() for an example of how a this plugin stores dialog settings there.