update library iText 2.0.1 to iText 2.1.7
-
Key: OFBIZ-3407
URL: https://issues.apache.org/jira/browse/OFBIZ-3407
Project: OFBiz
Issue Type: Improvement
Components: framework
Affects
Party component has dependancy with webPos
--
Key: OFBIZ-3408
URL: https://issues.apache.org/jira/browse/OFBIZ-3408
Project: OFBiz
Issue Type: Bug
Components: party
Affects Versions: SVN
Hi Jacques,
Sorry about the late reply, I am a little busy right now but I can
give it a try at the end of the next week.
Regards,
Rashko Rejmer
On 9 Jan 2010, at 01:51, Jacques Le Roux wrote:
Hi Rashko,
This is interesting, and one point more than what I proposed intialy
(when we
[
https://issues.apache.org/jira/browse/OFBIZ-3408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas malin updated OFBIZ-3408:
-
Attachment: OFBIZ-3408_CommonScreens.patch
Party component has dependancy with webPos
From: Rashko Rejmer rrej...@iguanait.com
Hi Jacques,
Sorry about the late reply, I am a little busy right now but I can
give it a try at the end of the next week.
No worries, you are welcome Rashko
Thanks
Jacques
Regards,
Rashko Rejmer
On 9 Jan 2010, at 01:51, Jacques Le Roux wrote:
I have a question about the GL account classes loaded with OFBiz seed data:
DEBIT
|___ NON_POSTING
|
|___ DISTRIBUTION
| |___ RETURN_OF_CAPITAL
| |
| |___ DIVIDEND
Jacopo,
According to our accountant you would want to do this (inline):
Jacopo Cappellato wrote:
I have a question about the GL account classes loaded with OFBiz seed data:
DEBIT
|___ NON_POSTING
|
|___ DISTRIBUTION
| |___
adri...@apache.org wrote:
Author: adrianc
Date: Tue Jan 12 14:24:36 2010
New Revision: 898338
URL: http://svn.apache.org/viewvc?rev=898338view=rev
Log:
First pass at converting UtilProperties.java to Java 6, plus some small code
cleanups.
Where exactly is the 1.6 syntax you are using?
Those public methods were created in anticipation of the Java 6 classes that
will replace them. I can put them back and deprecate them instead.
-Adrian
--- On Tue, 1/12/10, Adam Heath doo...@brainfood.com wrote:
From: Adam Heath doo...@brainfood.com
Subject: Re: svn commit: r898338 -
Adrian Crum wrote:
Those public methods were created in anticipation of the Java 6 classes that
will replace them. I can put them back and deprecate them instead.
If they were never in an official release of ofbiz, then go ahead and
remove them.
Adam Heath wrote:
Adrian Crum wrote:
Those public methods were created in anticipation of the Java 6 classes that
will replace them. I can put them back and deprecate them instead.
If they were never in an official release of ofbiz, then go ahead and
remove them.
Heh, based on your last
Done in rev 898648. Thanks for pointing that out - I didn't think anyone would
be using those methods.
Background info for anyone who might be interested:
At the 2007 Developers Conference, it was mentioned that clearing caches in
OFBiz didn't clear the UI labels. The only way to see changes
We had a discussion about accommodating multi-column layouts. Search the dev
list for Subject = Discussion: Column Widgets (was: How to add a splitter to
adjust the left column width by dragging it?
-Adrian
--- On Tue, 1/12/10, David E Jones d...@me.com wrote:
From: David E Jones d...@me.com
I am looking into an issue with formatting using a CSS-based multiple column
layout and with screenlets in each column.
The problem is that in the htmlScreenMacroLibrary.ftl file there is a
hard-coded clear on line 148:
br class=clear /
With most browsers these clears are no
The point isn't to accommodate multi-column layouts, we already have basic
stuff for that which works just fine. I'm not talking about anything like
dragging columns or configuring sizes or anything like that. It's an
interesting idea, but a different one.
The question I have is do we really
I disagree. The stuff we have doesn't work just fine. Try removing the clearing
element and see what happens. The multi-column layout you're working on looks
great, but now everything else is broken.
Our existing multi-column layout is extremely fragile and easily broken. That's
why I
I guess what you mean by this is as part of that larger effort you'll have to
introduce a new CSS pattern for multi-column layouts.
Do we really need a column widget in order to use a better CSS pattern for the
multi-column layout?
-David
On Jan 13, 2010, at 12:28 AM, Adrian Crum wrote:
I
No, we need the column container and column widgets so the renderers know when
to output clearing elements and when not to.
You're not going to solve the problem with CSS alone. The markup has to reflect
what you're trying to accomplish.
What you're describing is a tug-of-war that has been
Something to think about - and this is beyond the scope of your question - is
that someday we will need to change how screen widgets are rendered.
Right now model widgets are rendered directly to an output stream. It would be
preferable to have the model widgets rendered to an intermediate Java
19 matches
Mail list logo
