Hi All,
I'm about to start on a "best practices" webapp example effort for
Cocoon. I've added a number of enhancements to an existing PERL site
http://www.bringmethis.com. The site is a reverse auction site.
They've agreed to let me rewrite the site and use it as a live example
for a Cocoon web
> So I am all unofficial +1 for having a separate module for Cocoon
> contributions, where we can add the POI integration work, if enough
> people step up as a maintainer.
+1 if there are enough to justify it.
(personally I think more and better organized documentation for Cocoon is an
even be
I completely agree. I'm working (hopefully this weekend) on revising and
submitting patches for including the HSSF Serializer docs. This includes a
*how to* for setting up (by hand) the HSSF Serializer and *how to* use it in
a simple dynamic example. I noticed the SQL based example got dropped.
> That's really cool stuff, however I have some wonders about the source
> code that's been added to the Cocoon CVS :
This comes to me as a surprise; AFAIK it was unanimously voted upon like 2
months ago.
The package names were cross referenced with the location in the previous
CVS. The only thi
Appologies to those who get this twice.
>> Can you be a bit more specific? Is this something other than the
>alignment
>> bug?
>
>I'm not aware of POI bug list... Here are my observations:
>
you can access it here if you like:
http://nagoya.apache.org/bugzilla/buglist.cgi?product=POI
>http:
POI::HSSF 1.x does not support formulas as of yet. This development is in
the works. The serializer currently just ignores formula cells entirely for
the moment. If anyone is interested in helping with this (preferrably with
parser experience) check out the poi-dev list over on Jakarta.
I thin
>> From: Nicola Ken Barozzi [mailto:[EMAIL PROTECTED]]
>>
>> POI stuff committed with samples.
>>
>> :-)
>>
>> Please cross check.
> Wow. Looks cool! However, some examples behave *very* strange with
> Office XP...
>
> Vadim
Can you be a bit more specific? Is this something other than the al
>>
>> Excuse the mess that the old packages were in. I think its hard to get
>> it right the first two times.
>
>Hmmm, question: could POI become a component and have both Generators
>and Serializers use it?
>
Sorry, my question is more basic. Should serializers and generators use the
same e
>On Wed, 18 Jul 2001 12:59:43 -0700 Rick Tessner <[EMAIL PROTECTED]>
wrote.
>On Tue, 17 Jul 2001 13:19:13 PDT, acoliver wrote:
>
>>What should be the XML language. Currently my thoughts are this (for the
>>final transformed data before it is serialized):
>
>Hi t
>Hi Andy,
>Thanks a lot for all the detailed information.
>
>Actually, I tried transform the XML file(through XSLT) to some MS Excel
>spreadsheets(with the specific style that I desired), which can be open
>by Excel through the IE. The challege is I can not pass this Excel file
>through Coc
>Hi Andy,
>
> formulas and styles are nice features, which should at some point in
>time
>available, but for example we would be able to use it, if we can just
>export
>raw data to excel. We are currently using csv files, which is not that
>nice.
>
I plan to support raw data pretty early on.
Hi Jing,
Here's the basic status. I'm working with another developer Marc Johnson to
write the OLE Compound Document reader/writer. (Ole Compound document
format is Microsoft's wrapper around Word/Excel/etc docs, its nearly
completely undocumentedsee laola and libole2) we've finished the re
12 matches
Mail list logo
