Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (nike.apache.org: domain of maurice.amsellem@systar.com
 designates 66.129.85.153 as permitted sender)
From: Maurice Amsellem <maurice.amsellem@systar.com>
To: "dev@flex.apache.org" <dev@flex.apache.org>
Subject: RE: Issue with CallOut ASDOC
Thread-Topic: Issue with CallOut ASDOC
Thread-Index: 
 Ac7CriLivCVFIHWySkq94ce6xfl7IwAKAp4AAAXpW9D///KhgIAAQmPQ///CnYCAAD9WIP//JjWw
Date: Mon, 7 Oct 2013 16:06:31 +0000
Message-ID: 
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F52F91B@EXMBX05.netplexity.local>
References: 
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F52F2AE@EXMBX05.netplexity.local>
 <CACK5iZdQEfehO6P31rvZ+o3W2rcq+MxFFE4Tf6HOr5Tk7rbZQw@mail.gmail.com>
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F52F300@EXMBX05.netplexity.local>
 <CACK5iZcJDaVt7W5ruEQEEJnY+3kn5ohY+t+wYaTjCJidEBPmOA@mail.gmail.com>
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F52F32C@EXMBX05.netplexity.local>
 <CACK5iZc+JDzufVuyx_A_rMu1WAEsomJnUbC69y4qP7Ze_jU3Jg@mail.gmail.com>
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F52F370@EXMBX05.netplexity.local>
In-Reply-To: 
 <2095F5EBE04D59409DFCE91FFCEBF7AF3F52F370@EXMBX05.netplexity.local>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Hi Team,
This is the approach I took to  integrate Callout to spark:
- pushed s:Callout and related classes from mobilecomponents to spark
- copied the mobile skins to spark=20
- create a new base class that monkey patch MobileSkin in spark ( could ser=
ve for other components as well)
- changed the default css colors and settings.

Here is a simple demo app that shows the result.

https://dl.dropboxusercontent.com/u/12169005/ApacheFlex/DesktopCalloutDemo.=
swf

Note: I tried with a lighter background, but it does not look well, because=
 it's missing an 1 pixel dark outline.=20
Note2: does applicationDPI make sense also on desktop apps (maybe with Macb=
ook retina displays) ?=20

You feedback is welcome.

Maurice=20

-----Message d'origine-----
De=A0: Maurice Amsellem [mailto:maurice.amsellem@systar.com]=20
Envoy=E9=A0: dimanche 6 octobre 2013 21:27
=C0=A0: dev@flex.apache.org
Objet=A0: RE: Issue with CallOut ASDOC

Thanks for the info

-----Message d'origine-----
De=A0: omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de OmPrakash=
 Muppirala Envoy=E9=A0: dimanche 6 octobre 2013 21:13 =C0=A0: dev@flex.apac=
he.org Objet=A0: Re: Issue with CallOut ASDOC

On Sun, Oct 6, 2013 at 12:03 PM, Maurice Amsellem < maurice.amsellem@systar=
.com> wrote:

> >In fact, I like the mobile skin.  Perhaps we can use the same skin=20
> >for
> desktop as well?  We may want to lighten the default background color=20
> to match that of the default >Flex spark skins, though.
>
> Totally agree.  The desktop skin is very dull in comparison.  So a=20
> lighter mobile skin would be perfect for Desktop.
>
> So I will first try to merge the two host components in one, and then=20
> "PC-ize" the mobile skin.
>
> Do you know if any problems aroused when working on the experimental=20
> callout, so that I can avoid them (ie, benefit from previous experience) =
?
>
>
The experimental Callout components were created by Marcus Fritze and Maxim=
e Cowez.  There are more details in this JIRA ticket:
https://issues.apache.org/jira/browse/FLEX-33350

Hope that helps.

Thanks,
Om


> Regards,
>
> Maurice
>
> -----Message d'origine-----
> De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de=20
> OmPrakash Muppirala Envoy=E9 : dimanche 6 octobre 2013 20:55 =C0 :
> dev@flex.apache.org Objet : Re: Issue with CallOut ASDOC
>
> On Sun, Oct 6, 2013 at 11:11 AM, Maurice Amsellem <=20
> maurice.amsellem@systar.com> wrote:
>
> > Hi Team,
> >
> > Actually, after looking at the experimental CallOut code,  it's 95%=20
> > similar to the original Callout.
> >
> > I don't know the story from the beginning, but I think it has been=20
> > monkey-patched because the properties "actualHorizontalPosition" and=20
> > "actualVerticalPosition" were protected, to make them accessible=20
> > (mx_internal).
> >
> > So now that I know how to change and recompile the SDK :-),
> >
> > I just made that simple change (ie protected =3D> mx_internal) in the=20
> > original Callout class, and I can know use it in desktop (ie the=20
> > callout pops up)
> >
> > Of course, I used a dumb Skin, to it does not look like a callout at=20
> > all, but it should be feasible to adapt the experimental CallOutSkin=20
> > to make it work on the original class.
> > And it probably needs some more testing to make sure it works fine.
> >
> > So maybe we don't even need two classes, after all.
> >
> > After all, all other spark components (List, Panel, etc..) have the=20
> > same hostComponent , and only differ by their skin on mobile and=20
> > desktop platforms.
> >
> > What do you think?
> >
>
> I remember that there was a discussion about this a while ago.  Unsure=20
> as to why we decided on a new component.
> But I agree with you that we should merge these two components into one.
>
> In fact, I like the mobile skin.  Perhaps we can use the same skin for=20
> desktop as well?  We may want to lighten the default background color=20
> to match that of the default Flex spark skins, though.
>
> Thanks,
> Om
>
>
> >
> > Maurice
> >
> > -----Message d'origine-----
> > De : omuppi1@gmail.com [mailto:omuppi1@gmail.com] De la part de=20
> > OmPrakash Muppirala Envoy=E9 : dimanche 6 octobre 2013 18:54 =C0 :
> > dev@flex.apache.org Objet : Re: Issue with CallOut ASDOC
> >
> > On Oct 6, 2013 9:13 AM, "Maurice Amsellem"
> > <maurice.amsellem@systar.com>
> > wrote:
> > >
> > > Hi Team,
> > >
> > > I have noticed some classes asdoc link is broken on
> > flex.apache.org/asdoc
> > >
> > > https://issues.apache.org/jira/browse/FLEX-33802
> > >
> > > I propose an explanation and two possible fixes , but not sure=20
> > > what to
> > do, because I don't know how the release builds are done and deployed.
> > >
> > > Can you please confirm/contradict the proposed explanation and=20
> > > which fix
> > should be implemented.
> >
> > +1 for renaming the fault class names.
> >
> > Thanks for catching this!
> >
> > Om
> >
> > >
> > > Regards,
> > >
> > > Maurice Amsellem
> > > SYSTAR R&D - BusinessBridgeFX
> > >
> >
>