esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ethan Jewett <esjew...@gmail.com>
Subject UI vs. API vs. ESME server (was: Please take a look at)
Date Mon, 27 Jul 2009 15:02:20 GMT
It sounds like the project has been going down the road of decoupling the UI
from the backend for a while, resulting in a situation where we are pretty
close to having the ability to use a generic UI took like Atlas to build the
canonical front-end for ESME.
I assume that the interaction between the Atlas-built front-end and the ESME
server would be based on either the existing public API or a private API.
I'm not sure if this is the case, but maybe David can clarify.

Would it be of interest to the group to pursue a course of action in which
the ESME UI interacts only with publicly defined API methods (with the
possible exception of authentication)? This might help drive the evolution
of the API. It could also make it easier to have interchangeable UIs, so we
don't end up in UI limbo whenever a major change to the UI is proposed and
so that enterprise implementors can have an easier time deploying
custom(ized) UIs.

I'm going to start working on an ESME wrapper using YQL that will call the
API pretty soon now, so hopefully that will help drive the API development a
bit as well, but I figure the more people developing against the API the
better.

Ethan

On Mon, Jul 27, 2009 at 5:19 AM, Anne Kathrine Petter√łe
<yojibee@gmail.com>wrote:

> I agree with David.
> If Altas really is as good as it looks like, I think we should check out
> the option of switching from jQuery to Cappuccino.
>
> I think we need to clarify David's question about using non-open tools in
> Apache-hosted projects first though.
>
> /Anne
>
>
>
> On 21. juli. 2009, at 18.55, David Pollak wrote:
>
>  On Tue, Jul 21, 2009 at 1:11 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >wrote:
>>
>>  Question is when is the beta going to be released?
>>>
>>>
>> Dunno... but it does raise another issue... what's the Apache policy of
>> using non-open tools in order to build Apache-hosted projects?  Atlas is
>> not
>> open.
>>
>>
>>
>>> We might not be able to wait until it is released. The UI (or absence
>>> thereof) is the main probelm at the current time.
>>>
>>
>>
>> Yeah.
>>
>>
>>
>>>
>>> Another issue might be that we are currently focused on JQuery but
>>> 280atlas is Cappuccino-based.
>>>
>>
>>
>> The weight of the jQuery dependency is very light... I'd opt for the cost
>> of
>> switching to Cappuccino if we had a killer GUI builder option.
>>
>>
>>
>>>
>>> D.
>>>
>>> On Tue, Jul 21, 2009 at 12:18 AM, David
>>> Pollak<feeder.of.the.bears@gmail.com> wrote:
>>>
>>>> Folks,
>>>>
>>>> Please take a look at http://280atlas.com/
>>>>
>>>> Who has interest in building the ESME GUI with this tool?
>>>>
>>>> Thanks,
>>>>
>>>> David
>>>>
>>>> --
>>>> Lift, the simply functional web framework http://liftweb.net
>>>> Beginning Scala http://www.apress.com/book/view/1430219890
>>>> Follow me: http://twitter.com/dpp
>>>> Git some: http://github.com/dpp
>>>>
>>>>
>>>
>>
>>
>> --
>> Lift, the simply functional web framework http://liftweb.net
>> Beginning Scala http://www.apress.com/book/view/1430219890
>> Follow me: http://twitter.com/dpp
>> Git some: http://github.com/dpp
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message