Added the IE plugin source. Time to get cooking!

[dovy]

This is the IE plugin that we used. Based in Visual Studio 2008. The goal is to make this work without Visual Studio, obviously. If not, we'll have to have a build service for people.

Has some work to do. Good luck!

[honestbleeps]

i do still plan to look at this soon, I've just been swamped. I just wanted to post an update in case any interested parties are watching this as it's really exciting if we can get it working!

[dovy]

Is this dead then?

[honestbleeps]

hey Dovy, i'm really sorry for the lack of action, things outside of work have made it hard to work on BabelExt but I'm sincerely interested in reviving it... I haven't had the chance to get a VM going and my windows machine is hosed...

Do you have some time in the near future to perhaps get on a google hangout and walk me through testing / working with the IE portion of things? If we schedule something, that forces me to set aside the time, and I could use a refresher on how to deal w/the IE side of things because I don't quite know where to start and that's going to be a barrier to entry...

[dovy]

I actually found this...
https://github.com/trigger-corp/browser-extensions

It's called Open Forge and it already has IE. Perhaps we could marry the two?

[honestbleeps]

a few of us from the RES team actually discussed that one a while ago, a few concerns:

• it's not touched very often (a fair concern about BabelExt, too!)
• the requirements are cumbersome and a bit much -- python, mercurial, java, NSIS, etc?
• their documentation is officially deprecated: http://legacy-docs.trigger.io/en/v1.4/modules/browser/index.html

I'm certainly open to borrowing concepts and whatnot from the project, but it seems they've lost interest in it. I, on the other hand, haven't lost interest so much as available time :-(

That said, I'd like to schedule some time to get BabelExt in better shape, and if we could schedule some collab time I'm up for it. CC: @andytuba in case he is interested too.

[dovy]

• Heh, same?
• True, but man it's functioning.
• Only because they've moved to another system and left it to the community.

Yes, triggerIO the company could care less. But why not fork it and use it. I mean, you don't need another environment to build. They have that all built into one package and that's nice.

I'm fine for a chat sometime. I just am hoping to have something this year. :P

[honestbleeps]

I haven't tried trigger's package at all so I have no idea how functional
it is, etc... have you toyed with it at all?

If you have -- what makes you still want to tinker with BabelExt at all if
they've got something good/working? Should I just abandon BE?

I'm not thrilled with their startup requirements, but how much point is
there in my reinventing the wheel if you've played with what they have and
are happy with it?

On Mon, Sep 1, 2014 at 5:33 PM, Dovy Paukstys notifications@github.com
wrote:

• Heh, same?
• True, but man it's functioning.
• Only because they've moved to another system and left it to the
  community.

Yes, triggerIO the company could care less. But why not fork it and use
it. I mean, you don't need another environment to build. They have that all
built into one package and that's nice.

I'm fine for a chat sometime. I just am hoping to have something this
year. :P

—
Reply to this email directly or view it on GitHub
#16 (comment).

[dovy]

I just dug in. Creation was painless. They use a python environment so you can build with any OS I believe (docs haven't said otherwise). Haven't really dug in, but I don't think they have as many APIs as you do. That's why I suggested a marry. ;)

[Ithamar]

Just a warning, I've had a project use OpenForge, and even after upgrading the FF SDK version in there, it got bounced by the FF add-on review crew, so if you go and use that, you'll most likely not get it into the FF extension store.
Also, for the average browser extension, I think it is overly complicated and hard to maintain, I really like the relatively "minimalist" approach of BabelExt ;)
Edit: Also, IE support seems to be broken in OpenForce for anything more recent then IE9 IIRC. I might be able to find some time and allocate it to look into this IE patch, since it is high on our wishlist too..

[Ithamar]

@dovy, if it is just about the creation process, going with a yeoman generator for this project would be much easier, flexible, and easy to maintain (more people understanding yeoman generators then the custom hacked Python build system of OpenForge).
EDIT: hmmm, thinking about that, having a gulp script for running and testing, plus supporting CoffeeScript and other customizations would be really cool too ;)