At the moment we store the location and date of observing data for each bookmark item and this is not very frequently use by users.In future we may add tool for import observing lists from website (online import data) - of course if this tool will be very appropriated by users and we'll get feedback.All files in UTF-8 and we may use special extension for separate lists (an exchange format of data)."Empty" observingLists.json should store one list without objects - Bookmarks.Formal we may store only English name (or designation) and coordinates of object (currently in bookmarks we use coordinates to create a custom marker for object, who is not finded in Stellarium's objects) - and adding the coordinates (for finded objects - current coordinates), magnitude and abbreviation of constellation into table on stage of visualization of list. Translation should be applied on stage of visualization (creating table of view) data. All list shouldn't be stored translated data - english only names of designations.Export and import tool should export/import list of bookmarks as currently implemented (subset of observingLists.json file).Unique ID already implemented for current bookmarks. Any list should storing 2 additional hidden properties for manage import/export of the data - unique ID and data of latest changes. We may store all lists in one file - for example observingLists.json - and this file just storing list of lists.The Bookmarks tool will be deep refactored and visually splitted on 2 window - the first windows for using lists of bookmarked objects and the second list for adding/editing lists of objects. The bookmarks will be completely redone to become observation lists. This ticket will be attached to the pull request. I create a ticket to formalize the development of this new feature.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |