+30
Planned

Open the Code!

Alex P-B 11 jaar geleden bijgewerkt door George 5 jaar geleden 9

Hey - It would be great for this to be an open source project!

I imagine it would make it much easier to support the wide varity of platforms chrome runs on if people using (KDE for example) can tweak the code.

Antwoord

-1
Antwoord
Planned

Definitely will be doing once I get a bit more of the core functionality I want in place and stabilized, and tidy up the code a bit -- still got a lot of //TODOs floating around ;)


Without making any guarantees I am projecting to open the code in 3-6 months.

-1
Antwoord
Planned

Definitely will be doing once I get a bit more of the core functionality I want in place and stabilized, and tidy up the code a bit -- still got a lot of //TODOs floating around ;)


Without making any guarantees I am projecting to open the code in 3-6 months.

+2

Good to hear! I'm looking forward to it.

I'd be happier for it to be open sooner, but I am still very happy to hear you are planning on opening it at allready!

Sidewise is fantastic! keep up the good work :)

+6
Now that the planned 3-6 months turned out to be longer than 2 years, maybe it's time to just release the source code as-is? Experience (not only mine) shows that ugly code will be no problem (and no embarassment either) and bugs will get fixed.
+1

Please just dump the code into your github repo, messy as it may be. Code is never perfect.


By dumping, you'll retain all credit as main author as it will live on under your github name. (This won't happen if any unofficial github code-dump takes off). It will also reduce your work as people fix their own bugs and open PRs, all you have to do then is review and click "merge". So you can focus on implementing more interesting features.

+2

Thank you all for your patience and positive support. It has definitely taken me too long to get this open sourced.


I need to fix the build script which is currently heavily dependent on several arcane Windows-only tools, then it should be in sufficient shape to post up on Github. Once posted I will continue to address several much needed code fixes in the public repo, where others can also contribute fixes and improvements or repurpose the code for their own needs.

I actually don't want to build the software, I also don't want to modify it. I just want to look at it to figure out your file format quickly to process the file with my own tools. I have way too many tabs saved as sessions and always fear they might get lost; also recently my Chrome slowed down and it bothers me that I can't easily deactivate Sidewise, as I've grown dependent on it. It would comfort me to see that the code is available, so that I can fix it in principle, whenever I might have to.
So, please just put it online. Maybe have a public bitcoin address so that we can forward you some thank you in digital currency, if you're so inclined.

Do you mean the format of the "export" string? That's plain json, but being in one single long line, it is difficult to read. 


You can copy it into something like VisualStudio and have it reformat it for you. The structure is as below. The current data set seems to be in the "pageTree". In the below, I had three pages at the time I asked for an export.




And here is how an entry might look:




+1

It's been yet another two years, and six total, of course... And we still appreciate your work that went into this extension, and would like to see it on Github (ideally with a "donate" button, as suggested earlier).  I don't think there are any obscure build tools out there that would prevent people from being happy at this point with *something* official.

That said, considering the stated intent to open source and the lack of movement, perhaps we can consider this extension to be open-source already as far as its license goes, per the developer?  It being a Chrome extension, the source is pretty much embedded in it and can be extracted easily enough.  Someone could just put it on Github themselves at that point, I suppose.