TOPIC:

Hi Guys from Radaee.

How about using a repository with branches or tags for releasing a new version? To me it seems to have the advantage that I'll be able to merge changes in the new version with my customizations of your code.


Regards,

Daniel

no better way,
in next time, you'd better add special comments for all your customizations.
new version support 64 bits platform, so most native interfaces are changed.

handle value of native objects are changed from 32 bits int to 64 bits int.

I'm already using comments - what do you mean with 'special comments'? - in the classes. But still it's a lot of overhead compared to use an update/synchronize in an svn or git. I have to

• extract the ZIP
• startup WinMerge
• pick the extract folder
• pick the folder in my workspace
• check each 'different' file manually
• adapt the changes an copy my modifications
• do the same again for the resources

Using eclipse build in svn/git does a lot of the trivial merge and even some of the non-trivial merge by itself reducing the overhead to just taking care of my modifications.

Doing all the steps above by hand is especially "pain in the ass" when there is an new beta-release or RC every day.

i think the stpes shall be:
1. merge com.radaee.pdf.Global class
2. replace other classes in com.radae.pdf
3. merge com.radaee.view classes.
4. replace assets and res subdr
5. merge other classes in com.radaee.util and com.radaee.reader
6. fix other compiler issues by manual, if any.

Doesn't matter which steps you'll use, mine or your's, the merging and replcaing steps would become much easier if using a version control system.

Or are you using no version control system during development of PDFViewer SDK?!