|
Importing Firefox' bookmarksFirefox writes your bookmarks to your hard-disk. i2Brain can read them. Each bookmark is made into an item in i2Brain. The name of the bookmark becomes the name of the item, and the URL to which the bookmark points is transferred into the aspect "URL" in i2Brain. After this process has been carried out you merely have to click on an item to call up the website. Use:Activate i2Brain's menu "File | Import Firefox bookmarks": i2Brain can generally carry out the first step automatically. It finds Firefox's file containing the bookmarks. If that fails for any reason, you can search for the file yourself, then change the path and file-name. The file is always called "bookmarks.html". When you have the correct file, proceed to step 2. Here you have the choice as to HOW i2Brain should represent your bookmarks:
Let's take a look at these 3 different possibilities. (Of course, if you want to just try them out one by one to see how your bookmarks look, feel free.) Your bookmarks are probably arranged in various branches and sub-branches: These are in 3 levels, so the tree has a "depth" of 3. Or maybe you have them all directly under "Bookmarks", so your tree has a depth of 1: The dialog shows you the depth of your tree in Step 2. In the example above it is 4.
Keep the tree (simple)This is probably your best bet if you have a depth of 3 or more. i2Brain imports the tree like this: This is what happens when you import the same data using "Headings as values": So each bookmark appears in a column whose name is the name of the branch. BUT information has been lost! There is no longer a connection between "Techie stuff" and "Java stuff" in the i2Brain project. The fact that one was within the other has been "forgotten". So "Headings as values" is probably not your best choice if you have 3 or more levels. Tree with branch names as aspect valuesThis third variant allows you to make full use of the multi-dimensional nature of data in i2Brain. The tree apears just as it does in the 2nd variant, but more aspects are added: The following diagram shows you the effect of using "Keep the tree (simple)": Whereas "Tree with branch names as aspect values" produces this: "Tree with branch names as aspect values" has the advantage that you can use a filter to see all items which belong to, for example, "Techie stuff" AND ALL SUB-BRANCHES by setting a filter to "Level 1 = Techie stuff". "Keep the tree (simple)" produces a project in which the logical link between a branch (e.g. Techie stuff) and an item in one of its sub-branches, is only visible using the arrows. So you would have to follow the arrows yourself or use the "Visual database" rather than a filter. |