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

The Next Version #58

Closed
4 tasks
myobie opened this issue Mar 28, 2014 · 7 comments
Closed
4 tasks

The Next Version #58

myobie opened this issue Mar 28, 2014 · 7 comments
Assignees
Milestone

Comments

@myobie
Copy link
Collaborator

myobie commented Mar 28, 2014

Shortly, I want to begin the next version of ruby-gmail.

This gem should live up to this description:

A Rubyesque interface to Gmail, with all the tools you'll need. Search, read and send multipart emails; archive, mark as read/unread, delete emails; and manage labels.

To get there I think these steps need to be taken:

  • convert to use the mail gem behind the scenes
  • sketch a newer gmail dsl
  • spec out high level stuff
  • figure out and full spec out labels

These are very generic todos, but I think they are the path forward. Labels are super important. Also being able to peak and not mark as read will be huge.

If anyone is interested in helping or has comments on the direction please feel free to comment here.

The work for 2.0 will take place on my fork.

@myobie myobie added this to the v2.0 milestone Mar 28, 2014
@myobie myobie self-assigned this Mar 28, 2014
@gabrielengel
Copy link
Contributor

Hey!

I think we should make it as easy to use as possible and try to remove any kind of redundancy. Also, we can use only the Gmail style search so we don't have to implement many things. What do you think of something like this?

https://gist.github.com/gabrielengel/201e9661b4f92b8f543d

@johnnyshields
Copy link

@myobie I'm a user/maintaner of gmailgem/gmail (formerly nu7hatch/gmail which was originally forked from this repo.) We'd be very keen to join efforts on the gmailgem fork as our goals are the same, i.e. more usable API, better testing, etc.

@myobie
Copy link
Collaborator Author

myobie commented Jan 19, 2015

@johnnyshields awesome. I'd like to get some tests started so we can all get it going soon. I've added you as a collaborator.

@myobie
Copy link
Collaborator Author

myobie commented Jan 19, 2015

@gabrielengel regarding your gist I do have this feedback:

I don't think we need to manage any state, instead we can just return objects from every call. An example of what this would look like from your gist would be:

Gmail.new(username, password) do |gmail|
  gmail.in('inbox').count # => 100

  gmail.search('is:unread').count # => 60

  gmail.search('is:read').count # => 40

  gmail.search('before:2010-02-20 after:2010-03-20')
  gmail.search('on:2010-04-15')
  gmail.search('from:[email protected]')
  gmail.search('to:[email protected]')
  gmail.search('is:read from:[email protected] "you are a great employee"')

  gmail.peek do |peek|
    peek.in('Urgent').count
  end
end

@johnnyshields
Copy link

@myobie, I've added you to the gmailgem organization. Come over to our side--we have an awesome team and a reliable approach to test the gem on Travis CI with specs now green. Your suggested improvements are most welcome.

@simo2409
Copy link

simo2409 commented Mar 2, 2015

I think it would be useful in the new version to abandon username/password auth and using Gmail's API.
Until you use ruby (and ruby-gmail) on your desktop it's the same but using them on a webapp it drives to

Please log in via your web browser: http://support.google.com/mail/accounts/bin/answer.py?answer=78754 (Failure)

@myobie
Copy link
Collaborator Author

myobie commented Aug 16, 2018

I'm closing this since it's so old.

@myobie myobie closed this as completed Aug 16, 2018
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

4 participants