Hi,
After we discussed the requirements during the last two weeks with no
major changes, I wrote a design document for the PDF generation. Please
ensure to find your usecases covered in the attached design document
[1].
Comments on the current design and aspects of the implementation are now
Hi Kore,
is it right, that for this approach, you'll need a parser for the
simplified CSS? If yes, could this parser be an independent component,
that could later be enhanced to parse regular CSS?
We already have the case of ezcMail, which contains MIME parsing and
generation that could be used
Kore Nordmann wrote:
Hi,
After we discussed the requirements during the last two weeks with no
major changes, I wrote a design document for the PDF generation. Please
ensure to find your usecases covered in the attached design document
[1].
Comments on the current design and aspects of
On Tue, 2009-02-24 at 11:40 +0100, Thomas Koch wrote:
Hi Kore,
is it right, that for this approach, you'll need a parser for the
simplified CSS? If yes, could this parser be an independent component,
that could later be enhanced to parse regular CSS?
Not really, because
a) Real CSS is
On Tue, 2009-02-24 at 11:49 +0100, Alexandru Stanoi wrote:
Kore Nordmann wrote:
Hi,
After we discussed the requirements during the last two weeks with no
major changes, I wrote a design document for the PDF generation. Please
ensure to find your usecases covered in the attached design
On Tue, 24 Feb 2009, Kore Nordmann wrote:
After we discussed the requirements during the last two weeks with no
major changes, I wrote a design document for the PDF generation. Please
ensure to find your usecases covered in the attached design document
[1].
Comments on the current design
On Tue, 2009-02-24 at 10:58 +, Derick Rethans wrote:
On Tue, 24 Feb 2009, Kore Nordmann wrote:
After we discussed the requirements during the last two weeks with no
major changes, I wrote a design document for the PDF generation. Please
ensure to find your usecases covered in the
hi, could you help mei to explain the structure of workflow database table
structure? I would like to make my workflow system and add some fields, but I
do not know how to do this! I want to operate in the flow process with some
forms of data transfering !
--
Components mailing list
