× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yes, it is ExtJS, and all you see is comming from a little minimum sized
515.

Data is served from the same mashine - all written in RPG.

ExtJS has tree major groups that uses it - MS .NET, PHP, and Lotus Notes
people, and they write thousands of statements to achive what you see (in
fact they have to write the same, but has to do it manually for each
program), most of the code you see is written i 2 (two) RPG statements -
and the program was made in less than 5 minutes ;-)

ExtJS runs in the browser, so it can't call iSeries resources directly.

Yes, we will continue to see new technologies such a JQtouch etc. etc., I
don't se the big problem in that.

Henrik





Kelly Cookson <KCookson@xxxxxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
19-04-2010 19:45
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc

Subject
Re: [WEB400] Why use PHP? What are the disadvantages?






That's a pretty nifty use of Java script. I take it you are using the
products from this company (please correct me if I'm wrong):
http://www.extjs.com/

I have nothing against using tools like this. I'm actually curious. Is the
page you directed us to as an example showing us data from an IBM i? How
does ExtJS to access databases from a remote server? Can ExtJS access IBM
i resources other than database tables?

Sorry, but I have no idea how many lines of PHP & HTML code would be
needed to replicate the page. I noticed the source code of the page
devoted lines 4 to 1000 (out of 1006 lines total) to Java script. I would
hazard a guess that an experienced PHP developer could do it in several
hundred lines of code (comparable). I've seen some pretty compact PHP
code. Didn't understand how it worked. But I've seen it. :-)

The commercial internet is a huge space. We will continue to see all kinds
of technologies used in that space for years to come. There's no one
technology that's going make the rest of them obsolete. Pick your
poison...

Kelly Cookson
Senior Programmer/Analyst
Dot Foods, Inc.
217-773-4486 x12676
www.dotfoods.com


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of hr@xxxxxxxxxxxx
Sent: Monday, April 19, 2010 12:37 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Why use PHP? What are the disadvantages?

Here is a link to a RIA type of application, try to browse the source that

created the page .... how much PHP/HTML is needed ?

http://212.242.251.247:1550/pextcgi/pxwkpxx9.pgm

Henrik




Kelly Cookson <KCookson@xxxxxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
19-04-2010 18:50
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc

Subject
Re: [WEB400] Why use PHP? What are the disadvantages?






Facebook still uses PHP. Here's how a Facebook developer describes their
use of PHP, HipHop and C:

"HipHop for PHP isn't technically a compiler itself. Rather it is a source

code transformer. HipHop programmatically transforms your PHP source code
into highly optimized C++ and then uses g++ to compile it."

"One common way to address these inefficiencies is to rewrite the more
complex parts of your PHP application directly in C++ as PHP Extensions.
This largely transforms PHP into a glue language between your front end
HTML and application logic in C++."

So they still use PHP. They just take the complex parts of the PHP and run

it through HipHop to compile into C. The C programs are then used as PHP
extensions. Like the guy says, PHP becomes the glue between the HTML front

end and the C back end.

Now, wouldn't it be cool if Zend and IBM could partner up and get HipHop
running on IBM i? We could use an HTML front end, a C back end (which
through the magic of ILE could allow reuse of RPG and COBOL), and PHP as
the glue that ties it all together.

Here's the article if you want to read more:
http://developers.facebook.com/news.php?blog=1&story=358

Kelly Cookson
Senior Programmer/Analyst
Dot Foods, Inc.
217-773-4486 x12676
www.dotfoods.com


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Nathan Andelin
Sent: Monday, April 19, 2010 11:29 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Why use PHP? What are the disadvantages?

Well, JavaScript generation is just a minor auxiliary that most people
never pay any attention to. But Dreamweaver is the best tool we've found
for "writing", "editing", and "managing" HTML, CSS, and JavaScript
projects in an integrated & consistent manner.

I don't want to get off topic, either.

It seems that one trap that PHP developers may fall into might be called
the "Facebook syndrome", where the applications become robust enough and
popular enough, that you begin looking for ways to get them to perform &
scale better, after the fact. In the case of Facebook, that led them to
transform the code to C.

-Nathan.







----- Original Message ----
From: "TAllen@xxxxxxxxxxxx" <TAllen@xxxxxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Mon, April 19, 2010 9:43:12 AM
Subject: Re: [WEB400] Why use PHP? What are the disadvantages?

Not to get off-topic, but the JavaScript code that DreamWeaver generated
the last time I used it was horrendous. It would be a huge headache to
maintain.

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.