Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

entries containing data #37

Closed
dedan opened this issue Jun 11, 2012 · 11 comments
Closed

entries containing data #37

dedan opened this issue Jun 11, 2012 · 11 comments
Labels
🔒 Outdated wontfix Will not be fixed

Comments

@dedan
Copy link
Contributor

dedan commented Jun 11, 2012

Since quite some time I use evernote to write down text and snippets. basically for what I now use jrnl for. But what I mainly used it for is organization of pictures, pdf, etc. some documents that I needed to tag and organize, maybe annotate. basic simple things which still cannot be done by the normal file system. I would like to use jrnl also for this. Here my ideas of how to achieve this..

  • When you want to include a file, just paste its URL (local or on the web) in the entry you currently write. When finished writing and before the entry is added, jrnl will search the entered text for valid urls.
  • jrnl will then ask you whether you want to included the referenced file in your jrnl, when answered with yes, copies of the files will be created (downloaded from the web or just locally copied) in a data folder next to the jrnl textfile (also in the dropbox)
  • the urls could be kept in the text or written in the end of the jrnl entry.
  • content could be nicely rendered in markdown export
@dedan dedan mentioned this issue Jun 11, 2012
@maebert
Copy link
Contributor

maebert commented Jun 13, 2012

Hmm... doesn't immediately convince me - I think that'd blow up jrnl quite a bit and change the direction from note-taking and, well, journaling, to knowledge management. I always thought of jrnl as belonging to the "Do one thing, and do it well."-category...

@dedan
Copy link
Contributor Author

dedan commented Jun 14, 2012

well yes, I understand your point. I like the "do one thing and do it
well" philosophy.

But it would also be so useful for me. Maybe I'll just implement it on
a branch and then
we can see how well it works and how useful it is.

On Wed, Jun 13, 2012 at 12:12 PM, Manuel Ebert
reply@reply.github.com
wrote:

Hmm... doesn't immediately convince me - I think that'd blow up jrnl quite a bit and change the direction from note-taking and, well, journaling, to knowledge management. I always thought of jrnl as belonging to the "Do one thing, and do it well."-category...


Reply to this email directly or view it on GitHub:
https://github.com/maebert/jrnl/issues/37#issuecomment-6297315

@maebert
Copy link
Contributor

maebert commented Jun 16, 2012

I'm looking forward to see how it works for you!

@maebert maebert closed this as completed Jun 16, 2012
@maebert maebert reopened this Aug 9, 2012
@maebert
Copy link
Contributor

maebert commented Aug 9, 2012

Actually, the more I think about it, the more I like this idea. Let's stick heads together and see how we can do this in the cleanest way without messing with the existing stuff!

@dedan
Copy link
Contributor Author

dedan commented Aug 10, 2012

hey manu,

yes yes yes, let's meet soon and discuss how to do this. I once started
implementing a few things,
just to get a feeling for how it might be done. I'll publish this branch
now, but still lets meet soon.

On Thu, Aug 9, 2012 at 6:57 PM, Manuel Ebert notifications@github.comwrote:

Actually, the more I think about it, the more I like this idea. Let's
stick heads together and see how we can do this in the cleanest way without
messing with the existing stuff!


Reply to this email directly or view it on GitHubhttps://github.com/maebert/jrnl/issues/37#issuecomment-7619963.

@maebert
Copy link
Contributor

maebert commented Aug 10, 2012

I'll be off to Denmark and the states, so let's keep it digital. Basically my concerns were about how to keep the flat journal file readable and uncluttered when attaching additional information.

@dedan
Copy link
Contributor Author

dedan commented Aug 11, 2012

I published a first draft. But we should have a skype discussion soon

On Fri, Aug 10, 2012 at 1:15 PM, Manuel Ebert notifications@github.comwrote:

I'll be off to Denmark and the states, so let's keep it digital. Basically
my concerns were about how to keep the flat journal file readable and
uncluttered when attaching additional information.


Reply to this email directly or view it on GitHubhttps://github.com/maebert/jrnl/issues/37#issuecomment-7639558.

@iggyvolz
Copy link

Is this still being considered?

@flight16
Copy link

@dedan Can you share the draft you published?

What is the plan for behavior here? Still the original post?

jrnl will then ask you whether you want to included the referenced file in your jrnl, when answered with yes, copies of the files will be created (downloaded from the web or just locally copied) in a data folder next to the jrnl textfile (also in the dropbox) the urls could be kept in the text or written in the end of the jrnl entry.

@maebert maebert modified the milestones: 2.1, 2.0.0 Apr 14, 2015
@dedan
Copy link
Contributor Author

dedan commented Apr 14, 2015

Hey @flight16,

I can't find this draft anymore and it was really only very preliminary
work. Not something that could not be re-written in an hour. I'm also not
convinced of this feature anymore, at least not for the jrnl core. Could
make sense as a plugin though

On Mon, Apr 13, 2015 at 4:23 PM flight16 notifications@github.com wrote:

@dedan https://github.com/dedan Can you share the draft you published?

What is the plan for behavior here? Still the original post?

jrnl will then ask you whether you want to included the referenced file in
your jrnl, when answered with yes, copies of the files will be created
(downloaded from the web or just locally copied) in a data folder next to
the jrnl textfile (also in the dropbox) the urls could be kept in the text
or written in the end of the jrnl entry.


Reply to this email directly or view it on GitHub
https://github.com/maebert/jrnl/issues/37#issuecomment-92532036.

@wren wren added wontfix Will not be fixed and removed integration labels Jul 6, 2019
@wren wren removed this from the 2.1 milestone Jul 7, 2019
@maebert maebert closed this as completed Jul 8, 2019
@lock
Copy link

lock bot commented May 21, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot added the 🔒 Outdated label May 21, 2020
@lock lock bot locked as resolved and limited conversation to collaborators May 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🔒 Outdated wontfix Will not be fixed
Projects
None yet
Development

No branches or pull requests

5 participants