search

honestbleeps / BabelExt

BabelExt is a cross browser boilerplate/library for extension development
http://babelext.com/
MIT License
227 stars 36 forks source link

Internet Explorer #12

Open dovy opened 11 years ago

dovy commented 11 years ago

Any plans to expand to the dreaded IE?

patricksnape commented 11 years ago

Kango: It can be done!

honestbleeps commented 11 years ago

I'd be curious to see how full featured Kango is for IE, and how they did it.

I had a guy try and "help" get RES working on IE and it was a pretty miserable failure... but to be honest I never looked deeply at it... IE just doesn't have a similar enough extension architecture to make this reasonably simple...

On Mon, Sep 2, 2013 at 1:03 PM, Patrick Snape notifications@github.comwrote:

Kango http://kangoextensions.com/: It can be done!

— Reply to this email directly or view it on GitHubhttps://github.com/honestbleeps/BabelExt/issues/12#issuecomment-23672704 .

patricksnape commented 11 years ago

I had a little back and forth with the Kango guys and they are very protective of their IE stuff. I asked if we could use it for RES and they said they could provide a build server for building the IE extension - which is obviously not very useful.

dovy commented 11 years ago

I have some ie stuff, but it only works to include a single script on a URL regex. I'd love to do more, that's why I'm here. Heh.

I might be willing to give the code provided people expand it to be fully supportive. But I'd have to have a good use case. Cost us a bit to do.

honestbleeps commented 11 years ago

I'm absolutely willing to add IE support and would be excited if I could... I just see a lot of trouble with every single project I've seen try and cram in "userscript style" extension support to IE.

Kango may well have it figured, but obviously they're not gonna open source it.

To me, I'd like to see something like that open sourced. It would be good for IE11+ which finally is a decent browser save for its lack of "commonly used" extension support.

My goal with BabelExt is to democratize extension development - which obviously goes a bit counter to what Kango, Crossrider and others want, which is to make money on it (which I respect entirely, it's just not what I want)

On Mon, Sep 2, 2013 at 1:27 PM, Dovy Paukstys notifications@github.comwrote:

I have some ie stuff, but it only works to include a single script on a URL regex. I'd love to do more, that's why I'm here. Heh.

I might be willing to give the code provided people expand it to be fully supportive. But I'd have to have a good use case. Cost us a bit to do.

— Reply to this email directly or view it on GitHubhttps://github.com/honestbleeps/BabelExt/issues/12#issuecomment-23673510 .

kasbah commented 11 years ago

salsita/ancho is aiming for IE support, not sure about the status.

dovy commented 11 years ago

@honestbleeps We need a C# programmer then, heh.

@kasbah How interesting! That's a really fascinating take which I, honestly, like.

I just need a solution. I'm tired of doing it all manually.

What's the best route?

dovy commented 11 years ago

@honestbleeps ancho is an interesting concept. You could easily take your code and add in chrome, safari, and firefox support with what you've done thus far.

Don't know the benefits or issues. What would you think of merging the projects? Just a question.

honestbleeps commented 11 years ago

aside from the work they've done to support IE I'm not sure what they offer that BabelExt doesn't...

BabelExt mostly leans towards Chrome's APIs since they make the most sense, but I actually don't like the idea of "faking like it's the chrome API" when you're in Firefox, for example. To me, it makes more sense to abstract the things that can be abstracted, and rely on conditional code for things that can't/shouldn't be abstracted between all the browsers - but that's a personal preference.

Mostly I'm concerned about their nebulous license. I want BabelExt to be extremely permissive, and theirs is vague and probably not.

I'm not trying to shoot down the idea - having not seen an example extension built with Ancho it's hard to judge just by looking at the source... but those are my immediate concerns upon reviewing it.

On Mon, Sep 2, 2013 at 3:41 PM, Dovy Paukstys notifications@github.comwrote:

@honestbleeps https://github.com/honestbleeps ancho is an interesting concept. You could easily take your code and add in chrome, safari, and firefox support with what you've done thus far.

Don't know the benefits or issues. What would you think of merging the projects? Just a question.

— Reply to this email directly or view it on GitHubhttps://github.com/honestbleeps/BabelExt/issues/12#issuecomment-23677634 .

dovy commented 11 years ago

@honestbleeps I agree with all your points.

Do you have an IM account? Perhaps we could interact more about this? dovy@rtcollab.com for gchat...

honestbleeps commented 11 years ago

sure, steve@openingbands.com for gchat... I don't have long right now, but I'm up for discussion with you and anyone else interested!

On Mon, Sep 2, 2013 at 3:53 PM, Dovy Paukstys notifications@github.comwrote:

@honestbleeps https://github.com/honestbleeps I agree with all your points.

Do you have an IM account? Perhaps we could interact more about this? dovy@rtcollab.com for gchat...

— Reply to this email directly or view it on GitHubhttps://github.com/honestbleeps/BabelExt/issues/12#issuecomment-23678024 .

mitar commented 10 years ago

My goal with BabelExt is to democratize extension development - which obviously goes a bit counter to what Kango, Crossrider and others want, which is to make money on it

+1

dovy commented 10 years ago

Well, i handed off the source code for my IE plugin. We just need someone to finish it off...

dovy commented 10 years ago

Hey all, any progress here?