Re: Rialto Browser UI framework

["Dean, Robert" <rdean@xxxxxxxxxxxx>]

Here's an interesting possibility:

http://www.openxava.org/web/guest/home

I've come across this framework/product a few times over the years,
and what I found interesting about it was that there were indications
that the developer was clearly working with an iSeries.
________________________________________
From: web400-bounces@xxxxxxxxxxxx [web400-bounces@xxxxxxxxxxxx] On Behalf Of Booth Martin [booth@xxxxxxxxxxxx]
Sent: Saturday, January 23, 2010 8:25 PM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Rialto Browser UI framework

What are reactions to the idea  to the idea of an existing  portal
framework with development being devoted to building various JSR-286
portlets, as needed?

The portal framework itself deals with all the browser stuff  like
skins, decorations, sign-on, security, and deployment.  This means a
whole lot of overhead and PITA work is of no real concern to us
programmers?


On 1/23/2010 4:32 PM, Pete Helgren wrote:
> Nathan,
>
> I think the "pluggable" architecture is a key to the success of any
> framework.  With a documented framework/API that is extensible, you
> don't have to wait for the vendor to deliver.  Someone else might write
> one, or you could write your own plugin.
>
> The open source financial software Kuali, uses a similar concept.  Kuali
> provides very basic financial accounting.  Basically is has limited
> functionality (G/L, A/P, Purchasing,etc) But not *all* the functionality
> is there.  You can't write checks with it for example.  It will generate
> a check "transaction" that can be used to print a check, or direct
> deposit it, or whatever, but the actual model that would produce a paper
> check would be provided by the college using the software. You can find
> the Kuali project here: http://www.kuali.org/
>
> The basic concept is that it is a financial framework, not a complete
> solution, so they invite other colleges to write modules and contribute
> them to the project.
>
> You might even consider a similar concept with the financial package you
> are developing.  Your framework could provide the *core* functions
> including auditing, journaling and the like.  And, even if you continue
> go the proprietary route, you could at least publish the api's that can
> be used to "hook up" other applications.  Those apps could be written by
> schools or by third parties.
>
> It isn't a bad concept when you are limited by resources.  In your
> situation, all of the plugins could be proprietary and closed source but
> you get the advantage of the collaboration of many partners to deliver a
> complete solution.
>
> Just a thought.
>
> Pete
>
>
> Nathan Andelin wrote:
>
> > That leads to the question - what about using Widgets from multiple libraries?  Rialto doesn't appear to have an editable grid, for example.  Perhaps one of the secrets to jquery's success is that it begins with a lightweight library, and invites 3rd parties to write individual plug-ins.
> >
> > Nathan.
> >
> >
> >
> > ----- Original Message ----
> > From: Pete Helgren<Pete@xxxxxxxxxx>
> > To: Web Enabling the AS400 / iSeries<web400@xxxxxxxxxxxx>
> > Sent: Sat, January 23, 2010 1:33:15 PM
> > Subject: Re: [WEB400] Rialto Browser UI framework
> >
> > I have been using jqGrid which leverages jQuery and it has been pretty
> > productive, especially the inline editing which makes the grid work like
> > Excel (good for those finance types at School Districts who seem to
> > *love* Excel).
> >
> > Pete
--
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.