I just remembered my point. If you do package it as I described below ... you only need to distribute the following: 1. Stub EXE 2. J.EXE 3. J.DLL 4. IJS file (your script)
You can then proceed to what Oleg is suggesting which is providing a link to J. :) I'm normally addled. ;) -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Alex Rufon Sent: Tuesday, June 02, 2009 5:06 PM To: Chat forum Subject: Re: [Jchat] J for the iPhone I also agree in packaging the scripts into a stand-alone package. One of the main concept our my use with J is writing a wrapper class to hide its nitty-gritty (like initialization, loading scripts, finalization). By using a wrapper class, you can create a stub application that would load your J scripts and run them. You can then treat this stub as your "framework" for each package that you distribute. ;) I hope I was able to explain that clearly. :-SS -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Oleg Kobchenko Sent: Tuesday, June 02, 2009 3:37 PM To: Chat forum Subject: Re: [Jchat] J for the iPhone It will be more successful if you package the scripts into stand-alone applications ready to use, without exposing the underlying J platform. It could be packaged so that the platform is reused if coming with multiple apps. A reference inside About would guide curious developers to how it was built and possibly generate some additional interest. Frink is not gonna make it to iPhone, as it does not have Java and the policy does not allow apps with programming ability. The closest to J is graphing tools with computer algebra, eg http://www.spacetime.us/iphone/ at $20, one of priciest apps or spreadsheets http://www.macworld.com/article/138784/2009/02/iphonespreadsheet.html I am not sure if the policy allows linking to a shared library provided in closed source. That would be necessary to write apps in J without exposing the J programming itself. > From: Ian Clark <[email protected]> > > There's a version of J602 you can download free for Windows Mobile > devices. I have it installed on my HP iPAQ. I've been able to verify > (at least in principle) that I can develop under Win2000 and move the > scripts to the iPAQ to run them. Of course it's best to start by > modifying the (fairly elaborate) freebie scripts that come with the > Windows Mobile version. These serve as sample code for the iPAQ GUI > for most if not all of what I think I'm going to need. It's not as if > the iPAQ GUI is that complicated... :-) > > I plan to try selling the scripts on Handango. It'll be a bit like > selling batter mix (just add eggs, flour and milk). > > Ian > > > On Tue, Jun 2, 2009 at 7:47 AM, Alan K. Stebbens > wrote: > > On Jun 1, 2009, at 11:27 PM, Alex Rufon wrote: > > > >> J for the iPhone! > >> > >> Hahaha. Just had to get that off my chest. > > > > Are you laughing because the idea is ludicrous, or are you laughing > > from the pleasure of the idea? > > > > If the former, please explore the Frink pages at: > > > > http://futureboy.us/frinkdocs/faq.html#SmallDevices > > > > More information is at http://handhelds.freshmeat.net/projects/frinklang > > > > If Frink can be run on small devices, being a Java app, surely J can > > be run on small devices also (not 64-bit J, of course). > > > > I'd much rather be able to noodle around with J code on my handheld, > > than play solitare or sudoku. > > > > -- > > Alan ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
