Code Monkey home page Code Monkey logo

leovue's People

Contributors

kaleguy avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

leovue's Issues

Is it worth the effort to run locally (w/o local server)?

I was hoping to run this locally (I have a .leo file I'd love to distribute privately, can't really host it publicly).

I started looking at expanding how the .leo file is read. The following non-working code is food for thought:

function loadLocalFile(filename) {
  var p = new Promise((resolve, reject) => {
    if (!filename) {
      reject("File not found")
    }
    var reader = new FileReader()
    reader.onload = function(e) {
      var contents = e.target.result
      resolve(contents)
    };
    reader.readAsDataURL(filename);
  })
}

function loadDoc (filename) {
  console.log('loading file:', filename, window.lconfig, 'test')

  var p = new Promise((resolve, reject) => {
    if (window.location.origin === "file://") {
      return loadLocalFile(filename)
    }
    axios.get(filename)
      .then(function (response) {
        resolve(response.data)
      })
      .catch(function (error) {
        console.log(error)
        reject()
      })
  })
  return p
}

However, in order to continue, I think this would work:

  • Add a hidden tag with events
  • Populate the file with the filename
  • File loads (?)

But, I'm not absolutely positive the second step will work. I think it might violate javascript security and be blocked.

Any thoughts on this? Have you tried this already and know it won't work?

Currently, this code errors out with:
TypeError: Failed to execute 'readAsDataURL' on 'FileReader': parameter 1 is not of type 'Blob'

build err

Thanks @kaleguy for the new 2.0.1 release.. Can not wait to try. but met some error.

npm run build
was not successful.

After google, I was told timeline-vuejs need 1.0.3, I dont know why @johmun/vue-tags-input was not installed by "npm install"

ERROR in ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/TagSearch.vue
Module not found: Error: Can't resolve '@johmun/vue-tags-input' in '/Users/wangxu/Documents/github/leovue/src/components'
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/TagSearch.vue 7:20-53
 @ ./src/components/TagSearch.vue
 @ ./src/main.js

ERROR in ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/LVTimeline.vue
Module not found: Error: Can't resolve 'timeline-vuejs' in '/Users/wangxu/Documents/github/leovue/src/components'
 @ ./node_modules/babel-loader/lib!./node_modules/vue-loader/lib/selector.js?type=script&index=0!./src/components/LVTimeline.vue 19:21-46
 @ ./src/components/LVTimeline.vue
 @ ./src/main.js

ERROR in ./src/main.js
Module not found: Error: Can't resolve 'timeline-vuejs/dist/timeline-vuejs.css' in '/Users/wangxu/Documents/github/leovue/src'
 @ ./src/main.js 57:0-49

RTL Support

Hi,
There Are many languages like arabic/farsi/hebrew which are "right to left". fortunately Html Support for RTL languages is very straight forward, Would You PLEASE support RTL Languages.

some of the nodes body are not showing

Dear LeoVUE user,

I'm running leovue by putting the dist folder into my www root directory.
Most the the function is working as expected. However, I noticed some of the nodes, especially when the body text is long, are not being displayed on the right side panel.

The left side tree view works fine, I can still see the headline of the notes, but when I click the headline, the right side body panel doesn't change.

I tested with both apache server and python http.server.

Thanks,
Austin

vue-chartjs v3.2.x build error

Since in package.json has the vue-chartjs package ^3.0.0 declared version and their v3.2.x build raised an error, got this error in browser console after building leovue: apertureless/vue-chartjs#310

Used v3.1.0 explicitly in package json to fix the problem. Maybe using it would be safe bet to not let them to crash the build of leovue?

Missing scrollbars on long web pages

When the rendered content of a node results in a tall web page, there does not appear a scrollbar in the browser (tested in Chrome and Brave on MS Windows 10) when the View Type (from the hamburger menu in the top right corner) is Outline, Graphic Tree, or Nested Menu. OK though for Inline.
e.g. https://kaleguy.github.io/leovue/#/t/4

image

Make this the next generation of Leo

Well done, this is awesome!

Ok, I've known and used Leo since its pre-python days! I've always thought that it needs to be pushed to the web somehow, and I believe you are half of the way there! If only Edward could decouple the leo engine from its gui UI, you could plug it into your system and have a persistent editor via the web, with all the beautiful possibilities that that entails. ๐Ÿ‘

S

Parse error in LEO file: better reporting, why did it happen?

I attempted to deploy Leo to a github-pages site and got a blank screen. Using the inspector, I found the following parse error:

leo.js:342 Uncaught (in promise) SyntaxError: Unexpected token 	 in JSON at position 332
    at JSON.parse (<anonymous>)
    at leo.js:342

The file that created the parse error is here:
https://github.com/metaperl/being-doing-having/blob/master/docs/parse-error.leo

it would be nice if parse errors were more prominently fed back to the end user.

leo node with jinja template is not displayed

In my leo file, there are some node with the format of Jinja template, for example, it includes some text as below:

token {{ decrypt("gAAAAABdhei7v18G8cwZcLBVfOwmJDAvYVWvoxQlAX03gxdoGU6Kp9CE8O7Ki0N8iYpvWtVeLu__5-KlxYKwDhgKLo1aSiYDrw==" ,"wmGj7cOGAHS1q8L0N2F3Ig==")}}

When I tried to display those nodes, the body panel is empty.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.