You don't avoid this even with Xamarin - they themselves suggest you will likely achieve only 75% common code. Whether this is typical, or a best case, I don't know. And of course any code you write against platform API's is not portable.
Despite what you appear to think, it is possible to create portable code using RemObjects as well. Any code that does not rely on platform services or UI etc can be written in a manner that makes it portable across all of those platforms. On 11 July 2014 16:49, Leigh Wanstead <[email protected]> wrote: > Hi Jolyon, > > Thanks for your input. > > But by using RemObjects, you cannot get benefits from writing code once > for all platforms i.e. android, ios, windows 8 phone like Xamarin.Forms do. > You have to write multiple sets of code for each platform which means > maintenance > nightmare and delay release etc. > > Regards > Leigh > > > On 11 July 2014 16:42, Jolyon Smith <[email protected]> wrote: > >> Leigh, >> >> When it comes to gleaning insights from examples, you get far more >> benefit from a translation than from a blank sheet of paper. ;) >> >> And making a translation from Java to Pascal (or C# if using Xamarin) is >> really not that hard, or shouldn't be for anyone who is - or claims to be - >> a software developer. Certainly not one with ambitions to develop for >> multiple, disparate devices. imho. >> >> ;) >> >> >> On 11 July 2014 16:32, Leigh Wanstead <[email protected]> wrote: >> >>> Hi Jolyon, >>> >>> But you need a mental translation from java to delphi :-) >>> >>> Regards >>> Leigh >>> >>> >>> On 11 July 2014 16:17, Jolyon Smith <[email protected]> wrote: >>> >>>> But Leigh, the point is that an Oxygene developer does not need *Oxygene >>>> specific* support. >>>> >>>> When I was developing my battery widget I was using the same resources >>>> that a Java Android developer would use, which are plentiful (ditto my >>>> excursions into Cocoa). >>>> >>>> >>>> As some sort of idea, you might look at # of tagged questions on >>>> StackOverflow as a (crude) metric: >>>> >>>> Android: 500,000+ >>>> iOS: 250,000+ >>>> Delphi: 27,000+ >>>> Xamarin: 3,400+ >>>> FireMonkey: 880+ >>>> Oxygene: 101+ >>>> >>>> Initially this does not look good for Oxygene. But a high proportion >>>> of those 750,000 Android and iOS questions will be just as helpful to an >>>> Oxygene developer (and Xamarin for that matter). Not so much for a >>>> FireMonkey developer. >>>> >>>> Of the three, a FireMonkey developer is the most on their own. >>>> >>>> >>>> As for availability of skills, RemObjects and Xamarin have similar >>>> advantages - both are (or in the case of Xamarin, can be) Visual Studio >>>> based so experience with the IDE isn't an issue. With Xamarin and >>>> Hydrogene, language skills aren't an issue now that you can call on the >>>> pool of C# skills. Framework skills ? Well, again we're talking about >>>> Android SDK and Cocoa (or .NET), not some proprietary cross platform >>>> framework (although there are elements of this with Xamarin I believe). >>>> >>>> Again, Delphi with FireMonkey romps home with the "Rocking Horse >>>> Droppings" award. ;) >>>> >>>> >>>> On 11 July 2014 15:51, Leigh Wanstead <[email protected]> wrote: >>>> >>>>> Hi Jolyon, >>>>> >>>>> Thanks for your reply. >>>>> >>>>> I think the issue with RemObjects Oxygene is >>>>> developer community size. Delphi is already a minority compare to .net >>>>> developer population. Then RemObjects Oxygene for android, ios? I >>>>> think that as rare as hen's teeth :-) >>>>> >>>>> If a project has no developer to hire using a tech, what will happen? >>>>> :-) >>>>> >>>>> Anyway, by doing RemObjects Oxygene, everything is same learning >>>>> curve like native platform except change the language to be pascal. But >>>>> you >>>>> have far small community to ask questions and get answers. Answers are not >>>>> ready for you on the internet, you have to wait someone to answer it >>>>> first. >>>>> I already feel that xamarin developer community is too small compare to >>>>> asp.net mvc, desktop .net etc. >>>>> >>>>> Regards >>>>> Leigh >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> NZ Borland Developers Group - Delphi mailing list >>>>> Post: [email protected] >>>>> Admin: http://delphi.org.nz/mailman/listinfo/delphi >>>>> Unsubscribe: send an email to [email protected] >>>>> with Subject: unsubscribe >>>>> >>>> >>>> >>>> _______________________________________________ >>>> NZ Borland Developers Group - Delphi mailing list >>>> Post: [email protected] >>>> Admin: http://delphi.org.nz/mailman/listinfo/delphi >>>> Unsubscribe: send an email to [email protected] >>>> with Subject: unsubscribe >>>> >>> >>> >>> _______________________________________________ >>> NZ Borland Developers Group - Delphi mailing list >>> Post: [email protected] >>> Admin: http://delphi.org.nz/mailman/listinfo/delphi >>> Unsubscribe: send an email to [email protected] with >>> Subject: unsubscribe >>> >> >> >> _______________________________________________ >> NZ Borland Developers Group - Delphi mailing list >> Post: [email protected] >> Admin: http://delphi.org.nz/mailman/listinfo/delphi >> Unsubscribe: send an email to [email protected] with >> Subject: unsubscribe >> > > > _______________________________________________ > NZ Borland Developers Group - Delphi mailing list > Post: [email protected] > Admin: http://delphi.org.nz/mailman/listinfo/delphi > Unsubscribe: send an email to [email protected] with > Subject: unsubscribe >
_______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: [email protected] Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [email protected] with Subject: unsubscribe
