JBossDeveloper

P.P.S. Maybe a lock or something instead of Edit and Cancel? I.e.: Locked lock by default, click, unlocked lock to edit, then click again to relock the changes.

Would that be possible to support a "closed" window state.
Example of application : on the same page, I have an "order list" portlet + an "Order details" portlet.
When I select an order portlet A, I want portlet A to close and portlet B to display order content.

Would that be possible to support a "closed" window state.
Example of application : on the same page, I have an "order list" portlet + an "Order details" portlet.
When I select an order portlet A, I want portlet A to close and portlet B to display order content.

Ok, here's two major annoyance which I HOPE will be fixed in the future:

1) Login page is never themed... Kinda hard to fit into an organization's common look and feel.

2) The Login/Admin/Pages menu items are HARD CODED in ENGLISH ONLY inside a JBoss class... Didn't I read something about I18N in the features list? I hope to gawd that the JBoss Portal 2.6 final will be truly local-aware and translated/translatable in it's entirety...


Here's some nice to haves:

1) Some kind of information on how the Locale is managed... I work in a multilingual organization and users who are logged in or not should be able to switch from one language to another via the click of a button (one that we can preferably style ourselves and put where we need it).

2) Why not eliminate the login page entirely and replace it with a default portlet that performs the login function (like the one that tells you if you are logged in or not)?


I love the portal so far... We've got our own theme and it's almost usable in our organization... I hope the final release will have addressed the issues mentioned above and some of the usability stuff mentioned by the others on this thread...

Good work!