►
Description
Save Keywords, permanent test connection, new modules and Milestone 2
A
B
C
Okay,
nice,
so
let
me
introduce
maybe
the
first
one
and
the
biggest
contribution
made
the
previous
week.
I
think
it
was
a
great.
It
is
a
great
example
of
communication
between
contributors
and
magenta
engineers
and
I,
proud
to
represent
you
to
present
you,
the
keyword,
safe
functionality,
so
the
killing
feature
of
this
implementation
that
we
implement
the
latest
technical
approach
and
the
modern
way
in
magenta
in
saving
and
manipulating
data
resources.
So
just
we
for
keyboard,
which
is
not
just
some
independent
parts
of
the
asset
object,
but
it
just
depends
on
our
cities
we
create.
C
Next
we
have
a
key
world
model
which
is
pretty
simple,
yes,
but
it
also
they
have
asset
keyboards
repository,
which
consists
of
two
methods:
safe
asset
keyboards
and
get
get
asset
keyboards.
So
what
particular
asset
we
safe
and
get
keyboard
honest
on
the
side,
action
on
gate
and
here
the
main
the
main
feature.
So
we
have
a
keyboard
resource
model.
We
just
know
only
about
the
keyboard,
the
object
and
resource
connection.
So
here
we
do
not
rely
on
abstract
their
source
model
and
we
do
not
use
inheritance.
C
We
just
used
the
resource
connection
and
implement
our
own
custom
safe
message.
This
approach,
it
always
to
be
to
help
implementation
on
a
high
technical
level
and
reproduce
the
latest,
the
modern
and
the
best
tendency
in
the
magenta
development.
So
we
creates
a
custom,
safe
method,
load
method
and.
C
Insert
and
multiply
and
sort
these
two
lowers
to
have
a
great
performance
and
data
consistence.
So
and
yet,
maybe
maybe
technically
years
at
all,
and
from
my
point
of
view
this
is
a
good
example
of
how
we
will
implement
other
parts
for
asset
category
creator
and
other
required
assets
parts
so,
but
yet
maybe
about
this
part
at
all.
Certainly
do
you
want
to
add
something.
A
A
A
Preferable
as
preferable
approach
to
avoid
inheritance
and
to
average,
using
using
cause
of
resource
models,
it
is
not
required
for
the
operations
that
we
need
to
do
so.
We'll
try
to
in
scope
of
other
vista
configuration
project,
we'll
try
to
apply
that
approach
as
much
as
possible.
As
far
as
I
know
there,
at
only
the
only
problems
that
I
see
with
applying
custom
resource
modules
that
are
not
extending
magenta
resource
models
is
parsing.
The
search
criteria
for
resource
model
data
loading
collections,
like
loading
lists
of
results.
A
Currently
in
magenta
we
have
a
handy
process:
collection,
collection,
processor
that
is
working.
The
search
criteria
and
preparing
collection
force
very
nicely,
but
there
are
already
several
approaches
to
resolve,
to
use
alternative
way
to
work
with
search
criteria
and
magenta
that
we
will
try
to
apply
on
a
domestic
integration
project
as
well.
So
yeah
thanks
Alex.
It
was
a
really
nice
and
modern
in
magenta
world
implementation
of.
C
C
A
B
B
Object
we
we
use
in
here
currently
inherits
from
component
in
magenta,
so
I
start
removing
the
inheritance
from
there
and
under
the
last
bit,
I
need
to
finish.
Implementing
is
the
simplification
I
previously
described,
which
is
just
use.
A
asset
object,
get
information
from
there
and
then
use
it
to
to
provide
the
data
for
there
for
the
grid.
B
A
Yeah
thanks
roll
okay,
let's
probably
also
discuss
it,
discuss
the
details
of
fermentation
after
the
meeting
all
right,
yep
this
that's
nice,
we
will
be
able
to
remove
extra
cover
conversion
and
speed
up
the
process
of
retrieving
assets,
even
faster
cool,
good
thing.
So
finally,
I
would
like
to
provide
several
updates.
Yes,
let
me
share
my
screen.
A
Basically,
we
extracted
three
new
modules
and
those
are
I
Adobe
IMS
data,
the
IMS,
API
and
Adobe
stock
admin
UI
based
is
a
derby
I
am
last
module,
he's
he's
containing
the
functionality
to
login
the
user
to
adobe
integration,
and
it
also
includes
user
profiles,
so
user
data
user
profiles
a
prop
a
corresponding
resource
module
sense.
The
database
table
that
was
renamed
from
Adobe
stock
user
profile
to
just
a
double
user
profile
number
contains
the
same
fields
is
move
to
other
DMS
module
in
that'll,
be
IMS
API.
A
A
A
So
anytime
will
need
to
update
the
UI
that
is
not
related
to
image
that
it
that
can
be
used
for
any
potentially
can
be
used
for
any
a
doc
adopts
doc
asset
or
just
a
top
stack
integration
not
particularly
later
claim
it
should
be
located
in
Adobe
stock
admin
UI.
Well,
we
still
have
found
all
this
stock
image
admin
UI
that
contains
the
user
interface
related
to
specifically
image
image
as
assets.
A
Additionally,
there
is
a
pull
request
that
is
going
to
be
merge
soon.
We
are
moving
mustn't
agreed
to
other
Bui
module,
so
the
mustn't
regret
component
and
overlay
personality
will
be
moved
to
other
bi
model.
That
is
a
temporary
module
in
our
repository
and
these
module
is
going
to
be
merged.
So
the
contents
of
this
module
is
going
to
be
merged
to
magenta
core
to
magenta
UI
module,
so
much
magenta
UI
will
be
able
to
render
and
images
greed.
We
are
not
moving
all
the
great
functionality
that
we
currently
have
to
magenta
core.
A
A
Yeah
thanks
so
yeah.
Finally,
I
would
like
to
say
that
we
are
finishing
the
grooming
for
milestone
2,
so
you
might
have
noticed
that
we
have
a
lot
of
new
stories
in
the
backlog
and
I
have
started
creating
new
tasks
to
cover
functionality,
so
the
tasks
can
be
found
in
the
backlog
project
in
our
repository
and
there
were
a
couple
of
tasks
ready
for
development
just
30
minutes
ago
they
went
they
just
went
in
progress.
A
I
will
keep
populating
those
two
columns,
as
we
have
a
lot
of
tasks
to
do
in
the
second
milestone,
and
most
of
them
are
not
blocked,
as
we
really
developed
a
lot
of
basic
functionality
in
the
first
milestone
and
now
can
work
in
parallel.
So
just
to
remind
you
make
sure
if
you
would
like
to
take
a
task
to
implement
it,
make
sure
to
take
it
from
either
good
first
issue
or
ready
for
development
column,
because
tasks
in
ready
for
grooming
column
can
be
still
under
discussion
anyway.
A
A
Yeah,
if
you'd
like
to
review
the
roadmap,
the
stories
that
we
are
going
to
implement
in
this
second
milestone,
there
are
on
the
roadmap
page
on
our
wiki
and
Elena
is
our
in
the
links
to
the
stories
to
this
page.
All
the
functionalities
listed
here
and
those
links
are
basically
the
links
to
the
backlog.
The
stories
that
are
available
through
the
issue
stop.
C
This
question
may
be
proposition
based
on
my
own
experience
during
the
work
on
that
the
bestop
integration
magenta
yes,
and
I
wanna
post
on
scene.
Maybe
it
will
be
useful
for
complex
issue
or
maybe
epic
issue,
for
example,
when
the
issue
is
a
complex
and
requires
some
architecture,
parts
and
some
decision
of
how
to
implement
it
in
a
complex
issue
which
can
affect
other
functionality
and
process
and
models,
parts
and
tones
also
complex
issues
generally.
Yes,
maybe
we
should
market
like
a
complex
to
go.
For
example,
technique.
C
Architecture,
discussion
needed
I
want
maybe
to
hit
this,
because
this
can
boost
the
performance
of
contribution
and
increase
the
quality
of
the
delivery
tissue,
because
you
see
that
sometimes,
when
you
contribute
yes,
you
we
can
have
a
long
term
discussion.
Maybe
some
big
changes
which
can
be
discussed
before
and
this
may
be
total
for
the
whole
project
to
have
a
technical
medium
may
be
on
architectural
review.
When
we
make
a
decision
about
some
new
parts
or
maybe
complex
things,.
A
C
A
Architect
to
discuss
the
list
of
this
issues-
yes,
yes,
he
all
right,
yeah,
yeah,
I,
think
I,
think
that
can
be
useful.
So
it's
rough,
any
issues
that
are
lacking
details
or
or
they
require
require
some
basic
technical
design
for
implementation.
Just
or
just
discussions
I'm,
not
sure
actually
which
label
could
can
be
used.
But
let's
start
just
from.
A
A
A
A
So
in
the
Vidya
and
the
visual
design,
we
have
a
link
to
our
UI
prototype
and
it
was
recently
updated
by
eugen.
So
if
you,
when
you
open
the
UI
prototype,
you
see
the
nice
navigation
links
that
we
will
make
it
easier
to
find
to
the
mock-up
you
need,
for
example,
if
you
are
working
on
signing
functionality,
you
are.
You
can
use
the
link
to
open
the
appropriate
mock-up
on
the
sign-in
link
here
and
navigate
through
it
further.