Re: autologin to another HTML page from flex app

[Bogdan DINU]

Hi,

usually after login, service should provide you a session id which you can
pass in the second opened page. The same service will validate session id
before displaying content.

Hope it helps!

Best regards,
Bogdan

On Fri, Mar 22, 2013 at 5:41 PM, Nitin Gopi  wrote:

> Hi
> Honestly I have no idea how to do it in HTML only site.
> The requirement in our project is to do in this way. If there is no direct
> way can you suggest some alternate way to do this?
>
> Thanks
> Nitin Gopi
>
>
> On Fri, Mar 22, 2013 at 7:20 PM, Alex Harui  wrote:
>
> > How would you do it from an HTML-only site without Flash?
> >
> >
> > On 3/22/13 5:29 AM, "Nitin Gopi"  wrote:
> >
> > > The new url is third party.
> > >
> > >
> > > On Fri, Mar 22, 2013 at 3:18 PM, Madhu Dutta
> > > wrote:
> > >
> > >> is the new url is your own? or any third party?
> > >>
> > >> On Fri, Mar 22, 2013 at 1:30 PM, Nitin Gopi 
> > wrote:
> > >>
> > >>> Hi Madhu
> > >>> Thanks for replying. I have a doubt here. We can use the
> > >> ExternalInterface
> > >>> API to access the javascript functions in the enclosing HTML wrapper.
> > But
> > >>> in my case I have to move to another page in another tab using the
> > >>> navigateToUrl method, then how can I access the username, password,
> > auto
> > >>> fill them and submit.
> > >>>
> > >>>
> > >>> On Fri, Mar 22, 2013 at 10:45 AM, Madhu Dutta <
> > >> iammadhusudan...@gmail.com
> >  wrote:
> > >>>
> >  yes you can do that..flex is totally pat from independent. you can
> use
> >  external interface to do that. you can put the user name/password on
> > >>> start
> >  up of loading page.by external interface.go the external
> > interface,you
> > >>> can
> >  get the answer. i have implemented this on my mobile apps.it is
> > >> working
> >  fine.
> > 
> >  On Fri, Mar 22, 2013 at 10:38 AM, Nitin Gopi 
> > >>> wrote:
> > 
> > > Hi
> > > I have a flex application. From this application I want to navigate
> > >> to
> > > another url which is a html page. To do that I can use
> > >> navigateToURL()
> > > method. In the new url I have to login. I need to automate the
> login
> > >>> into
> > > the page. For example if I am in a flex app, then clicking on a
> > >> button
> > >>> I
> > > should auto login to my gmail page in another tab. I have all the
> >  necessary
> > > credentials in the flex app itself. Has anybody done that?
> > > --
> > > You can only depend on yourself. The cavalry ain't coming.
> > >
> > 
> > 
> > 
> >  --
> >  *Thanks & Regards*
> >  *Madhusudan Dutta*
> > 
> > >>>
> > >>>
> > >>>
> > >>> --
> > >>> You can only depend on yourself. The cavalry ain't coming.
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> *Thanks & Regards*
> > >> *Madhusudan Dutta*
> > >> *mob: +919427284202 & +919038386682***
> > >>
> > >
> > >
> >
> > --
> > Alex Harui
> > Flex SDK Team
> > Adobe Systems, Inc.
> > http://blogs.adobe.com/aharui
> >
> >
>
>
> --
> You can only depend on yourself. The cavalry ain't coming.
>



-- 
http://www.badu.ro

[jira] [Commented] (FLEX-33429) Bindable Metadata does not work in SubClass

