On Sun, Jan 25, 2004 at 11:38:14PM +0100, Finn Bock wrote:
> [Simon Pepping]
>
> >I have just catched up with the massive changes to the property
> >system. Allow me to share a few observations:
>
> Thanks for your comments. How do you otherwise think it compares to t
--- Finn Bock <[EMAIL PROTECTED]> wrote:
>
> Yes, but I would like to take the question a bit
> further and ask where
> such information should be cached? Storing it in
> static variables caches
> it in the classloader which makes it difficult to
> control the release of
> the memory.
>
Hmmm.
[Simon Pepping]
I have just catched up with the massive changes to the property
system. Allow me to share a few observations:
Thanks for your comments. How do you otherwise think it compares to the
previous generated property makers?
1. If I see correctly, PropertySets is not yet used.
Correct
Hi,
I have just catched up with the massive changes to the property
system. Allow me to share a few observations:
1. If I see correctly, PropertySets is not yet used. PropertyList is
still a HashMap keyed on property name. Is this waiting for
some other changes to be made?
2. In FOProperty
Finn Bock wrote:
I would guess that doing ~6 string compares to navigate the binary
tree (with 148 color keywords) is slower than one string hash, ~1.2
int compares and one string compare. But I haven't measured it, so you
might be well be right. Many keyword sets for other properties are
much
Finn Bock wrote:
I would guess that doing ~6 string compares to navigate the binary tree
(with 148 color keywords) is slower than one string hash, ~1.2 int
compares and one string compare. But I haven't measured it, so you might
be well be right. Many keyword sets for other properties are much
> -Original Message-
> From: Finn Bock [mailto:[EMAIL PROTECTED]
> [ Glen : ]
> > Sigh...I guess I *didn't* know bytecode by heart after
> > all! ;-)
>
> I didn't bring it up to discourage the use of static initialized arrays.
> If it makes sense to put something in a static array we shou
You should perhaps also be aware that the values in a static array
gets assigned to the array one element at a time. So
[J.Pietschmann]
That's an unpleasant surprise. I was always under the impression
statically initialized data was stored along with the string
constants, like in C. This means a
[Finn Bock]
You should perhaps also be aware that the values
in a static array gets
assigned to the array one element at a time. So
static int[] a = {
101,102,103,104,105,106,107,108 };
becomes in bytecodes:
Method static {}
0 bipush 8
2 newarray int
4 dup
5 iconst_0
[Glen Mazza]
--- "Peter B. West" <[EMAIL PROTECTED]> wrote:
[Finn Bock]
> >
> > You should perhaps also be aware that the values
> in a static array gets
> > assigned to the array one element at a time. So
> >
> > static int[] a = {
> 101,102,103,104,105,106,107,108 };
> >
> > becomes in bytecodes:
> >
Finn Bock wrote:
I probably need an example of what you thinking are here. Right now in
HEAD all the color keywords are stored in a HashMap created in
GenericColor so the keywords initialization is already done. Putting the
keywords in static array would require us to somehow search the array
a
--- Finn Bock <[EMAIL PROTECTED]> wrote:
>
> But the biggest improvement is IMHO the easy ability
> to create special
> maker subclasses to handle the corner cases. Take a
> look at
> IndentPropertyMaker for the calculation of start and
> end-indent and at
> BorderWidthPropertyMaker for the spe
Finn Bock wrote:
You should perhaps also be aware that the values in a static array gets
assigned to the array one element at a time. So
That's an unpleasant surprise. I was always under the impression
statically initialized data was stored along with the string
constants, like in C. This means a
Glen Mazza wrote:
One thing that *does* stick out, however, is the 100
or so addKeyword() calls for genericColor
...
I'd like us to have a static array of these
values--i.e., something done compile-time, that
genericColor can just reference, so we don't have to
do this keyword initialization.
Loo
to create special
maker subclasses to handle the corner cases. Take a look at
IndentPropertyMaker for the calculation of start and end-indent and at
BorderWidthPropertyMaker for the special handling of border-width when
border-style is NONE.
Comments right now:
1.) Unlike what I was saying
Finn,
I've looked at your changes--I like them, and I'm
thankful to have someone on our team to be able to
redesign the properties as you have. Getting rid of
the 250 autogenerated or so classes will be a welcome
improvement.
Comments right now:
1.) Unlike what I was saying earlie
Team,
If you have anything to add, please comment on this
issue in Bugzilla. More viewpoints may be good here.
Thanks,
Glen
--- [EMAIL PROTECTED] wrote:
> DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
>
> RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE
>
J.Pietschmann wrote:
Peter B. West wrote:
I recall, however, that it took me a year to gain that status, a year
during which I wrote a considerable amount of code which I maintained
in my ISP account. My crime was that I did not toe the Party line. I
hope those days are gone, and that, shoul
Peter B. West wrote:
I recall, however, that it took me a year to gain that status, a year
during which I wrote a considerable amount of code which I maintained in
my ISP account. My crime was that I did not toe the Party line. I hope
those days are gone, and that, should a developer happen a
Keiron,
Here's how the RCS works.
$ rlog names
RCS file: names,v
Working file: names
head: 1.2
branch:
locks: strict
access list:
symbolic names:
Rel_1: 1.1.1.2
RC1: 1.2.1.3
Rel: 1.1.1
Dev: 1.2.1
Base: 1.1
keyword substitution: kv
total revisions: 7;
Arved,
Obviously, I share many of your attitudes to properties, but I differ in
one respect. I think of properties not as rich, but as impoverished.
To me, they are just associations of names with values. The richness
lies in their treatment in the process of layout, where all of those
con
Keiron,
As I suspected, $Name$ is the tag used to check out the file. In my
maint checkout, I have a sticky CVS/Tag specifying "fop-0_20_2-maintain"
(symbolic names cannot contain dot, because "a revision is composed
of one or more numeric or symbolic fields separated by periods" -
This page has the cvs keywords:
http://www.loria.fr/~molli/cvs/doc/cvs_12.html
None of them seem to be useable for the version of a product.
You still need to change something to make this update anyway.
On 2002.04.05 00:44 Peter B. West wrote:
> Keiron,
>
> I don't know the nuts and bolts of
Keiron,
I don't know the nuts and bolts of CVS, but I always assumed that tags
were somehow related to the RCS symbolic name, accessible via $Name$.
$Name$ has some peculiarities due to the fact that there is not a
unique name attached to the current version; I think it is set in the
output
age-
From: Peter B. West [mailto:[EMAIL PROTECTED]]
Sent: April 3, 2002 12:23 PM
To: fop-dev
Subject: Some comments on the build system
Fops,
I would like to see the build system overhauled. The overall objectives
of the overhaul would be to simplify the build process and decrease
barr
On 2002.04.03 18:23 Peter B. West wrote:
> There are a couple of other things which encourage the separation of
> source and build.source trees. They involve the use of copy filtering
> in ant. Version information is, I think, supplied by ant via the
> build.xml file. This vile and disgustin
From: "Peter B. West" <[EMAIL PROTECTED]>
> I would like to see the build system overhauled. The overall objectives
> of the overhaul would be to simplify the build process and decrease
> barriers to entry for would-be developers.
There is a project going on to create a simple and powerful buil
Fops,
I would like to see the build system overhauled. The overall objectives
of the overhaul would be to simplify the build process and decrease
barriers to entry for would-be developers. The tactical objectives
would be to eliminate XSL from the build, and to generate the classes
directly
Matthew L. Avizinis wrote:
>
>Well, now that I consider it more, I have to say that I guess I am just used
>to a "corporate" way of developing software that has a definite
>administrative structure and plan of action with people assigned specific
>tasks. Since I've never worked on an Open Source
> > So what is your point?
>>
>> - that we need a whole lot more people working on this. We already know,
> > either people will volunteer or they won't.
> > - that you don't know how to help. You said you can see problems. Tell us
> > you are going to fix those problems. Then do it.
>
>W
> -Original Message-
> From: Keiron Liddle [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 07, 2002 4:05 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Seeking Comments on Status of Project
>
>
>
> So what is your point?
>
> - that we need a whole lo
our or two a week for something deemed
> useful by someone in charge.
> Btw, who's in charge? It doesn't seem clear to me.
>
> And reluctantly, but while I'm at it, what the hey (certainly Keiron's
> always very patient comments didn't provoke the following),
> To make sure there is no confusion about this, could someone clarify
> (once more I guess) what exactly the "main" and "maintenance" branches
> are, and how to get the source code for both of them?
You get the main branch by getting the sources from CVS without a tag.
The maintenance branch i
On Thursday 07 February 2002 03:57, Arved Sandstrom wrote:
>. . .
> If you do some code and want to
> see it added to the main or maintenance branches, then the onus is on
> one or more committers to explain why it's a bad idea, but there must
> be a good reason.
>. . .
To make sure there is no
-Original Message-
From: Peter B. West [mailto:[EMAIL PROTECTED]]
Sent: February 6, 2002 8:32 PM
To: [EMAIL PROTECTED]
Subject: Re: Seeking Comments on Status of Project
> As to who's in charge: Arved is the man, but Arved has recently started
> a new job, so you can imagi
he
bloke if he knows how to stand the egg on its end. The guy and the King
and a few others attempt to balance the egg, unsuccessfully. Columbus
raps the blunter end on the table, crushing the air sac, and stands the
egg on the crushed base. "It's easy when someone shows you how.&
p is not
always (or has ever been?) up to date with the current release.
I might be able to squeeze in an hour or two a week for something deemed
useful by someone in charge.
Btw, who's in charge? It doesn't seem clear to me.
And reluctantly, but while I'm at it, what the hey (certainly
At 07:31 AM 2/6/02 +0100, you wrote:
>I think that most people need some encouragement to take the
> > plunge in murky waters
and since so many seem to feel generous this week, allow me to
toss my hat into the ring - we would be pleased to help out with the
awt renderer and the print renderer --
Peter,
I think that is a good idea. I would rather just focus on the redesign. If
we try to explain the maintanence branch we will probably spend more time
explaining what cannot be done than actually achieving anything.
I will give it a go and see how things work.
On 2002.02.05 23:25 Peter B
On Tuesday 05 February 2002 23:25, Peter B. West wrote:
>. . .
> I think that most people need some encouragement to take the
> plunge in murky waters.
I agree, make sense with the various offers for help that came up in
the last few weeks.
- Bertrand
-
Keiron,
Welcome back. Been on holidays?
Looking at the number of people who have expressed an interest in being
of some help, I thought it might be of some use for you or Karen, or
both, to run a "school". I appreciate that many of the thorny problems
with fop require the redesign, but if t
I think you are right Keiron,
I would like to contribute to this software, I would of course like to
begin with the code that is an issue for me but I am ready to hear where to
look and what to do either in the maintenance branch or in the redesign one.
(For the story, my fop issues are with m
i'm willing to help with the FOp project... but i don't know if i'm good
enough to help ...
anyway, just let me know on this e-mail adress: [EMAIL PROTECTED]
Jochen Maes
EDP departement
Programmeur
KBC-Securities
Havenlaan 16
1080 Brussel
Tel : 02/429.96.81
Fax : 02/429.17.48
E-mail : [EMAIL
elease, yy is a change to what
> is supported, and zz is for minor changes / patches.)
>
> I see some notes about the inclusion of jfor (RTF output) into the FOP
> project. I think that would be really cool, and speaks very well of the
> effort put in thus far. Anyone care to comm
>Pete Tribulski wrote:
>> > One of our primary tenets is "no beta software should be included in
>>> production applications".
>
>This is a problem statement for any open source software. Although a
>particular version may be called a "release" in Open Source circles
>this usually does mean th
Matt Savino wrote::
>Actually I am willing to volunteer a few hours a week towards anything
>the group needs done. I know it's not much, but if there's some admin or
>minor programming task that no one wants to do, etc.
I think that one of the best ways anyone can contribute with just a few
hour
Actually I am willing to volunteer a few hours a week towards anything
the group needs done. I know it's not much, but if there's some admin or
minor programming task that no one wants to do, etc.
Matt Savino wrote:
>
> Thanks Alex, point taken. I would love nothing more than to help with
> the
Thanks Alex, point taken. I would love nothing more than to help with
the redesign for the challenge and experience. I think FOP is a great
project that the world needs yesterday. Unfortunately my company already
has too much work for me and my clone, and there's no money in the
budget for a third
Pete Tribulski wrote:
> > One of our primary tenets is "no beta software should be included in
> > production applications".
This is a problem statement for any open source software. Although a
particular version may be called a "release" in Open Source circles this
usually does mean that it is
At 03:37 25/01/02, Matt Savino wrote:
> > Arved, thanks for the status update. Looking forward to .20.3, and would
> > love to get a rough, non-binding idea when the redesign might be
> > accomplished.
If you ask this sort of question on any Apache project where Jon S Stevens
is active you will
On Friday 25 January 2002 00:12, [EMAIL PROTECTED] wrote:
> . . .
> I am involved with the approval process for bringing new technology into
> our company. We have several development groups who have seen the FOP
> engine and would like to include it their applications.
> . . .
> One of our prim
(cc to [EMAIL PROTECTED] - fyi)
On Friday 25 January 2002 00:12, [EMAIL PROTECTED] wrote:
> . . .
> I see some notes about the inclusion of jfor (RTF output) into the FOP
> project. I think that would be really cool, and speaks very well of the
> effort put in thus far. Anyone care to comment on
sure he will have
> more to say.
>
> If extensive feature support (XSL-FO compliance) is the _primary_ concern, I
> think you'd not go wrong in looking at either RenderX XEP or Antenna House
> XSL Formatter. I can't comment on the price.
>
> Expect other comments.
to say.
If extensive feature support (XSL-FO compliance) is the _primary_ concern, I
think you'd not go wrong in looking at either RenderX XEP or Antenna House
XSL Formatter. I can't comment on the price.
Expect other comments. :-)
Regards,
Arved Sandstrom
-Original Message
put in thus far. Anyone care to comment on when that may make it
into a release?
On a somewhat related note, any updated comments on the following would be
appreciated.
I have seen several posts that recommend Renderx XEP if you "need
production level code". Is that still the case?
Sometim
55 matches
Mail list logo
