Yep - I just did quick look into the bead and it's essentially have those things which are currently baked into Model. I hopefully remove that one and replace things using bead in Jewel Example.
Thanks for adding that! Piotr śr., 12 gru 2018 o 13:04 Carlos Rovira <[email protected]> napisał(a): > Hi Piotr, > > just migrated the bead I talked (DispatchChangeOnStartup) from our project > to royale so you can have all the pieces and help you to diagnose the > problem > > As I said you Greg did the latest changes on this components so I should as > well read the changes since I didn't have to analyze since that was working > in our app in many parts flawlessly. > > thanks for taking care and good luck > > :) > > El mié., 12 dic. 2018 a las 10:55, Piotr Zarzycki (< > [email protected]>) escribió: > > > Hi Carlos, > > > > Comments inline. > > > > śr., 12 gru 2018 o 10:44 Carlos Rovira <[email protected]> > > napisał(a): > > > > > Hi Piotr, > > > > > > This month Greg and I made some changes to get selectedIndex and > > > selectedItem work in List, ComboBox and DropDownList. Since Navigation > > is a > > > List in essence, is involved in this changes. We should see how to > avoid > > > the duplicated event without lost the current workflow that now is > > working > > > properly like it was in flex days. Was hard to reach to that point. > > > > > > About options, we already have a bead to dispatch a change event on > > startup > > > in our project that we must pass to Jewel library. But I think is not > > what > > > we want here. We want setting selectedIndex/selectedItem in mxml should > > put > > > the component in proper state. I think that's what you refer when talk > > > about getting to work "programmatically" right? > > > > > > > > *Generally yes those actions should put component in proper state, but I > > just feeling that those state should not be achieved through model which > > dispatch "change" event. "change" event is to tell user that someone > > interact with component from UI. If developer interacting through code > > selectedIndexChanged and selectedItemChanged should probably come with > > help.* > > > > > > > Basically I think we have all needed beads in place, So I'll try the > > > removal option. But I think that event was copied from Basic version, > so > > > maybe is right (can ensure right now). You can try to do it yourself. > You > > > should check Jewel Example (Tour de Jewel) and specially List, ComboBox > > and > > > DropDownList sections along Navigation (that is used in the drawer) and > > > check you don't see regressions when doing changes. See how the > examples > > > behave actually, and since debugger now works perfectly, you can put > > break > > > points to see where's the problem and how to diagnose the right > solution. > > > > > > > > *Yes ArrayListSelectionModel is essentially copy of Basic one, but you > have > > added there code which dispatch "change" event plus property which > > generally allows you to do this or not > (dispatchChangeOnDataProviderChange) > > - That whole part even if should exists - should be probably exposed to > > separate bead. * > > *I'm surprised that you don't have any problems using in your > applications > > Bead for dispatch "change" event + ListSingleSelectionMouseController > (it > > also dispatch that event) + model - All are able to dispatch change in > > almost the same cases!* > > > > *Ok I think I will have to work on that with all cautious to current > code.* > > > > > > > Thanks! :) > > > > > > > > > > > > > > > El mar., 11 dic. 2018 a las 23:49, Piotr Zarzycki (< > > > [email protected]>) escribió: > > > > > > > Carlos, > > > > > > > > I just looked into the problem with double call of change event. You > > are > > > > using as default ListSingleSelectionMouseController - in navigation > > > > component which is calling "change" event once someone is clicking on > > > item. > > > > > > > > However you are doing it again from ArrayListSelectionModel which > > > probably > > > > shouldn't happen. This model is calling only selectedItemChanged, > > > > *selectedIndexChanged. * > > > > > > > > I'm assuming you are calling "change" event in > ArrayListSelectionModel > > > > cause you wanted to know whether someone has changed selectedItem and > > > > selectedIndex programmatically . If that was the case you should > > create a > > > > bead which listening for events from model and react in specific way. > > > > > > > > My proposition is: > > > > 1) Remove call of change event from Jewel ArrayListSelectionModel > > > > 2) Create a bead if you need for operation of programmatic change - > in > > > that > > > > case do not use in parallel ListSingleSelectionMouseController > > > > > > > > Thoughts ? > > > > > > > > Thanks, > > > > Piotr > > > > > > > > wt., 11 gru 2018 o 22:13 Carlos Rovira <[email protected]> > > > > napisał(a): > > > > > > > > > Hi Piotr, > > > > > > > > > > but .nav will not do anything. As I write before the right things > > > should > > > > be > > > > > > > > > > .jewel.navigation > > > > > background-color: transparent > > > > > > > > > > This in you App css will win over the one in the theme. > > > > > > > > > > Didn't try, but that should work, at least is what I do when I want > > > some > > > > > quick change to try or something temporal, or even could be a final > > > > change > > > > > too depending on the case. > > > > > > > > > > > > > > > El mar., 11 dic. 2018 a las 22:04, Piotr Zarzycki (< > > > > > [email protected]>) escribió: > > > > > > > > > > > I have tried to do point #2 from your options, but when I declare > > my > > > > own > > > > > > class: > > > > > > > > > > > > .nav { > > > > > > background-color: #ffffff > > > > > > } > > > > > > > > > > > > It's being override by those one from framework. Maybe I have to > > > > > inherited > > > > > > from framework classes ? > > > > > > > > > > > > Thanks, Piotr > > > > > > > > > > > > wt., 11 gru 2018 o 20:44 Carlos Rovira <[email protected]> > > > > > > napisał(a): > > > > > > > > > > > > > Hi Piotr, > > > > > > > > > > > > > > El mar., 11 dic. 2018 a las 17:37, Piotr Zarzycki (< > > > > > > > [email protected]>) escribió: > > > > > > > > > > > > > > > Hi Carlos, > > > > > > > > > > > > > > > > I have started playing using Jewel lately more serious and > have > > > two > > > > > > > > questions related to Jewel Navigation component. > > > > > > > > > > > > > > > > I'm displaying horizontal navigation like that [1]. Because > > > > > Navigation > > > > > > is > > > > > > > > actually list my background color is white. The question is > how > > > to > > > > > make > > > > > > > my > > > > > > > > navigation transparent component transparent? I know that I > > could > > > > > make > > > > > > > some > > > > > > > > css trick, but maybe you have a better solution. > > > > > > > > > > > > > > > > > > > > > > > each component use to have a css in Jewel and other one in > > > JewelTheme > > > > > > (95% > > > > > > > of cases) > > > > > > > I still need to write some wiki for all of this > > > > > > > In the meanwhile, search for file "_navigation.sass". The one > in > > > > Jewel > > > > > > has > > > > > > > definitions for beads and use to have some > > > > > > > standard css for things regarding "structure" > > > > > > > in the _navigation.sass in JewelTheme instead you'll not find > > > almost > > > > > any > > > > > > > Royale bead, and css more related to colors, animations, fonts, > > > > sizes, > > > > > > > ....so more "theme" things that people would want to change. > > > > > > > > > > > > > > There you'll find > > > > > > > > > > > > > > // Navigation variables > > > > > > > .jewel.navigation > > > > > > > background-color: #ffffff > > > > > > > > > > > > > > So, you can do in many ways: > > > > > > > > > > > > > > 1) Create your own theme with the same structure as JewelTheme > > and > > > > just > > > > > > > change this navigation thing > > > > > > > 2) just do in your app in you css, since that will be taken > > instead > > > > the > > > > > > > JewelTheme > > > > > > > > > > > > > > Notice that this will change when we implement full dark mode, > > that > > > > > > > navigation still doesn't support since > > > > > > > that component was made after I make dark mode and still don't > > have > > > > > that > > > > > > > implemented in SASS so > > > > > > > compiling SASS will generate a light/dark theme and/or > > flat/noflat > > > > > theme > > > > > > > > > > > > > > Another question is - Did you notice that Navigation component > > fire > > > > > > change > > > > > > > > event two times - whenever you click on the item ? > > > > > > > > > > > > > > > > > > > > > > > Thanks for reporting, I didn't notice, please feel free to fix > > > that, > > > > > just > > > > > > > take into account that navigation renderer preventdefault to > > avoid > > > > > trying > > > > > > > to open a web page. I see this in the way google material > solved > > > > > > navigation > > > > > > > things > > > > > > > but maybe could be a better way to do it > > > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > Carlos > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Carlos Rovira > > > > > > > http://about.me/carlosrovira > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Piotr Zarzycki > > > > > > > > > > > > Patreon: *https://www.patreon.com/piotrzarzycki > > > > > > <https://www.patreon.com/piotrzarzycki>* > > > > > > > > > > > > > > > > > > > > > -- > > > > > Carlos Rovira > > > > > http://about.me/carlosrovira > > > > > > > > > > > > > > > > > -- > > > > > > > > Piotr Zarzycki > > > > > > > > Patreon: *https://www.patreon.com/piotrzarzycki > > > > <https://www.patreon.com/piotrzarzycki>* > > > > > > > > > > > > > -- > > > > > > <http://www.codeoscopic.com> > > > > > > Carlos Rovira > > > > > > Presidente Ejecutivo > > > > > > M: +34 607 22 60 05 > > > > > > http://www.codeoscopic.com > > > > > > > > > Conócenos en 1 minuto! <https://avant2.es/#video> > > > > > > > > > AVISO LEGAL: La información contenida en este correo electrónico, y en > su > > > caso en los documentos adjuntos, es información privilegiada para uso > > > exclusivo de la persona y/o personas a las que va dirigido. No está > > > permitido el acceso a este mensaje a cualquier otra persona distinta a > > los > > > indicados. Si Usted no es uno de los destinatarios, cualquier > > duplicación, > > > reproducción, distribución, así como cualquier uso de la información > > > contenida en él o cualquiera otra acción u omisión tomada en relación > con > > > el mismo, está prohibida y puede ser ilegal. En dicho caso, por favor, > > > notifíquelo al remitente y proceda a la eliminación de este correo > > > electrónico, así como de sus adjuntos si los hubiere. En cumplimiento > de > > la > > > legislación española vigente en materia de protección de datos de > > carácter > > > personal y del RGPD 679/2016 le informamos que sus datos están siendo > > > objeto de tratamiento por parte de CODEOSCOPIC S.A. con CIFA85677342, > con > > > la finalidad del mantenimiento y gestión de relaciones comerciales y > > > administrativas. La base jurídica del tratamiento es el interés > legítimo > > de > > > la empresa. No se prevén cesiones de sus datos, salvo que exista una > > > obligación legal. Para ejercitar sus derechos puede dirigirse a > > CODEOSCOPIC > > > S.A., domiciliada enPaseo de la Habana, 9-11, 28036 de Madrid > (MADRID), o > > > bien por email [email protected], con el fin de ejercer sus > derechos > > de > > > acceso, rectificación, supresión (derecho al olvido), limitación de > > > tratamiento, portabilidad de los datos, oposición, y a no ser objeto de > > > decisiones automatizadas, indicando como Asunto: “Derechos Ley > Protección > > > de Datos”, y adjuntando fotocopia de su DNI. Delegado de protección de > > > datos:[email protected] > > > > > > > > > -- > > > > Piotr Zarzycki > > > > Patreon: *https://www.patreon.com/piotrzarzycki > > <https://www.patreon.com/piotrzarzycki>* > > > > > -- > Carlos Rovira > http://about.me/carlosrovira > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
