Re: RuleModeler Xcode project
Re: RuleModeler Xcode project
- Subject: Re: RuleModeler Xcode project
- From: David Avendasora <email@hidden>
- Date: Sun, 11 Mar 2012 12:21:43 +0800
Hi Amy, everyone,
I looked through the RuleModeler source a while ago with the thought of possibly modernizing it and releasing it on the App Store. Since a lot of the code is licensed under LGPL, unless you can isolate the LGPL code into a library and simply link to it, whatever you release on the App Store will need to also be available as source code. (I am not a lawyer and don't construe what I'm saying as actual legal advice, it's simply my interpretation of the license statement. Yadda, yadda, yadda.)
I think there is still a market for people to pay for a compiled binary as opposed to downloading and building the source themselves.
We need to find opportunities to _let_ people give money to WOCommunity beyond memberships and WOWODC attendance. Whether it's through donations, purchases or bug bounties.
Dave
On Mar 11, 2012, at 1:17 AM, Amy Worrall wrote:
> "Try setting Mac OSX Deployment target to 10.5 and use Base SDK 10.6.
> This should build the application that can run on both I believe."
>
> Yes, this should work.
>
> I was having a look through the code the other day — I'm working on a
> rules-based Core Data app generator, and decided to use Rule Modeler
> as the thing to write the rule files. (I've got the start of an
> NSPredicate based rule file parser now, but before I wrote that I was
> looking inside the Rule Modeler source to see if it was something I
> wanted to nab.)
>
> I could help out getting it App Store clean if you wanted. I don't
> think Sandboxing should be an issue since the only iffy bit would be
> the talking to wolips, and AFAIK that's done through sockets — I'm
> pretty sure you just need to whack the network client entitlement in
> and that'll work. Regarding saving files, as long as the app uses
> standard open/save dialog boxes then there shouldn't be an issue. But
> if there's interest I can take a look in more detail. Of course, if we
> get it in there before June we won't need to sandbox it.
>
> We would need a WOCommunity dev account I reckon. While I have a
> personal one as I'm sure many others do, we'd end up in bother when
> someone no longer had time to help out and then nobody else could use
> their account.
>
> Amy
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden