Re: Flashbuilder 4.7 for Mac

[Paulus de B.]

We've been using IntelliJ for a couple of years now for Flex/AIR Windows/Mac
app development in a very large project without any real issues. I did have
to up the heap because of the size of the project, but for rest runs fine.



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: AIR Versions

[Paulus de B.]

Hi Paul, 

MX components should normally not be a problem. Are you sure you have the mx
namespace defined?

Like this e.g. in a spark VGroup that uses mx components (the xmlns:mx
part):


http://ns.adobe.com/mxml/2009; 
  xmlns:s="library://ns.adobe.com/flex/spark" 
  xmlns:mx="library://ns.adobe.com/flex/mx" 

Cheers

Paulus



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Create "web page" on the fly in AIR

[Paulus de B.]

Hi Paul, 

What if you create a local web server in AIR that when requested from the
browser (HTTP GET) performs a HTTP POST from your application to your server
and streams the response back to the browser? Doesn't that solve the
problem?

Cheers

Paulus



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Create "web page" on the fly in AIR

[Paulus de B.]

Hi Paul, 

You can create a local web server to your AIR app and redirect the user to
this local URL/port. This way you can stream anything you want to the
browser from your own local AIR web server.

Here's an example:
https://github.com/leopoldodonnell/airhttp

Cheers

Paulus



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Keeping user applications up to date in AIR.

[Paulus de B.]

Hi Paul, 

You could use javascript and the window dom as a middle ground for both
(setting up messaging between the two):
https://help.adobe.com/en_US/as3/dev/WS5b3ccc516d4fbf351e63e3d118666ade46-7ec2.html

Cheers

Paulus



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Tip/Solution after December/2020

[Paulus de B.]

Hi Diego, 

We faced the same problem and we just created a wrapper AIR / Flex
application with only one control in it: the HTML control which opens the
URL of our app.

Works like a charm (users will have to install your app, but since we're in
the B2B arena that's not a problem for us).

You can even add Flex functionality later on.

Cheers

Paulus



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Keeping user applications up to date in AIR.

[Paulus de B.]

Hi Paul, 

In our application there is no need for uploading / downloading files or
printing reports, but one shortcut I can think of for the printing part is
redirect users to the default browser and start the printing from there (if
this can be done from a HTML page in your application).

At the same time, since the wrapper AIR application is a Flex application,
you can do stuff around your swf application like uploading / downloading
and printing. You just have to do that in Flex / AIR, not in your swf.

Cheers

Paulus 



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Keeping user applications up to date in AIR.

[Paulus de B.]

Hi Paul, 

No, we will be migrating users from our Flash / browser application to Flex
/ AIR, but as this is an IT project it takes a bit longer than anticipated
:-)

So for now, we bought ourselves some time by putting the Flash application
in an AIR application.

Cheers

Paulus



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Keeping user applications up to date in AIR.

[Paulus de B.]

Hi Paul, 

We actually had the exact same setup in that we had an swf application we
needed to continue using after browsers stopped supporting flash.

What we did for the time being (but works very well): create an AIR
application that uses the flex HTML control to load your swfs like you did
in the browser.

Create a WindowedApplication (Flex) with just one control in it:


On the creationComplete
// Load your web application
htmlControl.location = "https://app...;;

In the end we did add the AIR updating functionality, but only for updating
the AIR app (which rarely happens). The swfs are loaded / reloaded like the
were in the browser.

Cheers

Paulus



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Board report time (March 2020)

[Paulus de B.]

The Flex/AIR combination rocks. In my 35 years of development experience
there is not much that comes close to its productivity.

We use it for desktop apps in combination with Granite Data Services (open
source) for real time and server data push.

Looking at other offerings there clearly is a market for real time desktop
app development tools.

How can we make a productive stack like this more top of mind?
- Apache Flex / Harman AIR frontend
- Apache Tomee / GraniteDS apps servers
- Any JDBC database cluster

