Re: What would it take?
Re: What would it take?
- Subject: Re: What would it take?
- From: James Cicenia <email@hidden>
- Date: Mon, 15 Feb 2010 16:39:52 -0600
David -
The real problem with D2W for me is where to look and when to cut into the templates. Hence my thought on templates.
I think the idea of a very robust Ajax capable template would be ideal. That way it can at least have its footing on the right foundation.
So, to me maybe the first thing would be a simple rule editor instead?
1) A basic Global Editor for standard Attribute type as in "prototypes" in EntityModeler.
This could maybe be extendable for arrays?
2) An outline view of all the entities and their default pageConfigurations nested below
a) ListEntity1
b) ListEntity2
c) CreateEntity1
allow for nesting some more i.e., for tabs, sections, etc.
3) A relationship editor.
a) Use prototype for display
b) Filters
c) Show this that and the other thing.
4) Have it be as visual/forms driven as possible.
Maybe it means to take RuleEditor up a notch or two or three? That is at least a codebase.
Regards,
James
On Feb 15, 2010, at 3:49 PM, David LeBer wrote:
>
> On 2010-02-15, at 3:10 PM, Chuck Hill wrote:
>
>>
>> On Feb 15, 2010, at 11:03 AM, James Cicenia wrote:
>>
>>> I have spent the last few weeks diving into D2W and Wonder.
>>>
>>> Amazing stuff... anyway.
>>>
>>> What would it take to make a new WebAssistant for D2W maybe WonderWebAssistant ?
>>
>> Talent and time. :-P
>>
>>
>>> I believe that to make a slick, ajaxy, WonderWebAssistant with choice of Templates would
>>> do more for promoting WebObjects than any other community endeavor.
>>>
>>> The above coupled with a step by step method of "breaking" out of D2W would be great.
>>>
>>> So what would it take? What would be the level of effort required? Does Apple hold back
>>> some intellectual property?
>>
>>
>> As a WAG, 3 - 6 months.
>
> D2W suffers (benefits) from the fact that the templates/components (and other custom objects) inform the rule vocabulary. In other words, the keys and values you can set depend on your Model (which can be interrogated), other rules (which can be interrogated), and your templates/components (which currently cannot) and custom factories or assignment objects (which also currently cannot).
>
> This makes writing a rule editor that knows all of the options at any give point difficult. I know there has been some discussion about enhancing the existing d2wclientConfiguration.plist and/or javadoc to make them easier to use for this, but I don't know if there was any clear consensus as to what the best approach may be.
>
> Like the discussions about creating a replacement for WOBuilder, maybe incremental improvements to the existing tools can help gain us much of the benefit you are looking for. What exactly are the things that the WebAssistant did for you that you are missing?
>
> ;david
>
> --
> David LeBer
> Codeferous Software
> 'co-def-er-ous' adj. Literally 'code-bearing'
> site: http://codeferous.com
> blog: http://davidleber.net
> profile: http://www.linkedin.com/in/davidleber
> twitter: http://twitter.com/rebeld
> --
> Toronto Area Cocoa / WebObjects developers group:
> http://tacow.org
>
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden