Hi Nathan,

exactly, the UI is the application - and the servers role is just to
deliever data
the app needs (or some of the data, because data can come from many
resources).

The "front end" guys I work with - they create apps (browser based or
native) on their
PC without having a server - they test the apps against static JSON/XML
files on
their PC emulating server responces and they don "give a s***" where the
final data
comes from - to them a server isn't a MS/LINUX or a IBM I discussion - the
server
it is just an URL (a resource) that deliveres data to their app.

My best advise to you is - try to mingle with this people - attend some
meeting in the
groups of "front end" programmers and it will enlighten you

Soon there will be a reference to IBM I on this page under Server
Integration because
why not offer the same plugins to IBM I as to .NET when the plugins it
completely
server unaware?

http://www.ext-scheduler.com/examples/

I the last couple of years I have been developing powerEXT as a software
product and
in the same time I have been busy making contact's outside the IBM I world
and
now I'm in the start of creating the powerEXT vision ...

http://powerext.com/pext.pdf

And the problem is not with the new "front end"-programmers - the problem in
my strategy
lies in IBM I ISV that believes in and thinks proprietary and sits in their
"one programmer
or small ISV can and must do it all" jail.

But anyway - the first is the hardest and maybe I don't experience the
openness in IBM I
ISV's just now - it may come when I introduces my new homepage where these
"front end"
programmers has faces on from all over the world and we can deliever a
commen global
concept with a mix of a backend (server side) framework and a mix of "front
end" solutions
and resources.







On Thu, May 12, 2011 at 6:41 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Hi Henrik,

You make an interesting point about using HTML, CSS, and JavaScript to
create a
web application, then using Phone Gap to transform it to a native i/OS or
Android application, so it might use the geo-location and phone number
dialing
features of the native environment. That would be a good topic for another
article. Does that mean that you control the UI using JavaScript, instead
of
controlling application flow from the server?

Nathan

----- Original Message ----
From: Henrik Rützou <hr@xxxxxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Thu, May 12, 2011 9:15:05 AM
Subject: Re: [WEB400] Mobile Development for the i

Hi Joe,

nice article, however I tends to disagree a little.

I work with products from www.Sencha.com <http://www.sencha.com/> <
http://www.sencha.com/> and a lot
of "front end" javascript programmers
and yes it is OOjavascript, HTML5 and CSS3 - and it is correct that
frameworks that uses
these techniques dosn't directly supports local device resources when the
runs in a browser
- BUT - OOjavascript, HTML5 and CSS3 can be compiled into native binary
App's with support
for these local device resources.

So you can actual develop to both browsers and native App's in one common
SDK
such as Sencha Touch and then just compile the code into most native Apps
at
your
choise with www.phonegap.com

IMO, this represents a whole new ballgame for the OOjavascript frameworks
and combine
this with SASS and Compass that introduces "program logic and variables"
into CSS3
you actually have common technique and programming language with rich
components
that covers all.
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.