I keep falling into the idea that ROP is a way of exposing cayenne API
as a web service, and that's why I sent a list of wannabe
webapp-applets-that-talk-to-a-database (something that would be dodgy
anyway because you'd lose the ability to maintain data integrity - the
client might have a valid username and pw but give bad orders due to
obscelescence or hacking). Sorry for making a dev list post in spite of
noting reservations about my knowledge of that area.
Andrus Adamchik wrote:
> I don't understand how any of this is related to the project at hand -
> a demonstration of Cayenne Remote Object Persistence (aka Cayenne 3-
> tier) capabilities? I.e. the assumption is that there is a relational
> database on the server accessed by a client via a Cayenne web service.
>
> Andrus
>
>
> On Jun 1, 2006, at 11:46 PM, Craig Turner wrote:
>
>>
>> Andrus Adamchik wrote:
>>
>>> Another possible system can be a multi-user calendar app with Swing
>>> or SWT interface where people can create schedule items and browse
>>> other's schedules. Again, not that there are no calendar apps out
>>> there, but this is a prime example of an ROP use.
>>
>>
>> I've got a list of cool things I'd like to have time to write so I
>> could plug them into webapps:
>> - Simple FX pricing system that streams rates for several currency
>> pairs to the user and gives them the opportunity to place a spot
>> trade for any of the pairs. A priority here would be low delivery
>> time between aquiring the rate and delivering it to the user, and at
>> the other end taking the user's purchase request at the rate they
>> hit. There'd also be an opportunity to see trade history for the
>> team. Opportunity to use Swing or SWT but the interface wouldn't be
>> that complex.
>> - Simple, hardy XML document editor. There is a predefined list of
>> styles, and each block of text can have one and only one style. It
>> would be useful to have this so as to plug it into webapps where
>> there is a publishing emphasis. Would require dev of simple widgets,
>> this may be too complex. Someone with experience developing widgets
>> could show off.
>> - A tree browser, styled as a whiteboard. At any time there's a node
>> in focus, and then that's surrounded by child nodes. Clicking on a
>> child puts it in focus. The rich-client version of this could be far
>> cooler than a non-ajax web version because you could do zooming and
>> pre-caching and stuff, and it would be far easier to create an
>> elegant layout mechanism.
>> - Simple tune player. Idea came when I was trying to describe a tune
>> to a friend over irc and had no means of expression. App has multiple
>> 'lines' of midi data and actually plays it on the client. User can
>> edit each line in a text field using a simple system much like the
>> that used for ringtones on mobile phones. Small amount of Swing/SWT
>> required. Audio aspect might be complex - I'm not sure.
>>
>> I haven't kept up with the list a lot recently - hope these examples
>> are in-spirit.
>>
>>
>> --
>> Craig Turner - crai..ynect.com
>> Synect Online Solutions - http://www.synect.com
>>
>
-- Craig Turner - crai..ynect.com Synect Online Solutions - http://www.synect.com
This archive was generated by hypermail 2.0.0 : Fri Jun 02 2006 - 00:48:51 EDT