Hi, I wanted to give you a short notice, that I dumped the
first two components into the sourceforge project.
Self coloring input components, one with and the other without client
side non blocking validation.
Perfect for the average input form.
I created a basic structure for future things to come.
You can find the component pack in the jar file located in the bin
dir and an example under src/web
dump both files into a myfaces project and you are set.
The sources can be found under the net.sf hierarchy of the source folder.
I have no build files yet due to time constraints, and I dont have put a
fully working webapp on the sourceforge site, because I dont wanna run
into any licensing issues.
But besides that have much fun with toying around with it,
more things (and more complicated controls) will follow the following
days and weeks.
(feel free to alter the structure of things and the dir structure)
Bear in mind, that I am rather new to myfaces and have a limited
knowledge of the internals of myfaces currently, so there are definitely
things which can be done by a few simple hooks into myfaces, which I
probably did to complicated, so constructive criticism is welcome.
The sources will be moved into the myfaces sandbox as soon as it is open.
Werner
Jesse Alexander (KBSA 21) wrote:
-----Original Message-----
We really appreciate your effort, Jesse ;-)
-----/Original Message-----
Thanks... After all I should profit as well, getting maybe one or two
components that I can reuse in our applications ;-)
And feel free to help out:
- ask for components
- ideas
- requirements
- test components as they become available
- write your own components and make them available
-----Original Message-----
Any guidelines regardring the package names for the components, how
the components can be sent in etc...?
-----/Original Message-----
None so far.
What are our options?
1) Package-structure
a) org.apache.myfaces...
b) net.sf.jsfcomp....
c) whatever.you.want.... (almost whatever...)
- I believe a) is out of discussion, because of org.apache rules
- b) and c) remain valid options
2) a) all component-parts in one package-branch
b) all similar artifacts for all components in the same package-branch
c) all components of one committer in one package-branch
a) net.sf.jsfcomp.--mycomp--.component...
.tag...
.renderer...
b) net.sf.jsfcomp.component....
.tag...
.renderer...
c) net.sf.jsfcomp.--myname--.--mycomp--....
Here I have no preference at all. So describe your ideas.
-----Original Message-----
I would be interested as well, to be able to commit, to start dumping
code by tomorrow (gotta pack it up for the jar distribution first, which
in case of JSF is new to me, I have to find out what has to go in there,
and make a small webapp
which uses them)
-----/Original Message-----
Well that distribution format:
- in "JSF in Action" there is a description in chapter 15.7 "Packaging
UI extensions" (page 660/661).
- Basically:
- the class- and property-files (as usual)
- in the META-INF directory
- put the tld file for your tags
- write the "partial" faces-config into a well-formed faces-config.xml
That's it. Your "customer" just has to drop the jar-file into WEB-INF/lib,
restart his web-container and your components are available.
-----Original Message-----
forgot to mention, my sourceforge name is werpu12
-----/Original Message-----
done. Welcome on board.
regards
Alexander
