search

mjs513 / monoxna

Automatically exported from code.google.com/p/monoxna
Other
0 stars 0 forks source link

Content Pipeline implementation Status #26

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Microsoft.Xna.Framework.Content.Pipeline need to be implemented.

Original issue reported on code.google.com by lav...@gmail.com on 25 Apr 2009 at 12:35

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[ContentPipeline]

Original comment by lav...@gmail.com on 25 Apr 2009 at 12:45

GoogleCodeExporter commented 9 years ago 
The stubs have been created
Have started work on the MonoDevelop addin

Original comment by lav...@gmail.com on 13 May 2009 at 9:11

GoogleCodeExporter commented 9 years ago 
OpaqueDataDictionary and NamedValueDictionary classes implemented

Original comment by raxxla...@gmail.com on 1 Dec 2009 at 4:01

Attachments:

GoogleCodeExporter commented 9 years ago 
First off, thanks for you contribution. In order for the code to be accepted you
should write some simple NUnit tests for them as well. When you have done this 
create
a new issue and supply the patch.

Sorry to make you do additional work, but we need to write the tests for new 
code, or
else it will never be done.

If you need help on how to write the tests just logon to out IRC channel and I 
will
try to assist.

Original comment by lav...@gmail.com on 1 Dec 2009 at 7:17

GoogleCodeExporter commented 9 years ago 
it is ok. i just never writing unit tests for the code like "hello world". I 
will
provide unit tests with next contribute.

Original comment by raxxla...@gmail.com on 1 Dec 2009 at 7:32

GoogleCodeExporter commented 9 years ago 
i haven't either until now ;) the tests in MonoXNA seem to have been written to
ensure proper results despite code changes...

Original comment by lav...@gmail.com on 1 Dec 2009 at 7:49

GoogleCodeExporter commented 9 years ago 
These are the current patches needed in MonoDevelop to allow for our MonoXNA 
addin.
The patches should be applied in the respective assemblies.

Original comment by lav...@gmail.com on 24 Jan 2010 at 5:00

Attachments:

GoogleCodeExporter commented 9 years ago 
The patches where not accepted (at least not without some modifications). The 
changes
in the patches are part of the core project model, and they are reluctant to 
change
it if they don't have to. In addition the fix I made for alternative filename
extensions had an issue that I hadn't considered as important that it in fact 
is.

Lluis made a less intrusive change in the project model instead that might 
solve the
problem. I'm currently testing it, but some issues have already been found.

Original comment by lav...@gmail.com on 1 Feb 2010 at 11:55

GoogleCodeExporter commented 9 years ago 
I misunderstood the reply by lluis. He only objected to the changes made to 
allow for
invisible solution items, the changes made to allow alternate extensions where 
ok,
except for one issue which I must solve before the patch is accepted.

I'll post the new patch when I'm finished

Original comment by lav...@gmail.com on 2 Feb 2010 at 4:10