build under mono 2.4

Aug 21, 2009 at 9:48 AM

This project have no test suit, so until now I can say, I can build this project with little fix under mono 2.4.2~~

mono 2.4 find 3 bug(arg type missing), (and a mono utf-16le can't read).

with these fix, npoi run fine under mono 2.4~~

Coordinator
Aug 21, 2009 at 10:24 AM

great! Are you willing to help checkin your changes to our branch? If so, please do it. I'll add you to the development team. Thank you very much for your efforts.

Aug 21, 2009 at 12:58 PM
当然可以,但是我的那些修改都没有经过严格的测试,只能算是一种HACKS行为。仅仅让我需要的几个测试程序跑起来了而已~

1、MONO 2.4还不稳定,我是在UBUNTU下编译的,所以不能算是官方环境,只能等到在SUSE的最新版MONO上编译调试成功才作数,或者等UBUNTU 9.10发行,官方包含MONO 2.4之后,再编译到MONO上去,才对劲儿。这个大约要到年底了,所以还是等等的好。

2、里面的UTF-16LE的问题我只是将代码换成UTF-16,所以还是不提交的好。

3、两个编译的BUGS,那个的确算是BUG,我认真读了代码,觉得VS2008不报错反而是相当不可思议。我稍后会提交~~

我看了NPOI的源代码,在项目中也准备使用它来生成EXCEL文件。

但是,NPOI的代码不够健壮,没有单元测试,让人编译起来心惊胆颤的。POI 3.5 BETA 6的代码我下载下来后,发觉有完整的测试代码,看起来很放心~

我有闲暇时间,也愿意加入开发,但是可惜的是,NPOI的PORT流程不清楚,让人无法下手。搞不清楚你是怎么PORT过来的,因为看起来 3.5 BETA的代码量比3.2要大得多了,觉得这种项目一个人手工翻译的话工作量太大了。

最后还是感激你的工作,起码让我在项目中生成真正的EXCEL 2003文件,可以不依赖ADO.NET或者是COM。



On Fri, Aug 21, 2009 at 5:24 PM, tonyqus <notifications@codeplex.com> wrote:

From: tonyqus

great! Are you willing to help checkin your changes to our branch? If so, please do it. I'll add you to the development team. Thank you very much for your efforts.

Read the full discussion online.

To add a post to this discussion, reply to this email (npoi@discussions.codeplex.com)

To start a new discussion for this project, email npoi@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Coordinator
Aug 21, 2009 at 3:08 PM
是这样的,其实poi中的test case NPOI中都有,而且95%都是pass的,只不过我发布的时候没有放在release中,因为觉得对使用的人用处不大,你可以看source code包里面,有大概1000多个test case,所以NPOI的质量总体上是有保证的。
至于NPOI怎么从poi转过来的,说实话我也考虑过用自动工具转,谁不想偷懒,但我看过几个自动转换工具,基本没有让人满意的。事实上,在转换过程中,我发觉很多就连人工做都很难弄的问题,所以自动转换本身就是一种理想状态。
貌似codeplex的添加成员功能出了点问题,老报错,我下周看能不能把你加进来。
2009/8/21 lemonhall <notifications@codeplex.com>

From: lemonhall

当然可以,但是我的那些修改都没有经过严格的测试,只能算是一种HACKS行为。仅仅让我需要的几个测试程序跑起来了而已~

1、MONO 2.4还不稳定,我是在UBUNTU下编译的,所以不能算是官方环境,只能等到在SUSE的最新版MONO上编译调试成功才作数,或者等UBUNTU 9.10发行,官方包含MONO 2.4之后,再编译到MONO上去,才对劲儿。这个大约要到年底了,所以还是等等的好。

2、里面的UTF-16LE的问题我只是将代码换成UTF-16,所以还是不提交的好。

3、两个编译的BUGS,那个的确算是BUG,我认真读了代码,觉得VS2008不报错反而是相当不可思议。我稍后会提交~~

我看了NPOI的源代码,在项目中也准备使用它来生成EXCEL文件。

但是,NPOI的代码不够健壮,没有单元测试,让人编译起来心惊胆颤的。POI 3.5 BETA 6的代码我下载下来后,发觉有完整的测试代码,看起来很放心~

我有闲暇时间,也愿意加入开发,但是可惜的是,NPOI的PORT流程不清楚,让人无法下手。搞不清楚你是怎么PORT过来的,因为看起来 3.5 BETA的代码量比3.2要大得多了,觉得这种项目一个人手工翻译的话工作量太大了。

最后还是感激你的工作,起码让我在项目中生成真正的EXCEL 2003文件,可以不依赖ADO.NET或者是COM。



On Fri, Aug 21, 2009 at 5:24 PM, tonyqus <notifications@codeplex.com> wrote:

From: tonyqus

great! Are you willing to help checkin your changes to our branch? If so, please do it. I'll add you to the development team. Thank you very much for your efforts.

Read the full discussion online.

To add a post to this discussion, reply to this email (npoi@discussions.codeplex.com)

To start a new discussion for this project, email npoi@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Read the full discussion online.

To add a post to this discussion, reply to this email (npoi@discussions.codeplex.com)

To start a new discussion for this project, email npoi@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Aug 23, 2009 at 3:10 AM
好的,没有问题,呵呵。我猜你也是手工转的,工作量是超大的说~~

在CODEPLEX上面没有使用SVN CHEKOUT的习惯,所以就没看到TEST SUIT~

没TEST SUIT让我在MONO下跑这东西,心里总是有些犯虚。

2009/8/21 tonyqus <notifications@codeplex.com>

From: tonyqus

是这样的,其实poi中的test case NPOI中都有,而且95%都是pass的,只不过我发布的时候没有放在release中,因为觉得对使用的人用处不大,你可以看source code包里面,有大概1000多个test case,所以NPOI的质量总体上是有保证的。
至于NPOI怎么从poi转过来的,说实话我也考虑过用自动工具转,谁不想偷懒,但我看过几个自动转换工具,基本没有让人满意的。事实上,在转换过程中,我发觉很多就连人工做都很难弄的问题,所以自动转换本身就是一种理想状态。
貌似codeplex的添加成员功能出了点问题,老报错,我下周看能不能把你加进来。
2009/8/21 lemonhall <notifications@codeplex.com>

From: lemonhall

当然可以,但是我的那些修改都没有经过严格的测试,只能算是一种HACKS行为。仅仅让我需要的几个测试程序跑起来了而已~

1、MONO 2.4还不稳定,我是在UBUNTU下编译的,所以不能算是官方环境,只能等到在SUSE的最新版MONO上编译调试成功才作数,或者等UBUNTU 9.10发行,官方包含MONO 2.4之后,再编译到MONO上去,才对劲儿。这个大约要到年底了,所以还是等等的好。

2、里面的UTF-16LE的问题我只是将代码换成UTF-16,所以还是不提交的好。

3、两个编译的BUGS,那个的确算是BUG,我认真读了代码,觉得VS2008不报错反而是相当不可思议。我稍后会提交~~

我看了NPOI的源代码,在项目中也准备使用它来生成EXCEL文件。

但是,NPOI的代码不够健壮,没有单元测试,让人编译起来心惊胆颤的。POI 3.5 BETA 6的代码我下载下来后,发觉有完整的测试代码,看起来很放心~

我有闲暇时间,也愿意加入开发,但是可惜的是,NPOI的PORT流程不清楚,让人无法下手。搞不清楚你是怎么PORT过来的,因为看起来 3.5 BETA的代码量比3.2要大得多了,觉得这种项目一个人手工翻译的话工作量太大了。

最后还是感激你的工作,起码让我在项目中生成真正的EXCEL 2003文件,可以不依赖ADO.NET或者是COM。



On Fri, Aug 21, 2009 at 5:24 PM, tonyqus <notifications@codeplex.com> wrote:

From: tonyqus

great! Are you willing to help checkin your changes to our branch? If so, please do it. I'll add you to the development team. Thank you very much for your efforts.

Read the full discussion online.

To add a post to this discussion, reply to this email (npoi@discussions.codeplex.com)

To start a new discussion for this project, email npoi@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Read the full discussion online.

To add a post to this discussion, reply to this email (npoi@discussions.codeplex.com)

To start a new discussion for this project, email npoi@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Read the full discussion online.

To add a post to this discussion, reply to this email (npoi@discussions.codeplex.com)

To start a new discussion for this project, email npoi@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Apr 19, 2010 at 2:50 PM

Hello guys.

Im new in town, and dont really understand cantoneese (chinese?, sry).

Im interested on your solution how to make it work under mono?

Coordinator
Apr 19, 2010 at 11:27 PM

This solution is not ready yet. lemonhall only tested on his own box. No code checkin. You can try to compile under mono.

May 14, 2010 at 3:56 PM

I have been testing around and after modyfing the source code it now works.

But...

How will i do now, what does the lisence say? I modified it and it works with my program, but should i put in the solutions in the work here or?

Coordinator
May 15, 2010 at 3:03 AM

Fantastic work! As I know, the Apache license doesn't require you to check-in the modifed code. If you are willing to check-in your code, it will be very useful for guys who uses NPOI on Mono. God will bless you :-)

My only concern is that which version of NPOI you modified. There may be some issues while merging the code. Please contact me via tonyqus@gmail.com for detailed merge issue.