On Feb 7, 2013, at 10:26 AM, Pascal Robert <[email protected]> wrote:
> > Le 2013-02-07 à 15:17, Johnny Miller <[email protected]> a écrit : > >> I didn't know that about Dojo. I believe Ember is built with JQuery. > > EmberJS is SproutCore 2.0. Yeah, I know but it still uses JQuery. > http://en.wikipedia.org/wiki/SproutCore > >> It seems like ERRest is the future for WO. > > It's part of the future. But if you need only REST services, you could use > Node.js, Cayenne with RestEasy, etc. It's ERRest + D2W that is the killing > stuff. > >> On Feb 7, 2013, at 10:10 AM, Pascal Robert <[email protected]> wrote: >> >>> >>> Le 2013-02-07 à 15:05, Johnny Miller <[email protected]> a écrit : >>> >>>> Hi, >>>> >>>> re: JQuery. I'm pretty bummed I worked on the MooTools framework instead >>>> of a JQuery one. Obviously, much more people are interested in JQuery. I >>>> keep thinking I'm going to start one but I've sort of made up my mind to >>>> limp through 2013 using MooTools and then switch over to something like >>>> EmberJS in 2014. If you haven't looked at EmberJS it is a lot like WO in >>>> that you define a model and then it handles the database updates (through >>>> a REST interface). >>> >>> Dojo has that too, and it doesn't look like that jQuery have that, or at >>> least it's not as "easy" as Dojo or EmberJS. >>> >>> We will have a ERRest lab at WOWODC and I think we should try to connect >>> many client-side JS, iOS and Android frameworks with ERRest to see if we >>> can improve ERRest to support a lot of REST clients. >>> >>>> One thing I would like to see is that we start using the template design >>>> pattern for the Ajax framework. A lot of the components don't need to be >>>> totally rewritten - you just need to override appendToResponse to format >>>> the HTML the right way for the JS framework. But you can't subclass the >>>> original component because it calls super in appendToResponse. So if >>>> appendToResponse called a method like fooBar and then when you subclass >>>> the component all you need to do is override fooBar and you don't have to >>>> work about the other methods like invokeAction/handleRequest etc... I >>>> basically ended up doing a bunch of copying and pasting but if something >>>> got improved in the original there is no guarantee it made it's way into >>>> the MooTools version. >>>> >>>> re: IDE - I wonder how much it would cost to get JetBrains or a JetBrain's >>>> plugin developer to create a WebObjects plugin? Having used their >>>> JavaScript editor it's become pretty obvious to me that they make a much >>>> better product. >>>> >>>> my 2 cents, >>>> >>>> Johnny >>>> >>>>> >>>>> - We need a jQuery framework. According to the surveys, members of the >>>>> community use jQuery almost as much as the Ajax framework from Wonder. In >>>>> fact, I'm wondering how you use it now, in Direct Actions? Just for >>>>> effects? If you already have a jQuery framework that you would like to >>>>> give to the community, we can work it out. >>>>> >>>>> - Better integration between WO and iOS (and Android). ERSync is a start, >>>>> and I was thinking maybe we could make a tool that reads a CoreData >>>>> model, convert it to a EOModel and automatically build REST services for >>>>> the model. >>>>> >>>>> - A "Project Wonder Cookbook". That book would contains, two pages max, >>>>> solutions to common problems and questions about Project Wonder. >>>>> >>>>> - Getting more people to understand and work on WOLips. >>>>> >>>>> - A easy-to-install development environment, that would install not only >>>>> WOLips and Eclipse, but also the core WO frameworks and Project Wonder. >>>>> >>>>> - A easy to use deployment service. Having helped many people with >>>>> deployment issues, it looks like deployment is still an issue. >>>>> >>>>> - Redesign of wocommunity.org. >>>>> >>>>> - Looking at how we can replace parts of WO with open source parts. The >>>>> Cayenne training day at WOWODC 2013 is the first step toward that goal. >>>>> >>>>> How are we going to finance this? We will change how the membership >>>>> works. We will have the following options: >>>>> >>>>> - $50 for regular membership. This $50 will be for paying recurrent >>>>> charges, like the hosting fees for wocommunity.org, and to pay for >>>>> deposits related to WOWODC. You still get early access to WOWODC >>>>> recordings. >>>>> >>>>> - $300 for Bronze Sponsorship. You get membership + your company logo on >>>>> wocommunity.org for 6 months (on rotation with other sponsors). >>>>> >>>>> - $750 for Silver Sponsorship. You get membership + your company logo on >>>>> wocommunity.org for 12 months (on rotation with other sponsors) and your >>>>> logo on the WOWODC site. >>>>> >>>>> - $1500 for Gold Sponsorship. You get membership + your company logo on >>>>> wocommunity.org for 12 months (no rotation) and your logo on the WOWODC >>>>> site. You also get one WOWODC 2013 ticket. >>>>> >>>>> For bigger tasks, like the jQuery framework and the Project Wonder >>>>> Cookbook, we will use Kickstarter or a similar system to raise money to >>>>> do it, and if we don't raise enough cash, the project simply dies. >>>>> >>>>> Comments about this? >>>>> >>>>> >>>>> _______________________________________________ >>>>> Do not post admin requests to the list. They will be ignored. >>>>> Webobjects-dev mailing list ([email protected]) >>>>> Help/Unsubscribe/Update your Subscription: >>>>> https://lists.apple.com/mailman/options/webobjects-dev/jlmiller%40kahalawai.com >>>>> >>>>> This email sent to [email protected] >>>> >>> >> > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
