The heirarchy is quite often used as a tree of directory; on your own
machine in your Workspace directory, for example. Seems to me that
"sdcard:com/mycompany/myprogram" is a pretty good (and pretty obvious)
way of avoiding confusion and duplication.

On May 29, 11:20 am, lbcoder <[email protected]> wrote:
> sdcard isn't java, its a filesystem. And the java package standard
> doesn't guarantee anything... just look how many packages there are
> with (incorrectly) "com.android". Besides, it would still get real
> ugly fast if everybody followed those standards -- you'd have an
> sdcard root full of junk thats hard to identify. Its nice to use a
> controlled heirarchy, i.e. /sdcard/data/games/game1, /sdcard/data/
> games/game2, /sdcard/media/music/album1, /sdcard/media/video/comedy.
> When properly organized, its very easy to navigate directly to the
> data you want without needing complex and slow searches.
>
> I know that its adding a little bit, but its not that much to add --
> just keep track of the chosen path somewhere within your /data/data/
> whatever area.
>
> On May 29, 12:49 pm, Sundog <[email protected]> wrote:
>
>
>
> > On May 29, 10:37 am, lbcoder <[email protected]> wrote:
>
> > > But PLEASE, make the path user configurable (you can put in a default
> > > if you like). Without this option, there can be file name conflicts
> > > and there will definitely be a mess, even if you think that your path/
> > > filename makes great sense in terms of organization.
>
> > How about simply following the Java package standard? Guaranteed no
> > namespace confusion.- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Android Discuss" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/android-discuss?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to