No worries on the delay, Christian, heh. Thanks for creating an issue! :-) Definitely agree about removing it. I'm going to continue my comment in the issue's mailing list thread...
On Wed, Apr 10, 2013 at 6:21 AM, Gord Tanner <[email protected]> wrote: > +1 > > I also agree we should probably remove the RIM specific code now that we > are in apache, there is a bit of it and is only used for the RIM > distribution of ripple and is not generic. > > Some of it is only used for integrating with a closed source service that > is not included in this project and should be removed for sure. > > Sent from my iPhone > > On 2013-04-10, at 5:30 AM, Christian Grobmeier <[email protected]> > wrote: > > > hi Brent, > > > > sorry for my delay. I created an issue with your answer: > > https://issues.apache.org/jira/browse/RIPPLE-12 > > > > and linked it to the related RIPPLE-4. Now we can't forgot about it :-) > > > > Cheers + thanks for your explaination > > > > > > > > On Sun, Mar 31, 2013 at 7:52 PM, Brent Lintner <[email protected]> > wrote: > >> Hey Christian, > >> > >> You are correct in your assumptions. :-) > >> > >> The hosted version _is_ essentially a standard website, but I'm not sure > >> off the top of my head if you can serve it up without using the CLI- > have > >> not tried. :-) > >> > >> The rim chrome extension is used for the > >> http://developer.blackberry.com/html5 release of Ripple, vs the Chrome > >> Store extension. It has a few extra things such as a slightly different > >> manifest.json, some different extension files to enable a UI to > >> build/deploy WebWorks applications, the ability to sign a EULA, etc. > >> > >> However now that we are in the incubator, I think stuff like that (and > >> other RIM specific things) needs to be figured out what to with (in the > >> best interests of the project as a whole). I.e should they be in an > >> external fork and not part of the main project? This is something I (or > >> some others) was hoping to start a discussion about soon. :-) > >> Hi, > >> > >> I found three build targets: > >> > >> - chrome extension > >> - hosted > >> - rim chrome extension > >> > >> The first one is clear. > >> > >> Am I assuming right the "hosted" one should act as standard website? > >> > >> I am unsure what the difference from the chrome ext to the rim chrom > >> ext ist. Maybe somebody can tell me :) > >> > >> Cheers > >> Christian > >> > >> -- > >> http://www.grobmeier.de > >> https://www.timeandbill.de > > > > > > > > -- > > http://www.grobmeier.de > > https://www.timeandbill.de > -- Brent
