I think the render kit approach is a good idea.

So it looks like RPGUI will be used more for internal or portal style
applications and not consumer based ones. Which I guess is where it makes
the most sense anyway...

Is RPGUI going to be component based? Not sure how that would work off the
top of my head.

I must admit I wasn't sure how I felt about a framework like this at first,
but I'm gaining some interest.

--
James R. Perkins


On Mon, Jan 25, 2010 at 05:06, Aaron Bartell <aaronbartell@xxxxxxxxx> wrote:

Yes, YUI is definitely in the top runnings. Somebody else made a comment
that it might be the combination of many frameworks that are then
honed/melded to meet the need of RPGUI. I would be fine with that, though
that is near exactly what ExtJS is - they started with YUI and jQuery (as I
understand it) and came up with a new name along with a much more refined
set of widgets. On that note, I am not an accomplished Javascript coder,
which is why I have favored ExtJS.

Regardless of what I hear back from ExtJS (I emailed them about licensing),
I think it (ExtJS) will still have a home in RPGUI. That's one of the
reasons I didn't name the tool RPG-ExtJS or RPG-Dojo or RPG-Silverlight -
because that would tie it to a particular UI which might not be what a
particular company wants. In the mindset of JSF I am going the route of
"UI
Render Kits" which basically means you have an agreed upon spec that the
View and Controller "talk" to and then Render Kits are built around that
spec (i.e. ExtJS, XUL, WML, Flex, Silverlight, custom, etc).

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/


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.