|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Reports and history in the Sisulizer
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Reports and history in the Sisulizer
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Reports and history in the Sisulizer - Wish list for software localization tool - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Several days ago I happened dangerous accident for my project - after updating sources (new version of file) I rescanned source, filtered and checked all new, and unused rows, but I forgot to check changed rows before flags resets – after similar accident translation of some strings could be incorrect. Happily I had additional, old copy of this project. After this accident I thought about any solution for this problem, because similar critical situations should be track able. I created small project of integrated system of reports contains also implementation this idea to the SL, but it is only very lose idea in my head. This is not such concrete suggestion like , for example proposal adding pathname of note to status bar, but only general vision certain idea. The Sisulizer already have possibility of creation various reports, but reports can be created only for currently executed actions, and are placed in several locations. I wait for your opinion and suggestions about described below project: Terminology: Event: operations executed by users (e.g. building, scanning, etc) trigger automatically saving specified for selected operation information to log Logs: Information saved after triggering events. This information can be exported to HTML. Report: External HTML file contains selected by user logs information. Types of log: - Translation (event: Saving of project) - Validation (event: Validation of project) - Scanning (event: Scanning of project) - Changes in original (event: New, Changed and Unused status after scanning) - Removing unused items (event: Removing unused items) - Clearing of statuses (event: reset flags) - Building (event: Building of item) - Import (event: Import) - Export (event: Export) - Exchange (event: sending or receiving of packet) - Saving to translation memory (event: Saving to TM) - Translation with translation memory (event: Translation with TM) - Statistics (event: Closing of session with project, or date) - General information about information (event: creation of project) - Others not listed important elements (excuse me, if I forgot any important elements of projects) Sample contents for some logs: Translation (for all translated rows): - Path of translated item - Original text - Date and time of changes - Status of translation (e.g. translated, changed, cleared) - User Changes in original (for all changed rows in original): - Path of translated item - Original text - Date and time of scanning - Flags (e.g. new status, changed status, unused status) - User Implementation to GUI: First I thought about special dialog window (for example available from command in Project menu) for system of report, but better solution will be adding new tab (for example with name “History”) in panes on bottom of main window (Validation, Output etc.). This location will get users quick access to creation reports. Pane should be to contain following items: 1. List box with list of all logs. List box should be contain following columns: - Date and time - Title of log (for example Building, Scanning or Translation) All columns should be to have possibility of sorting by title and date (by columns header). Sorting of contents may be very useful feature for user, for example user can sort all items of list box by title and quick find all scanning logs. Additional all logs selected by user in list box to adding to report should be highlighted in list box (for example by other color or bold) 2. Option for adding selected logs to report 3. Option for creating HTML report 4. Filter options – for filtering selected types of logs in list box. Filtering allow users disable displaying unnecessary logs in list box. For example list can contains lot of items of translation logs (this logs will be saved with every saving of project), and displaying only information about building, removing unused items etc. Filters should be contains checkboxes for all types of logs, for example Translation, Validation, Building etc. 5. Option for disable saving contents selected types of logs (as above). 6. Option for opening window with quick preview of selected log (plain text). Report contains formatted HTML text for one or more logs, Preview of log will be to contain only information from one selected log. 7. Option for Select all 8. Option for Unselect all 9. Option for remove logs Additional options: 1. Option for completely disable saving of logs for example in General settings 2. Option in Exchange Wizard for disable adding logs to Sisulizer packet. Sample reports: Reports created in this way can to contain any information saved while working with project and could be concerned to any types of operation and dates. First example - contains information about all operations (events) executed in selected day. Below are selected logs to saving in report. Of course, every log contain detailed information visible after creation of report. 2007-03-11 10:05, Scanning 2007-03-11 10:06, Changes in original 2007-03-11 10:20, Removing unused items 2007-03-11 10:55, Translation 2007-03-11 10:57, Clearing of statuses 2007-03-11 12:05, Translation 2007-03-11 12:07, Validation 2007-03-11 12:30, Translation 2007-03-11 12:32, Building Second sample – contains information about one type of event (operation) for whole time working with project: 2007-02-25 12:35, Building 2007-03-01 14:55, Building 2007-03-09 10:07, Building Summary: Reports created in this integrated system will be very flexible, comprehensive, concern to any moment during localization process, and will be created in one location of GUI. These reports can also help users undo unwanted changes or they will send these reports to their employers. I wrote above that it is only lose idea, but maybe my “lame” suggestion will provoke you to finding professional solutions. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Small supplement: Sometimes, one idea provoke next idea, like in this case… 1. Additional information about row in sheet. Let’s assume that you implemented my reports idea to the SL, all information about all translated rows will be saved to logs, and user has access to these information via “History” tab, but good idea will be adding also new columns to sheet (information for these columns already was saved to logs): - Date and time last modification for translation - Date and time last modification for original These columns give users quick and easy access to information about last changes (new translated or modification) for translated rows, and (after rescan) for original rows, additional could sort all rows by modification date and quick find searched changes. 2. History of row I propose also adding new window with whole history of selected in sheet row (translation, and original) accessible, for example from Row Menu and Toolbar, contains all information about changes in selected row while localization (new columns in sheet described above contains only information about last modification). Below are example for sample information about row for translation and original: 2007-02-28 15:31 – Translated 2007-03-10 14:36 – Changes in original, set changed status 2007-03-10 14:42 – Changed translation 2007-03-10 14:42 – Cleared changed status 2007-03-11 10:44 – Cleared translation 2007-03-11 10:47 – Translated Row history should be contains information from Translation log (translated changed, cleared), and from Changes in original, Clearing of statuses logs. For big projects good solution will be adding also name of user changing data of row. Row history, together with reports system will create complementary information system for SL, because: a) List box in History pane will be contain information about ALL events for ALL rows b) Log will be contain information about SELECTED event for ALL rows c) History of row will be contain information about ALL events for SELECTED row. For this reason, it seem that History window will be good solution. Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Sometimes, one idea provoke next idea, like in this case... While my thinking about solution for reports access from "History" tab in main window of the SL, I invent new idea for all panes (e.g. validation, output tab). Do you think about adding new option to every bottom pane – "Open in new window" for opening undocked, independent window with all typical windows controls, for example horizontal and vertical scrollbar, minimize, maximize, close buttons, possibility of resizing, and eventual, additional option for adding grid (rows or rows and columns)? Possibility of opening pane in independent window increase comfort of working with the Sisulizer, I think it is very interest idea. BTW Do you think about moveable panes and moveable and fully customizable toolbars, customizable shortcuts, and new theme (Office 2003, Vista) for the Sisulizer in future? Best regards Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Siikanen Administrator
|
This on a very good feature. We will implement it into next major build (2.0). regards, Ilkka Last edited on Wed Mar 14th, 2007 03:44 pm by Ilkka.Siikanen ____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello friends, Thank you for interest my ideas. I am pleased I can help you in improving the Sisulizer. Implementation Reports feature will be probably hard job, but do you think about earlier implementation (in version 1.xxx) - before implementation Reports future - my idea about opening already existing tabs (panes) in new windows? Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Ilkka.Siikanen Administrator
|
"Reports feature will be probably hard job, but do you think about earlier implementation (in version 1.xxx) - before implementation Reports future - my idea about opening already existing tabs (panes) in new windows?" Yes, that can we implement before 2.0. Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Ideas described above about reports and history requires total rebuilding of the Sisulizer and probably implementation of these features take lot of time, but I have also some suggestions for already existing reports features, that can improve convenience of using it. Every time when I would like to create selected report (for example Output report) I can replace existing html report file or change report name or path, if I want keep previous generated report. Below is some samples reports from typical translation process (three sample steps to localize  ).Attachment: Screenshot1.gif (Downloaded 39 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Scan... Attachment: Screenshot2.gif (Downloaded 37 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Build... Attachment: Screenshot3.gif (Downloaded 37 times) Last edited on Mon Oct 1st, 2007 11:34 am by Janusz Grzybek ____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Unfortunately, current method of reports saving is inconvenient for users, because translator need every time to change name of report, if he want to keep previous reports. Additional, translator need open several html files, If would like to compare contents of reports. Do you think about adding “Append” feature to save report dialog (active only, if selected report exists). This feature should copy partial (new) contents of created report to existing report, for example whole contents after <h1>report title</h1> to </table> tag should be copy to line before </body> in existing report. Below is example with above output reports integrated to one report. Best, Janusz Attachment: Screenshot4.gif (Downloaded 37 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Of course this feature could to be helpful only for output and statistics reports, but not for validation and TM reports I think. And next step… Do you think about adding auto-save (appending) to html reports option for statistics (trigger: saving or exit from project) and output (trigger: events in output pane)? Best, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 02:27 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Reports and history in the Sisulizer | |
Sisulizer software localization tool - Three simple steps to localize
