Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

look into BabelExt #4

Open
chadwhitacre opened this issue Nov 27, 2012 · 4 comments
Open

look into BabelExt #4

chadwhitacre opened this issue Nov 27, 2012 · 4 comments

Comments

@chadwhitacre
Copy link

@ironchefpython would BabelExt from @honestbleeps help here? It promises Chrome, Firefox, Opera, and Safari. Would obviate #2 and #3.

@honestbleeps
Copy link

I'd be more than happy to answer any questions about BabelExt if you're interested in using it! I haven't written extensive documentation yet, which is why I haven't actively promoted it, but I'd be more than happy to help if I can!

@ironchefpython
Copy link
Owner

The code is currently a userscript that adds a single button to github pages. While BabelExt seems to focus on abstracting browser variances, the current userscript does pure DOM manipulation, and thus doesn't really need to worry about brwoser quirks.

That being said, if you had a pipeline where you could drop a userscript into one end, and have all browser extentions build, signed, and uploaded to the various repositories, that would be useful.

@honestbleeps
Copy link

Well, BabelExt provides the necessary "boilerplate" for all 4 browsers as
well, which would save you a little bit of time, but it doesn't do a full
build pipeline in terms of automating compilation, etc. I'm not sure that
it ever will because Chrome and Safari have their own internal methods done
from within the browser, and while they may exist - I'm not aware of any
commandline tools that'll replace that.

On Wed, Nov 28, 2012 at 1:46 PM, ironchefpython [email protected]:

The code is currently a userscript that adds a single button to github
pages. While BabelExt seems to focus on abstracting browser variances, the
current userscript does pure DOM manipulation, and thus doesn't really need
to worry about brwoser quirks.

That being said, if you had a pipeline where you could drop a userscript
into one end, and have all browser extentions build, signed, and uploaded
to the various repositories, that would be useful.


Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-10818086.

@ironchefpython
Copy link
Owner

Chrome and Safari have their own internal methods done from within the browser, [...] I'm not aware of any commandline tools that'll replace that.

I wondder if one could leverage existing browser automation tools (likes the ones for Selenium) to script the browser specific actions...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants