|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > The Visual Editor doesn't handle custom components
|
|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > The Visual Editor doesn't handle custom components
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| The Visual Editor doesn't handle custom components - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
jon Member
|
Hi We are currently evaluating Sisulizer. First of all I'm impressed with the 1.0 version of the product. I've could commented some minor issues, but the most important issue for me right now is the Visual Editor: It's not able to layout our forms wich in general use both inhouse and 3rd-party components. We also have base classes for most our dialogs and childforms. I suppose the main problem is that you don't use the .NET-designer?? But do you plan to make improvements to your Visual Editor and can we expect our forms to show in the near future? Even standard .NET controls doesn't show up right when mixed with our components. Any comments on this?
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Hi, You are right. We do not use .NET designer. The reason is that it would require the translators to install .NET runtime and all possible .NET libraries in order to get visual editor working. Instead we have collection of UI component and we use component mapping where a .NET component is mapped to a Sisulizer's component. We have premapped the component of .NET runtime and some of the most common 3rdParty components. However if the component is not mapped you can map it by clicking a unmapped component and selecting a component type from the list. We are currently improving .NET localization and visual editors. We will premap most popular 3rdParty components and cheking that visual editor is as much WYSIWYG as possible. However Sisulizer users still have to map their own custom controls. You only have to mapping once. Sisulizer remember the mapping. Mapping is also very fast. The advantage of all this is that Sisulizer's translation edition (the one your translators use) does not need any .NET runtime or library. Standard Windows 200, XP or later is enough. I you have wishes please tell me. I am happy to improve your .NET support. Best regards, Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
jon Member
|
Jaakko.Salmenius wrote: However Sisulizer users still have to map their own custom controls. You only have to mapping once. Sisulizer remember the mapping. Mapping is also very fast. Thanks for quick response. I've tried to map the controls, but they don't shown up right anyway. I've tried many different mappings 
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
What kind of controls they are. If they are 3rdParty controls please tell them name. I will check them. What about your inhouse controls. What kind of controls are they. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
jon Member
|
They are mostly composite controls built up of several standard controls on a System.Windows.Forms.UserControl. jon
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
I see you point now. Composite controls that do not belong to the project file are a bit problemetic. Currently Sisulizer can not show their content on the visual editor. However Sisulizer scan and addes the string of the control to the project and you can localize them. If a UserControl is a part of the project Sisulizer scan visual show it. I will study to a bit more and come back early new week. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
jon Member
|
Thank you. The Visual Editor also have problems with drawing the correct size (and form) of these controls boundaries. It also seems like they disturb the drawing of standard controls.. I'll quit testing the Visual Editor for now. And focus on other areas of Sisulizer  jon
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
ajensen Member
|
I am also having these same issues. We use third party components from DevExpress for our GUI, plus a few user controls. None of these are showing up correctly. Even when I try to map them I do not get the correct layout of the form.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Can you tell what is the DevExpress component library that you use?
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
André Bitzer Member
|
Hi We use quite a lot of them, but it seems that sisulizer has problems to show all of them correctly. Do I have to add a reference to the source files or the assemblies of DevExpress to my project? Or is there an other workaround? Best regards, André
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
If Sisulizer does not know what is the type of the component it will show a pink panel where is Click me to map text. This means that component is unmapped. In susch case you need to tell Sisulizer what is the type of the component (e.g. button, label, check box, etc). Click the Click me text and choose the component. The rescan the proejct after you have mapped the components. On rescan Sisulizer will use the new mappings. If you tell me the name of the DevExpress component library we will premap the components. Best regards, Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
André Bitzer Member
|
Thanks in advance. We use - Developer Express .NET 2005 v6.2 and for example the "XtraNavBar"-Control. Unfortunately, there is no similar Windows-Control to map to. Since we do have all the source code, there is maybe a way to add a reference to them in my project. Best regards, André
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thanks. I will download this component library, test it, and map the components. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Is it this control http://www.devexpress.com/Products/NET/WinForms/XtraNavBar/
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
André Bitzer Member
|
Yes! Actually we have the following product: DXperience Enterprise v.6.2 this includes a lot of different controls, more infos: http://www.devexpress.com/Products/NET/DXperienceEnt/Index.xml Thanks André Last edited on Thu Nov 2nd, 2006 11:36 am by André Bitzer |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi André, I downloaded this and am currently testing and mapping items. The library contains dozens of controls and some of th are quite complex to use so this is going to take few days. I let you know when I have completed it. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
André Bitzer Member
|
Hi Jaakko Sounds great. In this case, you will be able to fully support this controls for visual localization? Thanks for your support! André
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
Hi Not fully visually (some of the component are very complex) but better than now. In any cases all the string that the component contains always gets to the project and are editable on the sheet. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
DREYFUS Member
|
I Still have the same type of problem with "home-made" control (in BC ++ Builder V5 , from *.BPL files)The concern control DONT SHOW PROPELLY and make a MESS of the other control , this in Sizulizer V268 //6 October 2008 , 2 Years after these related problems ..... SEE my question : "Home-Made" Controls Problems /6 OCT 2008 JC DREYFUS PARIS
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Janusz Grzybek Super Moderator 
|
I Still have the same type of problem with "home-made" control This job will never end. Authors of developer tools and components still improve their components and release completely new components. This is result of technological progress and we couldn’t expect what will happen in next year. Two years ago you couldn’t to find any ribbon components, now on every PC you could to find software use these components. For this reason I think in next year and next after next users still will be ask about mapping new components. Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 04:42 pm | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > The Visual Editor doesn't handle custom components | |
Sisulizer software localization tool - Three simple steps to localize
