Well, it’s a team job for sure.

There’s tough programming in WO - components, frameworks, inheritance and 
trickery.

There’s tough programming in javascript - not just implementation, but 
identifying the original designs and retrofitting something that seamlessly 
enhances Wonder projects simply by linking to the frameworks…serious wizardry.

There’s tough programming in D2W, stuff that I was shocked to see! The trouble 
was not understanding any particular rule, although there were some (a lot?) 
that I was amazed by — but actually understanding the bigger picture of how 
they FIT these frameworks right into the Wonder stuff - link and unlink and 
magic comes and goes.

So, if it were to be done, it would have to be US that does it!

It’s a really hard task…

I wish I had a suggestion, because I believe it is THAT important.



> On Oct 29, 2019, at 9:18 AM, Theodore Petrosky <tedp...@yahoo.com> wrote:
> 
> do you think it would be possible to find someone that CAN do the work, and 
> then set up a fund me instance so we could pay him/her?
> 
> I would put money into this if I thought there were others that would also 
> add funds!
> 
> Ted
> 
>> On Oct 29, 2019, at 9:08 AM, Jesse Tayler via Webobjects-dev 
>> <webobjects-dev@lists.apple.com> wrote:
>> 
>> Yes, I recall something about show/hide but it’s fuzzy now.
>> 
>> I did however, conclude that we are all hosed!
>> 
>> The value of things like the AJAX list panel that can load up new batches or 
>> a tab panel that reloads like magic?
>> 
>> These old Ajax frameworks have tricks to override rules in D2W so simply 
>> adding the framework inserts itself into the interface frameworks 
>> beautifully.
>> 
>> Then I went into the AJAX frameworks to trace the code and found the group 
>> of them to be deeply intertwined, and the code depends on long hierarchies 
>> of those too-long-inheritance chains that we’ve all seen arise over time. 
>> You just keep going into superviews and different WOD bindings until you are 
>> lost.
>> 
>> I strongly sense we’d have to quite literally rewrite a batch of related 
>> frameworks -- and we’d have to be able to use the same code/D2W trickery to 
>> make the new frameworks ride on top of our apps seamlessly.
>> 
>> However, it IS possible to do!
>> 
>> I wish I had a solution to this problem.
>> 
>> 
>> 
>> 
>> 
>>> On Oct 29, 2019, at 8:57 AM, René Bock <b...@salient-doremus.de> wrote:
>>> 
>>> Well, you may use both frameworks,  prototyps.js and jQuery if you use 
>>> jQuery in non-conflict mode (because both frameworks defines the variable $ 
>>> as shortcut)
>>> 
>>> We had some additional issues when using the bootstrap framework, as 
>>> prototypes.js add functions like show, hide, toggle to each element.     
>>> 
>>>> Am 29.10.2019 um 12:55 schrieb Jesse Tayler via Webobjects-dev 
>>>> <webobjects-dev@lists.apple.com>:
>>>> 
>>>> I have trouble with this as well, the older code conflicts with newer 
>>>> jQuery based stuff.
>>>> 
>>>> So bad, that it will eventually stop your work because some bugs are 
>>>> critical and you’ll not be able to work around them.
>>>> 
>>>> I’ve found that the code way back in those Ajax frameworks is indeed 
>>>> amazing but also unreadable and unmaintainable.
>>>> 
>>>> In fact, I believe there is no way with our current resources that WO 
>>>> folks will overcome this critical issue — our legacy is dragging us down.
>>>> 
>>>> If anyone can figure this out, or even has ideas or wants to try — I’m up 
>>>> for it, but I’ve found myself that the weight is impossibly heavy.
>>>> 
>>>> 
>>>> 
>>>>> On Oct 29, 2019, at 3:18 AM, Jérémy DE ROYER via Webobjects-dev 
>>>>> <webobjects-dev@lists.apple.com> wrote:
>>>>> 
>>>>> Hello,
>>>>> 
>>>>> Log time ago (10/2014), there was an old thread around migrating ajax 
>>>>> from prototype to jquery as :
>>>>> - prototype is out of date
>>>>> - we « all » use jQuery to deal with ajax-front-end-requests
>>>>> 
>>>>> There was a link to the work made by johnny miller 
>>>>> https://github.com/johnnykahalawai/wonder
>>>>> 
>>>>> To deal with ajax-back-end-requests, we currently use :
>>>>> - AjaxModaDialog
>>>>> - AjaxUpdateContainer
>>>>> - AjaxUpdateLink
>>>>> - AjaxObserveField
>>>>> - AjaxSubmitButton
>>>>> - AjaxLongResponse
>>>>> 
>>>>> How do you deal with Ajax ? Still use wonder with prototype ? Any new 
>>>>> idea ?
>>>>> 
>>>>> Jérémy
>>>>> _______________________________________________
>>>>> Do not post admin requests to the list. They will be ignored.
>>>>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>>>>> Help/Unsubscribe/Update your Subscription:
>>>>> https://lists.apple.com/mailman/options/webobjects-dev/jtayler%40oeinc.com
>>>>> 
>>>>> This email sent to jtay...@oeinc.com
>>>> 
>>>> _______________________________________________
>>>> Do not post admin requests to the list. They will be ignored.
>>>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>>>> Help/Unsubscribe/Update your Subscription:
>>>> https://lists.apple.com/mailman/options/webobjects-dev/bock%40salient-doremus.de
>>>> 
>>>> This email sent to b...@salient-doremus.de
>>> 
>>> Mit freundlichen Grüßen 
>>> 
>>> René Bock
>>> 
>>> --
>>> Telefon: +49 69 650096 18
>>> 
>>> salient GmbH, Lindleystraße 12, 60314 Frankfurt
>>> Telefon Zentrale: 069 / 65 00 96 - 0  |  www.salient-doremus.de
>>> 
>> 
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
>> Help/Unsubscribe/Update your Subscription:
>> https://lists.apple.com/mailman/options/webobjects-dev/tedpet5%40yahoo.com
>> 
>> This email sent to tedp...@yahoo.com
> 

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to