Changes in Core IDateChooserModel interface breaking Jewel

Hi Alex, I send this to 2 other threads yesterday, but seems it was missed by you. You added a new method to Core IDateChooseModel interface that Jewel implements. So Jewel is failing to build. I think the change is just needed by MXRoyale but not for Jewel, so not seems PAYG Can you move to some

Build failed in Jenkins: royale-asjs_jsonly #728

See Changes: -- [...truncated 1.59 MB...] clean-tests: check-compiler-home: check-transpiler-home: check-compiler: compile: compile-js: [echo]

Build failed in Jenkins: royale-asjs_jsonly #727

See Changes: -- [...truncated 1.59 MB...] clean-tests: check-compiler-home: check-transpiler-home: check-compiler: compile: compile-js: [echo]

Re: Jewel TodoMVC Example

Carlos, This is simply amazing. Great job on porting the standard TodoMVC app to Royale! Om On Thu, Jan 30, 2020 at 2:27 PM Carlos Rovira wrote: > Hi All, > > just upload a first version of TodoMVC to the website. It implements all > functionality, with Routing and Local Storage included. >

Build failed in Jenkins: royale-asjs_jsonly #726

See Changes: [carlosrovira] jewel-layout-basic: position needs to be forced. Still need so JS calcs [carlosrovira] left from last commit [carlosrovira] left from last

Jewel TodoMVC Example

Hi All, just upload a first version of TodoMVC to the website. It implements all functionality, with Routing and Local Storage included. Is done with Jewel UI Set showing how you can customize look and feel of included components (Button, Toggles, List, TextInput, BarRow...). Still I need to

Re: SharedObject should be in Storage lib

Hi Alex, I'm a huge fan of AMF and I think is worth it to use with the current SharedObject implementation done by Greg that already support AMF. Of course others could use other options. As you say, we need to give options. El jue., 30 ene. 2020 a las 21:16, Alex Harui () escribió: >

Re: SharedObject should be in Storage lib

SharedObjectJSON sounds useful and a good alternative short of AMF. I'm sure you're not surprised to hear me say that we should give users choices depending on their needs. If they only need to store simple values, LocalStorage should work. I think we do have Strong-Type to JSON and back

Build failed in Jenkins: royale-asjs_jsonly #725

See Changes: [carlosrovira] Revert "shared-object: Move LSO to Storage since is not flex" -- [...truncated 1.59 MB...] clean-tests:

Re: SharedObject should be in Storage lib

I think the browser can store objects already? Perhaps there is some way to do that, but I could not find anything for localStorage: ' The keys and the values are *always strings* (note that, as with objects, integer keys will be automatically converted to strings). ' The LSO version is an

Re: SharedObject should be in Storage lib

Hi Carlos, I probably don't understand your use case. I would not recommend to new projects to use AMF to store data locally. I think the browser can store objects already? And I would think the difficulty of re-coding SharedObject.setProperty to LocalStorage.setItem would be worth the

Re: [royale-asjs] branch develop updated: shared-object: Move LSO to Storage since is not flex

Hi Alex, yes, I tried a solution but didn't worked. So reverted it. Thanks for letting me know. Please take a look at the problem with the IDateChooserModel I said. People trying to build Jewel can't due to the new method added. I think that method should go to another interface used for MXRoyale

Re: SharedObject should be in Storage lib

Hi Alex, I tried this and reverted the commit since it has more things to be considered. LSO can be considered part of the AMF set of code, and depends on AMF classes that are currently in MXRoyale, for that reason Greg created there and not in Storage. These classes will need to be refactored

Build failed in Jenkins: royale-asjs_jsonly #724

See Changes: [carlosrovira] shared-object: Move LSO to Storage since is not flex [carlosrovira] mxroyale-Objectutil: fix failing test in CruxQuickStartBasic due to

Re: [royale-asjs] branch develop updated: shared-object: Move LSO to Storage since is not flex

I may be misreading this commit, but IMO, other than SparkRoyale, no other SWC should have dependencies on mx packages. My 2 cents, -Alex On 1/30/20, 9:08 AM, "carlosrov...@apache.org" wrote: This is an automated email from the ASF dual-hosted git repository. carlosrovira pushed

Re: SharedObject should be in Storage lib

I don't know if it would be more "general" since it would be Flash-specific, but re-use of code from Storage is always a great goal. The MXRoyale components re-use quite a bit of code from Basic. Taking a quick look at the ASDoc, SharedObject offers both Local and Remote flavors and a

Re: SharedObject should be in Storage lib

Possibly a MX version with Flash APIs should use a more general version from Storage? > On Jan 30, 2020, at 5:45 PM, Alex Harui wrote: > > I don't know LSO or the Storage SWC that well, but there is some sort of > LocalStorageProvider.as file already in Storage. > > IMO, if you are planning

Re: SharedObject should be in Storage lib

I don't know LSO or the Storage SWC that well, but there is some sort of LocalStorageProvider.as file already in Storage. IMO, if you are planning to 100% emulate the Flash LSO, that should go in MXRoyale. A more platform-independent API for local storage should go in Storage. I don't know

SharedObject should be in Storage lib

Hi, I was searching for some Flex counter part to the LSO classes in MXRoyale but didn't find anything. So if nobody opposite I'll move to the Storage library that seems its natural place. Thanks -- Carlos Rovira http://about.me/carlosrovira

Build failed in Jenkins: royale-asjs_jsonly #723

See Changes: [carlosrovira] todomvc-jewel-example: added routing -- [...truncated 1.59 MB...] clean-tests: check-compiler-home:

Build failed in Jenkins: royale-asjs_jsonly #722

See Changes: -- [...truncated 1.59 MB...] clean-tests: check-compiler-home: check-transpiler-home: check-compiler: compile: compile-js: [echo]

Fwd: [MAVEN-BUILD] Royale-asjs - Build # 2597 - Still Failing

Hi Alex, this addition to Core's IDateChooserModel : /** * If true, the DateChooser will dispatch change * events even if the date clicked is the selected date. * This flag is used by DateField to get the * dropdown to dismiss when clicking the selected date. * * @langversion 3.0 *

Jenkins build is back to normal : royale-typedefs #307

See

Build failed in Jenkins: royale-asjs_jsonly #721

See Changes: [carlosrovira] todomvc-jewel-example: refactor to separate pieces and make it more -- [...truncated 1.59 MB...] clean-tests:

Build failed in Jenkins: royale-asjs_jsonly #720

See Changes: [noreply] Change Calender icon in DateFieldView.as [carlosrovira] jewel-tooltip: organize imports -- [...truncated 1.59

Build failed in Jenkins: royale-asjs_jsonly #719

See Changes: [aharui] allow DateField dropdown to close when the selectedDate is clicked on. -- [...truncated 1.58 MB...] clean-tests: