cornercorner
FeaturesPluginsDocs & SupportCommunityPartners

WoodstockInjMaki

Woodstock Widget Integration in jMaki

The following table outlines the status for wrapping the Woodstock widgets in jMaki

Widget Owner Status Milestone
accordion Dmitry Updated FF
alarm Bill Updated M1
alert Bill Updated M1
anchor Bill Updated M1
bubble Dmitry Updated M1
button Dan Updated M1
calendar Dmitry Updated FF
calendarField Dmitry Updated FF
checkbox Bill Updated M1
checkboxGroup Bill Updated M1
dropDown Bill Updated M1
editableField Dmitry Updated M1
hiddenField Bill Updated FF
hyperlink Bill Updated M1
image Bill Updated M1
imageHyperlink Bill Updated M1
label Bill Updated M1
listbox Bill Updated M1
login Bill Updated FF
modalWindow Dmitry Updated M1
passwordField Dmitry Updated M1
panner Bill Updated FF
popupMenu Dmitry Updated M1
progressBar Bill Updated M1
radioButton Bill Updated M1
radioButtonGroup Bill Updated M1
rating Dmitry Updated M1
text Dan Updated M1
table Dmitry Add events FF
tabset Bill Updated FF
textArea Bill Updated M1
textField Bill Updated M1
tree Bill Updated FF


The following table outlines the issues found during sanity testing of woodstock jMaki wrappers

No. Synopsis Priority Status
1. Accordion: Customozer does not turn up P2 New
2. ProgressBar: BottomText misplaced P3 New
3. CalendarField: Large spacing between components P3 New
4. All: Widget names should start with Capital letters in palette. P3 New
5. PopUpMenu: Customozer does not turn up P2 New
6. TextArea: Throws an error Unable to create an instance of
jmaki.widgets.woodstock.textArea.Widget. Enable logging
for more details.
P2 New
7. Different appearance on Mozilla and IE.The jMaki app run into
IE seems to be showing correct appearance and incorrect on mozilla,firefox
P3 New
8. ModalWindow: Customozer does not turn up P2 New
9. ModalWindow: Is not available at runtime P2 New
10. Login Component Is not available at runtime P2 New

Once the widgets are wrapped, the jmaki changes are checked into the Wooodstock CVS repository. The Woodstock builds then create two additional binaries: a standalone widget library and a set of jMaki wrappers. The jMaki wrappers are delivered into the jMaki source tree, which is then built and a binary distro is delivered into NetBeans.