supermemo / supermemoassistant.plugins.import Goto Github PK

via SMA import inline PNGs show up like this

whereas with SM import they show up properly

Note: wikipedia preferences have been set that LateX will render as PNGs

Description

• From discord discussion and my discovery of SM functionality of storing videos in this weird place
• This is not an idea but a beginning of an idea or path to an idea (related to videos)
• Alexis mentioned in browser extracts

Sketches, Videos, ...

This is what i see in IE browser history

This is what opens when i click the link (same overlay that SM uses in incremental video)

Link looks like this:
http://supermemory.info/iv/yt.htm?videoid=QX50u92RqKg&resume=0:00&start=2:17&stop=4:08&ts=2020329318447

Motivation

This issue is about utilizing the fact that videos are stored that way.

See supermemo/SuperMemoAssistant#56

Some images accessible from the browser might not be in the form of a url. I have to account for that. (Would you mind creating an issue for it ? In the Import repo)

When a WebsiteCfg doesn't define a RootElement, or when no WebsiteCfg can be found, fallback to a default, customizable RootElement.

This RootElement would be configured in a General settings tab, under the Import Settings.

Note: this will require improving the website config interface (e.g. add a search box)

When you're on chrome have an ability to extract just a small part of a webpage or an entire webpage that get's saved and auto imported into supermemo when you open it. That way for mac users they can create extracts while supermemo is on a different PC - like have a SMA account where you're extracts are saved.

Maybe extend the functionality to mobile, where you can create imports that get saved online, that auto import into SM next time you open SM.

• Scripts
• Inline style (?)

API: chrome.tabs.remove(closeIDs);

Description

List of additional Regex's in configured websites to extract user-defined information, such as the author, publication date, etc.

Environment

When should this feature be enabled ? Which environments should support it ?

During importing a website. Supported for any configured website.

Motivation

Why do you want to see this feature ? What use cases does it support ? Approximately how big percent of user base do you think would use this feature ?

I often import information from the same websites, which is why I've set up some configured websites. However, these configs only let me extract the title and date, not any of the other relevant bits of context. Many people who use website configs would use this.

Documentation-type explanation

1. Open the configured website of choice
2. Click "Add context Regex (optional)"
3. Add a name
4. Define the Regex
5. Save
6. Import website, and see the new field in the context information (yay!)

Drawbacks

What potential issues should we consider ? Why should we not do this ?

I think this would fit quite naturally. Possible reasons would be overcomplication through too many features, and incompatibility with some parts expecting a fixed set of extracted context fields.

Allow user to write scripts to customize/edit the page content in more detail.

• Extract to SM
• Extract to SM with options
  • Destination node
  • Priority
• Highlight extracts