Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Mar 02 2018 07:29
    egolus opened #96
  • Apr 06 2017 09:49
    coveralls commented #62
  • Oct 29 2016 15:10
    egolus closed #92
  • Oct 29 2016 15:10
    egolus commented #92
  • Oct 29 2016 09:59
    baudren unlabeled #95
  • Oct 29 2016 09:59

    baudren on devel

    add a button to insert an image… filter update Add tests for the image inserti… and 3 more (compare)

  • Oct 29 2016 09:59
    baudren closed #95
  • Oct 29 2016 09:59
    baudren commented #95
  • Oct 21 2016 15:19
    egolus synchronize #95
  • Oct 21 2016 15:19

    egolus on egolus-insertImage

    added image-button to new-entry… (compare)

  • Oct 21 2016 14:31
    egolus commented #95
  • Oct 21 2016 07:34
    baudren commented #95
  • Oct 21 2016 07:32
    baudren commented #95
  • Oct 16 2016 16:29
    egolus unlabeled #93
  • Oct 16 2016 16:29
    egolus closed #93
  • Oct 16 2016 16:29
    egolus commented #93
  • Oct 16 2016 14:36
    baudren labeled #95
  • Oct 16 2016 14:36
    baudren labeled #95
  • Oct 16 2016 14:36
    baudren opened #95
  • Oct 16 2016 14:35

    baudren on egolus-insertImage

    add a button to insert an image… filter update Add tests for the image inserti… and 1 more (compare)

Benjamin Audren
@baudren
http://bottlepy.org/docs/dev/tutorial.html#quickstart-hello-world maybe this would be a nice framework to use (it is extremely minimalistic) for implementing the end-points.
Benjamin Audren
@baudren
or http://falconframework.org/, this seems to be very fast.
Benjamin Audren
@baudren
After a bit more browsing, falcon seems too much trouble than its worth. It seems twice as fast as bottle on standard cases, but if it is several times more painful to use...
Benjamin Audren
@baudren
there are some interesting parts in this https://idolstarastronomer.com/docker-and-bottle.html
Benjamin Audren
@baudren
other points to discuss:
  • The answers we'll give from the API calls should be in json, right?
  • do we use a DB, finally, or not? So we store the entries inside a DB (how does this work for long text entries?), then have the possibility to "export to files"? Or we use the file system as a sort of DB, with a file per entry, then recreate at will a more compact version? I am somehow not a big fan of it, as I like having files...
Benjamin Audren
@baudren
I was reading about zeroMQ as an alternative to HTTP for the API part, and was not necessarilly convinced that it's a good idea. It looks really low-level, which sometimes is nice, and some others... well, not so much.
egolus
@egolus
  • answers .. hmm, yes, I haven't actually used json, but it looks like the way to go
egolus
@egolus
  • the question, db or not .. I think we can use a db and don't have to think about text fields that much. I don't know If there are any limits for the text fields. DBs should have "fulltext" fields that can get pretty big.
    If we don't want to use a db, we can stay with the current system. One file per notebook, then we can use almost all the current code, we can just refactor it a bit to get a better separation. The "export" would just be a copy or you can even go into the filesystem directory as we do at the current point.
    One file per entry would mean, we can move away from the stiff notebooks more easily. An export would mean, read all needed notes and write them sequential, right?
    Flat files as we use them now allways have the benefit that you can throw away all the code and just open the files again without loosing (any|much) information.
    In the stackoverflow question they talk about real database servers that lead to a lot of overhead. I think we should compare flat files to sqlite .. that's a different story.
the longer I think about it the more I doubt that we need a real RESTful API. That would only be needed when we really want to have a server/client model. If not, we just need to put the storage code into a library with a clear API or architecture, but we don't need to build two separate applications
egolus
@egolus
have you seen the issue on github?
looks like an issue with qtpy
egolus
@egolus
ok, I reproduced the issue and solved it by installing qtpy==0.1.3 instead of 1.0b1. Can you check this on linux? We could just force this version, right?
Benjamin Audren
@baudren
yep, I did this (I actually forced <=0.1.3, because for me 0.1.2 works just fine).
egolus
@egolus
allright thanks
I'll look further into the issue with version 1.0b1. It looks like they pulled some code from upstream that messed up the check for the QT-library
egolus
@egolus
this is just strange.. I set up the virtualenv again: python 3.4.4 x86, pyside 1.2.4, QtPy 1.0b1
when I import qtpy, there's no assert error
so it only triggers when called from qtawesome?
egolus
@egolus
I can't reproduce the error manually. When I import the libraries in a python session, the error doesn't trigger ..
do we set the environment variable? I remember that you had problems with it, when both PySide and PyQt were installed ..
and they check for another string:
'PySide' != 'pyside'
egolus
@egolus
can you check my PR? But I guess, you don't have your old setup with both libraries installed any more
Benjamin Audren
@baudren
I checked it, and it looks like it is working fine for me too
I'll merge that, thanks for investigating
egolus
@egolus
the question is should we send a bugreport to qtpy? I think they should check caseinsensitive
Benjamin Audren
@baudren
that could be a good idea, yes
at least to see what is their opinion on that
egolus
@egolus
I must say I'm really satisfied using pentadactyl instead of vimperator on my arch. Firefox manages to break it with every update (even the minor update 46.0.1 -> 46.0.1-1) but at least the maintainers fix these problems fairly quickly.
I just learned that I can just use <C-I> in any input area to edit the text in an external editor. It took some time but I got it working with nvim in a terminal
set editor='termite -e "nvim +<line> +\"sil! call cursor(0, <column>)\" <file>"'
egolus
@egolus
so maybe now I won't go crazy using jupyter notebooks .. it really breaks my flow to code in a browser-window
egolus
@egolus
whoops I didn't want to put this into the noteorganiser chat ..
egolus
@egolus
grr. now my python2 pytest doesn't work any more .. it can't import pytest-mock.. So I can only test python3 locally and have to rely on travis for python 2
Benjamin Audren
@baudren
Virtual environment?
egolus
@egolus
I don't use one for noteorganiser atm. I could set one up and try it there
Benjamin Audren
@baudren
I can see why people don't like to maintain for the two versions...
Although dropping python 3 support is not, definitely not, what should be done
egolus
@egolus
why would you want to do such a horrible thing? python 3 has so many nice things ..
I'll start adding type hints in my scripts, soon .. It really helps with the readability if you always know what type you have to expect
(yes, there are type hints as comments in python 2, but I think the syntax is very clean in python 3)
egolus
@egolus
(still building pyside in the venv ...)
your comment to go for a walk while it's building was meant quite literal, I guess
egolus
@egolus
ok, from the virtualenv it runs ..
Benjamin Audren
@baudren
Yeah, building pyside the first time is incredibly slow
egolus
@egolus
while reading the neovim-newsletter I've seen that it's possible to embed this nodejs-component to another app. Would be nice to have as an editor
Benjamin Audren
@baudren
Looks super cool to have in one's toolbox!