I can see nowhere a UI where I could enter a free text email.
I can only search and select from the existing users.

Sebastian


2013/7/21 Maxim Solodovnik <[email protected]>

> Hello Sebastian,
>
> Currently there is only 1 button: "Add attendee".
> If attendee added is OM user (and not of type CONTACT) the attendee
> appended is internal.
> If attendee added was selected and of type CONTACT or email address was
> entered missing in the list of the internal users and contacts, the new
> user of type CONTACT is created ant this will be external attendee.
>
> this was an idea and Vasiliy has commited this code on Friday.
>
>
>
> On Sun, Jul 21, 2013 at 7:26 AM, [email protected] <
> [email protected]> wrote:
>
> > Hi Maxim,
> >
> > "Calendar UI add external attendee'sNo possibility currently to add
> > external
> > attendees. You first need to create that user as OpenMeetings user,
> before
> > you can incite them to a meetings"
> >
> > There is a button in the PopUp where you can add internal members, but
> > nothing happens if you click on it.
> > I would also rather put the plus icon directly next to the existing one
> for
> > the internal users. It does not seem to make logical sense to have yet
> > another popup in the popup for external users.
> >
> > Sebastian
> >
> >
> >
> > 2013/7/21 Maxim Solodovnik <[email protected]>
> >
> > > I'll try to add additional items with missing functionality (on Monday)
> > >
> > >
> > > On Sat, Jul 20, 2013 at 9:37 PM, Maxim Solodovnik <
> [email protected]
> > > >wrote:
> > >
> > > > I believe this one:
> > > >
> > > >  Calendar UI add external attendee's No possibility currently to add
> > > > external attendees. You first need to create that user as
> OpenMeetings
> > > > user, before you can incite them to a meetings
> > > >
> > > > is already implemented. In case email address is entered User of type
> > > > Contact is being created automatically.
> > > >
> > > >
> > > > On Sat, Jul 20, 2013 at 8:04 AM, [email protected] <
> > > > [email protected]> wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> there is some common shared opinion (at least from my point of view)
> > > about
> > > >> the 3.0.0 release.
> > > >> The consens was so far: OpenMeetings 3.0.0 will deliver all features
> > of
> > > >> OpenMeetings 2.x in HTML5, except of the conference room itself.
> > > >>
> > > >> We made some very good progress (congrats!!!) and we can now start
> to
> > > >> really go through every feature to see what is missing or is a
> > > *must-have*
> > > >> to get a production ready release.
> > > >>
> > > >> So I would like to discuss, priortize and define further the scope
> of
> > > the
> > > >> version 3.0.0 release.
> > > >>
> > > >> I started a document at:
> > > >>
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/OPENMEETINGS/List+of+Missing+Features+OpenMeetings+3.x
> > > >>
> > > >> Please carefully read the subject lines of that wiki document. I
> will
> > > try
> > > >> to keep a Google Document in sync with it as a backup. However I
> hope
> > we
> > > >> are an educated crowd that does not need that :)
> > > >>
> > > >> Please add your own ones in the list.
> > > >> The plan would be to convert this list to a Jira item for every
> line,
> > > >> anybody can pick up any item and start working on it.
> > > >>
> > > >> Happy to hear your input on that.
> > > >>
> > > >> Thanks
> > > >> Sebastian
> > > >>
> > > >> --
> > > >> Sebastian Wagner
> > > >> https://twitter.com/#!/dead_lock
> > > >> http://www.webbase-design.de
> > > >> http://www.wagner-sebastian.com
> > > >> [email protected]
> > > >>
> > > >
> > > >
> > > >
> > > > --
> > > > WBR
> > > > Maxim aka solomax
> > > >
> > >
> > >
> > >
> > > --
> > > WBR
> > > Maxim aka solomax
> > >
> >
> >
> >
> > --
> > Sebastian Wagner
> > https://twitter.com/#!/dead_lock
> > http://www.webbase-design.de
> > http://www.wagner-sebastian.com
> > [email protected]
> >
>
>
>
> --
> WBR
> Maxim aka solomax
>



-- 
Sebastian Wagner
https://twitter.com/#!/dead_lock
http://www.webbase-design.de
http://www.wagner-sebastian.com
[email protected]

Reply via email to