I am not sure you have to go all the way to xcode. One alternative is something like RealBasic. I have developed in it for years, but not much of late. The apps from RB can be in the app store.
http://www.realsoftwareblog.com/2010/12/real-studio-and-mac-app-store.html When I chose RB for apps like the one we did for eventpix.com, java was on the table. The reason we chose RB was that there is one code base to manage, but it can compile into several platforms, now linux, mac, and windows. Also, it is NOT java like. The user interface uses standard windows and mac dialogs by calling to the operating system. In my experience, 90% of the code will be shared, with some deviations for special user interface elements. I have always felt that witango would be a good candidate for RB, and discussed it with Phil many moons ago. The only Java interface, that I have been able to "get used to" is the latest eclipse, and many dev languages are going that way. Zend/PHP, Adobe Flex, etc. They have done a decent job of making it more mac friendly, but it is still very foreign, and takes on that "one window" approach. -- Robert Garcia President - BigHead Technology VP Application Development - eventpix.com 15520 Coutelenc Rd Magalia, Ca 95954 ph: 530.645.4040 x222 fax: 530.645.4040 [email protected] - [email protected] http://bighead.net/ - http://eventpix.com/ On Jan 19, 2011, at 5:16 AM, Steve Smith wrote: > Changing the "open with..." does not resolve the problem. It does launch the > new Studio if it is not already running, but the file doesn't open. > > Also Command+Q doesn't work, neither does the menu selection for "Quit > WitangoDevelopmentStudio" (should there not be spaces between those words?). > Closing the window does quit the application which goes against standard Mac > user interface development. Quite often I want to close a window but leave > the application running to open a new file. Surprisingly Command+H does hide > the app which is correct behaviour. > > Apple no longer supporting Java in the future shouldn't be an issue, as it > should continue to be supported by other companies (i.e. Oracle). My > understanding is that Apple supporting Java on their own caused problems as > they were never in sync with Oracle's Java releases. > > I do agree with CNET's Erica Ogg who said "As for why Apple is going this > route, we know CEO Steve Jobs prefers native applications for his devices. > Java, like Flash, is inherently cross platform. To Jobs, that means they're > coded for the lowest common denominator interface, which for him, means > they're terrible. > > (Full Article) > > I have to agree. Java apps tend to be terrible look and feel apps. You're not > going get a lot of new users with an app written for the Mac market in Java, > regardless of how good the functionality of the app is, simply because most > users won't be able to get past the user interface. > > One important thing to remember about Java Apps is that they will not be > accepted by the new App Store. This is incredibly important. Anyone walking > into an Apple Store in recent months might have noticed that the software > section seems to have shrunk. Makes sense if they are going to promote the > App Store. I realize that Witango is not something you'd expect to see on a > shelf in a retail store (although I do have some old Tango 2000 boxes for > souvenirs). However I believe that a software developer would be foolish not > to have their apps listed on the App Store and have them up there as soon as > possible. > > Apple shipped 4.13 million Macs in the most recent quarter. Eventually all of > those machines are going to have the App Store icon sitting on their docks. > Combine that with all of the existing machines already running Snow Leopard > and you've got hundreds of millions of potential users who at some point will > browse the App Store's listings. Having your app up there, even if it is just > a 'lite' version, will be a very easy (and inexpensive) way to market your > application to the largest single source of potential customers you'll ever > find. > > I believe that over time, Mac users will stop searching for software anyplace > other than the App Store. > > While I was at EveryWare, I was one of the biggest criticizers of the Tango > for FileMaker product. By far, we took in more support calls for it than all > of the other products combined and yet it was our cheapest product. It was > explained to me that it was primarily a marketing tool (or loss leader) that > was being used to get the product in the hands of as many people as possible, > so that we'd get our foot in the door in as many places as possible. > > It worked. I don't recall the exact details but I believe that we got into > places like Disney, Sony, and many of the universities after they first tried > Tango for FileMaker. The majority of these led to sales of the other > products, usually the Mac Studio combined with the Unix Server which was the > highest ticket item. (BTW, the majority of users who were Unix Server users > were using the Mac Studio, not the Windows one). > > So my best advice would be to find a way in the not too distant future to > recode the application using xCode and get at least a 'lite' version of teh > Studio up on the App Store in front of the eyeballs of the Mac user base. > Even if it is just used to draw attention to the fact that Witango exists and > drives traffic to the web site where they can learn about the server and > everything else. > > I'm not a developer at that level but I thought I read somewhere that if you > use one of the traditional Mac tools (was it xCode, or Cocoa or ???) for your > development, it makes it very easy to port to Windows? > > Steve Smith > > Oakbridge Information Solutions > Oakville Office: (416) 628-0793 > Cambridge Office: (519) 489-0142 > Email: [email protected] > Web: www.oakbridge.ca > > Certified DayLite Master Partner > Certified DayLite Trainer > Billings Consultant > FileMaker Business Alliance Member > MoneyWorks Consultant > LightSpeed Authorized Reseller > > On 2011-01-19, at 1:29 AM, Christian Platt wrote: > >> Hi Wayne, >> >> you are completely right. >> >> To open with studo, take the .taf file and get information of that file. >> There is an area "open with...". There you should select Studio. >> Below is a "change all" button, which you should use, so all taf's are >> opened with Studio later on. (Can be named different, i translated that from >> german) >> >> That should work, if Studio accepts .taf files. >> >> Seems that that is a pure Java APP with all there Pronlems, so even Apple no >> more supporting Java in the future... >> >> Christian >> >> Am 19.01.2011 um 06:37 schrieb Wayne Irvine: >> >>> I realise this is still pre-release, and that it is a JAVA application >>> (correct me if I'm wrong) but some of the non-Mac-like things are a bit >>> annoying. I'm wondering how many of them will be changed in the release >>> version and how many are the nature of the beast of a JAVA application. >>> >>> If I create a new V6 TAF and save it to the desktop and then quit, at >>> present double clicking on the TAF won't start up the Dev Studio and open >>> the document. Something I am very used to from V5.5 and other applications >>> across all platforms. >>> >>> Also, when in the studio, opening a file uses an abnormal dialog box for >>> navigating the hard drive and volumes. There are no shortcuts on the left >>> and my favourite tool (DefaultFolder) is not active. >>> >>> I have to confess I am not a fan of the way the elements of the Dev Studio >>> all live within a rectangular space on the screen and don't share screen >>> space with other applications. I am used to having Witango, BBEdit, >>> Photoshop etc all open at once and sharing screen space. >>> >>> Are these just restrictions I am going to have to get used to or will some >>> of them change in the release version? >>> >>> Wayne Irvine >>> >>> ---------------------------------------- >>> >>> To unsubscribe from this list, please send an email to [email protected] >>> with "unsubscribe witango-talk" in the body. >>> >> >> >> >> ---------------------------------------- >> >> To unsubscribe from this list, please send an email to [email protected] >> with "unsubscribe witango-talk" in the body. >> > > > To unsubscribe from this list, please send an email to [email protected] > with "unsubscribe witango-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to [email protected] with "unsubscribe witango-talk" in the body.
