How do you use your Notecase?
malarky101
I'm new to this group, having just got myself a copy of Notecase Pro
having migrated from Tuxcards. I'm basically learning how to use the
program at the moment...much trial and error. Having looked through
some of the posts I've already discovered how to turn my Notecase Pro
into a diary/journal. At the moment, I'm using mine as a general
notes repository and as a note taking application as I plod through a
unix tutorial. At the moment I think there must be many different ways
of using the program. I suppose it can be used for anything that uses
an index of any sort. Ideas, hints and tips, anyone?
Pete
Miro
speaking of myself, I tend to put all important things in a Notecase
document.
Basically, this includes my passwords, lists of websites and their
login info,
my HOWTOs (linux etc), my personal plans, lists of my friends
birthdays, ...
In the future I hope to integrate GStreamer library into Notecase to
be able to
listen/create audio notes from within the program.
Regards,
Miroslav
Anna Sheridan
I bought it initially (after experimenting with the free version)
because I was looking for Linux equivalent of KeyNote. I was looking
for an outlining software that would be free of somebody else's ideas
and imposing customisations (ie when they try to guess what you might
want). My primary usage is fiction writing, novellas and longer books.
I've explored many programs 'for writers' and found that, because they
try to offer too much, it turns to be not enough :-). I wanted
something that I could mould into anything I want.
In November I've completed the first draft of a new novel with
NaNoWriMo (www.nanowrimo.org) using NoteCase Pro on my Asus EEE 901.
I've found it to be perfect tool, offering structure for chapters and
scenes, yet flexible enough to merge and divide on the go. One file to
hold my book, another for locations, character notes, anything else I
might need. With several files opened at the same time, and loading
automatically, with multiple backups and autosave, and not too many
distractions, it was just what I needed.
Since then I've started using NoteCase for about anything, from diary
to drafts of longer e-mails, letters, minutes of RSPCA meetings,
collections of snippets from the Internet. I like its look, not as
cluttered as some word processors, yet more elegant than KeyNote. It
works very well on EEE's small screen, because it's so easy to turn it
into a full screen editor.
Anna
dher...@googlemail.com
not to forget its great platform independency!
My Notecase files are all encrypted and reside on a Sandisk "SD plus
USB" card, these ultra-convenient SD cards which turn into a USB
memory stick with one "click". I have this card in a small compartment
on my keychain.
See here for pics:
http://images.google.de/images?um=1&hl=de&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&q=sandisk+%22sd+plus+usb%22&btnG=Bilder-Suche
I run Notecase on all of my computers:
- A Macbook (Mac OS Leopard), which runs at home as my main computer
and which I take on longer travels
- An ASUS eeePC 901 with Windows XP or sometimes Linux, which I take
on shorter travels, to seminars and other meetings, or other occasions
where the Macbook would be too heavy and overkill
- Sometimes an ASUS EeePC 701 (Xandros Linux)
- A Sharp Zaurus PDA (weeXpc / Linux), which I can take everywhere in
my pocket, because it is so small (See www.hermocom.com/en/services/weexpc
)
- And I have the Windows portable version of Notecase on the SD card
as well, so when I don't have a computer with me, I can use Notecase
and my files in every Windows computer I have access to.
So I can really always and everywhere work on my Notecase files. This
flexibility can only be achieved by plain text files normally (MS
Office files can also be used on all these platforms, but not that
conveniently and always with some compatibility issues, at least on
Linux).
I use Notecase for almost all kind of textual information:
Diaries, todo lists (task management features), project and workshop
planning, meeting records (with HTML export you can greatly distribute
the records afterwards), website authoring (the HTML export and HTML
web export feature allows easy creation of entire HTML webs with one
keypress), etc etc.
Notecase is one of the very few tools which serve so many needs at
once WITHOUT being bloated and huge and slow.
It has become my main productivity tool.
daniel
marbux
and writing. I very much want NC Pro to be a success because it is
easily the most useful new app I have encountered in more than a
decade. My major uses include:
1. Managing a very large collection of Notes 'n Quotes begun years ago
using a different outliner, relating to technical, political, and
legal aspects of software interoperability (currently about 1.6 MB)
as well as other similar documents on other topics;
2. My primary editor for generating HTML content for articles on my
Drupal web site and for commenting on articles on other web sites that
allow use of HTML markup;
3. My primary editor for generating initial drafts of lengthy
OpenOffice.org word processing documents.
Major advantages for the above purposes:
Common to all of those uses, NC Pro generates a clean minimalist HTML
upon export to HTML as well as a hyperlinked table of contents. To my
knowledge (after considerable investigation), KnowIt and NoteCase are
the only outliners that produce a minimalist hyperlinked HTML table of
contents. There are other outliners that produce hyplinked tables of
contents, but all I found do so in a form unusable in other editors,
e.g., gussied up with Javascript, CSS, and icons. NC Pro can do that
too (the framed HTML export), but for interoperability with other rich
text editors one needs minimalist HTML.
Topic specific advantages:
1. Managing Research Notes 'n Quotes:
NC Pro is fairly unique in allowing not only hierarchical organization
of nodes, but also provides several means for escaping the bounds of a
strict hierarchical organization. Such information tends toward
defying strict classification. E.g., one node may may really belong
under multiple classifications. As another example, the original
system of hierarchical classification may become largely irrelevant in
the blink of an eye if one is drafting a new document with a different
slant. So the following additional features become important:
a. Find: NC Pro has a quite powerful Find feature, allowing searching
not only for strings but also patterns (the PCRE regular expression
engine). One may not only traipse through the document reviewing each
occurrence of a character string or pattern, but instead fill the
search result to a list of all found nodes and their content, and do
so repeatedly very easily using the save query tool. Major drawback
here: no method yet to run either a Find or Replace operation across
multiple files, so have to repeat one file at a time.
b. Node Clones: The node cloning feature is major step forward.
Multiple clones of a single node can be maintained under multiple
branches whilst maintaining the ability to edit the original and all
clones from any one of them (single editing point for recurring data).
There are still some kinks to work out in this new feature, such as
losing node clone content when exporting to HTML (haven't checked
build 2.5.9 on this yet). But I've already found the node clone
feature very useful for content that belongs under multiple branches.
c. Node Tags: If you have not yet discovered the Node Properties
dialog, be sure to check it out soon. It's in the Tree menu. From
there you can manipulate node properties including tagging a node with
one or more keywords. That might seem like much until you more closely
inspect the Find dialog. There, searches can be limited to nodes
containing the keyword(s) you want. And the results of the query can
be filled to a list to display the content of all nodes that contain
that keyword or keyword combination.
So this is yet another way of escaping the bounds of strict
hierarchical organization. Combined with the ability to save queries
in the Find dialog and consistent use of a well designed ontology,
such queries will produce not only the information it did the last
time you ran the query, but any new nodes you have created in the
meantime that share the same keywords.
As Miro gets farther along with exporting methods for Lua scripting,
the tagging feature will become far more useful. E.g., one script I'm
aiming toward is one that will automatically create a set of
hyperlinks at the end of each node to all other nodes in the same
document that share any of that node's keywords. This would sidestep
the need to run a query to navigate to the related nodes. More
importantly, the hyperlinks would survive export to HTML, allowing
creation of large web documents chock full of cross-referencing
hyperlinks.
2. Editing Content for Web Pages:
Because NC Pro's can export a minimalist HTML, it is an excellent rich
text editor for any web-based content management system that enables
direct editing of content using HTML markup, although on some CMS you
must change the settings to allow particular markup tags, such as
definition list markup. Very few web apps perform autosaving of
content so there is always a risk that data entered directly in a web
app can disappear before being saved, due to power failures, browser
crashes, accidentally closed browser tabs, etc.
To boot, I'm not a fan of content management systems that create a
nested and hyperlinked table of contents by requiring a different
heading style to be used for each level of nesting. You wind up with
headings that are both ridiculously large and small. One of the NC Pro
HTML export options allows you to produce a hyperlinked table of
contents without applying heading styles.
I've also found that with minimal post-export processing, I can still
add HTML markup that is not yet supported by NC Pro plus custom HTML
markup required by my Drupal installation, e.g., markup for HTML
blockquotes. It's a simple matter of using unique strings within NC
Pro, e.g., "blockquote" and "/blockquote", and then running a replace
operation post-export using a text editor to convert the strings to
the proper markup. With the custom markup features coming in NC Pro,
this will become even easier, with conversion being handled by an NC
Pro export script.
3. Creating Draft Word Processing Documents:
The NC Pro vanilla HTML export makes it fairly easy to import NC Pro
documents into at least three word processors without data loss: [i]
OpenOffice.org; [ii] Google Docs; and [iii] Zoho Writer.
If one exports to HTML using the "simple HTML with <H1...H6> headings
option, in each of the above apps headings will be imported using
heading styles. From there, a variety of table of contents styles can
be applied, e.g., with different numbering schemes. Or if numbering is
not desired, use the export options for a simple table of contents
without using the <H1 ... H6> option.
There is also an option in NC Pro under Tools > Configure Note Case
Pro > Export to apply numbering to nodes when exporting to HTML. In
the three word processors listed above, that numbering will be picked
up when generating the table of contents.
NC Pro's vanilla HTML export will import directly into Zoho Writer and
Google Docs. There are a couple of extra steps necessary to get the
HTML into the main OOWriter app in non-HTML editor mode.
-- Open the HTML document in OOWriter;
-- Use File > Publish to publish the document to ODT format.
-- Close the HTML file and open the ODT version.
The document can now be polished in OOWriter or saved/exported to any
of the multitude of file formats supported by OOWriter. A smaller
number of export formats are supported by Zoho Writer and Google Docs.
But between ODT, RTF, and Doc, you should be able to then open the
document in virtually any word processor on the market. I'm a
WordPerfect power user from way back, so I tend to use OOWriter just
to get NC Pro documents into RTF or DOC, then open them in
WordPerfect.
The major disadvantage of using NC Pro to create draft documents is
missing features, such as footnotes and tables. With footnotes, I
store them inline in the paragraphs at the point where I want the
footnote linked from, set off with greater than and lesser than
symbols, e.g., "<<footnote text>>. Once in WordPerfect, I run a script
written by a friend that converts such text to footnotes.
<http://wptoolbox.com/library/ConvertR.html>. With tables, I create
them in WordPerfect and merge them with the NC Pro document after
getting the document into WordPerfect.
But for me, advantages of producing the first draft of lengthy
documents in NC Pro outweigh the disadvantages. With nearly all my
research notes in NC Pro, I like to be able to create my draft using
the same app that my notes are stored in.
Moreover, I really like working in a dual pane outliner during the
assembly phase of a document's development. WordPerfect has strong
outliner features, but it folds nodes rather than managing them in a
tree structure. I seem to think better using a tree structure,
beginning from an unordered laundry list of topics to cover in the
document assembled in a single node, then using the NC Pro Node
Splitting feature to break the list into separate nodes, rearranging
them into a sensible order under a major writing outline that uses
complete sentences for headings,
Because I tend to write repeatedly about different facets of the same
subject, recycling quotes, citations, and content is a real work
saver. I used to rely extensively on desktop search to retrieve such
information. The outliner I used previously really was not very good
for organizing the notes. E.g., there was no way to copy or import one
outline into another.
My productivity has soared since I got my notes 'n quotes far better
organized in NC Pro.
Best regards,
Paul
--
Universal Interoperability Council
<http:www.universal-interop-council.org>
gbuergisser
I started using Notecase (not Pro) after I replaced my Palm LiveDrive
with a Nokia N810 Internet Tablet. I needed something to store all the
information I formerly stored in the Palm's Memo application. Notecase
was (and is still) very good for that. Especially because I can use
the same file also on the desktop PC. Some kind of sync, like I had
with the Palm. Because printing entries became a need I upgraded to
Notecase Pro.
I maintain about five Notecase documents. On is a diary, where I have
one node for per day. Another (encrypted) document contains account
data, like URLs and passwords for websites or bank account numbers.
Then I have one document where I organize my job at the office. It
contains nodes for meetings, todos, bits of source code, how-to's etc.
The other documents mainly contain general information which I simply
store there so I will find it when needed.
Regards,
Gregor
Daniel H
HTML export:
Miroslav did a really great job in implementing a lot of features I
have implemented in MM/LX before. MM/LX ("MindMap/LX", see
http://www.dasoft.com/MMLX/index.html ) is a mind mapping software for
Hewlett Packard 200LX palmtops (these old MS-DOS-based palmtops, see
http://www.daniel-hertrich.de/200lx ).
I was one of the developers of MM/LX and implemented large portions of
the HTML export features, especially CSS support, presets etc., so
that one-button generation of nicely formatted HTML documents for
handouts etc was possible.
I am so glad that NoteCase Pro now supports most of these features,
because I don't use the HP palmtop anymore and MM/LX was my main
productivity software. Except of the mindmap presentation of
information, NoteCase can now replace MM/LX entirely and even supports
a lot of new very nice features.
When I abandoned the HP palmtops and switched toward the Sharp Zaurus
platform (http://www.daniel-hertrich.de/zaurus), I was evaluating a
series of Linux outliners and came across NoteCase and Miroslav.
Miroslav was so cooperative and open for new ideas, that we quickly
found ourselves in long discussions about new feature ideas and I
write long (NCD ;-) documents with bug reports and feature requests.
NoteCase became an essential part of my entire computing life, and
now, as I wrote earlier, I use it on all my computers, having my
NoteCase files on my keychain.
So now you know a little more about my background. Sorry for getting
off-topic. :-)
Tagging:
I would like the tags easily to be chosen using the context menu,
instead of going through the properties dialog. Miro, do you think
this will be possible? Maybe for adding new tags (and not selecting
from the existing tags) the dialog must still be opened. But for
selecting, the context menu could have an item "apply tag" which has a
submenu consiting of all available tags. Each selected tag gets a
checkmark...
Find:
The drawback you mention can be overcome if you first combine the
files (using import) to one file and later seperate them again. I am
not sure what is more efficient: Combining and then replacing over the
one result file, or doing the find / replace steps ofer each file
seperately. Probably depends on the amount of find / replace steps you
want to do.
NC as a word processor:
Using NC as a draft tool for later import into a word processor is an
excellent idea I didn't have myself before!
I had a lot of problems with copy and pasting contents to or from
NoteCase in the past, so I put the idea of easy interoperation between
NoceCase with other applications aside for now. But using the HTML
files for content interchange is an excellent idea, thank you!
Have you tried to use the plain NCD files (Which are also HTML with a
lot of comments for holding additional NC-specific parameters) for
import into different applications?
daniel
marbux
>
> I was evaluating a
> series of Linux outliners and came across NoteCase and Miroslav.
> Miroslav was so cooperative and open for new ideas, that we quickly
> found ourselves in long discussions about new feature ideas and I
> write long (NCD ;-) documents with bug reports and feature requests.
> NoteCase became an essential part of my entire computing life,
My experience was very similar. Miro is a precious jewel among the
software developers I've worked with. And other than utilities, I do
nearly all my work now with NC Pro and a web browser.
> and
> now, as I wrote earlier, I use it on all my computers, having my
> NoteCase files on my keychain.
I'm running a system with WinXP running as a virtual guest atop
Kubuntu 8.04, with NC Pro running on each.
> So now you know a little more about my background. Sorry for getting
> off-topic. :-)
Please don't apologize. I'm enjoying getting to know folks on this list.
> Tagging:
> I would like the tags easily to be chosen using the context menu,
> instead of going through the properties dialog. Miro, do you think
> this will be possible? Maybe for adding new tags (and not selecting
> from the existing tags) the dialog must still be opened. But for
> selecting, the context menu could have an item "apply tag" which has a
> submenu consiting of all available tags. Each selected tag gets a
> checkmark...
I like the idea with the caveat that some of my tag ontologies are
large enough that all tags could not be displayed in a single screen.
Perhaps a separate tag dialog that breaks the tag functionality out of
the Node Properties dialog except for a linking button? (Just thinking
out loud here; I suspect that design of a separate tagging dialog
deserves far more discussion and study.)
A work-around in the meantime: I added the Node Properties dialog's
icon to the toolbar as the last item on it. It saves the menu
navigation steps.
I've suggested a few enhancements for tagging. One is to be able to
import and export tag ontologies, which would be stored as HTML <meta>
keywords in the header lines of the NCD and would appear as available
tags in the Node Properties dialog. Likewise, adding a new tag to a
node would be echoed in the <meta> keywords.
The problems to work past here include: [i] use of different tags,
e.g., "interop" and "interoperability," for the same meaning in
different outlines leads to tag clashes when combining portions of
different outlines; [ii] I tend toward spending a fair bit of time
developing ontologies; I'd like to be able to edit them as a TXT file,
1 tag per line in alphanumeric order, that can be imported into a new
outline, etc.
Another tagging enhancement I've suggested is the ability to apply a
tag retroactively to all children of a node. Relationships of multiple
nodes' content is not always clear at the time a branch is begun, when
you can use the templating feature to apply tags to all children.
It might be useful to start a separate thread to discuss tagging needs
and brainstorm solutions. Particularly with Lua scripting and custom
markup coming, I see node tags as playing much more vital and flexible
roles.
> Find:
> The drawback you mention can be overcome if you first combine the
> files (using import) to one file and later seperate them again. I am
> not sure what is more efficient: Combining and then replacing over the
> one result file, or doing the find / replace steps ofer each file
> seperately. Probably depends on the amount of find / replace steps you
> want to do.
Find is not as big a problem because the queries can be stored.
Replace is more problematic. I've suggested some methods to export
from NC Pro for Lua scripting in aid of batch processing multiple
documents. In the meantime, my work-around is much as you describe; I
build rather huge and complex outlines. The major drawback there is
that as complexity increases, hierarchical relationships tend to
become less useful for finding your way back to particular content;
memory begins to fail.
>
> NC as a word processor:
> Using NC as a draft tool for later import into a word processor is an
> excellent idea I didn't have myself before!
> I had a lot of problems with copy and pasting contents to or from
> NoteCase in the past, so I put the idea of easy interoperation between
> NoceCase with other applications aside for now. But using the HTML
> files for content interchange is an excellent idea, thank you!
One of the advantages of this list is that we can learn from each
other. Thank you for your contributions.
> Have you tried to use the plain NCD files (Which are also HTML with a
> lot of comments for holding additional NC-specific parameters) for
> import into different applications?
I haven't. But I have played with two other methods: [i] the
tab-delimited export feature works fairly well for getting content
into some spreadsheets and database apps; [ii] saving as NCDB then
using an SQLite tool to convert to comma-delimited format works
better. I've been using SQLite Database Browser for the purpose,
http://sqlitebrowser.sourceforge.net/. Public domain, lightweight,
runs on Windows, OS X, Linux, Unix, and all POSIX-based operating
systems. Requires no knowledge of SQL to use for simple operations
like converting an NCDB to CSV comma-delimited format. Just rename the
.NCDB as a .DB file, import into the Database Browser. Most commonly,
I select "notes" as the table type to be exported to CSV.
From CSV, I import into DabbleDB, an outstanding online relational
database service that requires no knowledge of SQL.
<http://dabbledb.com/>. From Dabble, I can create different
applications and views of the data, and include the views in external
web sites via an iFrame. I haven't done that last step yet, but am
aiming toward getting my Interop Notes 'n Quotes onto my Drupal site
by that means.
Miro got me started looking in this direction when he pointed out that
.NCDB was just an SQLite 3 database with a custom file extension, that
renaming it was all that was needed to treat is like any other SQLite
database.
Here are some links to some other SQLite resources I gathered:
HowTo -- Convert SQLite 3 to CSV using SQLite,
http://forums.mysql.com/read.php?145,71867,92624#msg-92624.
SQLite Studio, http://sqlitestudio.one.pl/index.rvt?act=about
(Linux/Solaris) (GPLv2) Exports to various formats (SQL statements,
CSV, HTML, XML). Many more features. Runs on Windows 9x/2k/XP/Vista,
Linux, Solaris, OS X support in development. Licensed under GPLv2.
SQLite Administrator, http://sqliteadmin.orbmu2k.de/ Exports to XSL,
CSV, HTML, XML. Many other features. Runs on Win2000, XP, Vista.
Freeware.
SQLite2008 Pro Enterprise Manager, http://osenvistasuite.com/?xp=3
Exports to XSL, CSV, HTML, and XML, has LUA embedded. Runs on WinXP;
not sure about other Windows versions. Freeware.
SQLite ODBC driver, <http://www.ch-werner.de/sqliteodbc/>; see also
<http://www.sqlite.org/cvstrac/wiki?p=SqliteOdbc>. Reportedly, this
driver works with OpenOffice.org to connect SQLite databases to the
app. I haven't played with it yet. Builds available for Windows,
Linux, and OS X. Might work with other apps that support ODBC, e.g.,
the word processor table and spreadsheet apps in MS Office and
WordPerfect Office. FOSS licensing.
Lots of other SQLite management tools,
<http://www.sqlite.org/cvstrac/wiki?p=ManagementTools>. Includes tools
for getting SQLite databases into other apps not listed above.
Returning to the topic of NC Pro as a word processor, I maintain one
outline named "Working." It has only two root level nodes. One is
In-Box, a place to quickly place information I encounter that doesn't
clearly fit into an existing outline's categories. This frees me from
the need to interrupt a project to rethink and rework an existing
outline's structure. Every now and then, I tackle integration of the
new information under that root node with existing outlines.
The second root node is "Article Ideas." It has two children. One is
"Ideas," whilst the other is "In Progress." As an idea for an article
or other writing occurs to me, I quickly take a few notes about the
idea, then return to what I was working on when the light bulb moment
struck.
When I begin fleshing out an idea into a finished work, it moves under
the In Progress branch, acquiring children and content. I usually have
a dozen or so such works in progress simultaneously at different
stages of drafting. (One of the advantages of retirement is that I no
longer face deadlines so I now have the luxury of putting projects on
the shelf for a bit so I can get a fresh look at what's done so far
before doing more work on them.)
Another method of getting an emotionally fresh look when you reach the
mental state where you've lost your way on creating a lengthy piece is
an old word processing trick, switching the content's type face and
size. Reviewing what you've done in a different typeface and size
usually imparts enough of a fresh look to arrive at a more creative
mental state. :-)
Phillip Gramly
i primarily use notecase as an index to my real filing cabinets. so i
have a NC document that lists every file folder i have in my office
filing cabinet, another one that lists all the folders in my home
filing cabinet(s). then within each folder i put a line for each
document in the real file folder. e.g.
article: /article title/ by joe robinson at ABC co.
email: /subject of email/ from jan robinson at XYZ co.
brochure: /name of brochure/
etc.
this allows me to use the Find feature of NC and not have to dig thru
my real folders to find things. and i have been adding content with
cut/paste that is only in the NC document and not in the filing
cabinet.
other uses:
* i work with computers and so i have a section with notes on each
server that i manage.
* notes on computer commands in various contexts (unix, tivoli storage
manager, CMS, etc.)
* class notes from technical conferences, seminars, & classes
* i insert pictures of my family so i can show off my wife and kids
* i'm also implementing GTD productivity principles and use NC as an
electronic version of my tickler file (one file for each day of the
month (1-31) and one for each month (jan-dec)
* just starting to move my notes from Yeah Write over to NC. these are
more personal notes and lists related to books i've read, movies i've
seen, book lists, quotes, diary, journal, recipes, poems, some short
ebooks, etc.
is anyone using NC as an address book? Yeah Write has a nice template
for address book entries - can templates be set up in NC pro?
PrG
malarky
> Quote>
> have a NC document that lists every file folder i have in my office
> filing cabinet, another one that lists all the folders in my home
> filing cabinet(s). then within each folder i put a line for each
I would never have considered this use at all. In the past I have
tried to
reduce the amount of paperwork I kept, particularly at home. I used a
Windows product called Paperport which I liked. Basically, it allowed
you to
scan documents as pdf files and then store them in a hierarchical form
digitally, either on your home computer or server. I'm sure the
program was
capable of so much more but that was all I ever used it for. The
trouble
was that it was time consuming to scan every document that you wanted
to
keep and in effect I ended up keeping the paper copies too! When I
decided
to use linux some years ago one of the reasons I maintained a linux/
windows
dual boot was to use Paperport. However, I can see more merit in your
system. Being a 'belt and braces' man wouldn't it be good if I could
use
NC-Pro in the same way?
Regards to All
Pete
Miro
1. Find
I find the Paul's idea on the option to search within all open
documents very interested.
I've added it into my "to do" list, and hopefully it should be
implemented soon.
2. Tagging
I think that adding a separate place to quickly view/add tags is
reasonable.
I am more along the lines of having a separate dialog (and menu
option), because number of tags can be enormous.
I would be interested if Paul and Daniel (and anyone interested in
this topic) could come with a spall set of requests/specifications
for this feature :)
3. Phillip's question:
templates be set up in NC pro?"
child note of this template note will inherit all the properties of
its parent: note text contents, attachments, ...
To use this is simple:
- create a template note
- create a child note (template instantiation)
- now you can move this new note anywhere within the document (once it
copied the data from its template parent)
Regards,
Miroslav
Anna Sheridan
> In the future I hope to integrate GStreamer library into Notecase to
> be able to
> listen/create audio notes from within the program.
>
from my voice recorder? It would be really cool to have audio file in
a node with a brief annotation what the file is about.
Anna
Miro
> from my voice recorder? It would be really cool to have audio file in
> a node with a brief annotation what the file is about.
> Anna
are strongly advised in that case),
but, in the future, you could play them from within the program
itself.
More that that, you could record new audio files from within the
program too.
Anyway, that's the plan. It might take some time, now I plan to
concentrate on fixing bugs
in the next few releases. So everyone, feel free to report your
"favorite" bug for fixing.
You know my mail :)
Regards,
Miro