Community
Participate
Working Groups
There should be a switch on the translation-website to toggle display between translated/untranslated/all Texts.
This is a great idea and would help find work that needs to be done. At this point we are not going to be able to make these type of enhancements until we finish milestones 1 tasks. The babel server code uses the YIU library for doing AJAX/DOM fun. YUI has a tabbed display component. It was my original intention to short all strings returned from the ajax call into 3 buckets untranslated,unrated,translated & rated (a forth bucket of 'all' could be added for completeness). This really shouldn't be too hard to do, patches anyone? gO'
What version of YUI is babel currently using? Do we have the complete package? The only references to the Tabview code have been commented out and those files being referenced are nonexistent.
(In reply to comment #2) > What version of YUI is babel currently using? Do we have the complete package? > Babel is currently using a small subset of YUI 2.3.1. There is an open CQ for the entire 2.5.2 minus the docs and examples (for the Phoenix project) that is awaiting analysis. When (and if) 2.5.2 is approved the Babel team plans on using 2.5.2 as well. These are the YUI files we currently have permission to use: yahoo.js dom.js event.js connection.js logger.js All the above files are located in 'server/html/js/yui2.3.1/' in the Babel CVS repository. Let me know if you have anymore questions.
Since the tabview class isn't currently available (and I read the bug too quickly) I implemented a solution that filters the FILES that are displayed using a simple dropdown (all, translated, untranslated). Since this isn't the nature of the original bug, should I open an enhancement to filter the file list and attach my patch there? Also, what do we have to do to get the tabview YUI code into babel? Or, do we still want to follow the tabbed approach?
> Since this isn't the nature of the original bug, should I open an enhancement > to filter the file list and attach my patch there? Yes, please. Thanks! > Also, what do we have to do to get the tabview YUI code into babel? Or, do we > still want to follow the tabbed approach? We just need to wait for Eclipse Legal to approve YUI 2.5.2.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
