You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Erik de Bruin <er...@ixsoftware.nl> on 2017/10/31 15:30:17 UTC
Restarting contributions
Hi,
I'm looking into how I can back into coding for the framework.
I think I'll try a simple component first. Any ideas? Is there a list of
'wanted' components?
Also, I really want to make my efforts JS only. I don't think it's worth it
to invest time in getting SWF versions working, as Flash (esp. browser
support) will be going the way of the Dodo sooner than we'll be able to
"finish" the framework, most likely. Is that possible?
Thanks,
EdB
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: Restarting contributions
Posted by Alex Harui <ah...@adobe.com.INVALID>.
IMO, we will let the users decide. I still think the Flash runtime is
better for testing complex multi-module applications. It will find errors
sooner. So, I would gently encourage new components to have bounding box
or wireframe visuals and functionality. I wouldn't spend energy on making
it truly look the same as the JS, just take up roughly the same space so
you can interact with it for testing purposes and validate your business
logic with the Flash runtime. If folks start asking for better visuals
then we'll work on that.
My 2 cents,
-Alex
On 10/31/17, 9:07 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>Hi Dave,
>
>although JS is priority, and as well other possible outputs like WebAsm,
>swift or android (java), I think people that wants to put effort in SWF
>fits perfectly in Apache Royale. We want to have one base code in AS3/MXML
>and output consistently to as many outputs we can.
>
>2017-10-31 16:55 GMT+01:00 Dave Fisher <da...@comcast.net>:
>
>> Hi -
>>
>> > On Oct 31, 2017, at 8:30 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>> >
>> > Hi,
>> >
>> > I'm looking into how I can back into coding for the framework.
>> >
>> > I think I'll try a simple component first. Any ideas? Is there a list
>>of
>> > 'wanted' components?
>> >
>> > Also, I really want to make my efforts JS only. I don't think it's
>>worth
>> it
>> > to invest time in getting SWF versions working, as Flash (esp. browser
>> > support) will be going the way of the Dodo sooner than we'll be able
>>to
>> > "finish" the framework, most likely. Is that possible?
>>
>> The main reason that we are now Royale is to focus on the JS (and
>>future)
>> and to drop the Flash (past)
>>
>> Regards,
>> Dave
>>
>> >
>> > Thanks,
>> >
>> > EdB
>> >
>> >
>> >
>> > --
>> > Ix Multimedia Software
>> >
>> > Jan Luykenstraat 27
>> > 3521 VB Utrecht
>> >
>> > T. 06-51952295
>> > I.
>>https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl&data
>>=02%7C01%7C%7C065f9bad0c1c48fb121d08d52079993b%7Cfa7b1b5a7b34438794aed2c1
>>78decee1%7C0%7C0%7C636450628992943547&sdata=WGjBYPRtei848QG1gVb6%2FO9SjN%
>>2FOeObvFklUpJTQgCI%3D&reserved=0
>>
>>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7C065f9bad0c1c48fb121d08d52079993b%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636450628992943547&sdata=ngzG3WTKl0ZBsq9E
>5ewj%2FEk11834Tipmc0i9ZVNlSU8%3D&reserved=0>
>
>Carlos Rovira
>
>Director General
>
>M: +34 607 22 60 05
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
>copic.com&data=02%7C01%7C%7C065f9bad0c1c48fb121d08d52079993b%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636450628992943547&sdata=ngzG3WTKl0ZBsq9E5
>ewj%2FEk11834Tipmc0i9ZVNlSU8%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7C065f9bad0c1c48fb121d08d52079993b%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636450628992943547&sdata=oqOFNyv9t0nsso
>EJlm0%2FVXmQJfTNCFiOFXW6Ju8gGjE%3D&reserved=0>
>
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>proceda a su destrucción.
>
>De la vigente Ley Orgánica de Protección de Datos (15/1999), le
>comunicamos
>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
>S.A. La finalidad de dicho tratamiento es facilitar la prestación del
>servicio o información solicitados, teniendo usted derecho de acceso,
>rectificación, cancelación y oposición de sus datos dirigiéndose a
>nuestras
>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
>necesaria.
Re: Restarting contributions
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Dave,
although JS is priority, and as well other possible outputs like WebAsm,
swift or android (java), I think people that wants to put effort in SWF
fits perfectly in Apache Royale. We want to have one base code in AS3/MXML
and output consistently to as many outputs we can.
2017-10-31 16:55 GMT+01:00 Dave Fisher <da...@comcast.net>:
> Hi -
>
> > On Oct 31, 2017, at 8:30 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
> >
> > Hi,
> >
> > I'm looking into how I can back into coding for the framework.
> >
> > I think I'll try a simple component first. Any ideas? Is there a list of
> > 'wanted' components?
> >
> > Also, I really want to make my efforts JS only. I don't think it's worth
> it
> > to invest time in getting SWF versions working, as Flash (esp. browser
> > support) will be going the way of the Dodo sooner than we'll be able to
> > "finish" the framework, most likely. Is that possible?
>
> The main reason that we are now Royale is to focus on the JS (and future)
> and to drop the Flash (past)
>
> Regards,
> Dave
>
> >
> > Thanks,
> >
> > EdB
> >
> >
> >
> > --
> > Ix Multimedia Software
> >
> > Jan Luykenstraat 27
> > 3521 VB Utrecht
> >
> > T. 06-51952295
> > I. www.ixsoftware.nl
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.
Re: Restarting contributions
Posted by Dave Fisher <da...@comcast.net>.
Hi -
> On Oct 31, 2017, at 8:30 AM, Erik de Bruin <er...@ixsoftware.nl> wrote:
>
> Hi,
>
> I'm looking into how I can back into coding for the framework.
>
> I think I'll try a simple component first. Any ideas? Is there a list of
> 'wanted' components?
>
> Also, I really want to make my efforts JS only. I don't think it's worth it
> to invest time in getting SWF versions working, as Flash (esp. browser
> support) will be going the way of the Dodo sooner than we'll be able to
> "finish" the framework, most likely. Is that possible?
The main reason that we are now Royale is to focus on the JS (and future) and to drop the Flash (past)
Regards,
Dave
>
> Thanks,
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
Re: Restarting contributions
Posted by Peter Ent <pe...@adobe.com.INVALID>.
I created the Mobile kit. I did it separately because it was supposed to
mimic how UINavigationController, UIViewController, and UITabController
work on iOS (which I'm more familiar with than Android). But there is
nothing specific in that kit (that I remember) which ties it to a mobile
device. That's opposed to Storage kit, which is dependent on AIR to
provide a file system on the SWF platform.
I think once we look into refactoring the packages, a lot of Mobile could
be moved out.
‹peter
On 11/2/17, 8:36 AM, "Harbs" <ha...@gmail.com> wrote:
>The classes probably do not belong necessarily in mobile.
>
>Here¹s what I¹m using:
>css:
>
> js|TabbedViewManager {
> IBeadView:
>ClassReference("org.apache.royale.mobile.beads.TopTabbedViewManagerView");
> }
>
>mxml:
> <js:TabbedViewManager id="navController" x="109" y="96" width="682"
>height="360" viewChanged="tabbedViewChanged(event)">
> <js:views>
> <js:TitleView title="Suites">
> <!-- Suites Data Grid -->
> <ex:DataGrid id="suiteDG" x="109" y="96" width="682" height="360"
> dataProvider="{suiteProvider}"
> change="handleExtensionDGChange(event)" rowHeight="30">
> <js:beads>
> <js:DataGridPercentageView />
> </js:beads>
> <js:columns>
> <js:DataGridColumn label="Product" dataField="product"
>columnWidth="30"
>itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> <js:DataGridColumn label="Status" columnWidth="33"
>itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
> <js:DataGridColumn label="Version" dataField="iVersion"
>columnWidth="12"
>itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> <js:DataGridColumn label="Latest Version" columnWidth="25"
>itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
> </js:columns>
> </ex:DataGrid>
> </js:TitleView>
> <js:TitleView title="Plugins">
> <!-- Suites Data Grid -->
> <ex:DataGrid id="pluginDG"
> dataProvider="{pluginProvider}"
> change="handleExtensionDGChange(event)" rowHeight="30">
> <js:beads>
> <js:DataGridPercentageView />
> </js:beads>
> <js:columns>
> <js:DataGridColumn label="Product" dataField="product"
>columnWidth="30"
>itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> <js:DataGridColumn label="Status" columnWidth="33"
>itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
> <js:DataGridColumn label="Version" dataField="iVersion"
>columnWidth="12"
>itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> <js:DataGridColumn label="Latest Version" columnWidth="25"
>itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
> </js:columns>
> </ex:DataGrid>
> </js:TitleView>
> </js:views>
>
>Things that need improvement:
>1. The tabs take up the full width.
>2. The tabs are simple buttons and the TabBar is hard-coded in. It really
>needs to be toggle buttons which have a selected state.
>
>Otherwise it works pretty well.
>
>Harbs
>
>> On Nov 2, 2017, at 2:29 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>>
>>
>>
>> For now, we would like to have an Apache Royale "ViewStack" equivalent
>>but we do not know where to start.
>> What do you think the parent component should be ? Could you give to us
>>some cues ?
>>
>> I think Harbs got StackedViewManager [1] to work for him in one of his
>>apps. It¹s in the mobile package but I¹m not sure there¹s a reason not
>>to use it on desktop.
>> [1]
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>om%2Fapache%2Froyale-asjs%2Fsearch%3Fp%3D1%26q%3DStackedViewManager%26typ
>>e%3D%26utf8%3D%25E2%259C%2593&data=02%7C01%7C%7Cce7a50ce362b4799aca808d52
>>1ee6a48%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636452230225743860&s
>>data=72MhSsPyVCSCXur8nnNjtCW9zAQn819lY3ycO3%2FWEeM%3D&reserved=0
>>
>
Re: ViewStack implementation [was : Restarting contributions]
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Unlike Flex, I believe the className property on HTMLElements in the
browser is a space-separate list of classes. Royale app devs will be
setting className. typeNames is for the component developer to dictate
part of the list that shouldn't be changed.
If it turns out that typeNames is always going to be a single value, then
yes, we could try to find some way for the compiler to auto-generate it,
but I'm not sure that will always be the case. Having a list of class
names sort of allows a form of multiple-inheritance which might be useful.
Of course, I could be wrong...
-Alex
On 11/4/17, 2:26 AM, "Idylog - Nicolas Granon" <ng...@idylog.com> wrote:
>Ok. Thank you.
>Found the typeNames property in UIBase.
>If I read it correctly, it is possible to have several space-separated
>values in typeNames (hence the final "s") ?
>What would be the usage for that ?
>
>Is it necessary to explicitly add the class name to typeNames ? Cannot be
>done automatically ?
>
>Nicolas Granon
>
>
>
>
>> -----Message d'origine-----
>> De : Alex Harui [mailto:aharui@adobe.com.INVALID]
>> Envoyé : samedi 4 novembre 2017 08:25
>> À : dev@royale.apache.org; ngranon@idylog.com
>> Objet : Re: ViewStack implementation [was : Restarting contributions]
>>
>> I hope if you search the code for 'typeNames' you will find proper
>> usage.
>> The typeName is supposed to be the name of the "type selector" in CSS.
>> So I think that code should have been
>>
>> typeNames = "StackedViewManager";
>>
>> HTH,
>> -Alex
>>
>> On 11/3/17, 2:33 PM, "Idylog - Nicolas Granon" <ng...@idylog.com>
>> wrote:
>>
>> >(I have changed the thread object to better reflect its content)
>> >
>> >That is crystal clear ! Thank you for that explanation.
>> >
>> >We are considering rewriting "ViewStack" based on Harb's work.
>> >
>> >In order to be more compliant, how should we use the typeNames
>> property
>> >you are talking about ?
>> >
>> >Nicolas Granon
>> >
>> >
>> >
>> >
>> >> -----Message d'origine-----
>> >> De : Alex Harui [mailto:aharui@adobe.com.INVALID] Envoyé : vendredi
>> 3
>> >> novembre 2017 18:23 À : dev@royale.apache.org; ngranon@idylog.com
>> >> Objet : Re: Restarting contributions
>> >>
>> >> We do that to try to get some backward compatibility with Flex.
>> >>
>> >> Flex extended the CSS type selector system to allow a type selector
>> >> for any component. So you could do:
>> >>
>> >> DataGrid { font-weight: bold }
>> >>
>> >> You can't extend the type selector system in the browser (AFAIK) so
>> >> we mimic this by converting a non-standard type selector to a class
>> >> selector.
>> >> So the CSS file in the JS output looks like:
>> >>
>> >> .DataGrid { font-weight: bold }
>> >>
>> >> And then to get that to work, we add DataGrid to the list of class
>> >> names on the HTMLElement. I think that StackedViewManager may need
>> >> its code updated because components are supposed to use the
>> typeNames
>> >> property which the framework appends to the classNames list instead
>> >> of directly setting className itself.
>> >>
>> >> HTH,
>> >> -Alex
>> >>
>> >> On 11/3/17, 8:41 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
>> >> wrote:
>> >>
>> >> >Many thanks.
>> >> >
>> >> >Quite useful.
>> >> >
>> >> >Question : I read the source code, and saw that in the
>> >> >StackedViewManager class, you explicitly assign the class name (as
>> a
>> >> >String) to the className property like that :
>> >> >className = "StackedViewManager";
>> >> >
>> >> >Why is that ?
>> >> >
>> >> >Nicolas Granon
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >> -----Message d'origine-----
>> >> >> De : Harbs [mailto:harbs.lists@gmail.com] Envoyé : jeudi 2
>> >> >> novembre
>> >> >> 2017 13:37 À : dev@royale.apache.org Objet : Re: Restarting
>> >> >> contributions
>> >> >>
>> >> >> The classes probably do not belong necessarily in mobile.
>> >> >>
>> >> >> Here’s what I’m using:
>> >> >> css:
>> >> >>
>> >> >> js|TabbedViewManager {
>> >> >> IBeadView:
>> >> >>
>> >>
>> ClassReference("org.apache.royale.mobile.beads.TopTabbedViewManagerVi
>> >> >> ew
>> >> >> ");
>> >> >> }
>> >> >>
>> >> >> mxml:
>> >> >> <js:TabbedViewManager id="navController" x="109" y="96"
>> >> >> width="682" height="360" viewChanged="tabbedViewChanged(event)">
>> >> >> <js:views>
>> >> >> <js:TitleView title="Suites">
>> >> >> <!-- Suites Data Grid -->
>> >> >> <ex:DataGrid id="suiteDG" x="109" y="96"
>> >> >> width="682" height="360"
>> >> >>
>> >> >dataProvider="{suiteProvider}"
>> >> >>
>> >> >> change="handleExtensionDGChange(event)" rowHeight="30">
>> >> >> <js:beads>
>> >> >> <js:DataGridPercentageView
>> >> >/>
>> >> >> </js:beads>
>> >> >> <js:columns>
>> >> >> <js:DataGridColumn
>> >> >label="Product"
>> >> >> dataField="product" columnWidth="30"
>> >> >>
>> >>
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"
>> >> />
>> >> >> <js:DataGridColumn
>> >> >label="Status"
>> >> >> columnWidth="33"
>> >> >> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
>> >> >> <js:DataGridColumn
>> >> >label="Version"
>> >> >> dataField="iVersion" columnWidth="12"
>> >> >>
>> >>
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"
>> >> />
>> >> >> <js:DataGridColumn
>> >> >label="Latest
>> >> >> Version" columnWidth="25"
>> >> >> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
>> >> >> </js:columns>
>> >> >> </ex:DataGrid>
>> >> >> </js:TitleView>
>> >> >> <js:TitleView title="Plugins">
>> >> >> <!-- Suites Data Grid -->
>> >> >> <ex:DataGrid id="pluginDG"
>> >> >>
>> >> >> dataProvider="{pluginProvider}"
>> >> >>
>> >> >> change="handleExtensionDGChange(event)" rowHeight="30">
>> >> >> <js:beads>
>> >> >> <js:DataGridPercentageView
>> >> >/>
>> >> >> </js:beads>
>> >> >> <js:columns>
>> >> >> <js:DataGridColumn
>> >> >label="Product"
>> >> >> dataField="product" columnWidth="30"
>> >> >>
>> >>
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"
>> >> />
>> >> >> <js:DataGridColumn
>> >> >label="Status"
>> >> >> columnWidth="33"
>> >> >> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
>> >> >> <js:DataGridColumn
>> >> >label="Version"
>> >> >> dataField="iVersion" columnWidth="12"
>> >> >>
>> >>
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"
>> >> />
>> >> >> <js:DataGridColumn
>> >> >label="Latest
>> >> >> Version" columnWidth="25"
>> >> >> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
>> >> >> </js:columns>
>> >> >> </ex:DataGrid>
>> >> >> </js:TitleView>
>> >> >> </js:views>
>> >> >>
>> >> >> Things that need improvement:
>> >> >> 1. The tabs take up the full width.
>> >> >> 2. The tabs are simple buttons and the TabBar is hard-coded in.
>> It
>> >> >> really needs to be toggle buttons which have a selected state.
>> >> >>
>> >> >> Otherwise it works pretty well.
>> >> >>
>> >> >> Harbs
>> >> >>
>> >> >> > On Nov 2, 2017, at 2:29 PM, Yishay Weiss
>> >> >> > <yi...@hotmail.com>
>> >> >> wrote:
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > For now, we would like to have an Apache Royale "ViewStack"
>> >> >> equivalent but we do not know where to start.
>> >> >> > What do you think the parent component should be ? Could you
>> >> >> > give to
>> >> >> us some cues ?
>> >> >> >
>> >> >> > I think Harbs got StackedViewManager [1] to work for him in one
>> >> >> > of
>> >> >> his apps. It’s in the mobile package but I’m not sure there’s a
>> >> >> reason not to use it on desktop.
>> >> >> > [1]
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi
>> >> >>th
>> >> u
>> >> >>b.c
>> >> >>om%2Fapache%2Froyale-
>> >> &data=02%7C01%7C%7C8ca096bd31024951eb4608d522d16c
>> >> >>8d%
>> >>
>> >>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453205224099105&sda
>> >> >>ta
>> >> =
>> >> >>s%2
>> >> >>Fr5KzGaKVqOLy8wTZ4QEHCspnV8UyHxn0XhvhN2KlM%3D&reserved=0
>> >> >> asjs/search?p=1&q=StackedViewManager&type=&utf8=%E2%9C%93
>> >> >> >
>> >> >
>> >> >
>> >
>> >
>
>
RE: ViewStack implementation [was : Restarting contributions]
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
Ok. Thank you.
Found the typeNames property in UIBase.
If I read it correctly, it is possible to have several space-separated values in typeNames (hence the final "s") ?
What would be the usage for that ?
Is it necessary to explicitly add the class name to typeNames ? Cannot be done automatically ?
Nicolas Granon
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com.INVALID]
> Envoyé : samedi 4 novembre 2017 08:25
> À : dev@royale.apache.org; ngranon@idylog.com
> Objet : Re: ViewStack implementation [was : Restarting contributions]
>
> I hope if you search the code for 'typeNames' you will find proper
> usage.
> The typeName is supposed to be the name of the "type selector" in CSS.
> So I think that code should have been
>
> typeNames = "StackedViewManager";
>
> HTH,
> -Alex
>
> On 11/3/17, 2:33 PM, "Idylog - Nicolas Granon" <ng...@idylog.com>
> wrote:
>
> >(I have changed the thread object to better reflect its content)
> >
> >That is crystal clear ! Thank you for that explanation.
> >
> >We are considering rewriting "ViewStack" based on Harb's work.
> >
> >In order to be more compliant, how should we use the typeNames
> property
> >you are talking about ?
> >
> >Nicolas Granon
> >
> >
> >
> >
> >> -----Message d'origine-----
> >> De : Alex Harui [mailto:aharui@adobe.com.INVALID] Envoyé : vendredi
> 3
> >> novembre 2017 18:23 À : dev@royale.apache.org; ngranon@idylog.com
> >> Objet : Re: Restarting contributions
> >>
> >> We do that to try to get some backward compatibility with Flex.
> >>
> >> Flex extended the CSS type selector system to allow a type selector
> >> for any component. So you could do:
> >>
> >> DataGrid { font-weight: bold }
> >>
> >> You can't extend the type selector system in the browser (AFAIK) so
> >> we mimic this by converting a non-standard type selector to a class
> >> selector.
> >> So the CSS file in the JS output looks like:
> >>
> >> .DataGrid { font-weight: bold }
> >>
> >> And then to get that to work, we add DataGrid to the list of class
> >> names on the HTMLElement. I think that StackedViewManager may need
> >> its code updated because components are supposed to use the
> typeNames
> >> property which the framework appends to the classNames list instead
> >> of directly setting className itself.
> >>
> >> HTH,
> >> -Alex
> >>
> >> On 11/3/17, 8:41 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
> >> wrote:
> >>
> >> >Many thanks.
> >> >
> >> >Quite useful.
> >> >
> >> >Question : I read the source code, and saw that in the
> >> >StackedViewManager class, you explicitly assign the class name (as
> a
> >> >String) to the className property like that :
> >> >className = "StackedViewManager";
> >> >
> >> >Why is that ?
> >> >
> >> >Nicolas Granon
> >> >
> >> >
> >> >
> >> >
> >> >> -----Message d'origine-----
> >> >> De : Harbs [mailto:harbs.lists@gmail.com] Envoyé : jeudi 2
> >> >> novembre
> >> >> 2017 13:37 À : dev@royale.apache.org Objet : Re: Restarting
> >> >> contributions
> >> >>
> >> >> The classes probably do not belong necessarily in mobile.
> >> >>
> >> >> Here’s what I’m using:
> >> >> css:
> >> >>
> >> >> js|TabbedViewManager {
> >> >> IBeadView:
> >> >>
> >>
> ClassReference("org.apache.royale.mobile.beads.TopTabbedViewManagerVi
> >> >> ew
> >> >> ");
> >> >> }
> >> >>
> >> >> mxml:
> >> >> <js:TabbedViewManager id="navController" x="109" y="96"
> >> >> width="682" height="360" viewChanged="tabbedViewChanged(event)">
> >> >> <js:views>
> >> >> <js:TitleView title="Suites">
> >> >> <!-- Suites Data Grid -->
> >> >> <ex:DataGrid id="suiteDG" x="109" y="96"
> >> >> width="682" height="360"
> >> >>
> >> >dataProvider="{suiteProvider}"
> >> >>
> >> >> change="handleExtensionDGChange(event)" rowHeight="30">
> >> >> <js:beads>
> >> >> <js:DataGridPercentageView
> >> >/>
> >> >> </js:beads>
> >> >> <js:columns>
> >> >> <js:DataGridColumn
> >> >label="Product"
> >> >> dataField="product" columnWidth="30"
> >> >>
> >>
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"
> >> />
> >> >> <js:DataGridColumn
> >> >label="Status"
> >> >> columnWidth="33"
> >> >> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
> >> >> <js:DataGridColumn
> >> >label="Version"
> >> >> dataField="iVersion" columnWidth="12"
> >> >>
> >>
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"
> >> />
> >> >> <js:DataGridColumn
> >> >label="Latest
> >> >> Version" columnWidth="25"
> >> >> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
> >> >> </js:columns>
> >> >> </ex:DataGrid>
> >> >> </js:TitleView>
> >> >> <js:TitleView title="Plugins">
> >> >> <!-- Suites Data Grid -->
> >> >> <ex:DataGrid id="pluginDG"
> >> >>
> >> >> dataProvider="{pluginProvider}"
> >> >>
> >> >> change="handleExtensionDGChange(event)" rowHeight="30">
> >> >> <js:beads>
> >> >> <js:DataGridPercentageView
> >> >/>
> >> >> </js:beads>
> >> >> <js:columns>
> >> >> <js:DataGridColumn
> >> >label="Product"
> >> >> dataField="product" columnWidth="30"
> >> >>
> >>
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"
> >> />
> >> >> <js:DataGridColumn
> >> >label="Status"
> >> >> columnWidth="33"
> >> >> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
> >> >> <js:DataGridColumn
> >> >label="Version"
> >> >> dataField="iVersion" columnWidth="12"
> >> >>
> >>
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"
> >> />
> >> >> <js:DataGridColumn
> >> >label="Latest
> >> >> Version" columnWidth="25"
> >> >> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
> >> >> </js:columns>
> >> >> </ex:DataGrid>
> >> >> </js:TitleView>
> >> >> </js:views>
> >> >>
> >> >> Things that need improvement:
> >> >> 1. The tabs take up the full width.
> >> >> 2. The tabs are simple buttons and the TabBar is hard-coded in.
> It
> >> >> really needs to be toggle buttons which have a selected state.
> >> >>
> >> >> Otherwise it works pretty well.
> >> >>
> >> >> Harbs
> >> >>
> >> >> > On Nov 2, 2017, at 2:29 PM, Yishay Weiss
> >> >> > <yi...@hotmail.com>
> >> >> wrote:
> >> >> >
> >> >> >
> >> >> >
> >> >> > For now, we would like to have an Apache Royale "ViewStack"
> >> >> equivalent but we do not know where to start.
> >> >> > What do you think the parent component should be ? Could you
> >> >> > give to
> >> >> us some cues ?
> >> >> >
> >> >> > I think Harbs got StackedViewManager [1] to work for him in one
> >> >> > of
> >> >> his apps. It’s in the mobile package but I’m not sure there’s a
> >> >> reason not to use it on desktop.
> >> >> > [1]
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgi
> >> >>th
> >> u
> >> >>b.c
> >> >>om%2Fapache%2Froyale-
> >> &data=02%7C01%7C%7C8ca096bd31024951eb4608d522d16c
> >> >>8d%
> >>
> >>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453205224099105&sda
> >> >>ta
> >> =
> >> >>s%2
> >> >>Fr5KzGaKVqOLy8wTZ4QEHCspnV8UyHxn0XhvhN2KlM%3D&reserved=0
> >> >> asjs/search?p=1&q=StackedViewManager&type=&utf8=%E2%9C%93
> >> >> >
> >> >
> >> >
> >
> >
Re: ViewStack implementation [was : Restarting contributions]
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I hope if you search the code for 'typeNames' you will find proper usage.
The typeName is supposed to be the name of the "type selector" in CSS. So
I think that code should have been
typeNames = "StackedViewManager";
HTH,
-Alex
On 11/3/17, 2:33 PM, "Idylog - Nicolas Granon" <ng...@idylog.com> wrote:
>(I have changed the thread object to better reflect its content)
>
>That is crystal clear ! Thank you for that explanation.
>
>We are considering rewriting "ViewStack" based on Harb's work.
>
>In order to be more compliant, how should we use the typeNames property
>you are talking about ?
>
>Nicolas Granon
>
>
>
>
>> -----Message d'origine-----
>> De : Alex Harui [mailto:aharui@adobe.com.INVALID]
>> Envoyé : vendredi 3 novembre 2017 18:23
>> À : dev@royale.apache.org; ngranon@idylog.com
>> Objet : Re: Restarting contributions
>>
>> We do that to try to get some backward compatibility with Flex.
>>
>> Flex extended the CSS type selector system to allow a type selector for
>> any component. So you could do:
>>
>> DataGrid { font-weight: bold }
>>
>> You can't extend the type selector system in the browser (AFAIK) so we
>> mimic this by converting a non-standard type selector to a class
>> selector.
>> So the CSS file in the JS output looks like:
>>
>> .DataGrid { font-weight: bold }
>>
>> And then to get that to work, we add DataGrid to the list of class
>> names on the HTMLElement. I think that StackedViewManager may need its
>> code updated because components are supposed to use the typeNames
>> property which the framework appends to the classNames list instead of
>> directly setting className itself.
>>
>> HTH,
>> -Alex
>>
>> On 11/3/17, 8:41 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
>> wrote:
>>
>> >Many thanks.
>> >
>> >Quite useful.
>> >
>> >Question : I read the source code, and saw that in the
>> >StackedViewManager class, you explicitly assign the class name (as a
>> >String) to the className property like that :
>> >className = "StackedViewManager";
>> >
>> >Why is that ?
>> >
>> >Nicolas Granon
>> >
>> >
>> >
>> >
>> >> -----Message d'origine-----
>> >> De : Harbs [mailto:harbs.lists@gmail.com] Envoyé : jeudi 2 novembre
>> >> 2017 13:37 À : dev@royale.apache.org Objet : Re: Restarting
>> >> contributions
>> >>
>> >> The classes probably do not belong necessarily in mobile.
>> >>
>> >> Here’s what I’m using:
>> >> css:
>> >>
>> >> js|TabbedViewManager {
>> >> IBeadView:
>> >>
>> ClassReference("org.apache.royale.mobile.beads.TopTabbedViewManagerVi
>> >> ew
>> >> ");
>> >> }
>> >>
>> >> mxml:
>> >> <js:TabbedViewManager id="navController" x="109" y="96"
>> >> width="682" height="360" viewChanged="tabbedViewChanged(event)">
>> >> <js:views>
>> >> <js:TitleView title="Suites">
>> >> <!-- Suites Data Grid -->
>> >> <ex:DataGrid id="suiteDG" x="109" y="96"
>> >> width="682" height="360"
>> >>
>> >dataProvider="{suiteProvider}"
>> >>
>> >> change="handleExtensionDGChange(event)" rowHeight="30">
>> >> <js:beads>
>> >> <js:DataGridPercentageView
>> >/>
>> >> </js:beads>
>> >> <js:columns>
>> >> <js:DataGridColumn
>> >label="Product"
>> >> dataField="product" columnWidth="30"
>> >>
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
>> >> <js:DataGridColumn
>> >label="Status"
>> >> columnWidth="33"
>> >> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
>> >> <js:DataGridColumn
>> >label="Version"
>> >> dataField="iVersion" columnWidth="12"
>> >>
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
>> >> <js:DataGridColumn
>> >label="Latest
>> >> Version" columnWidth="25"
>> >> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
>> >> </js:columns>
>> >> </ex:DataGrid>
>> >> </js:TitleView>
>> >> <js:TitleView title="Plugins">
>> >> <!-- Suites Data Grid -->
>> >> <ex:DataGrid id="pluginDG"
>> >>
>> >> dataProvider="{pluginProvider}"
>> >>
>> >> change="handleExtensionDGChange(event)" rowHeight="30">
>> >> <js:beads>
>> >> <js:DataGridPercentageView
>> >/>
>> >> </js:beads>
>> >> <js:columns>
>> >> <js:DataGridColumn
>> >label="Product"
>> >> dataField="product" columnWidth="30"
>> >>
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
>> >> <js:DataGridColumn
>> >label="Status"
>> >> columnWidth="33"
>> >> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
>> >> <js:DataGridColumn
>> >label="Version"
>> >> dataField="iVersion" columnWidth="12"
>> >>
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
>> >> <js:DataGridColumn
>> >label="Latest
>> >> Version" columnWidth="25"
>> >> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
>> >> </js:columns>
>> >> </ex:DataGrid>
>> >> </js:TitleView>
>> >> </js:views>
>> >>
>> >> Things that need improvement:
>> >> 1. The tabs take up the full width.
>> >> 2. The tabs are simple buttons and the TabBar is hard-coded in. It
>> >> really needs to be toggle buttons which have a selected state.
>> >>
>> >> Otherwise it works pretty well.
>> >>
>> >> Harbs
>> >>
>> >> > On Nov 2, 2017, at 2:29 PM, Yishay Weiss <yi...@hotmail.com>
>> >> wrote:
>> >> >
>> >> >
>> >> >
>> >> > For now, we would like to have an Apache Royale "ViewStack"
>> >> equivalent but we do not know where to start.
>> >> > What do you think the parent component should be ? Could you give
>> >> > to
>> >> us some cues ?
>> >> >
>> >> > I think Harbs got StackedViewManager [1] to work for him in one of
>> >> his apps. It’s in the mobile package but I’m not sure there’s a
>> >> reason not to use it on desktop.
>> >> > [1]
>> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
>> u
>> >>b.c
>> >>om%2Fapache%2Froyale-
>> &data=02%7C01%7C%7C8ca096bd31024951eb4608d522d16c
>> >>8d%
>> >>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453205224099105&sdata
>> =
>> >>s%2
>> >>Fr5KzGaKVqOLy8wTZ4QEHCspnV8UyHxn0XhvhN2KlM%3D&reserved=0
>> >> asjs/search?p=1&q=StackedViewManager&type=&utf8=%E2%9C%93
>> >> >
>> >
>> >
>
>
ViewStack implementation [was : Restarting contributions]
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
(I have changed the thread object to better reflect its content)
That is crystal clear ! Thank you for that explanation.
We are considering rewriting "ViewStack" based on Harb's work.
In order to be more compliant, how should we use the typeNames property you are talking about ?
Nicolas Granon
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com.INVALID]
> Envoyé : vendredi 3 novembre 2017 18:23
> À : dev@royale.apache.org; ngranon@idylog.com
> Objet : Re: Restarting contributions
>
> We do that to try to get some backward compatibility with Flex.
>
> Flex extended the CSS type selector system to allow a type selector for
> any component. So you could do:
>
> DataGrid { font-weight: bold }
>
> You can't extend the type selector system in the browser (AFAIK) so we
> mimic this by converting a non-standard type selector to a class
> selector.
> So the CSS file in the JS output looks like:
>
> .DataGrid { font-weight: bold }
>
> And then to get that to work, we add DataGrid to the list of class
> names on the HTMLElement. I think that StackedViewManager may need its
> code updated because components are supposed to use the typeNames
> property which the framework appends to the classNames list instead of
> directly setting className itself.
>
> HTH,
> -Alex
>
> On 11/3/17, 8:41 AM, "Idylog - Nicolas Granon" <ng...@idylog.com>
> wrote:
>
> >Many thanks.
> >
> >Quite useful.
> >
> >Question : I read the source code, and saw that in the
> >StackedViewManager class, you explicitly assign the class name (as a
> >String) to the className property like that :
> >className = "StackedViewManager";
> >
> >Why is that ?
> >
> >Nicolas Granon
> >
> >
> >
> >
> >> -----Message d'origine-----
> >> De : Harbs [mailto:harbs.lists@gmail.com] Envoyé : jeudi 2 novembre
> >> 2017 13:37 À : dev@royale.apache.org Objet : Re: Restarting
> >> contributions
> >>
> >> The classes probably do not belong necessarily in mobile.
> >>
> >> Here’s what I’m using:
> >> css:
> >>
> >> js|TabbedViewManager {
> >> IBeadView:
> >>
> ClassReference("org.apache.royale.mobile.beads.TopTabbedViewManagerVi
> >> ew
> >> ");
> >> }
> >>
> >> mxml:
> >> <js:TabbedViewManager id="navController" x="109" y="96"
> >> width="682" height="360" viewChanged="tabbedViewChanged(event)">
> >> <js:views>
> >> <js:TitleView title="Suites">
> >> <!-- Suites Data Grid -->
> >> <ex:DataGrid id="suiteDG" x="109" y="96"
> >> width="682" height="360"
> >>
> >dataProvider="{suiteProvider}"
> >>
> >> change="handleExtensionDGChange(event)" rowHeight="30">
> >> <js:beads>
> >> <js:DataGridPercentageView
> >/>
> >> </js:beads>
> >> <js:columns>
> >> <js:DataGridColumn
> >label="Product"
> >> dataField="product" columnWidth="30"
> >>
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> >> <js:DataGridColumn
> >label="Status"
> >> columnWidth="33"
> >> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
> >> <js:DataGridColumn
> >label="Version"
> >> dataField="iVersion" columnWidth="12"
> >>
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> >> <js:DataGridColumn
> >label="Latest
> >> Version" columnWidth="25"
> >> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
> >> </js:columns>
> >> </ex:DataGrid>
> >> </js:TitleView>
> >> <js:TitleView title="Plugins">
> >> <!-- Suites Data Grid -->
> >> <ex:DataGrid id="pluginDG"
> >>
> >> dataProvider="{pluginProvider}"
> >>
> >> change="handleExtensionDGChange(event)" rowHeight="30">
> >> <js:beads>
> >> <js:DataGridPercentageView
> >/>
> >> </js:beads>
> >> <js:columns>
> >> <js:DataGridColumn
> >label="Product"
> >> dataField="product" columnWidth="30"
> >>
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> >> <js:DataGridColumn
> >label="Status"
> >> columnWidth="33"
> >> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
> >> <js:DataGridColumn
> >label="Version"
> >> dataField="iVersion" columnWidth="12"
> >>
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> >> <js:DataGridColumn
> >label="Latest
> >> Version" columnWidth="25"
> >> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
> >> </js:columns>
> >> </ex:DataGrid>
> >> </js:TitleView>
> >> </js:views>
> >>
> >> Things that need improvement:
> >> 1. The tabs take up the full width.
> >> 2. The tabs are simple buttons and the TabBar is hard-coded in. It
> >> really needs to be toggle buttons which have a selected state.
> >>
> >> Otherwise it works pretty well.
> >>
> >> Harbs
> >>
> >> > On Nov 2, 2017, at 2:29 PM, Yishay Weiss <yi...@hotmail.com>
> >> wrote:
> >> >
> >> >
> >> >
> >> > For now, we would like to have an Apache Royale "ViewStack"
> >> equivalent but we do not know where to start.
> >> > What do you think the parent component should be ? Could you give
> >> > to
> >> us some cues ?
> >> >
> >> > I think Harbs got StackedViewManager [1] to work for him in one of
> >> his apps. It’s in the mobile package but I’m not sure there’s a
> >> reason not to use it on desktop.
> >> > [1]
> >>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith
> u
> >>b.c
> >>om%2Fapache%2Froyale-
> &data=02%7C01%7C%7C8ca096bd31024951eb4608d522d16c
> >>8d%
> >>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453205224099105&sdata
> =
> >>s%2
> >>Fr5KzGaKVqOLy8wTZ4QEHCspnV8UyHxn0XhvhN2KlM%3D&reserved=0
> >> asjs/search?p=1&q=StackedViewManager&type=&utf8=%E2%9C%93
> >> >
> >
> >
Re: Restarting contributions
Posted by Alex Harui <ah...@adobe.com.INVALID>.
We do that to try to get some backward compatibility with Flex.
Flex extended the CSS type selector system to allow a type selector for
any component. So you could do:
DataGrid { font-weight: bold }
You can't extend the type selector system in the browser (AFAIK) so we
mimic this by converting a non-standard type selector to a class selector.
So the CSS file in the JS output looks like:
.DataGrid { font-weight: bold }
And then to get that to work, we add DataGrid to the list of class names
on the HTMLElement. I think that StackedViewManager may need its code
updated because components are supposed to use the typeNames property
which the framework appends to the classNames list instead of directly
setting className itself.
HTH,
-Alex
On 11/3/17, 8:41 AM, "Idylog - Nicolas Granon" <ng...@idylog.com> wrote:
>Many thanks.
>
>Quite useful.
>
>Question : I read the source code, and saw that in the StackedViewManager
>class, you explicitly assign the class name (as a String) to the className
>property like that :
>className = "StackedViewManager";
>
>Why is that ?
>
>Nicolas Granon
>
>
>
>
>> -----Message d'origine-----
>> De : Harbs [mailto:harbs.lists@gmail.com]
>> Envoyé : jeudi 2 novembre 2017 13:37
>> À : dev@royale.apache.org
>> Objet : Re: Restarting contributions
>>
>> The classes probably do not belong necessarily in mobile.
>>
>> Here’s what I’m using:
>> css:
>>
>> js|TabbedViewManager {
>> IBeadView:
>> ClassReference("org.apache.royale.mobile.beads.TopTabbedViewManagerView
>> ");
>> }
>>
>> mxml:
>> <js:TabbedViewManager id="navController" x="109" y="96"
>> width="682" height="360" viewChanged="tabbedViewChanged(event)">
>> <js:views>
>> <js:TitleView title="Suites">
>> <!-- Suites Data Grid -->
>> <ex:DataGrid id="suiteDG" x="109" y="96"
>> width="682" height="360"
>>
>dataProvider="{suiteProvider}"
>>
>> change="handleExtensionDGChange(event)" rowHeight="30">
>> <js:beads>
>> <js:DataGridPercentageView
>/>
>> </js:beads>
>> <js:columns>
>> <js:DataGridColumn
>label="Product"
>> dataField="product" columnWidth="30"
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
>> <js:DataGridColumn
>label="Status"
>> columnWidth="33"
>> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
>> <js:DataGridColumn
>label="Version"
>> dataField="iVersion" columnWidth="12"
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
>> <js:DataGridColumn
>label="Latest
>> Version" columnWidth="25"
>> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
>> </js:columns>
>> </ex:DataGrid>
>> </js:TitleView>
>> <js:TitleView title="Plugins">
>> <!-- Suites Data Grid -->
>> <ex:DataGrid id="pluginDG"
>>
>> dataProvider="{pluginProvider}"
>>
>> change="handleExtensionDGChange(event)" rowHeight="30">
>> <js:beads>
>> <js:DataGridPercentageView
>/>
>> </js:beads>
>> <js:columns>
>> <js:DataGridColumn
>label="Product"
>> dataField="product" columnWidth="30"
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
>> <js:DataGridColumn
>label="Status"
>> columnWidth="33"
>> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
>> <js:DataGridColumn
>label="Version"
>> dataField="iVersion" columnWidth="12"
>> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
>> <js:DataGridColumn
>label="Latest
>> Version" columnWidth="25"
>> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
>> </js:columns>
>> </ex:DataGrid>
>> </js:TitleView>
>> </js:views>
>>
>> Things that need improvement:
>> 1. The tabs take up the full width.
>> 2. The tabs are simple buttons and the TabBar is hard-coded in. It
>> really needs to be toggle buttons which have a selected state.
>>
>> Otherwise it works pretty well.
>>
>> Harbs
>>
>> > On Nov 2, 2017, at 2:29 PM, Yishay Weiss <yi...@hotmail.com>
>> wrote:
>> >
>> >
>> >
>> > For now, we would like to have an Apache Royale "ViewStack"
>> equivalent but we do not know where to start.
>> > What do you think the parent component should be ? Could you give to
>> us some cues ?
>> >
>> > I think Harbs got StackedViewManager [1] to work for him in one of
>> his apps. It’s in the mobile package but I’m not sure there’s a reason
>> not to use it on desktop.
>> > [1]
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.c
>>om%2Fapache%2Froyale-&data=02%7C01%7C%7C8ca096bd31024951eb4608d522d16c8d%
>>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636453205224099105&sdata=s%2
>>Fr5KzGaKVqOLy8wTZ4QEHCspnV8UyHxn0XhvhN2KlM%3D&reserved=0
>> asjs/search?p=1&q=StackedViewManager&type=&utf8=%E2%9C%93
>> >
>
>
RE: Restarting contributions
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
Many thanks.
Quite useful.
Question : I read the source code, and saw that in the StackedViewManager
class, you explicitly assign the class name (as a String) to the className
property like that :
className = "StackedViewManager";
Why is that ?
Nicolas Granon
> -----Message d'origine-----
> De : Harbs [mailto:harbs.lists@gmail.com]
> Envoyé : jeudi 2 novembre 2017 13:37
> À : dev@royale.apache.org
> Objet : Re: Restarting contributions
>
> The classes probably do not belong necessarily in mobile.
>
> Heres what Im using:
> css:
>
> js|TabbedViewManager {
> IBeadView:
> ClassReference("org.apache.royale.mobile.beads.TopTabbedViewManagerView
> ");
> }
>
> mxml:
> <js:TabbedViewManager id="navController" x="109" y="96"
> width="682" height="360" viewChanged="tabbedViewChanged(event)">
> <js:views>
> <js:TitleView title="Suites">
> <!-- Suites Data Grid -->
> <ex:DataGrid id="suiteDG" x="109" y="96"
> width="682" height="360"
>
dataProvider="{suiteProvider}"
>
> change="handleExtensionDGChange(event)" rowHeight="30">
> <js:beads>
> <js:DataGridPercentageView
/>
> </js:beads>
> <js:columns>
> <js:DataGridColumn
label="Product"
> dataField="product" columnWidth="30"
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> <js:DataGridColumn
label="Status"
> columnWidth="33"
> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
> <js:DataGridColumn
label="Version"
> dataField="iVersion" columnWidth="12"
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> <js:DataGridColumn
label="Latest
> Version" columnWidth="25"
> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
> </js:columns>
> </ex:DataGrid>
> </js:TitleView>
> <js:TitleView title="Plugins">
> <!-- Suites Data Grid -->
> <ex:DataGrid id="pluginDG"
>
> dataProvider="{pluginProvider}"
>
> change="handleExtensionDGChange(event)" rowHeight="30">
> <js:beads>
> <js:DataGridPercentageView
/>
> </js:beads>
> <js:columns>
> <js:DataGridColumn
label="Product"
> dataField="product" columnWidth="30"
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> <js:DataGridColumn
label="Status"
> columnWidth="33"
> itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
> <js:DataGridColumn
label="Version"
> dataField="iVersion" columnWidth="12"
> itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
> <js:DataGridColumn
label="Latest
> Version" columnWidth="25"
> itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
> </js:columns>
> </ex:DataGrid>
> </js:TitleView>
> </js:views>
>
> Things that need improvement:
> 1. The tabs take up the full width.
> 2. The tabs are simple buttons and the TabBar is hard-coded in. It
> really needs to be toggle buttons which have a selected state.
>
> Otherwise it works pretty well.
>
> Harbs
>
> > On Nov 2, 2017, at 2:29 PM, Yishay Weiss <yi...@hotmail.com>
> wrote:
> >
> >
> >
> > For now, we would like to have an Apache Royale "ViewStack"
> equivalent but we do not know where to start.
> > What do you think the parent component should be ? Could you give to
> us some cues ?
> >
> > I think Harbs got StackedViewManager [1] to work for him in one of
> his apps. Its in the mobile package but Im not sure theres a reason
> not to use it on desktop.
> > [1] https://github.com/apache/royale-
> asjs/search?p=1&q=StackedViewManager&type=&utf8=%E2%9C%93
> >
Re: Restarting contributions
Posted by Harbs <ha...@gmail.com>.
The classes probably do not belong necessarily in mobile.
Here’s what I’m using:
css:
js|TabbedViewManager {
IBeadView: ClassReference("org.apache.royale.mobile.beads.TopTabbedViewManagerView");
}
mxml:
<js:TabbedViewManager id="navController" x="109" y="96" width="682" height="360" viewChanged="tabbedViewChanged(event)">
<js:views>
<js:TitleView title="Suites">
<!-- Suites Data Grid -->
<ex:DataGrid id="suiteDG" x="109" y="96" width="682" height="360"
dataProvider="{suiteProvider}"
change="handleExtensionDGChange(event)" rowHeight="30">
<js:beads>
<js:DataGridPercentageView />
</js:beads>
<js:columns>
<js:DataGridColumn label="Product" dataField="product" columnWidth="30" itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
<js:DataGridColumn label="Status" columnWidth="33" itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
<js:DataGridColumn label="Version" dataField="iVersion" columnWidth="12" itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
<js:DataGridColumn label="Latest Version" columnWidth="25" itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
</js:columns>
</ex:DataGrid>
</js:TitleView>
<js:TitleView title="Plugins">
<!-- Suites Data Grid -->
<ex:DataGrid id="pluginDG"
dataProvider="{pluginProvider}"
change="handleExtensionDGChange(event)" rowHeight="30">
<js:beads>
<js:DataGridPercentageView />
</js:beads>
<js:columns>
<js:DataGridColumn label="Product" dataField="product" columnWidth="30" itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
<js:DataGridColumn label="Status" columnWidth="33" itemRenderer="com.intools.dashboard.renderers.StatusRenderer"/>
<js:DataGridColumn label="Version" dataField="iVersion" columnWidth="12" itemRenderer="com.intools.dashboard.renderers.CenteredStringRenderer"/>
<js:DataGridColumn label="Latest Version" columnWidth="25" itemRenderer="com.intools.dashboard.renderers.VersionUpdater"/>
</js:columns>
</ex:DataGrid>
</js:TitleView>
</js:views>
Things that need improvement:
1. The tabs take up the full width.
2. The tabs are simple buttons and the TabBar is hard-coded in. It really needs to be toggle buttons which have a selected state.
Otherwise it works pretty well.
Harbs
> On Nov 2, 2017, at 2:29 PM, Yishay Weiss <yi...@hotmail.com> wrote:
>
>
>
> For now, we would like to have an Apache Royale "ViewStack" equivalent but we do not know where to start.
> What do you think the parent component should be ? Could you give to us some cues ?
>
> I think Harbs got StackedViewManager [1] to work for him in one of his apps. It’s in the mobile package but I’m not sure there’s a reason not to use it on desktop.
> [1] https://github.com/apache/royale-asjs/search?p=1&q=StackedViewManager&type=&utf8=%E2%9C%93
>
RE: Restarting contributions
Posted by Yishay Weiss <yi...@hotmail.com>.
For now, we would like to have an Apache Royale "ViewStack" equivalent but we do not know where to start.
What do you think the parent component should be ? Could you give to us some cues ?
I think Harbs got StackedViewManager [1] to work for him in one of his apps. It’s in the mobile package but I’m not sure there’s a reason not to use it on desktop.
[1] https://github.com/apache/royale-asjs/search?p=1&q=StackedViewManager&type=&utf8=%E2%9C%93
RE: Restarting contributions
Posted by Idylog - Nicolas Granon <ng...@idylog.com>.
Hi Erik,
Welcome back !
Rather than "ask for" components, we would like to learn how to build components.
I don't think that we are good enough (or experienced enough) to contribute to the SDK at this stage.
However, we would like to build some components ourselves for our own usage.
We will be happy to share the results if they are of any interest..
For now, we would like to have an Apache Royale "ViewStack" equivalent but we do not know where to start.
What do you think the parent component should be ? Could you give to us some cues ?
Also, we are in great need of an AdvancedDataGrid equivalent, but maybe we should wait until the DataGrid is more or less complete ?
Thank you
Nicolas Granon
> -----Message d'origine-----
> De : Erik de Bruin [mailto:erik@ixsoftware.nl]
> Envoyé : mardi 31 octobre 2017 16:30
> À : dev@royale.apache.org
> Objet : Restarting contributions
>
> Hi,
>
> I'm looking into how I can back into coding for the framework.
>
> I think I'll try a simple component first. Any ideas? Is there a list
> of 'wanted' components?
>
> Also, I really want to make my efforts JS only. I don't think it's
> worth it to invest time in getting SWF versions working, as Flash (esp.
> browser
> support) will be going the way of the Dodo sooner than we'll be able to
> "finish" the framework, most likely. Is that possible?
>
> Thanks,
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
Re: Restarting contributions
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Erik,
great to hear from you and see you back to coding! :)
in my opinion one of the things more needed are to get Forms and Validation
working.
I think we cannot reach 1.0 without this since is something we had in
almost all Flex applications.
Harbs made some work on Validators, but I think is only experimental now,
maybe he could let us know more about that
Just my 2cnts :)
Carlos
2017-10-31 16:30 GMT+01:00 Erik de Bruin <er...@ixsoftware.nl>:
> Hi,
>
> I'm looking into how I can back into coding for the framework.
>
> I think I'll try a simple component first. Any ideas? Is there a list of
> 'wanted' components?
>
> Also, I really want to make my efforts JS only. I don't think it's worth it
> to invest time in getting SWF versions working, as Flash (esp. browser
> support) will be going the way of the Dodo sooner than we'll be able to
> "finish" the framework, most likely. Is that possible?
>
> Thanks,
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.
De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.