[JBoss JIRA] Created: (JBIDE-1682) <rich:calendar> missing features in VPE.
by Andrei Scherbovich (JIRA)
<rich:calendar> missing features in VPE.
----------------------------------------
Key: JBIDE-1682
URL: http://jira.jboss.com/jira/browse/JBIDE-1682
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor
Affects Versions: 2.0.0.GA
Reporter: Andrei Scherbovich
<rich:calendar> missing features in VPE.
1) attribute: popup="true" doesn't work properly. Popup should be dynamic.
2) attributes: "buttonLable", "buttonIcon", "direction", "cellHeght", "cellWidth", "datePattern", "disabled", "horisontalOffset", "verticalOffset", "locale", "showApplyButton", "showInput", showScrollerBar", "showWeeksDayBar", "showWeeksBar", "todayControlMode="hidden"" don't work
3) <f:facet> not supported. (see developer guide for more information about <f:facet> in calendar)
4) styles don't work
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Created: (JBIDE-1910) Scrolling in JBoss Tools Tag Library Editor is rather slow and not always works.
by Andrei Scherbovich (JIRA)
Scrolling in JBoss Tools Tag Library Editor is rather slow and not always works.
--------------------------------------------------------------------------------
Key: JBIDE-1910
URL: http://jira.jboss.com/jira/browse/JBIDE-1910
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 2.0.1
Reporter: Andrei Scherbovich
Assigned To: Alexey Kazakov
Priority: Minor
Scrolling in JBoss Tools Tag Library Editor is rather slow and not always works.
Steps:
1. EXECUTE: Open tld file in JBoss Tools Tag Library Editor (rich.tld)
2. ASSERT: We see "rich" section to the left and "Tag Description", "Tag Attributes" and "Tag variables" sectionы to the right
3. EXECUTE: Open "rich" section and try to use scrolling there
4. ASSERT: Scrolling works good
5. EXECUTE: Open "Tag Description", "Tag Attributes" and "Tag variables" sections and try to use scrolling there
6. ASSERT: Scrolling works but very slow
7. EXECUTE: Choose some tag in "Tag Attributes" section and try to use scrolling
8. FAILURE: Scrolling doesn't work
9. ASSERT: Point cursor in some field of "Tag Description" section and try to use scrolling
10. FAILURE: Scrolling doesn't work
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years
[JBoss JIRA] Created: (RHDS-277) Creating JBoss Seam project (or anyother project actually) in Maven2 compatible directory structure
by Mehmet Salgar (JIRA)
Creating JBoss Seam project (or anyother project actually) in Maven2 compatible directory structure
---------------------------------------------------------------------------------------------------
Key: RHDS-277
URL: http://jira.jboss.com/jira/browse/RHDS-277
Project: Red Hat Developer Studio
Issue Type: Feature Request
Reporter: Mehmet Salgar
Hi,
my request is Red Hat Studio and Maven 2 related.
I think Red Hat Studio should create (or at least give the possibility) for the Jboss Seam projects in a structure that is compatible with a Maven 2 structure.
It is undeniable fact that java programmers are moving toward Maven 2 to manage their depenencies (even JBoss http://in.relation.to/Bloggers/Pete, http://www.michaelyuan.com/blog/2007/10/09/jboss-seam-project-setup-with-..., http://www.jroller.com/wesleyhales/, http://jbossportal.blogspot.com/), in this time it is interesting that an IDE that is developed with Red Hat and JBoss is not supporting directory structure of Maven 2.
With Beta2, I can create a JBoss Seam project and create necessary pom.xml for the web module to be compatible with Maven 2 but with ejb module it is not possible, because maven-ejb-plugin needs ejb-jar.xml (or anything in META-INF) to be in src/main/resources. It is not possible to configure this for any other directory in maven-ejb-plugin.
It is not possible to change the directory structure in RHDS also, it is default ejbModule/META-INF, there must be at least a way to set this to src/main/resources during the project creation.
Same is valid for the web project creation, there I can choose the directory but on a flat level, so it can be src, main but not src/main/java or src/main/webapp.
As I said little bit more compatablity with Maven 2 or little bit more configurablitiy from RHDS would be nice, it would be really stupid not be able to use Maven 2 while it is not RHDS project structure compatible and it would be also stupid not to be able to use RHDS features while it is Maven 2 project structure incompatible......
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years