Hello,
I'll have to add outputDocument selector to the XML doc file as well if
it's in the repository already.
Also, a teammate of mine uploaded the required label and content patch.
However, he's going on another project, so I'll take on that issue from
now on. It contains some new selectors as well that will need some
documentation, namely:
af|input*::label
af|input*::required::content
af|input*::required::label
af|select*::label
af|select*::required::content
af|select*::required::label
For now the selector uses '::' instead of ':' because he had to go to the
new project prety fast and did not have the time to alter FileSystemCache
to intercept :required as a non-CSS pseudo-element.
Regards,
Simon Lessard
Fujitsu Consulting
Jeanne Waldman <[EMAIL PROTECTED]>
2006-08-10 16:27
Please respond to adffaces-dev
To: [email protected]
cc:
Subject: Re: Writing release notes... where?
I was just thinking about what happened to the skin-selectors.xml doc
where we keep track of our skin selectors. I'll see if you've added this
Adam, if not, I can add it. I'll need to add my inputNumberSpinbox
skinning keys to this doc.
- Jeanne
Adam Winer wrote:
> OK; one point to make up front is that we should be generating
> our doc using "mvn site" *not* from trinidad-api, but from
> the top level of trinidad.
>
> I've just checked in a bunch of docs from the Oracle
> side of things to trinidad/src/site, including our devguide
> (for things like configuration, etc).
>
> -- Adam
>
>
>
> On 8/8/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrote:
>
>> the website is currently not really compliant; some things have been
>> fixed during my renaming/repackaging *inside* the maven poms. Before
>> it used the Apache brand in a wrong way ("Apache ADF Faces API") or
>> so.
>>
>> We should have a page which has *its* source inside the svn (in a
>> special "site" dir). Since we use maven we still have to address
>> the SVN publishing requirement that the Apache infrastructure team
>> has laid out.
>> For more see [1].
>>
>>
>> @release_notes or work todo for a release.
>> I was following the Tuscany C++ release request. They did a good job
>> [2] and
>> got the OK from the incubator PMC. The releasemanagement guide ([3])
>> has still
>> lot's of todos.
>>
>> I try to help out later this week; currently bussy.
>>
>> -Matthias
>>
>> [1] http://incubator.apache.org/guides/sites.html
>> [2]
http://www.mail-archive.com/[email protected]/msg05710.html
>> [3] http://incubator.apache.org/guides/releasemanagement.html
>>
>> On 8/8/06, Adam Winer < [EMAIL PROTECTED]> wrote:
>> > I'd like to help write some release notes (for the plugins,
>> > at least, for now), but it's not obvious where they should
>> > be written. Or, more generally, what we should be doing to
>> > make our website "incubator compliant". Any pointers?
>> >
>> > -- Adam
>> >
>> >
>>
>>
>> --
>> Matthias Wessendorf
>>
>> further stuff:
>> blog: http://jroller.com/page/mwessendorf
>> mail: mwessendorf-at-gmail-dot-com
>>
>
