Scratch

I would make two lists:
one for the values, one for the path.
So, to use XML as an example.
If we have the file:

<xml>
   <level1>
      <level2>level2 info1</level2>
      <level2>level2 info2</level2>
      <level2>level2 info3</level2>
      <level2>
         <level3>level3 info</level3>
      </level2>
   </level1>
</xml>

Now, we take this and extract the data:
1) level2 info1
2) level2 info2
3) level2 info3
4) level3 info
And extract the corresponding pathnames, to Xpath:
1) xml/level1/level2[1]/
2) xml/level1/level2[2]/
3) xml/level1/level2[3]/
4) xml/level1/level2[4]/level3/
From this data, we can build the tree:
1) read path 1.
2) create xml node.
3) create level1 node.
4) create level2 node.
5) note that there are more level 2's in this root.
6) add data for path 1.
7) read path 2.
8) note that xml node is already there, and there aren't any copies.
9) note that level1 node is already there, and there aren't any copies.
10) remember that there are copies of level2.
11) read that this is the second level2 in this level1.
12) add data for path 2.
13) continue on similarly.
As you can see, this is just a functional outline... but it should work.

billyedward wrote:

I would make two lists:
one for the values, one for the path.
So, to use XML as an example.
If we have the file:

Code:

<xml>
   <level1>
      <level2>level2 info1</level2>
      <level2>level2 info2</level2>
      <level2>level2 info3</level2>
      <level2>
         <level3>level3 info</level3>
      </level2>
   </level1>
</xml>

Now, we take this and extract the data:
1) level2 info1
2) level2 info2
3) level2 info3
4) level3 info
And extract the corresponding pathnames, to Xpath:
1) xml/level1/level2[1]/
2) xml/level1/level2[2]/
3) xml/level1/level2[3]/
4) xml/level1/level2[4]/level3/
From this data, we can build the tree:
1) read path 1.
2) create xml node.
3) create level1 node.
4) create level2 node.
5) note that there are more level 2's in this root.
6) add data for path 1.
7) read path 2.
8) note that xml node is already there, and there aren't any copies.
9) note that level1 node is already there, and there aren't any copies.
10) remember that there are copies of level2.
11) read that this is the second level2 in this level1.
12) add data for path 2.
13) continue on similarly.
As you can see, this is just a functional outline... but it should work.

O_o XML! BTW you have to put this in an XML file first

<? xml version = "1.0" encoding = "utf-8" ?>

Greatdane wrote:

ThePCKid wrote:

O_o XML! BTW you have to put this in an XML file first

He's giving an example.

I'm not stupid!

AddZero wrote:

cool, thanks for the the thoughtful responses, just noticed, sorry.

I'm working on a new version now.

from the project:
"instead of two lists, just one, each 'file' has a header, starting with how long (how many lines till the next file at that level) that file is, the name, the type. (1 for folder) the creator, the color of the icon. so the header is 5 lines long, if it is a folder type, the user can navigate into that.(adds that folder to the path list) then lists everything inside that folder. I'm still working on that one, should be out soon. "

This will be a 'file manager menu' type front end for projects that store information.
like my lathe 3d modeler and music program. (I'm working on)

I'll try to explain how it works better when I release it.

Nice. Something I've been thinking about for a long time is designing a text-based code- a bit like HTML or C++ within Scratch. You could then implement a file browser into an OS  design to make a fully-working OS... You could even make an installer, to install other projects onto your system!