A standardised development stack would go a long way in getting people on
board.

Maybe Harman would be interested? It would sell more AIR licences.

Any thoughts?

Cheers

WP



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

RE: Adobe AIR Maintenance and support changes

[Paulus de B.]

Our revenue model does not depend on the number of users but on how they use
it. So each user (actually client) gets charged a different monthly amount
depending on usage, not on how many users this client has. And by usage, we
mean actual processing done on our servers for our clients. They use the app
to determine what to do, but our servers do the processing (hence we can
charge for usage).

Therefore, with every development tool / IDE / platform / database we have
to select, as soon as there is a per end user license we drop it from our
list of options.

Besides the cost, the per end user license is a nightmare to administer. We
have thousands of users currently using our Flash app which we intend on
migrating to Flex/AIR. With users being added / removed every week I can
tell you upfront we are not going to setup an entire administration just for
license fees. And remember, we are coming from the Flash player in the web
browser which both have no per end user license model. 

And what if you want a freemium model? With a per user license you can't
roll out a freemium model because you want users to use your app for free to
start with.

The per end user limits the deployment of apps whereas AIR is such a great
solution to the multi platform problem it should be all over the place.

I completely understand if you are going to maintain and develop the AIR
player you have to get paid. But the per end user route limits the AIR
deployment severely (and thus in the end will actually give you less
revenue).

Don't get me wrong, I love the Flex/AIR combination and we don't mind paying
a (reasonable) developer seat fee for it. But like I said, the per end user
license is a no go will make us drop it from our list.



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

RE: Adobe AIR Maintenance and support changes

[Paulus de B.]

If it is per seat licensing for the end users we are out.

Per seat licensing for developers is OK.



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Adobe AIR Maintenance and support changes

[Paulus de B.]

I’m actually very exited about this because as said a paid version of AIR for
developers will secure the future. And Harman seems like a logical choice.



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: [Release] New Flex Apps - Medical Support

[Paulus de B.]

That's a great looking app and putting Flex to very good use!

Continuing your encouragement for people working with Flex, I'd like to
share what we have developed in Flex. 

We have developed a rebuild of our Flash / browser UI into an AIR/Flex app.
One of the features in this new app we use a lot is our newly built workflow
system. We use a tree with drag and drop etc to define the workflow, our
Tomee cluster than executes the workflow. It supports all kinds of steps
like assigning task forms, encryption/hashing, maps/lists, loops, opening
http/browser sessions, doing SQL queries etc.

Flex saves us a lot of time developing a cross platform UI (compared to e.g.
the HTML/CSS/Javascript hell) and the workflow system we built with it saves
a lot of time getting our new products and offers in production.

Our stack is:
- MySQL Percona Cluster, MySQL Cluster, Aerospike and Elasticsearch
- Tomee cluster
- AIR/Flex

Here is a screenshot of the workflow part in our AIR/Flex app currently in
use:

 



--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Adobe AIR App distribution: Questions

[Paulus de B.]

Hi Carlos, 

With regards to an update framework, we use this one for our desktop apps
developed in Flex/AIR and deployed on AIR, not as an .EXE (yes, it’s an old
one but it works very well):
https://github.com/thanksmister/CustomApplicationUpdater

Cheers, 

WP




--
Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: Life after FlashPlayer, are you prepared?

[Paulus de B.]

We develop business desktop and mobile apps in Flex/AS3 running on AIR,
connecting to a Java/JEE backend with real time data push.

We are in the process of migrating one of our apps from Flash/Browser to
Flex/AIR, adding new functionality as we go. It's just so easy to develop in
Flex.

Very impressed with the development speed compared to other technologies.
Not a big fan of HTML/JS/CSS, so if we can avoid the browser we will (e.g.
compare laying out an application in CSS with MXML).

Pauls de B.



--
Sent from: http://apache-flex-users.246.n4.nabble.com/