I am disappointed by the attitude expressed here. Testing whether two related
projects are compatible should be a basic part of the release process. It is
simple QA. That so many releases have gone through without such an essential
check raises questions about the competence of those involved
Hello.
The Compatibility Matrix is so severely out of date as to be useless. Could
someone familiar with the releases update this on the wiki:
http://wiki.apache.org/myfaces/CompatibilityMatrix
I have been trying to upgrade Tomahawk (from 1.1.3) and MyFaces core (from
1.1.4, the last
I dislike the use of the lowercase m in the particular font used in the logo,
because it makes the ambiguous F/f look lowercase as well. With the lowercase
m, I see the logo as myfaces not myFaces. With the capital M, I see it as
MyFaces. I would definitely rather read MyFaces than myfaces, but
Not that my opinion should count for much, but I like 7, 8, and 10. I think the
first shape (first five images) makes the one face express a somewhat horrified
expression; the second shape (last five images) with the smile is much
friendlier. I like the multiple colors as well, aside from the
Hello.
I noticed in the SVN repository that there are no tags for the 1.2.0 release of
the Core or the 1.1.6 release of Tomahawk. The branches are available, but no
tags. Since these are released, should there be tags?
Also, is there anyone willing and able to update the compatibility matrix
As someone who mostly just lurks on the dev list, I did want to comment on
Werner's post. I would be very interested in component programming, and I have
a fair number of ideas for what I think would make useful and interesting
components. (Wouldn't it be nice to have a Google Maps component,
I would pronounce Kleber as klee-ber with a long E sound like cleaver (a large
knife or an instrument for cutting things apart, which might be ironic given the
word's meaning in German). The word Kleber has no obvious meaning in English.
Even after reading the description on the Wiki page, I
Hi.
Looking at the release notes, I see:
Release Notes - MyFaces Core - Version 1.1.5
** Bug
* [long listing of bugs]
This phrasing is ambiguous. Are these bugs present in the Release, or bugs
fixed in the Release? This might be obvious to developers, but release notes
should be more
Hi.
I am not sure of the best implementation for this feature, but I want to note
that I think the feature itself would be valuable. My organization had to write
a custom export servlet to do just this for some of our data tables, so
providing this functionality within MyFaces may have been a
Hello.
I sent this to the list last week, but think it may have been lost as I was not
currently subscribed.
+ Richard
-Original Message-
From: Barbalace, Richard
Sent: Friday, June 30, 2006 1:21 PM
To: 'dev@myfaces.apache.org'
Cc: Barbalace, Richard
Subject: MyFacesHack.js bug
Hello.
Last November, I submitted some JavaScript changes for the JSCookMenu component,
which have been incorporated into MyFacesHack.js in the most recent release
(1.1.3). These lines (23 through 25 of that file), however, were changed
slightly from my original version:
// Link is a
PROTECTED]; Barbalace, Richard
Subject: Re: JavaScript in jsCookMenu component?
Can you send me a final verion for cmItemMouseUp? I will patch the
current version.
Thomas
On 11/2/05, Barbalace, Richard [EMAIL PROTECTED] wrote:
Simon Kitching [mailto:[EMAIL PROTECTED] writes:
I'd rather see
Simon Kitching [mailto:[EMAIL PROTECTED] writes:
I'd rather see detection of *any* protocol on the front of the URL
rather than checking just for http:. The protocols
https:, mail:
etc are also useful.
== proposal: ==
The URL *always* has menu_id: on the start, so presumably the
13 matches
Mail list logo