[Bogdan Dinu (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603172#comment-13603172
 ] 

Bogdan Dinu commented on FLEX-33429:


As the old documentation states [1] on point 3, the [Bindable] is declared to 
the setter. Metadata is inherited - I've runned the test before writing the 
comment.

[1] 
http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7cc5.html

> Bindable Metadata does not work in SubClass
> ---
>
> Key: FLEX-33429
> URL: https://issues.apache.org/jira/browse/FLEX-33429
> Project: Apache Flex
>  Issue Type: Bug
>  Components: .Unspecified - Compiler
>Affects Versions: Apache Flex 4.8 (parity release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: Japanese
>Reporter: hiroyuki kikuchi
>
> If Parent Class has defined a Bindable Metadata, it is not active in SubClass.
> It was working in Flex3.
> The following code demonstrates the problem. Bindable Metadata is not exist 
> in the Sub classes.
> Parent.as
> 
> public class Parent
> {
> private var _value:String;
> [Bindable]
> public function get value():String
> {
> return _value;
> }
> public function set value(value:String):void
> {
> if (_value != value)
> {
> _value = value;
> }
> }
> public function Parent()
> {
> super();
> }
> }
> 
> Sub.as
> 
> public class Sub extends Parent
> {
> override public function get value():String
> {
> return super.value;
> }
> public function Sub()
> {
> super();
> }
> }
> 
> Main.mxml
> 
> 
> http://ns.adobe.com/mxml/2009";
>xmlns:s="library://ns.adobe.com/flex/spark"
>xmlns:mx="library://ns.adobe.com/flex/mx"
>width="100%" height="100%">
> 
> 
> 
> 
> 
> 
> 
>  text="{describeType(parentClass).toString()}" />
>  text="{describeType(subClass).toString()}" />
> 
> 
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-15224) Listener not called when click="listenerFunc" set on mx:Button without an id property when executing in Firefox 3.0 browser

[Bogdan Dinu (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-15224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602158#comment-13602158
 ] 

Bogdan Dinu commented on FLEX-15224:


Could not replicate. Probably bad click handler definition. Not a bug.

> Listener not called when click="listenerFunc" set on mx:Button without an id 
> property when executing in Firefox 3.0 browser
> ---
>
> Key: FLEX-15224
> URL: https://issues.apache.org/jira/browse/FLEX-15224
> Project: Apache Flex
>  Issue Type: Bug
>  Components: Events
>Affects Versions: Adobe Flex SDK 3.0 (Release)
> Environment: Affected OS(s): Windows
> Affected OS(s): Windows XP
> Browser: Other (specify version)
> Language Found: English
>Reporter: Adobe JIRA
>
> Steps to reproduce:
> 1. Create an application with a two mx:Buttons with click="listenerfunc" 
> where one has an id property and one does not have an id property. Define the 
> listenerfunc function.
> 2. Execute application and click both buttons.
>  
>  Actual Results:
> Firefox 3.0 browser
> Listener function is called when clicking the button with an id property.
> Listener function is not called when clicking the button without an id 
> property.
> IE 6.0 browser
> Listener is called when clicking button whether it has an id property or not.
>  
>  
>  Expected Results:
> Listener function is called when clicking a button whether it has an id 
> property or not.
>  
>  
>  Workaround (if any):
> Always define an id property on components with listeners.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (FLEX-33429) Bindable Metadata does not work in SubClass

[Bogdan Dinu (JIRA)]

[ 
https://issues.apache.org/jira/browse/FLEX-33429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13602092#comment-13602092
 ] 

Bogdan Dinu commented on FLEX-33429:


Not true! You are declaring the getter of the parent to be [Bindable] : the 
correct way to declare a setter / getter as [Bindable] is to place it to the 
setter as following :
[Bindable]  
public function set value(value:String):void 
{ 
if (_value != value) 
{ 
_value = value; 
} 
}
This is not a bug.

> Bindable Metadata does not work in SubClass
> ---
>
> Key: FLEX-33429
> URL: https://issues.apache.org/jira/browse/FLEX-33429
> Project: Apache Flex
>  Issue Type: Bug
>  Components: .Unspecified - Compiler
>Affects Versions: Apache Flex 4.8 (parity release)
> Environment: Affected OS(s): All OS Platforms
> Language Found: Japanese
>Reporter: hiroyuki kikuchi
>
> If Parent Class has defined a Bindable Metadata, it is not active in SubClass.
> It was working in Flex3.
> The following code demonstrates the problem. Bindable Metadata is not exist 
> in the Sub classes.
> Parent.as
> 
> public class Parent
> {
> private var _value:String;
> [Bindable]
> public function get value():String
> {
> return _value;
> }
> public function set value(value:String):void
> {
> if (_value != value)
> {
> _value = value;
> }
> }
> public function Parent()
> {
> super();
> }
> }
> 
> Sub.as
> 
> public class Sub extends Parent
> {
> override public function get value():String
> {
> return super.value;
> }
> public function Sub()
> {
> super();
> }
> }
> 
> Main.mxml
> 
> 
> http://ns.adobe.com/mxml/2009";
>xmlns:s="library://ns.adobe.com/flex/spark"
>xmlns:mx="library://ns.adobe.com/flex/mx"
>width="100%" height="100%">
> 
> 
> 
> 
> 
> 
> 
>  text="{describeType(parentClass).toString()}" />
>  text="{describeType(subClass).toString()}" />
> 
> 
> 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Flex-Spring Integration

[Bogdan DINU]

Hi Cataldo,

what do you mean by BlazeDS it's not compatible with the latest releases of
Spring? If you are having troubles with Hibernate 4, there is an patch to
make it work, which you can find attached here [1].

I'm using BlazeDS integrated with Spring 3.1 and Hibernate 4 - works really
fine.

Best regards,
Bogdan

[1] https://jira.springsource.org/browse/FLEX-220

--
http://www.badu.ro

Re: Spark Accordion

[Bogdan DINU]

If I recall correctly, mobile components have destruction policy declared
by ViewNavigatorBase. However, I don't deny that a NavigatorContent with
creation/destruction policy is useful, but altering UIComponent (which is
already huge) is not the best option in my opinion.

All the best,
Bogdan


On Fri, Mar 1, 2013 at 8:11 AM, Alex Harui  wrote:

>
>
>
> On 2/28/13 9:53 PM, "Cyrill Zadra"  wrote:
>
> > Hey
> >
> >> a while ago, I've looked over the Accordion from "adobe.next" branch,
> >> having the same intention on my mind. What I found out is that they went
> >> all the way down, modifying UIComponent to add elementCreationPolicy and
> >> elementDestructionPolicy to the NavigatorContent, in order to make the
> >> Accordion support creation and destruction policies.
> >>
> >> Since Accordion component seems the only one who needs that, my approach
> >> (which remained an experiment that I haven't had time to finish), was to
> >> create a class named NavigatorContentWithPolicies that extends
> >> SkinnableContainer, so UIComponent doesn't need to be altered.
> >
> > @Alex or Carol do you know if there were any reason why
> > elementDestructionPolicy was added in UIComponent and not in a way as
> > Bogdan describes?
> I don't know for sure.  It maybe be that we wanted all kinds of containers
> to allow for destruction policies.  I think there are lots of scenarios in
> mobile where destruction policies are important and NavigatorContent may
> not
> always be involved.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>


-- 
http://www.badu.ro

Re: Spark Accordion

[Bogdan DINU]

Hi all,

a while ago, I've looked over the Accordion from "adobe.next" branch,
having the same intention on my mind. What I found out is that they went
all the way down, modifying UIComponent to add elementCreationPolicy and
elementDestructionPolicy to the NavigatorContent, in order to make the
Accordion support creation and destruction policies.

Since Accordion component seems the only one who needs that, my approach
(which remained an experiment that I haven't had time to finish), was to
create a class named NavigatorContentWithPolicies that extends
SkinnableContainer, so UIComponent doesn't need to be altered.

Besides a bug about specifying width / height on AccordionContent that
produces malfunction (never closes), the Accordion component seems
compliant to pairing the MX one.

By the way, there is also a Spark ViewStack in that branch...

Best regards,
Bogdan

On Thu, Feb 28, 2013 at 7:42 PM, Frédéric THOMAS wrote:

> Hi Cyrill,
>
> Thank you for pointing out the ones of Carol, I didn't know, I'll have a
> look ASAP.
> Few weeks ago I had a look at the Tink work, as well here [1] as here [2]
> and they look good, still have to be tested thought.
>
> I guess we could really investigate them and see if we could push some in
> the experimental lib.
>
> Btw, what about you Tink , do you still follow this list ?
>
> -Fred
>
> [1] http://tink.googlecode.com/**svn/trunk/flex4.5/spark/src/**
> ws/tink/spark/
> [2] 
> http://www.tink.ws/examples/**apache-flex/
>
> -Message d'origine- From: Cyrill Zadra
> Sent: Thursday, February 28, 2013 6:12 AM
> To: dev@flex.apache.org
> Subject: Spark Accordion
>
>
> Hey
>
> I was looking for a Spark Accordion and found the one in tinks and
> cframpton whiteboard (branch adobe.next). I moved all the relevant
> classes from cframpon's adobe.next branch to my develop branch and
> after a couple of hours I had a working accordion and it looks great.
>
> Before I continue to do some work and tests on accordion I just wanted
> to ask if there is already a decision which accordion is going to be
> in apache flex?  If not.. what needs to be done to have a decision.
>
> Cyrill
>



-- 
http://www.badu.ro

Re: Bogdan Components [Was: Getting source working in Flash Builder]

[Bogdan DINU]

Hi,

1) indeterminate ProgressBar can be made by customizing the skin. You can
also customize the labelFunction to display whatever you need.
2) ColorPicker doesn't allow you to set dataProvider - indeed you can
extend it to suit your needs (overriding childrenCreated() will allow you
to set any dataProvider you need).
3) Alert has a skin : note that if in your skin messageDisplay is not
defined, message will not show.

All the best,
Bogdan Dinu


On Fri, Feb 22, 2013 at 10:18 AM, Gavriel Harbater wrote:

> 2) ColorPicker: It does not seem to allow setting the dataProvider or
> handle anything beyond an Array of color values. Arrays of Objects for
> named colors is pretty important. If this in fact missing, I guess I'll
> work at expanding the component…
>
> 3) Alert: Does not show the error message. It looks to me that the problem
> is here that the messageDisplay is null.
> if (messageDisplay) {
> messageDisplay.text = _message;
> }
>
> On Feb 21, 2013, at 10:20 PM, Harbs wrote:
>
> > Some questions on the components:
> >
> > 1) ProgressBar: It does not seem to have feature parity with the mx
> version. There does not seem to be a way to specify an indeterminate
> progress bar. There's no mode property. Am I missing something? There's
> also no label property. Is the text set by specifying the
> percentDisplay.text? Will that get overwritten as the progressbar updates?
>
>


