You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Carlos Rovira <ca...@apache.org> on 2019/10/21 08:34:14 UTC
[Discuss] About showing Tour De Flex in website and posting on RSS
Hi,
I see TDF working in many parts here:
http://apacheroyaleci2.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html
I think a clear warning in top would benefit it so people understand that
is still a work in progress and some parts of it still are not working
(ColorPicker, ProgressBar,...). I think warn is better than left people
navigate and see it's not working. The other point here's look and feel in
order to expose it to public, maybe some basic work here would benefit the
global, (although this could cause a problem for people using MXRoyale just
for AMF, HTTPService, Validators,.. and other non visual things, that will
know they need to exclude CSS from MXRoyale to avoid interferences with
Jewel, Basic, Express, and other sets...) maybe doing this on a theme
project to separate it from MXRoyale lib would be a solution for this.
if possible would be good to get it a better URL like:
http://royale.apache.org/tourdeflex (as we have similar for tourdejewel)
Depending on your opinion I can show it in website. The pros and cons I see
are:
Pros:
- People trying to migrate from flex will see things are progressing and
they could be interested in see if they can do to.
Cons:
- People could not understand parts not working (unless we warn about it in
top of TDF)
- Look and feel could be a problem too depending on the viewer.
About look and feel, a solution is not post in website but share in twitter
as a work in progress.
just some ideas here to explore with you guys
thanks
--
Carlos Rovira
http://about.me/carlosrovira
Re: [Discuss] About showing Tour De Flex in website and posting on
RSS
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Feel free to add a warning, but I would prefer if the warning was a dismiss-able popup because the goal of migrating TDF is to incrementally reach the point where differences are fewer and fewer (it may never get to zero differences). It helps if the Flex TDF and the Royale TDF have the same set of widgets so it is easier to compare.
And because of that, the UI and CSS for MXRoyale will change over time to more closely match the Flex TDF. If it impacts folks using Jewel or Basic then we either have to finish carving out the RPC library from MXRoyale or instruct those folks to exclude the CSS, but for sure, the CSS will change. It can't be done in a separate theme because we want to have the lowest number of changes required to migrate to MXRoyale. We don't want to ask folks to fiddle with compiler settings if we don't have to.
I don't care much either way if TDF is linked from the site. We can continue to tell folks about it on dev@.
My 2 cents,
-Alex
On 10/21/19, 1:34 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi,
I see TDF working in many parts here:
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapacheroyaleci2.westus2.cloudapp.azure.com%3A8080%2Fjob%2FTourDeFlexMigration%2FlastSuccessfulBuild%2Fartifact%2Fexamples%2Fmxroyale%2Ftourdeflexmodules%2Fbin%2Fjs-debug%2Findex.html&data=02%7C01%7Caharui%40adobe.com%7Cb28dd32883474a14ed5408d756018234%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637072436787751695&sdata=yIvtI4ffGgu1sXAqh0WFdl76%2BZKcdyKXj5kHiNI43FU%3D&reserved=0
I think a clear warning in top would benefit it so people understand that
is still a work in progress and some parts of it still are not working
(ColorPicker, ProgressBar,...). I think warn is better than left people
navigate and see it's not working. The other point here's look and feel in
order to expose it to public, maybe some basic work here would benefit the
global, (although this could cause a problem for people using MXRoyale just
for AMF, HTTPService, Validators,.. and other non visual things, that will
know they need to exclude CSS from MXRoyale to avoid interferences with
Jewel, Basic, Express, and other sets...) maybe doing this on a theme
project to separate it from MXRoyale lib would be a solution for this.
if possible would be good to get it a better URL like:
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.apache.org%2Ftourdeflex&data=02%7C01%7Caharui%40adobe.com%7Cb28dd32883474a14ed5408d756018234%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637072436787751695&sdata=AC67ngm%2BGeTN6ZgJDkKhvEUBWZS7ZWSlNYDbOlPaj1Y%3D&reserved=0 (as we have similar for tourdejewel)
Depending on your opinion I can show it in website. The pros and cons I see
are:
Pros:
- People trying to migrate from flex will see things are progressing and
they could be interested in see if they can do to.
Cons:
- People could not understand parts not working (unless we warn about it in
top of TDF)
- Look and feel could be a problem too depending on the viewer.
About look and feel, a solution is not post in website but share in twitter
as a work in progress.
just some ideas here to explore with you guys
thanks
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Cb28dd32883474a14ed5408d756018234%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637072436787751695&sdata=9bWLwrhxl0dF1nPIWBYhaxb8fNm12mk7oK7bXfosopA%3D&reserved=0