uilabels and screenlet widget

[Hans Bakker <ma...@antwebsystems.com>]

Hi Adrian...

Thank you very much for the excellent work you are doing. I just
received a compliment from a customer who just upgraded from a year ago:
he especially mentioned that the user interface is now so much better
looking.

I like to use your new features and have some comments:

the upgrade from the properties to xml files, now use a simple editor
and you can see if a text for a language is missing. However it looks
like when the key is not found the system does not display the
translation of the label which is normal, however at the moment it does
not display anything, shouldn't it display the key value?

The screenlet widget: another excellent peace of work, i am now using it
in the projectmanager and surely save a lot of code and you are able now
to use command and paging in the screenlet header.
But here also a comment: the title of the screenlet, shouldn't that be
on the left and not on the right?
Then there is a menu name, but not a menu location?

Regards, Hans
-- 
AntWebsystems.com: Quality OFBiz services for competitive rates.....

Re: uilabels and screenlet widget

[Jacopo Cappellato <ti...@sastau.it>]

Hans Bakker wrote:
> ...
> the upgrade from the properties to xml files, now use a simple editor
> and you can see if a text for a language is missing. However it looks
> like when the key is not found the system does not display the
> translation of the label which is normal, however at the moment it does
> not display anything, shouldn't it display the key value?
> 

Yes, I've noticed that too (at least for screen and menu labels); we 
should really display the key if no value is found.

I've also noticed that in the migration from language properties to xml 
files some labels have been missed... I don't think that this is only 
affecting labels added recently.
For example, yesterday, I've noticed that the following labels (rather 
old ones, I guess) have been removed:

AccountingAssignPurchaseInvoiceToRevenue
AccountingAcctgTrans

Is it possible that the labels that just had one value in the English 
properties file, and no translations in the other languages, have been 
dropped in the migration?

Jacopo

Re: uilabels and screenlet widget

[Adrian Crum <ad...@yahoo.com>]

Hans Bakker <ma...@antwebsystems.com> wrote: Hi Adrian...

Thank you very much for the excellent work you are doing. I just
received a compliment from a customer who just upgraded from a year ago:
he especially mentioned that the user interface is now so much better
looking.

I can't take credit for that, Hans. I supplied some new styles, but it took a lot of work from other members of the community to make it happen. Jacopo and Jacques reviewed, tested and committed early patches. Andrew Zeneski refactored the Order component to use the new styles. Marco has done a tremendous amount of work updating the whole project to the new styles. Then there are others who update styles here and there as they work on things. So the whole developer community was involved in that.

I like to use your new features and have some comments:

the upgrade from the properties to xml files, now use a simple editor
and you can see if a text for a language is missing. However it looks
like when the key is not found the system does not display the
translation of the label which is normal, however at the moment it does
not display anything, shouldn't it display the key value?

If you could provide me with an example, that would really help. I haven't run into that problem myself, so I wasn't aware of it.

The screenlet widget: another excellent peace of work, i am now using it
in the projectmanager and surely save a lot of code and you are able now
to use command and paging in the screenlet header.
But here also a comment: the title of the screenlet, shouldn't that be
on the left and not on the right?
Then there is a menu name, but not a menu location?

I'll take another look at the code. I was planning on using the new widget in the Asset Maintenance component, so I'll probably run across the problem you mentioned.

Regarding the menu name - that attribute contains the name of the menu subwidget, so no location is needed - since the <include-menu> element will contain the menu location. In other words, the <screenlet> element has an <include-menu> subelement and you want that subelement displayed in the screenlet title bar. So whatever name is used in the <include-menu> subelement is the same name you would use in the <screenlet> navigation-menu-name attribute.

-Adrian


       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.