Jump to content

jemostrom@w

Level 2
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

3 Neutral

About jemostrom@w

  1. I have two accounts, premium + basic, with a shared notebook. In this notebook I merged some notes (photos, PDFs) into one note. This note sometimes show up with a header and sometimes without, see screenshots. (Note: A few moments ago I realized that I had downloaded b3 but not installed it, so this happened in b2 ... I haven't seen this in b3 so far but I have only used it a few minutes)
  2. Yes, this is what got me to try Evernote once again (for note taking that is, not just clipping info). What worries me a bit is the talk about the enex format, if I read the specification correctly a note can contain anything - which of course is good in one way. But I can't see any rules for an optional semantic markup of the content. My way of reasoning is: YES, it's very nice that Evernote is rewriting the editor so the behavior will be consistent across platforms but I don't think that's not enough. There has to be a way to define the meaning of different parts of the notes so that formatting etc can be kept consistent. Perhaps they are thinking about this, I couldn't say based on the posts. The Markdown support announced in beta 1 could be a first sign but I got the impression that it was treated more like some kind of shortcuts for formatting commands not to mark up the content. I hope I worry unnecessarily ...
  3. I've been an on/off user of Evernote for many years. I really like that it's available on many platforms, the syncing works just fine for me, the web clipping is great, organization works great for me, etc but there is one thing that makes me stop using Evernote for note taking every time I try: writing notes doesn't work well. For a long time I thought it was me (I prefer non-wysiwyg editors) but then I realized that Evernote misses a the concept of semantic markup. That is, instead of actually considering a heading a heading Evernote just applies some styling information to it. So if I send a HTML note to Evernote that contains headers, Evernotes converts those headers to "bold, slightly larger text" as soon as I start editing it. And from within Evernote there is no concept of headers at all, which means that trying to style text is a multi-step task ... and then trying to keep things consistent is difficult, especially when different clients seem to generate different results for the same actions. I've found that Alternote is a huge improvement for writing notes, it's way faster to write text with headlines, bullet lists, etc. Not to mention that it's a much nicer writing environment. My suggestions for improving Evernote would be 1. Introduce semantic markup, let a header be a header, etc 2. This is what I really would like to see: introduce an option that would allow those who so desire to write their notes in plain text, preferable using Markdown, and keep these notes as is (including tabs, whitespace, etc) and then have rendered view that displays the formatted version. Examples of apps that do it this way are DayOne and DevonThink,
  4. From the release notes 7) Removed inline markdown-inspired formatting. this was based on user feedback on b1
  5. Here is one thing with the editor that is driving me crazy. This note is generated by a script on my iPhone that pulls out stuff from my calendar, formatted as markdown and then converts it to HTML before sending it to Evernote. The "bold stuff" is h-tags. This is what happens when I try to edit it Evernote (if I edit it on the web client different things happens): https://goo.gl/photos/VHdsTE5gXhUjcRJf6 Every time I try to actually use Evernote for writing notes, instead of just capture web pages, storing photos/screenshots/PDFs etc something like this happens and I go back to my non-Evernote solution. In my opinion the choice of using HTML for storing notes isn't the best solution, it becomes too much of a hassle to keep formatting similar (since there are no styles) and editing HTML is ... should we say sub-optimal. While I understand that I'm probably in a very small group of Evernote users and that most users are satisfied with the current solution, I think that having a non-WYSIWYG method of writing notes would be a huge improvement to Evernote. If I could wish it would be a editing view and a display view where the editing view would accept Markdown. Having this as an alternative to the current implementation would be a huge improvement ... at least to me
  6. I think that the editor teams idea of how it shouldn't work didn't agree with how most users thought it should work, and they decided to roll back and ... I hope ... make a different implementation that is more in line with what many users expect.
  7. FWIW - doing a dual-mode interface would be "attractive" to me personal - but I do realize that I'm not the typical Evernote user so ... Currently I'm keeping my personal notes as markdown files and handle syncing/backup using dropbox/git but it would be nice to be able to keep the notes in Evernote.
  8. Another bug with b2 is that typing four dashes sometimes gives a horisontal rule, sometimes two em-dashes
  9. This looks a bit strange, when I select a notebook from the sidebar "Notes" gets highlighted, not the current notebook ... very confusing This is with b2
  10. Here is another interesting "feature". I have a Workflow script on my iPhone that generates some Markdown and then it translates this to HTML and sends it to Evernote. This works just fine but editing of the note have different behaviors on the web and in the Mac app. If I look at the source of the note on the web the last two lines of the notes are two headers (which is exactly what is expected), like this <h2>First header<h2> <h3>Second header</h2> If I now place the cursor at the end of the note and press return and type "Hello world" the resulting HTML is <h2>First header</h2> <h3>Second header</h3> <div>Hello world</div> (shouldn't that be a p-tag???). If I create a new note and do the exactly same thing in the Mac app then I get <h2>First header</h2><div> <br></div><div style="font-weight: bold; font-size: 16px;" data-mce-style="font-weight: bold; font-size: 16px;">Second header</div><div style="font-weight: bold; font-size: 16px;" data-mce-style="font-weight: bold; font-size: 16px;">Hello world</div> In other words I get an empty line between the two headers, the second header is changed to a div element and the text now gets some messy formattning. I see several problems here, first the use of div elements instead of what to me looks like a typical p-tag (both web and mac), the insertion of an empty line, the change of a header element to a div tag and finally the unnecessary styling. If I forget about the changes in HTML my user experience is that I get different results depending on where I edit the note!! I do understand that editing of HTML is messy (and it's why I prefer Markdown and rendering when necessary) but not the different results.
  11. For what it's worth, I've been testing this for about 10 minutes and my impressions so far: I like that you're considering supporting Markdown formatting but I think that the current implementation could be more useful. Typing **bold** is actually more "complicated" than hitting 'command-B'bold'command-B' so I don't see any improvement there. Same for the other commands (except tables)The above would have made sense if I could get the markdown formatted text by copying the text (preferable I would be able to toggle between the views like for example DevonThink or DayOne) but right now it doesn't really make sense to me.The table commands could be an improvement but I rarely use tables so I'm leaving this open for others to comment on.If I copy markdown formatted text into Evernote nothing happens, so here I don't get any change at all.I'm writing most of my stuff in Markdown, I almost never use a word processor for writing things, and when I'm not using Markdown I'm using LaTeX. So one of my biggest irritations with Evernote is the use of WYSIWYG, I would like to be able to store raw text - most often source code or markdown - evernote. Right now I avoid using Evernote for these type of notes (which probably explain the low number of notes in my account) and mostly store web clippings and photos of documents. I don't know if it's a good solution but an option for a "dual mode" view of notes would be very useful for me. With this I mean that I can edit/write files using markdown and the text files are stored as is (including tabs/spaces) and a "view" option that displays the rendered version of the note (see DayOne and DevonThink). This would also make the new editing features much more useful. The second thing I want to bring up is something more difficult to describe, using the note editor in Evernote doesn't feel as solid/relaxing/calming as I would like (yes, I said it was difficult to describe). The editing experience is way more solid/relaxing/calming when I use Alternote to write things (which have the same kind of formatting that the new editor uses).
  12. > I don't see how Markdown and plain text are equivalent. Sure, Markup is done using plain text (so is HTML), but that's not what it represents. You don't get Markdown automatically if you have plain text (ask my text editor). It has to be interpreted. You can store Markdown and HTML in a note already. Is that what's wanted? I don't think so This is mixing two things again, storing markdown is the same as storing text which is the same as storing the current HTML content. Like I said above this shouldn't be a problem (you can do it now). The other thing is how, as I said above, to displaying it. Here you have to differ between three different markups: Plain text - already possibleHTML - already possibleMarkdownIt's the last one where I'm a bit different from many others who ask for Markdown support. I have no need for built-in rendering of markdown I'm fine with a plain text display of markdown notes. I just want an efficient way of working with plain text files in Evernote (so in reality I don't need any special markdown support at all). From my experience with other programs (for example VoodooPad, Devonthink), the most efficient way of working with an external editor is to use the ODB Editor protocol (on the Mac). > ENML Format: XHTML subset, with augmentation. See http://dev.evernote.com/doc/articles/enml.php. > More than one note can be stored per file (easy enough to do, at least in the Windows client, and probably the Mac. Select some notes and export them -- they'll come out as one file. Yes, it looks like then the separate notes are stored as XML notes "within" the multinote file ... interesting. > I believe it's a practical decision, based on technical reasons. See, e.g., post #5 in this topic: http://discussion.evernote.com/topic/33759-markdown-wysiwyg-support-plz/?p=40681, post #14 http://discussion.evernote.com/topic/33759-markdown-wysiwyg-support-plz/?p=64718 and so on. They can't provide a full editing experience with Markdown, so it's unlikely to happen. That could change, I do understand. That I understand and I'm OK with that (others might not like it), as I said above, I just want to use Evernote as a "storage database" for text. Of course, this can be done by any text editor by implementing support for Evernotes API - which is unlikely to happen. However, on the Mac many text editors support the ODB Editor protocol which would mean that if Evernote implemented support for it, these editors would all get the ability to work efficiently with text files (= click a button in Evernote to edit with external editor, when I save in my text editor Evernote sees the changes and updates the note). As for iOS, the text editor would have to implement support for the Evernote API. I'm pretty sure that we will never see support for the ODB Editor protocol for reasons given in a previous post. Some iOS editor might implement support for using Evernote as the storage backend (there are a couple of note takers but I haven't seen a text editor). I haven't seen a Mac text editor that uses the Evernote API (does one exist?). In short, I'll probably never see what I'm looking for ... but I can dream
  13. I think there is a mix up here between two things: The functionality of using markdown (or plain text file - if we get one we get the other) The format used to store the notesAs I see it these are to a large degree independent. I'm looking for better support for (1) - being able to use my favorite text editor to write markdown code and marked for generating HTML/PDF/LaTeX when needed. For that I think that ODB Editor support is the best way to go on the Mac. (2) is something else and probably only of interest to developers of programs that uses the API. But I opened an enml file and took a quick look (no I didn't read the docs ) and from what I can see it's an XML file ... which means that it just a matter of defining what you want to store and create a definition of how it should look like. To me it looks like Evernote stores one note per enml file with one content node per file. The content seem to be a note node with some attributes and then HTML code in the text node. So storing plain text here shouldn't be a problem (displaying it is another thing). My personal opinion here is that Evernote has to be careful in designing their programs, they can't make the clients too confusing and should probably focus on the core features and only add new features when they are really needed. And even if we think that markdown is an essential features (I think so) we might only be 0.01% of the Evernote users ... which would make a stupid design decision to include markdown support since it would probably confuse at least 95% of the others who use Evernote making it a bad product for them. On the other hand if 30% or so of the users asked for markdown support we would probably see markdown support real soon. So I'm pretty sure that it isn't a technical issue that has prevented us from seeing markdown support in Evernote, but a design decision - which might change over time.
  14. Yep, I'm a very modest person So what I would like to see is builtin support for ODB (makes the workflow for editing text soooo much better) - something that needs to implemented by Evernote. But the "markdown" iOS editor could be implemented by someone else ... perhaps one already exists?
  15. Count me in as one who want Markdown support in Evernote. It might be that I'm even satisfied with a simpler solution than most of you. I would like to use Evernote as the backend for keeping notes written in (multi)markdown - I want to use Marked to format in the cases when I want HTML/PDF etc. But mostly I just want Evernote to store the raw markdown which I then can read/edit in some application. In other words I would like Evernote to support the ODB Editor Suite on the Mac (I have no idea how this works on Windows). I also would like to have a good text editor on iOS - Byword can publish to Evernote but is there some app that uses Evernote as the note database?
×
×
  • Create New...