Hi Stephane, all,
Hope you are having a great day.

> Right, that will be useful to associate shapes (and points as well?) to
> each level.
>

Yes, points are also available within the shape editor.

That could work indeed, but won't it be a bit cumbersome if a user has many
> shapes at a given level? We could also introduce a Level class and let the
> user associate a shape with a specific level, what do you think?


Sounds great but would that not become a two way process for the user?
The user will have to first create a level and then add all the levels into
an indoor structure. While he can do the same inside a single class.
Another option we can opt is to have a custom structure like custom
classes. (Which I think is more flexible to our needs)
Something like:
---------
-1:Maps.Shapes.Shape1
-1:Maps.Shapes.Shape2
0:Maps.Shapes.Shape3
1:Maps.Shapes.Shape4
1:Maps.Shapes.Shape5
---------


>  Great. What specific options do you have in mind for indoor?


Fairly simple ones like visually defining popup content and style for each
shape separately similar to the uMap editor.
Something like: https://up1.xwikisas.com/#eQ9Mck57dv0U0A7kpAvumQ
If there are any suggestions you think should be available as options, let
me know.

Peace,
Fawad


On Wed, Aug 21, 2019 at 1:49 PM Stéphane Laurière <slauri...@xwiki.com>
wrote:

> Hi Fawad, Hi all,
>
> > Hi all,
> >
> > After much analyzing I have found a good workflow for creating indoor
> maps.
> > What I have in mind is that we treat indoor structures as map items
> rather than a completely separate map.
>
> This sounds like a good approach indeed imho.
>
> > The levels can be specified along with the shapes to be used for each
> level. Each shape will be created separately using the ShapeSheet.
>
> Right, that will be useful to associate shapes (and points as well?) to
> each level.
>
> > We can have a static list for indoor levels and another one for shapes.
> The shapes will be selected in order of the levels defined.
> > For example,
> > *Shapes List:* Shape1|Shape2}Shape3
> > *Levels List:* -1|0|1
> > In this case, level 0 will be mapped to Shape2.
>
> That could work indeed, but won't it be a bit cumbersome if a user has
> many shapes at a given level? We could also introduce a Level class and let
> the user associate a shape with a specific level, what do you think?
>
> > I am working on separately defining options for each shape so they can
> be better used with indoor structures.
>
> Great. What specific options do you have in mind for indoor?
>
> Cheers
>
> Stéphane
>
>
>
> > What do you think?
> >
> > Best,
> > Fawad
>
>

Reply via email to