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

DnD between any containers, not just tables/collections #16

Closed
SteveFortune opened this issue Mar 12, 2014 · 3 comments
Closed

DnD between any containers, not just tables/collections #16

SteveFortune opened this issue Mar 12, 2014 · 3 comments
Milestone

Comments

@SteveFortune
Copy link
Member

This is a pretty premature ticket as there are lots of issues to sort, but it would be cool if in the future we supported normal views as 'container's and their subviews as 'draggables', not just tables, collections and cells.

@pubnubcraig
Copy link

This would be useful.

SteveFortune added a commit that referenced this issue Sep 13, 2014
… the CGPoint instead of NSIndexPath.

Retrieving Cells from UI[Table | Collection]View s is easy with NSIndexPath, however one of the goals of 2.0.0 is to resolve #16. We need to decouple the coordination / rendering logic from the actual collection<->item types and impl

In the future, we should endevour to provide some sort of utility for mapping CGPoint to a cell so that users don't have to go around repeating allot of boilerplate code
@SteveFortune SteveFortune added this to the 2.0.0 milestone Sep 18, 2014
@SteveFortune
Copy link
Member Author

Still have yet to actually test the new I3Collection abstraction for v2 with anything other than a subclass of UITableView. Next phase maybe?

@SteveFortune
Copy link
Member Author

Fixed for v2. If you really want to, you can implement I3Collection in your UIView and it will be treated as a collection.

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

No branches or pull requests

2 participants