On Thursday 01 March 2007 16:52, Alex Chapman wrote:
> >
> > tetris-piece => tetris.piece
> >
> > And the file would be:
> >
> > libs/tetris/piece/piece.factor
>
> I don't like this -- I just want one directory with all my .factor files,
> not one directory per file. Maybe this just means I should only have used
> one vocab.
I'm glad you spoke up about this. It's something not to like and at first I
didn't like it either. Moreover, when I was thinking about different mapping
schemes and imagining what they would be like to actually use, I ruled this
mapping scheme out as ridiculous! Like you said, I though "one directory per
file" was silly and "all my files in one directory" was desired.
With that said...
It's the best mapping scheme I've found. When I moved from imagining what it
would be like to actually using it, it didn't seem bad at all. It ends up not
being one file per directory but one vocabulary, it's documentation, and
tests per directory. These days, you see this in a directory:
a.factor
a.facts
b.factor
b.facts
c.factor
c.facts
Now you would see this:
a/
b/
c/
When I started browsing through my filesystem looking at my vocabs using this
scheme, that visual difference immediately hit me; it means directories are
vocabularies.
apps/tetris would contain this:
board/
colours/
gadget/
gl/
piece/
tetromino/
tetris.factor
And each of those directories would correspond to these vocabularies:
tetris.board
tetris.colours
tetris.gadget
tetris.gl
tetris.piece
tetris.tetromino
tetris
Ed
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Factor-talk mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/factor-talk
