|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Real Designer for the VCL-Form View
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Wish list for software localization tool > Real Designer for the VCL-Form View
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Real Designer for the VCL-Form View - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
stoyan Member
|
Hi, Have you considered including a "real" designer for the VCL-Forms? This way all components can be show. Right now, most of the DevExpress components for example doesn't show at all (or at lease the form looks kind of strange). We have recently purchased the form editor from http://www.econtrol.ru We are using it for run-time customizations of our forms. Seems to work very good. And it can directly handle the DevExpress Grid and even the Layout Control (I have seen a couple of questions about it in the forums). It is for Delphi VCL only, but you can even include run-time packages of unknown for you components, which will then show correctly in the designer. Your customers would have double benefit from such integration: 1. Every component can be correctly shown, means Form Layouts will not be broken. Non usual components can be included on run-time via BPLs. 2. You can even reposition/resize components, if there is not enough space for the translated version. So please take a look on it. We are using DevExpress almost everywhere, so translation is not very beautiful right now. Best regards, Stoyan P.S. I am not affiliated with econtrol.ru. Just a customer. There are also other VCL Designer Components which might be suitable.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Hi Stoyan, We considered using native VCL code on our VCL form editor. However we decided not to use it. Here are the reasons: 1) In order to use native code Sisulizer has to use the runtime packages of the component library. To make that work the package must be compatible for Delphi version that was used to compile Sisulizer itself. Customer might use some other Delphi verison and his BPL would not be compatible to Sisulizer's Delphi version. 2) Developer for sure has BPL that he/she uses. It might also be that they are compatible to Sisulizer's VCL version. However it is the translator that needs the WYSIWYG. In most cass he/her does not have BPLs. Developers would have to send them to his/her computer. This is against most license agreement of 3rd party components. You can deploy them with your application but not of any other purposes such as with Sisulizer's translator edition that is considered as development tool. This license issue is a show stopper here. 3) Sisulizer is a multiplatform localization tool. Our form editor must be able to handle not only VCL but WinForms (.NET), WPF (.NET), Silverlight, classic VB, XLIFF and Qt. More are coming. When we decided to use a platform independern form editor we can share the same code for all platforms. I know that our current solution won't bring 100% WYWIWYG but it is enought for localization purposes. Even when Sisulizer fails to show item visually it shows the strings the item contains and it can be localzied. This way we can make sure that translator always get visual editor too without needing to install runtime engine (.NET) or 3rd party components. Best regards, Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
stoyan Member
|
Hi Jaakko, thank you very much for the quick response. I must add, that I actually like your product very much and am quite happy with it. Still, it is almost Christmas, so everybody has an extra Wish (or two) :-) I do understand your arguments and they definitely make sense. Different versions of BPLs and Licenses of 3rd party makes it impossible for you to deliver single version. But this made me think... Given that: 1) Susilizer is written with Delphi, so you know Delphi very well. 2) Normally, when developing Delphi project, the right Delphi version and Packages are available at the developers site (usually on the same computer). There are some interesting possibilities: 1) You can provide IDE-Intergrated version of Susilizer. You get all the right packages right from the IDE. 2) You can call the DCC to "compile" custom translator application, which includes the right BPLs (as statically linked or as run-time BPLs). This way it will be a new compiled application and not a developer tool (so no license problem). 3) You can provide Delphi-Components (Tools, BPLs, DCU, etc, even source code if you like) so we can build our own custom translation tool specific to our application. This way we can even offer translation for our run-time generated forms (which we do also with the econtrol.ru designer and are saved in the database). I know, Delphi (VCL) is not that big of a market anymore (compared to .NET), but hey, it is Christmas :-) Best regards, Stoyan
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
stoyan Member
|
Hi Jaakko, one more idea to my previous post: ... 4. Just encapsulate your visual editor in kind of a plug-in, define clear interface (where to show, what was clicked, etc.) and let us write (and plug) our own editor. This way, I can put all my components in it (home cooked or 3rd party) and everybody is happy :-) This way you can later also provide yourself diffent editors for different plaforms (if required). I can imagine that silverlight or the new javafx could need special editor. Best regards, Stoyan
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for your ideas. We are currently implementing a feature called preview view. It is something similar to visual editor but is is read only. No way to move components or resize them. The purpose it is give as 100% WYSIWYG view of the item currently being localized. We will bring this first to HTML. Whenever there is both visual editor and preview view available the use can choose what one to show. I will think about possibility to implement preview view for VCL. That would use actual package files and the WYSIWYG would be the same as in runtime or in Delphi IDE. About plug-ins. They are currently on our roadmap and will come to Sisulizer at some point. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
djayc Member
|
Hello Jaako, I'm evaluating the Sisulizer software. I installed Sisu latest build 281 but i can't see the DevExpress grid columns on the visual editor. Is there any way that we can see the DevExpress TcxGrid DBBandedTableView or DBTableView columns on the Sisulizer visual editor? Take this object as an example: object cxGrid1: TcxGrid Left = 0 Top = 0 Width = 417 Height = 467 Align = alClient TabOrder = 2 object cxGridCNoteCapture: TcxGridDBBandedTableView NavigatorButtons.ConfirmDelete = False NavigatorButtons.PriorPage.Visible = False NavigatorButtons.NextPage.Visible = False NavigatorButtons.Insert.Visible = False NavigatorButtons.Append.Visible = False NavigatorButtons.SaveBookmark.Visible = False NavigatorButtons.Filter.Visible = False OnFocusedRecordChanged = cxGridCNoteCaptureFocusedRecordChanged DataController.DataSource = dmDrg.dtskbmCNoteLine DataController.KeyFieldNames = 'pk' DataController.Summary.DefaultGroupSummaryItems = DataController.Summary.FooterSummaryItems = < item Format = 'Items: 0,' Kind = skCount end item Kind = skSum end item Kind = skSum end item Kind = skSum end> DataController.Summary.SummaryGroups = OptionsBehavior.FocusCellOnTab = True OptionsBehavior.FocusFirstCellOnNewRecord = True OptionsBehavior.GoToNextCellOnEnter = True OptionsBehavior.NavigatorHints = True OptionsBehavior.FocusCellOnCycle = True OptionsData.Inserting = False OptionsView.ShowEditButtons = gsebAlways OptionsView.CellAutoHeight = True OptionsView.Footer = True OptionsView.FooterAutoHeight = True OptionsView.FooterMultiSummaries = True OptionsView.HeaderAutoHeight = True OptionsView.Indicator = True Preview.Visible = True Bands = < item Caption = 'Item' Width = 302 end> object cxGridCNoteCaptureColumnrecord_pk: TcxGridDBBandedColumn DataBinding.FieldName = 'pk' Visible = False VisibleForCustomization = False Position.BandIndex = 0 Position.ColIndex = 0 Position.RowIndex = 0 end object cxGridCNoteCaptureColumna_brand_name: TcxGridDBBandedColumn Caption = 'Brand Name' DataBinding.FieldName = 'b_name' Options.Editing = False Position.BandIndex = 0 Position.ColIndex = 2 Position.RowIndex = 0 end object cxGridCNoteCaptureColumntotal_value: TcxGridDBBandedColumn Caption = 'Expected Total' DataBinding.FieldName = 'total' PropertiesClassName = 'TcxCurrencyEditProperties' Options.Editing = False Position.BandIndex = 0 Position.ColIndex = 3 Position.RowIndex = 0 end object cxGridCNoteCaptureColumnsupplier_total: TcxGridDBBandedColumn Caption = 'Supplier Total' DataBinding.FieldName = 'supplier' PropertiesClassName = 'TcxCurrencyEditProperties' Position.BandIndex = 0 Position.ColIndex = 4 Position.RowIndex = 0 end object cxGridCNoteCaptureColumna_atkode: TcxGridDBBandedColumn Caption = 'ZI Number' DataBinding.FieldName = 'a_atkode' Options.Editing = False Position.BandIndex = 0 Position.ColIndex = 1 Position.RowIndex = 0 end object cxGridCNoteCaptureColumna_applied: TcxGridDBBandedColumn Caption = 'Applied' DataBinding.FieldName = 'applied' PropertiesClassName = 'TcxCheckBoxProperties' Position.BandIndex = 0 Position.ColIndex = 5 Position.RowIndex = 0 end object cxGridCNoteCaptureColumnsupplier_ref_number: TcxGridDBBandedColumn Caption = 'Supplier Reference' DataBinding.FieldName = 'ref_number' Visible = False Position.BandIndex = 0 Position.ColIndex = 6 Position.RowIndex = 0 end end object cxGrid1Level1: TcxGridLevel GridView = cxGridCNoteCapture end end end Regards, Duarte
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator 
|
Hi Duarte, The preview view Jaakko talked about is not yet available. You have to use mapping in the meantime. This is not the perfect preview in any case. Off course you can localize the strings. But it has the advantage, that your translator does not need to have a developer license of the controls you want to localize. It can become expensive really fast if each of your translators need to have a license of DevExpress just to see it in the editor. This is needed because some controls have own data storage and the need to think that they are in a development system to draw the interface. Unlike standard controls where Sisulizer can draw the GUI third party controls have own drawing routines who need to be invoked. You see, even if the mapping does not look as fancy as the original it has many advantages. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
djayc Member
|
Hello Markus, Thanks for the explanation. Can the mapping features help me get the standard visual information of a grid like the column captions and width? For example, say that tcxgrid.dbtableview.dbcolumn means that it is a generic grid.column. I have already set tcxgrid as a grid but that didn't help much. Regards, Duarte
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Duarte, It would be not fair if I would promise you some better preview for the near future for these grids. Our R&D is working already at 110% to fulfill promises made in the past ;-) Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 04:03 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 > Real Designer for the VCL-Form View | |
Sisulizer software localization tool - Three simple steps to localize
