[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [rap-dev] Contributions Policy
|
Hi,
how about having a folder for each type/category of component like so:
incubator
timeline
o.e.r.timeline.simile
o.e.r.timeline.google
...
visualization
o.e.r.vis.google
o.e.r.vis.jit
...
Any comments?
BTW does it make sense to "hide" the different implementations behind a
common API? For example there is one timeline-widget and whether the
timline.google- or timeline.simile-implementation is used is
"configured" at runtime or decided otherwise.
But that's probably an entirely differnet topic...
Regards,
Rüdiger
On 29.01.2010 19:44, Austin Riddle wrote:
Hello,
What Rüdiger suggests sounds good. I like having the components in
folders, but I am unsure as to what the folders should be named. I
envision that there will be various providers of the same types of
components, so we would need to keep some bundle naming conventions that
indicate the category and provider of a component.
For instance we might have several providers of timeline widgets:
o.e.timeline.simile
and
o.e.timeline.google
and
o.e.timeline.dipity
And for visualizations or visual analytics we might have:
o.e.visualization.google
and
o.e.visualization.jit
And for maps we might have:
o.e.map.google
and
o.e.map.openlayers
And worse:
o.e.charts.emprise
and
o.e.charts.flot
Any ideas?
Rüdiger said:
I am asking myself how to structure the incubator code repository. My
current thinking is to have a separate folder for each "component"
like so:
incubaor
spreadsheet
o.e.spreadsheet
o.e.spreadsheet.tests
...
infovis
o.e.infovis
...
themeeditor
o.e.themeeditor
o.e.themeeditor.tests
Any thoughts on this?
