musketyr / wavid

Automatically exported from code.google.com/p/wavid
0 stars 0 forks source link

Hierarchy #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Describe what feature you want to have as part of Wave IDE:
There should be defined how to store source in waves in some hierarchy.

If you have idea how should be this feature implemented please describe it:
Blibs allows to have other blibs within. This should work as composite 
pattern having blibs used as directories and/or source files. Wavelet should 
by handled as root directory.

Original issue reported on code.google.com by vladimir.orany on 4 Jun 2009 at 6:04

GoogleCodeExporter commented 9 years ago

Original comment by vladimir.orany on 4 Jun 2009 at 6:25

GoogleCodeExporter commented 9 years ago

Original comment by vladimir.orany on 4 Jun 2009 at 6:26

GoogleCodeExporter commented 9 years ago
Wave can be a workspace, wavelet a project folder, blip a source file and blips
inside of blip could be methods,....

How is the visibility sorted out i.e. can a blip see other blips/wavelets 
content?
Probably not, that's why a robot for passing information between blips might be
needed (for example: info from oher blips is necessary for content assist on
function, fields,...).

Original comment by mitja.be...@gmail.com on 5 Jun 2009 at 7:20