


I wonder if it would be useful or even practical to combine the typical heirarchical system with the labeling system somehow? Or have both options available in the same program? Does anyone think that's even possible, without causing mass confusion, or a breakdown of the organizational system?
I certainly don't expect mass confusion. Some folks will use tags, others the tree, and some both.


i was certainly impressed with surfulater but after some use i do miss features that i would have thought basic requirements.



Hi nevf, I hope I didn't offend you with any of my comments...
Let me ask a couple of questions:
1) Could you provide a more detailed description of what Surfulator is specifically designed for? It would help us sort out it's role among all these information collection programs.
...
Let's assume Surfulater is the best way to capture information from the web. Unless Surfulater is ALSO not one of the best notetaking programs, then where are we going to store and organize the information? Are we going to use Surfulater to capture the information, but then port it somehow to another program that is a more powerful notetaking application or organizer? I don't think so, that would be very frustrating. Anyway, I'll have more thoughts on this later.
I like where this discussion is going... because I too am in favor of the note-side of things! Real quick note: Keynote did have capturing capability. It was a fledgling start but compared to many other apps of it's time it was special.
But, I have to jump back on my soapbox, sorry! Note programs need to be able to store and relate information... this ought to be the primary function. I should be able to build very rigid structures (a la Keynote) but I should also be able to build weak relationships and strengthen them over time. And now, before I go off on a wild-eyed tangential dream (and repeat myself!)... I go.
Kevin
Here's what I propose: the categories or labels can be structured in the tree/heirarchy format, but the individual notes can be placed in multiple branches of that tree. Maybe Gmail can do this also...confirmation BrotherS?Google Mail does show the labels in a alphabetical order, and you can label every email with as many labels as you like - I don't label some at all, many get one label, and then some get two or three labels.



... It would be extremely powerful to be able to build relationships instead of just a simple heirarchy. I think the fundamental difference here is that a note won't be restricted to one location, but can be shared between several categories. Like a note about Screenshot Captor can be under the categories of "Windows Utilities" and "Graphics Utilities", but the note itself is a single note, not copied in two places. That is powerful indeed.
So I guess we want our cake and eat it, too! We want to be able to have the traditional heirarchy, but we also want the notes to be governed by relationships. Here's what I propose: the categories or labels can be structured in the tree/heirarchy format, but the individual notes can be placed in multiple branches of that tree. Again, I think Evernote is a living example of this right now, if you want to try it out.
"PS I wasn't aware of Keynote's capturing abilities!"
Sorry if I misunderstand your sentence here, but I'm interpreting it as you want to know more. (?) If you already know or have since found out, please disregard this post!
If you go into the Keynote options, there is a whole panel for clipboard capture. Basically Keynote watches the clipboard and captures the clip as it comes in. There are some format modifying that can be done, and then the clip is sent straight to the active Tab in a new note. My main problem is that the new node cannot be named on the fly. Even if a dialog box popped up that you could type the name in would make it more useful in my opinion.
Kevin
Surfulater works this way. There is only ever one physical instance of a 'note', but it can be in as many tree folders as you want.
Surfulater also lets you link related 'notes' together so you build a web of related information. This is very useful.
I don't see a tight connection between the hierarchical tree and tags (labels, keywords whatever).
Tags are separate organizational method which can be used in a variety of ways. For example you get a list of all tags and selecting one shows all notes which include that tag. Tags could also be used in conjunction with filtered tree views. In this mode the tree would only include notes that included a certain tag or tags. With a good implementation of tags some folks might not even use the tree.
Time to go get some sleep.
I mostly agree with you... except I think that trees should still be an option. If you're trying to write a book or write an outline you want only certain nodes in a certain order. The final implentation should allow both. You should be able to throw things in, but then "hard assign" them as needed (they would still be in the database pool for other groupings, but that one group would always contain it).
Kevin









Original address: https://www.donationcoder.com/forum/index.php?topic=2362.0