Issues with latest merge from CreepGin/D3BIt master about d3bit HOT 5 CLOSED

Right, I added a reference to Newtonsoft.Json.dll for the json used for parsing localized affixes. You can read a little about it in the last section in the user guide, http://d3up.com/guide/94/d3bit-user-guide

I think there's a mac equivalent of that (https://github.com/ayoung/Newtonsoft.Json).

And sure Unit test is a good idea. So I'll wait for your pull request?

from d3bit.

@CreepGin I'm having issues with merging the branches and building D3Bit, both Newtonsoft.Json and NHunspell give me a "Assembly not available for Mono / .Net 4.0 (in Mono)".

https://github.com/ttdonovan/D3Bit/tree/d3bit-test-nunit (prior to merge able to build D3Bit and all passing tests on Mac)

https://github.com/ttdonovan/D3Bit/tree/d3bit-test-nunit-merge (not able to build D3Bit)

Also I think https://github.com/ayoung/Newtonsoft.Json is for MonoTouch not MonoMac.

I could be wrong about all this. I'll keep Googling but any suggestions or guidance would greatly be appreciated.

Maybe for now is it possible to conditional have code compile depending on the platform?

from d3bit.

Right now I feel it may be wise to keep the Windows and Mac separate as different branches, or even better repositories.

The project may get a little convoluted in terms of structure and/or code if we keep the 2 ports together under one repos. Personally, I just don't want any of my choices to bog you down on your progress.

The 2 missing assemblies are just providing some convenience on the windows side. For Mac, there are standard cocoa classes for handling json. For spell correction, I have zero idea. Right now, the spell correction is not really necessary. So you can even just take it out.

from d3bit.

It would be nice if all the core functionality could be keep in one repo. Most of image processing working with the exception of fixing a the Path's and symbolic link for tesseract. If you think having two repos would be better I'ld be down for that. Create a Mac repo and I'll rip out the code that doesn't work for me.

from d3bit.

Yea originally, I wanted to keep the core multi-platform too. That's why I separated the core from the GUI from the start.

However after some consideration I think it'll be best to have different repos for the core as well. First, I think it'll make your job easier (if you just need to focus on the mac side of things). Second, it'll open up possibilities for more Mac-specific functionalities.

And I think you can just go ahead and create a repos for the mac port. You worked on it a lot and deserve the credit and ownership. =)

Once I'm done with testing the localization stuff, I'll be more committed on the mac port.

from d3bit.