-- 
http://www.badu.ro

Re: Spark Tree

[Bogdan DINU]

Hi, I've used Kachurovkiy's version - seems well written.

On Fri, Feb 22, 2013 at 11:02 AM, Harbs  wrote:

> I realized I need another missing Spark component: Tree.
>
> There's a few components out there that fill this gap:
> https://github.com/kachurovskiy/Spark-Tree
> https://github.com/wasbridge/flex-4-tree
> http://saturnboy.com/2011/09/spark-treelist/
>
> Anyone have a preference here? Should we talk to one of those three about
> donating their component to Apache Flex? I don't mind doing work getting it
> ready if need be…
>
> Harbs




-- 
http://www.badu.ro

Re: Getting source working in Flash Builder

[Bogdan DINU]

Indeed, it's not in the spark namespace yet. Try using direct namespaces.

On Thu, Feb 21, 2013 at 2:46 PM, Nicholas Kwiatkowski wrote:

> From what I understand, the experimental swc had a different namespace...
>  I don't think it was in spark yet
>
> -Nick
>
> On Thu, Feb 21, 2013 at 3:31 AM, Harbs  wrote:
>
> > Yes. I'm talking about experimental.
> >
> > I linked to the 4.9 release and s:Alert and s:ColorPicker were not
> > available. I'm using the en_US locale. Not sure what to say here…
> >
> > This is all clear as mud to me. I'll play around a bit trying to wrap my
> > head around this. I'll probably come back with more questions later…
> >
> > On Feb 21, 2013, at 2:45 AM, Frédéric THOMAS wrote:
> >
> > > Harbs,
> > >
> > >> 2) I need the Alert and ColorPicker components that's not in the 4.9
> > release.
> > >
> > > If you're talking about the ones in the experimental.swc, there are in
> > the 4.9 but you can use them with en_US only, I re-worked them in the
> > develop branch, so if you want to use them and even to have an SDK you
> can
> > use with IntelliJ, constantly updated, chekout the develop branch, do a
> > first build, a release, use the makeApacheFlexForFlashBuilder on the
> > released develop branch itself, not the resulting binaries.
> > >
> > > Like that you can set this fresh SDK as the SDK you use if you want to
> > make change in the SDK, you'll have only to run the ant target
> > corresponding to the lib you modified (and the other.locales too) and
> > you'll be able to test it right away on your sample projects.
> > >
> > > Ask me if I haven't been completly clear.
> > >
> > > -Fred
> > >
> > > -Message d'origine- From: Justin Mclean
> > > Sent: Thursday, February 21, 2013 1:27 AM
> > > To: dev@flex.apache.org
> > > Subject: Re: Getting source working in Flash Builder
> > >
> > > Hi,
> > >
> > >> I did use the installer.
> > > Which would of given you last release 4.9.
> > >
> > >> The issue is that I'm trying to use the source rather than the
> > distribution for two reasons:
> > >> 1) I wanted to look into the TLF bugs that were reported.
> > >> 2) I need the Alert and ColorPicker components that's not in the 4.9
> > release.
> > >
> > > Make a release build from the source with ant release, copy and
> > unzip/untar the release and use the script in the IDE directory to make
> an
> > SDK usable for Flash Builder or any other IDE.
> > >
> > >> Does the source need to be compiled before it can work?
> > > Um yes. The source gets compiled in swcs (in the frameworks/lib
> > directory) that your Flex application uses.
> > >
> > >> I wonder if now would be a good time to try InteliJ IDEA...
> > > You would still have the package the SDK up, your issue is not unique
> to
> > just Flash Builder.
> > >
> > > Hope that helps.
> > >
> > > Justin
> >
> >
>



-- 
http://www.badu.ro