mleibman / SlickGrid

A lightning fast JavaScript grid/spreadsheet
http://wiki.github.com/mleibman/SlickGrid
MIT License
6.82k stars 1.98k forks source link

Alternative Repo Available #1055

Open 6pac opened 9 years ago

6pac commented 9 years ago

I'm offering an 'alternative master' repo at https://github.com/6pac/SlickGrid, while MLeibman is busy

This aims to keep the main trunk of the project up to date with bugfixes, small enhancements and recent versions of dependencies. Read more: https://github.com/6pac/SlickGrid/wiki

I have released a SlickGrid v2.2 on this repo.

This is in no way an attempt to hijack the project, I just want to ensure there is an up to date version available for new users to avoid some of the basic issues that seem to be repeatedly coming up.

mgpGit-zz commented 9 years ago

I've been looking for updates/bug fixes to slickgrid for some time without going down a very customized/forked path.

I'm going to check this out. Let's keep the project humming along. Thanks!

dss010101 commented 9 years ago

A bit confused. Are you the author of slickgrid or a contributor branching it to carry on work?

-----Original Message----- From: "mpGitHub" notifications@github.com Sent: ‎3/‎16/‎2015 4:55 PM To: "mleibman/SlickGrid" SlickGrid@noreply.github.com Subject: Re: [SlickGrid] Alternative Repo Available (#1055)

I've been looking for updates/bug fixes to slickgrid for some time without going down a very customized/forked path. I'm going to check this out. Let's keep the project humming along. Thanks! — Reply to this email directly or view it on GitHub.

6pac commented 9 years ago

I'm a contributor, but I don't have access to the master repo. MLeibman, the author, is the one with access to the repo, but he's been too busy to keep it updated of late. I'm attempting to fill that maintenance role with this fork. Perhaps if I show I can do it well, one day MLeibman will give me commit access to the master, and then there won't be any need for this fork. Read more: https://github.com/6pac/SlickGrid/wiki

squanto commented 9 years ago

:+1:

dss010101 commented 9 years ago

thanks. it's good i think that others are keeping it going/active

mgpGit-zz commented 9 years ago

Hi 6pac, If issues are found in your fork how do we let you know? I don't see an issues category in your fork?

mgpGit-zz commented 9 years ago

6pac, have you tested running multiple slickgrids on the same page? The formatting of the columns in the first slickgrid is broken after loading the second slickgrid on the page. The column widths are uneven/overlapping.

6pac commented 9 years ago

whoops, had to turn the Issues tracker on. done. thanks for the heads-up.

6pac commented 9 years ago

as to multiple grids, I haven't done that recently. pretty sure I've seen issues from people that have done that successfully though. multiple grids is a requirement I have too, and I've noticed that particularly some of the events are not as supportive of that scenario as they could be (the events should pass grid-specific settings to allow event re-use on multiple grids, rather than relying on closures or global vars, which can't be easily made grid-specific if re-used). it'll probably take me a few more weeks to explore that fully though.

simonzack commented 9 years ago

Awesome, slickgrid is still the best grid around, glad to see the project gaining new life.

dsozzi commented 9 years ago

Nice!!! Thanks a lot for your support!

hakancunier commented 9 years ago

Good!

andyforever commented 9 years ago

+1

amcdnl commented 9 years ago

@6pac you should almost rename it and not make it a fork anymore since they have deviated so much.

6pac commented 9 years ago

Hi @amcdnl, actually I have been trying really hard not to deviate it. The idea is only to fix bugs, keep it up to date, and complete features that need more work.

I have my own personal branch that has been extensively hacked for my own projects. I've completely reworked that one to add a DataProvider interface so the grid can be used with other complex datasources than DataView, and made a bunch of other changes. I have been thinking about releasing that as a separate fork again, but it still needs a little work.

But perhaps you are right. I have been hoping MLeibman might reintegrate my branch into the master at some point, but as time goes on perhaps rebranding as a separate project is a better approach.