So port it, you C dude, you! :-P Code in C, Code in C, Code in C, Code in C Java's just for sissies Code in C
(to the tune of "Let it Be", for those who might not have got the reference; it's also a reference to an old parody titled "Code in C" that can be found via Google.) Dave 2008/12/15 Schaefer, Doug <[email protected]> > The only thing I've wished for so far for Dalvik is that it run on > architectures other than ARM. > > Doug. > > ------------------------------ > *From:* [email protected] [mailto:[email protected]] *On > Behalf Of *David Orme > *Sent:* Monday, December 15, 2008 12:45 PM > *To:* E4 Project developer mailing list > *Subject:* Re: [e4-dev] JDK level for e4 work? > > BTW, the only thing I've wished for so far in Android/Dalvik that isn't > there is java.beans. So I ported it from the Apache Harmony sources. > > > Regards, > > Dave Orme > > On Mon, Dec 15, 2008 at 11:42 AM, Gorkem Ercan <[email protected]> wrote: > >> I do not think there is/should be a single answer for the JDK level on >> e4. I do not really know how to formulate it but the closer the work >> to the RCP, it is more likely that we can use it in the embedded >> space. If we need to really come up with a rule of thumb. I guess we >> could formulate it with dependencies. Here is my quick dirty version >> "if feature is mainly built on top of org.eclipse.swt, >> org.eclipse.jface, org.eclipse.core.runtime, org.eclipse.ui, >> org.eclipse.update.core only then consider using CDC FP 1.1" >> -- >> Gorkem >> >> >> 2008/12/15 Ed Merks <[email protected]>: >> > Kevin, >> > >> > Not that it's entirely a relevant question, but will the embedded space >> ever >> > more forward again? At Eclipse we'd argue: if the community cared >> enough, >> > they'd produce a Foundation 1.2 for Java 5.0. It can't be that hard, >> but I >> > suppose Sun leaves the community in a straight jacket. This seems an >> ideal >> > approach for making Java go extinct in the embedded space. Basing an >> > important design decision around this terribly sad story, seems terribly >> > sad. And of course the target is likely to move by the time the arrow >> comes >> > close... >> > >> > You recall there was talk about cross compiling 5.0 code to 1.4? There >> is a >> > "secret flag" already, but I think that goes against the rules as well. >> I'm >> > not sure the purpose for such rules. It seems all very wrong... >> > >> > Regards, >> > Ed >> > >> > >> > Kevin McGuire wrote: >> > >> > Hi all, >> > >> > I'm a little confused about what JDK level we said we'd use for e4 work. >> > >> > In the former e4-incubator mail list [1] we said, "We'll discuss at the >> > summit". In the summit notes I see lots of discussion [2] but no >> > conclusion. I was not in that session, so perhaps there was a >> conclusion >> > that I missed/was missed in the notes? >> > >> > In doing the recent CSS work I set the dependency as JDK1.5 because >> that's >> > what I saw in the following projects: >> > org.eclipse.e4.ui.services >> > org.eclipse.e4.ui.workbench >> > >> > Many would like 1.5 for various reasons (myself included), but as in the >> > email below, those in the embedded space would naturally like something >> more >> > like Foundation 1.1. >> > >> > We need a definitive answer to avoid costly reworking of code to a lower >> JDK >> > level. >> > >> > Regards, >> > Kevin >> > >> > [1] >> > >> http://dev.eclipse.org/mhonarc/lists/eclipse-incubator-e4-dev/msg00234.html >> > [2] http://wiki.eclipse.org/E4/Architectural_Foundations see "Summit >> Notes >> > for Java 5/supported platforms" >> > >> > ----- Forwarded by Kevin McGuire/Ottawa/IBM on 12/15/2008 10:32 AM ----- >> > "Gorkem Ercan" <[email protected]> >> > Sent by: [email protected] >> > >> > 12/15/2008 05:37 AM >> > >> > Please respond to >> > E4 Project developer mailing list <[email protected]> >> > To >> > "E4 Project developer mailing list" <[email protected]> >> > cc >> > Subject >> > [e4-dev] The targets for CSS Engine >> > >> > >> > >> > >> > >> > >> > I have been trying to get the existing code working with the eRCP >> > runtime. The good news is after a few hours of hacking and commenting >> > I was able to get it working. I am now wondering what are the platform >> > targets for the CSS engine. We can possibly help with the existing >> > code base to complete it and make it compatible with CDC FP 1.1 >> > (better yet CLCD 1.1 ) also add eSWT and eJface support. Are those >> > things in the interest and target of the css related work? >> > -- >> > Gorkem >> > _______________________________________________ >> > e4-dev mailing list >> > [email protected] >> > https://dev.eclipse.org/mailman/listinfo/e4-dev >> > >> > ________________________________ >> > _______________________________________________ >> > e4-dev mailing list >> > [email protected] >> > https://dev.eclipse.org/mailman/listinfo/e4-dev >> > >> > >> > _______________________________________________ >> > e4-dev mailing list >> > [email protected] >> > https://dev.eclipse.org/mailman/listinfo/e4-dev >> > >> > >> _______________________________________________ >> e4-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/e4-dev >> > > > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > >
_______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
