|
|
Post by Dave on Aug 17, 2011 19:00:02 GMT
From my preliminary search on the topic of converting c++ code to java, it does not look promising. It would take a massive amount of reprogramming to convert the current code of Seventh Sense into Java language. There would be a lot of difficulties, not the least of which would come from working around Java's limitations in comparison to c++, such as lack of operator overloading, which is used quite a bit in Seventh Sense code.
I think it would be most efficient to start a new Java-based program for Android.
|
|
|
|
Post by alderaine on Aug 18, 2011 9:05:45 GMT
When I tried before, the hardest part was converting the mechanics of each book into some kind of navigation file - is there anything extractable for the format you use to allow your engine to understand the books?
|
|
|
|
Post by Dave on Aug 18, 2011 22:27:04 GMT
Certainly there is. In fact, I've been bending my mind lately to the CNF (Common Navigation File) that kind of petered out some tim ago.
If I were given a method for how the various things should appear in the XML (like tags /headers/ whatever else makes for a valid or useful XML file) I could create a script in my program that exports everything for each section of my books done so far.
Knowing that some sections are crazy and complex, and some are simple and straightforward, with others lying somewhere in-between, I think it may be helpful for new book-reader makers to have a reference as to which sections they need to deal with specifically on a program level, and which are the basic "if you have xxxx, turn to xxx" type sections. I could incorporate this sort of labeling, as well.
Realistically, only 80-90% of any book would be simple enough able to be processed automatically on the "reader" end of things - but even so, if the sections are marked in the XML with some kind of nomenclature like : "READER_TASK: SIMPLE", "READER_TASK: COMPLEX", "READER_TASK: CUSTOM", any programmer could just have their program deal automatically with "simple" sections, and focus their energies on the "complex/custom" stuff.
Like I said, I think that would generally entail only about 10-20% most books, with the later books obviously being more complex than earlier ones.
I was thinking of doing this after I finished book 12, so we'd have the whole of the Kai and Magnakai in one fell swoop. (350 * 12 = 4000+ sections of text, and probably ~3400 of that falling into the "simple/automatic" category.)
I'd be willing to do it sooner, but in either case, it has to wait until dissertation is finished. Good news on that - I'm making serious progress. Speaking of which - back to the grind!
|
|
|
|
Post by alderaine on Aug 24, 2011 8:26:13 GMT
Hi
That would be great - I'm very happy to help with ideas on how to slot things into XML (we can be pretty creative - I think the idea would be to have one XML file for items, and either another for navigation or update the existing ones)
Let me know when you'd like to pick this up again - no rush!
Many thanks
James
|
|
