[CCC DEV] JNI - Native Calls to WinSparkle.dll

[Dave Gilmore]

On 9 July 2010 14:06, cljacobsen at gmail.com <cljacobsen at gmail.com> wrote:
> But I'd think that you might be naming your package kroc.winsparkle
> but not putting it in the appropriate directory structure for that?
> Check the macupdater code to see how I've named the package and
> created the corresponding dir structure. Also the naming conventions
> for packages [1] states that they "should [start with] one of the
> top-level domain names, currently com, edu, gov, mil, net, org, or one
> of the English two-letter codes identifying countries". Check the
> package structure of the macupdater to see if you can copy that and
> make things work.

OK I didn't know that or hadn't looked or was blissfully unaware -
Thanks for the heads up!

>

> Don't know what this could be off the top of my head. Though we need a
> standalone ant script for compilation (again see the macupdater, in
> particular build.xml). There will of course be some differences in the
> command line for building the native windows bits (in the
> native-compile target in build.xml), but if you commit what you've got
> I can look at that.

I'll look at the MacUpdater stuff again and follow the same conventions


> I'd need to check things here, not done enough JNI stuff to give you
> an answer to that. Of course you could just do like the macupdater and
> implement as little in Java as possible, to avoid parameter passing :)

That sounds great to me :-)

> The macupdater is able to pull out all the relevant information from
> the .app bundle so that pretty much no settings have to be set
> manually, I don't think this will be the case in Windows though.
> On windows I usually use notepad2 [2] and the command prompt :) At
> least for the macupdater. I do use eclipse for the occplug development
> but, eclipse/netbeans might be a bit overkill for the updater code!

I'll just use Notepad++ then :-)

I'll keep you updated on my progress

Thanks for that,

Dave