Please return the export options

[Zulu Ripper]

I know we can now copy and paste the links in various formats.

And while that can be useful for editing,  this just adds another step for those of us who just simply want to export to html.  I know, most likely, this was done to simplify the import process, since users will most likely export to formats that the extension has yet to effectively parse for importing.  Thus, only allowing us to only "copy" that data to paste and save ourselves.   You know you could've just specified that importing only works for JSON exports.  Please reconsider... b/c for those of us who have used this plugin over the years, this all feels like a slap in the face.   

This tool was perfect as it was, just to get a facelift, lose/change exporting options, and easily lose saved sessions that have not been exported.  

This is what we need to see returned:

https://sessionbuddy.com/import-export/

As the saying goes:  If it "ain't" broke, don't fix it!

Sincerely,

Zu

[Session Buddy Support]

The next release brings back support for more import formats, including v3 import formats. It also adds a few new ones:

This support will be added to Import as well as a new way to add links to collections or tabs to the current session.

Export formats will be expanded as well, though initially just to a subset of those listed above. This will be extended later to include all import formats and possibly HTML, Markdown, and others.

It's clear now that we didn't do a great job communicating the UI changes in v4, and especially WHY those changes were needed. We also should have better explained why it was necessary to drop features in the initial v4 release and that those gaps would be addressed in follow-up releases.

The situation was much more complicated than anyone not directly involved in SB development could possibly know. I won't go into detail here, but I assure you that SB v3 was far from perfect in terms of feature set, usability, reliability, and especially maintainability. These issues, along with impending Chrome deprecations  (Manifest v2 and Web SQL Database) impacting major portions of the codebase, made the v4 rewrite an inevitability. Withholding a handful of features from the initial v4 release was necessary to meet the hard deadlines imposed by those deprecations. The alternative was that a significant percentage of users would end up losing their data.

Please understand that v4 was a huge leap forward in establishing the technical foundation required for continued growth. There are hundreds of feature and enhancement requests in the backlog, many of which would have been difficult or impossible to accommodate on the v3 codebase. v4 also included hundreds of user-facing improvements in the form of new features, enhancements, and bug fixes. Some of them are outlined in the release notes.

Cheers,

Hans

--
You received this message because you are subscribed to the Google Groups "Session Buddy Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sessionbuddy-dis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sessionbuddy-discuss/fcf0305f-5f1c-486d-aad4-335814d07113n%40googlegroups.com.

[Zulu Ripper]

Much thanks, Hans.

I look forward to the updates mentioned.

Any idea of eta?

[Session Buddy Support]

Within a couple weeks.

Hans

To view this discussion visit https://groups.google.com/d/msgid/sessionbuddy-discuss/6de695de-8bf6-4b1d-b5d5-3113b330cbb2n%40googlegroups.com.

[Josh Stephens]

Looking forward to the next release!