Re: WOCommunity membership and goals / MontageJS
Thanks Chuck! Benoit On Apr 8, 2013, at 10:30 AM, Chuck Hill wrote: > Hi Benoit! > > It is looking good! > > For anyone else who had the old Tetsubo site bookmarked, here is where it now > lives: > http://montagejs.org/ > > > Chuck > > > > On 2013-04-07, at 5:09 PM, Benoit Marchant wrote: > >> Hi Guys, >> >> Sorry I have not been tracking this, Montage JS is alive and well! For those >> you knew about it's ancestor I did at Apple, well, it's even better! You >> probably figured out looking at it, it takes inspiration from both >> WebObjects for the Components as well as Cocoa for other patterns/API like >> data binding. >> >> For those of you who want to move more to the client side without going back >> to Cocoa/UIKit, there isn't a better choice ;-) ! >> >> Would love to get more feedback on the Google Group or IRC channel! >> >> Thanks, >> >> Benoit >> >> >> On Wed, Feb 13, 2013 at 3:46 PM, wrote: >> Anyone who went to WOWODC 2009 knows the origin of Montage. >> >> Envoyé de mon iPhone >> >> Le 2013-02-13 à 18:44, "Johnny Miller" a écrit : >> >>> Hi, >>> >>> The more I look at MontageJS the cooler it becomes. Are a lot of people >>> tracking this? I feel like WebObjects 6 came out and nobody told me. >>> >>> If you haven't seen it yet, check out their Fiddle page: >>> http://montagejs.github.com/mfiddle/#!/4163708 Look familiar? >>> >>> Johnny >>> >>> On Feb 9, 2013, at 1:47 PM, Johnny Miller wrote: >>> > Let me guess, based on MontageJS? Wow this is really cool! >>> >> >> ___ >> 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/marchant%40gmail.com >> >> This email sent to march...@gmail.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/chill%40global-village.net >> >> This email sent to ch...@global-village.net > > -- > Chuck Hill > Executive Managing Partner, VP Development and Technical Services > > Practical WebObjects - for developers who want to increase their overall > knowledge of WebObjects or who are trying to solve specific problems. > http://www.global-village.net/gvc/practical_webobjects > > Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest Growing > Companies in B.C! > Global Village Consulting ranks 76th in 24th annual PROFIT 200 ranking of > Canada’s Fastest-Growing Companies by PROFIT Magazine! > > > > > > > > > > > ___ 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
Re: WOCommunity membership and goals / MontageJS
On Feb 13, 2013, at 6:46 PM, prob...@macti.ca wrote: > Anyone who went to WOWODC 2009 knows the origin of Montage. .. It was shown at the WWDC too, in a small session that got people very excited. I never thought it would see the light of day. Thanks for drawing attention to it. (and this is not the place for it -- but it installs fine on my MB Air, not my MP Pro -- I'd happily go off-list to resolve it) .. Gavin ___ 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
Re: WOCommunity membership and goals / MontageJS
Hi Benoit! It is looking good! For anyone else who had the old Tetsubo site bookmarked, here is where it now lives: http://montagejs.org/ Chuck On 2013-04-07, at 5:09 PM, Benoit Marchant wrote: > Hi Guys, > > Sorry I have not been tracking this, Montage JS is alive and well! For those > you knew about it's ancestor I did at Apple, well, it's even better! You > probably figured out looking at it, it takes inspiration from both WebObjects > for the Components as well as Cocoa for other patterns/API like data binding. > > For those of you who want to move more to the client side without going back > to Cocoa/UIKit, there isn't a better choice ;-) ! > > Would love to get more feedback on the Google Group or IRC channel! > > Thanks, > > Benoit > > > On Wed, Feb 13, 2013 at 3:46 PM, wrote: > Anyone who went to WOWODC 2009 knows the origin of Montage. > > Envoyé de mon iPhone > > Le 2013-02-13 à 18:44, "Johnny Miller" a écrit : > >> Hi, >> >> The more I look at MontageJS the cooler it becomes. Are a lot of people >> tracking this? I feel like WebObjects 6 came out and nobody told me. >> >> If you haven't seen it yet, check out their Fiddle page: >> http://montagejs.github.com/mfiddle/#!/4163708 Look familiar? >> >> Johnny >> >> On Feb 9, 2013, at 1:47 PM, Johnny Miller wrote: >> >>> Let me guess, based on MontageJS? >>> >>> Wow this is really cool! >>> >> > > ___ > 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/marchant%40gmail.com > > This email sent to march...@gmail.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/chill%40global-village.net > > This email sent to ch...@global-village.net -- Chuck Hill Executive Managing Partner, VP Development and Technical Services Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/gvc/practical_webobjects Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest Growing Companies in B.C! Global Village Consulting ranks 76th in 24th annual PROFIT 200 ranking of Canada’s Fastest-Growing Companies by PROFIT Magazine! ___ 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
Re: WOCommunity membership and goals / MontageJS
Hi Guys, Sorry I have not been tracking this, Montage JS is alive and well! For those you knew about it's ancestor I did at Apple, well, it's even better! You probably figured out looking at it, it takes inspiration from both WebObjects for the Components as well as Cocoa for other patterns/API like data binding. For those of you who want to move more to the client side without going back to Cocoa/UIKit, there isn't a better choice ;-) ! Would love to get more feedback on the Google Group or IRC channel! Thanks, Benoit On Wed, Feb 13, 2013 at 3:46 PM, wrote: > Anyone who went to WOWODC 2009 knows the origin of Montage. > > Envoyé de mon iPhone > > Le 2013-02-13 à 18:44, "Johnny Miller" a écrit : > > Hi, > > The more I look at MontageJS the cooler it becomes. Are a lot of people > tracking this? I feel like WebObjects 6 came out and nobody told me. > > If you haven't seen it yet, check out their Fiddle page: > http://montagejs.github.com/mfiddle/#!/4163708 Look familiar? > > Johnny > > On Feb 9, 2013, at 1:47 PM, Johnny Miller wrote: > > > Let me guess, based on MontageJS? > > > Wow this is really cool! > > > > ___ > 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/marchant%40gmail.com > > This email sent to march...@gmail.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
Re: WOCommunity membership and goals / MontageJS
Anyone who went to WOWODC 2009 knows the origin of Montage. Envoyé de mon iPhone Le 2013-02-13 à 18:44, "Johnny Miller" a écrit : > Hi, > > The more I look at MontageJS the cooler it becomes. Are a lot of people > tracking this? I feel like WebObjects 6 came out and nobody told me. > > If you haven't seen it yet, check out their Fiddle page: > http://montagejs.github.com/mfiddle/#!/4163708 Look familiar? > > Johnny > > On Feb 9, 2013, at 1:47 PM, Johnny Miller wrote: > >> >>> Let me guess, based on MontageJS? >> >> Wow this is really cool! > ___ 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
Re: WOCommunity membership and goals / MontageJS
Hi, The more I look at MontageJS the cooler it becomes. Are a lot of people tracking this? I feel like WebObjects 6 came out and nobody told me. If you haven't seen it yet, check out their Fiddle page: http://montagejs.github.com/mfiddle/#!/4163708 Look familiar? Johnny On Feb 9, 2013, at 1:47 PM, Johnny Miller wrote: > >> Let me guess, based on MontageJS? > > Wow this is really cool! > ___ 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
Re: WOCommunity membership and goals
Le 2013-02-11 à 08:43, jazz a écrit : > Hi all, > > I was reading through the comments others made. For me two things are > important: > > 1. How to integrate WebObjects and iOS (mobile apps): client - server > communication without the use of Javascript frameworks on the client > 2. Easy setup and deployment like the good old Apple WebObjects > > Where do I fill in the survey? I missed that. Organization Survey: https://www.survs.com/survey/8ZOU47TJC4 Individual Survey: https://www.survs.com/survey/FNKGDKF361 ___ 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
Re: WOCommunity membership and goals
Hi all, I was reading through the comments others made. For me two things are important: 1. How to integrate WebObjects and iOS (mobile apps): client - server communication without the use of Javascript frameworks on the client 2. Easy setup and deployment like the good old Apple WebObjects Where do I fill in the survey? I missed that. Regards, Bart ___ 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
Re: WOCommunity membership and goals
> Let me guess, based on MontageJS? Wow this is really cool! ___ 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
Re: WOCommunity membership and goals
It would be wise to work on a tight integration of emberjs framework. Sent from my iPhone On Feb 9, 2013, at 7:55, doug andrews wrote: > I'd would do at least the regular membership fee. > > > On Feb 7, 2013, at 7:59 AM, Pascal Robert wrote: > >> Hello everyone, >> >> Based on the feedback we have so far in the surveys (if you haven't answered >> the 2013 surveys, please do it in the next 7 days), we established a list of >> goals for 2013: >> >> - 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 (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/dandrews%40mediaspansoftware.com >> >> This email sent to dandr...@mediaspansoftware.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/michael%40aspireauctions.com > > This email sent to mich...@aspireauctions.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
Re: WOCommunity membership and goals
I'd would do at least the regular membership fee. On Feb 7, 2013, at 7:59 AM, Pascal Robert wrote: > Hello everyone, > > Based on the feedback we have so far in the surveys (if you haven't answered > the 2013 surveys, please do it in the next 7 days), we established a list of > goals for 2013: > > - 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 (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/dandrews%40mediaspansoftware.com > > This email sent to dandr...@mediaspansoftware.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
Re: WOCommunity membership and goals
Mixing is no problem. We mix our JQuery Framework and wonder Ajax Framework every day, in all projects. Really No Problem. But you have to know how to do it. Ken On 2013/02/07, at 17:59, Matteo Centro wrote: > Speaking for my company, sometimes we are forced to use jQuery for some > things. > We try to do as much as possible with Ajax.framework (prototype) but some > things are simply not feasible without jQuery. We generally have use the two > mixed, which is sometimes a source for headaches. A nice thing would be to > have a port of the prototype Ajax.framework to jQuery but that's way beyond > our area of expertise, I can't even say if it's feasible. > > Matteo > > On 07/feb/2013, at 17:23, Pascal Robert wrote: > >> >> Le 2013-02-07 à 11:21, Musall Maik a écrit : >> >>> >>> Am 07.02.2013 um 16:58 schrieb Pascal Robert : >>> Le 2013-02-07 à 10:44, Johann Werner a écrit : > > Am 07.02.2013 um 16:12 schrieb James Cicenia : > >> I concur... a strong integration of WO with CoreData and Syncing, would >> be a really nice marketing hook too. Which could translate into more >> members! >> >> And yes, jQuery does have the momentum in the AJAX world. > > I see jQuery as an important option for Wonder though I am not sure if > its the best way to have a separate AjaxPrototype, AjaxJQuery, > AjaxMooTools, … framework which would make maintenance a nightmare if you > want to keep those feature equal. If I remember correctly long time ago > the idea to make some sort of Javascript API wrapper was already > discussed / proposed on the list to have only one single Ajax framework > and being able choose if you want to use prototype, jQuery or any other > supported JS library. > I already played with the thought to do some test code in that direction > though had not enough time yet. What do you think, is that something the > we should realize or does the community want a complete jQuery > replacement of the prototype framework? I'm curious about this too, because looking at the surveys, looks like most people use both jQuery and the Ajax framework: Ajax framework from Wonder 81% jQuery 69% Last year: Ajax framework from Wonder 69% jQuery 47% >>> >>> The survey was bit biased because it listed jQuery specifically but not moo >>> tools. >> >> This is why we have a "Other" option, and two organizations listed MooTools >> in "other". >> >>> I'm with Johann. We should have one server-side framework that supports the >>> main JS libs, or we'll be seeing more frameworks eventually make their way >>> into the "Archive" attic ;-) >>> >>> Maik >>> >>> >>> ___ >>> 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/probert%40macti.ca >>> >>> This email sent to prob...@macti.ca >> >> >> ___ >> 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/mcentro%40altera.it >> >> This email sent to mcen...@altera.it > > > ___ > 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/ken%40ksroom.com > > This email sent to k...@ksroom.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
Re: WOCommunity membership and goals
Le 2013-02-08 à 13:44, Amedeo Mantica a écrit : > > On 07/feb/2013, at 13:59, Pascal Robert wrote: > >> Hello everyone, >> >> Based on the feedback we have so far in the surveys (if you haven't answered >> the 2013 surveys, please do it in the next 7 days), we established a list of >> goals for 2013: >> >> - 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. > > I'm more for a WOCore.js that is totally disconnected from any existing js > framework (no conflicts), no animations/effects at all, just for ajax > request/response support (ie, get rid of prototype and made wo ajax full > html5 compilant), if you want effects you may plug your preferred js lib, and > use css effects too! Let me guess, based on MontageJS? >> >> - 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. > > Started > >> >> - 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. >> > > agree > >> 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? >> > > Amedeo > >> >> ___ >> 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/amedeomantica%40me.com >> >> This email sent to amedeomant...@me.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
Re: WOCommunity membership and goals
On 09/02/2013, at 9:47 AM, Chuck Hill wrote: > On 2013-02-08, at 10:44 AM, Amedeo Mantica wrote: > >> On 07/feb/2013, at 13:59, Pascal Robert wrote: >> >>> - 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. >> >> I'm more for a WOCore.js that is totally disconnected from any existing js >> framework (no conflicts), no animations/effects at all, just for ajax >> request/response support (ie, get rid of prototype and made wo ajax full >> html5 compilant), if you want effects you may plug your preferred js lib, >> and use css effects too! > > I like that idea. So do I. Is this something you've started on Amedeo? IMHO, this is the kind of thing we should think about passing the hat around to fund properly. -- Paul Hoadley http://logicsquad.net/ ___ 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
Re: WOCommunity membership and goals
On 2013-02-08, at 10:44 AM, Amedeo Mantica wrote: > > On 07/feb/2013, at 13:59, Pascal Robert wrote: > >> Hello everyone, >> >> Based on the feedback we have so far in the surveys (if you haven't answered >> the 2013 surveys, please do it in the next 7 days), we established a list of >> goals for 2013: >> >> - 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. > > I'm more for a WOCore.js that is totally disconnected from any existing js > framework (no conflicts), no animations/effects at all, just for ajax > request/response support (ie, get rid of prototype and made wo ajax full > html5 compilant), if you want effects you may plug your preferred js lib, and > use css effects too! I like that idea. Chuck > >> >> - 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. > > Started > >> >> - 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. >> > > agree > >> 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? >> > > Amedeo > >> >> ___ >> 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/amedeomantica%40me.com >> >> This email sent to amedeomant...@me.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/chill%40global-village.net > > This email sent to ch...@global-village.net -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/gvc/practical_webobjects Global Village Consulting ranks 13th in 2012 in BIV's Top 100 Fastest Growing Companies in B.C! Global Village Consulting ranks 76th in 24th annual PROFIT 200 ranking of Canada’s Fastest-Growing Companies by PROFIT Magazine! ___ 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
Re: WOCommunity membership and goals
On 07/feb/2013, at 13:59, Pascal Robert wrote: > Hello everyone, > > Based on the feedback we have so far in the surveys (if you haven't answered > the 2013 surveys, please do it in the next 7 days), we established a list of > goals for 2013: > > - 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. I'm more for a WOCore.js that is totally disconnected from any existing js framework (no conflicts), no animations/effects at all, just for ajax request/response support (ie, get rid of prototype and made wo ajax full html5 compilant), if you want effects you may plug your preferred js lib, and use css effects too! > > - 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. Started > > - 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. > agree > 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? > Amedeo > > ___ > 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/amedeomantica%40me.com > > This email sent to amedeomant...@me.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
Re: WOCommunity membership and goals
Hi Ramsey,
Am 07.02.2013 um 19:50 schrieb Ramsey Gurley :
> Maybe we should have some WOCommunity highlights or something. A monthly
> "Hey, check out this {framework | component | class}. Did you know ...?" sort
> of thing. Validation is one of these things. WO offers validation. Wonder
> improves it greatly. Everyone seems to make up their own anyway.
thats a really good idea. The old Project Wonder Blog was already doing a
little bit in this direction. What about creating a new blog where there are
one or two maintainers checking and coordinating articles that everyone can
contribute about a certain {framework | component | class}. Making this a
weekly/biweekly post with all those classes and components in Wonder we would
have material for the next couple of decades ;-) Those articles could even be
taken as the basis to create a more detailed documentation on the wiki.
jw
___
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
Re: WOCommunity membership and goals
Hi David, Am 08.02.2013 um 03:48 schrieb David LeBer : > On 2013-02-07, at 10:44 AM, Johann Werner wrote: > >> >> Am 07.02.2013 um 16:12 schrieb James Cicenia : >> >>> I concur... a strong integration of WO with CoreData and Syncing, would be >>> a really nice marketing hook too. Which could translate into more members! >>> >>> And yes, jQuery does have the momentum in the AJAX world. >> >> I see jQuery as an important option for Wonder though I am not sure if its >> the best way to have a separate AjaxPrototype, AjaxJQuery, AjaxMooTools, … >> framework which would make maintenance a nightmare if you want to keep those >> feature equal. If I remember correctly long time ago the idea to make some >> sort of Javascript API wrapper was already discussed / proposed on the list >> to have only one single Ajax framework and being able choose if you want to >> use prototype, jQuery or any other supported JS library. >> I already played with the thought to do some test code in that direction >> though had not enough time yet. What do you think, is that something the we >> should realize or does the community want a complete jQuery replacement of >> the prototype framework? > > Unfortunately there are impedance mismatches between Prototype/Scriptaculous > and JQuery (and I'm sure the other libraries) that makes it nearly impossible > (or at least highly undesirable) to make them drop in replaceable for one > another - or API identical for that matter. so you would suggest to follow the route of a "new" ajax framework that would replace the old one? > > I have a bunch of JQuery stuff that is implemented in a fairly unobtrusive JS > way. But I keep discovering stuff that necessitates me going back and > re-writing bunches of it. > > My plan has always been to contribute the bones once it is done. But getting > there is proving difficult. Looking forward to it :) > > D > >> >>> >>> >>> >>> On Feb 7, 2013, at 7:49 AM, Jesse Tayler wrote: >>> the future is mobile. getting a complete ERSync <---> iOS app with clearly readable demonstration code is an essential part of the future as it relates to mobile or other clients. I will certainly work with anyone to get to that point for all of us. JQuery, and continued AJAX and modern UI for the web is also a top priority it seems to me, however I can't offer much help there outside of cheering for those who can. here's to a WO 2013 everybody! On Feb 7, 2013, at 8:11 AM, Markus Ruggiero wrote: > > On 07.02.2013, at 13:59, Pascal Robert wrote: > >> Hello everyone, >> >> Based on the feedback we have so far in the surveys (if you haven't >> answered the 2013 surveys, please do it in the next 7 days), we >> established a list of goals for 2013: >> >> - 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. > +1 > >> - A "Project Wonder Cookbook". That book would contains, two pages max, >> solutions to common problems and questions about Project Wonder. > +10 > >> - Getting more people to understand and work on WOLips. > +1 > >> - A easy-to-install development environment, that would install not only >> WOLips and Eclipse, but also the core WO frameworks and Project Wonder. > +10 > >> - A easy to use deployment service. Having helped many people with >> deployment issues, it looks like deployment is still an issue. > +1 Ken Ishimoto's script might be a start > >> - 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. > I'll certainly buy a regular membership > >> - $300 for Bronze Sponsorship. You get membership + your company logo on >> wocommunity.org for 6 months (on rotation with other sponsors). >> >> -
Re: WOCommunity membership and goals
On 2013-02-07, at 10:44 AM, Johann Werner wrote: > > Am 07.02.2013 um 16:12 schrieb James Cicenia : > >> I concur... a strong integration of WO with CoreData and Syncing, would be a >> really nice marketing hook too. Which could translate into more members! >> >> And yes, jQuery does have the momentum in the AJAX world. > > I see jQuery as an important option for Wonder though I am not sure if its > the best way to have a separate AjaxPrototype, AjaxJQuery, AjaxMooTools, … > framework which would make maintenance a nightmare if you want to keep those > feature equal. If I remember correctly long time ago the idea to make some > sort of Javascript API wrapper was already discussed / proposed on the list > to have only one single Ajax framework and being able choose if you want to > use prototype, jQuery or any other supported JS library. > I already played with the thought to do some test code in that direction > though had not enough time yet. What do you think, is that something the we > should realize or does the community want a complete jQuery replacement of > the prototype framework? Unfortunately there are impedance mismatches between Prototype/Scriptaculous and JQuery (and I'm sure the other libraries) that makes it nearly impossible (or at least highly undesirable) to make them drop in replaceable for one another - or API identical for that matter. I have a bunch of JQuery stuff that is implemented in a fairly unobtrusive JS way. But I keep discovering stuff that necessitates me going back and re-writing bunches of it. My plan has always been to contribute the bones once it is done. But getting there is proving difficult. D > >> >> >> >> On Feb 7, 2013, at 7:49 AM, Jesse Tayler wrote: >> >>> >>> the future is mobile. >>> >>> getting a complete ERSync <---> iOS app with clearly readable demonstration >>> code is an essential part of the future as it relates to mobile or other >>> clients. >>> >>> I will certainly work with anyone to get to that point for all of us. >>> >>> JQuery, and continued AJAX and modern UI for the web is also a top priority >>> it seems to me, however I can't offer much help there outside of cheering >>> for those who can. >>> >>> here's to a WO 2013 everybody! >>> >>> >>> On Feb 7, 2013, at 8:11 AM, Markus Ruggiero >>> wrote: >>> On 07.02.2013, at 13:59, Pascal Robert wrote: > Hello everyone, > > Based on the feedback we have so far in the surveys (if you haven't > answered the 2013 surveys, please do it in the next 7 days), we > established a list of goals for 2013: > > - 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. +1 > - A "Project Wonder Cookbook". That book would contains, two pages max, > solutions to common problems and questions about Project Wonder. +10 > - Getting more people to understand and work on WOLips. +1 > - A easy-to-install development environment, that would install not only > WOLips and Eclipse, but also the core WO frameworks and Project Wonder. +10 > - A easy to use deployment service. Having helped many people with > deployment issues, it looks like deployment is still an issue. +1 Ken Ishimoto's script might be a start > - 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. I'll certainly buy a regular membership > - $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
Re: WOCommunity membership and goals
On Feb 7, 2013, at 10:26 AM, Pascal Robert wrote: > > Le 2013-02-07 à 15:17, Johnny Miller 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 wrote: >> >>> >>> Le 2013-02-07 à 15:05, Johnny Miller 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
Re: WOCommunity membership and goals
On Feb 7, 2013, at 10:19 AM, Chuck Hill wrote: > > On 2013-02-07, at 12:05 PM, Johnny Miller wrote: > >> 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). 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. > > Anjo put me onto this one, it looks pretty interesting: http://angularjs.org/ I've checked that one out too. It seems really easy to use. I'm kind of torn between which of the ones that makes the most sense for me. I'm planning on doing a wiki article on how to do the TODOS app with WO as a backend for both when my schedule quiets down. > >> 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. > > The Component Editor and Entity Modeler might be a lot of work! They do have Tapesty support built into the IDE. Which makes me think that they already would have a good idea on how to do it. > Chuck > > >>> >>> - 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 (Webobjects-dev@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev
Re: WOCommunity membership and goals
Le 2013-02-07 à 15:17, Johnny Miller a écrit : > I didn't know that about Dojo. I believe Ember is built with JQuery. EmberJS is SproutCore 2.0. 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 wrote: > >> >> Le 2013-02-07 à 15:05, Johnny Miller 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
Re: WOCommunity membership and goals
Le 2013-02-07 à 15:24, Theodore Petrosky a écrit : > Is there a problem with CentOS? I deploy at Rackspace with CentOS 6.3 and in > the office. I was actually going to play this weekend on a box at home. Fresh > install of Centos and try to create a developer box. (really just an exercise) It's just that CentOS have old stuff on it, it's not cutting edge. In fact, that's why I love it for deployment, because it's not full of new stuff that might not be stable and the RedHat people really make sure stuff works. > Ted > > > --- On Thu, 2/7/13, Pascal Robert wrote: > >> From: Pascal Robert >> Subject: Re: WOCommunity membership and goals >> To: "Bastian Triller" >> Cc: "WebObjects Development" >> Date: Thursday, February 7, 2013, 3:16 PM >>>> +1. And the OS X >> development package should be a .pkg so that it can be >> integrated in a workflow like ARD or other tools. >>>> >>> Are people out there developing on Debian/Ubuntu? >> >> I see some people in the survey who develop on Linux, but I >> didn't ask on which distribution (I assume either Fedora or >> Ubuntu, I don't think people would use CentOS for >> development). >> >> >> >> ___ >> 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
Re: WOCommunity membership and goals
Is there a problem with CentOS? I deploy at Rackspace with CentOS 6.3 and in the office. I was actually going to play this weekend on a box at home. Fresh install of Centos and try to create a developer box. (really just an exercise) Ted --- On Thu, 2/7/13, Pascal Robert wrote: > From: Pascal Robert > Subject: Re: WOCommunity membership and goals > To: "Bastian Triller" > Cc: "WebObjects Development" > Date: Thursday, February 7, 2013, 3:16 PM > > > +1. And the OS X > development package should be a .pkg so that it can be > integrated in a workflow like ARD or other tools. > > > > > Are people out there developing on Debian/Ubuntu? > > I see some people in the survey who develop on Linux, but I > didn't ask on which distribution (I assume either Fedora or > Ubuntu, I don't think people would use CentOS for > development). > > > > ___ > 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
Re: WOCommunity membership and goals
On 2013-02-07, at 12:05 PM, Johnny Miller wrote: > 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). 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. Anjo put me onto this one, it looks pretty interesting: http://angularjs.org/ > 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. The Component Editor and Entity Modeler might be a lot of work! Chuck >> >> - 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 (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/jlmiller%40kahalawai.com >> >> This email sent to jlmil...@kahalawai.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/chill%40global-village.net > > This email sent to ch...@global-village.net -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to incre
Re: WOCommunity membership and goals
I didn't know that about Dojo. I believe Ember is built with JQuery. It seems like ERRest is the future for WO. On Feb 7, 2013, at 10:10 AM, Pascal Robert wrote: > > Le 2013-02-07 à 15:05, Johnny Miller 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 (Webobjects-dev@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/jlmiller%40kahalawai.com >>> >>> This email sent to jlmil...@kahala
Re: WOCommunity membership and goals
> > +1. And the OS X development package should be a .pkg so that it can be > > integrated in a workflow like ARD or other tools. > > > Are people out there developing on Debian/Ubuntu? I see some people in the survey who develop on Linux, but I didn't ask on which distribution (I assume either Fedora or Ubuntu, I don't think people would use CentOS for development). ___ 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
Re: WOCommunity membership and goals
On Feb 7, 2013, at 11:01 AM, Pascal Robert wrote:
>
> Le 2013-02-07 à 13:50, Ramsey Gurley a écrit :
>
>>
>> On Feb 7, 2013, at 5:59 AM, Pascal Robert wrote:
>>
>>> Hello everyone,
>>>
>>> Based on the feedback we have so far in the surveys (if you haven't
>>> answered the 2013 surveys, please do it in the next 7 days), we established
>>> a list of goals for 2013:
>>>
>>> - 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.
>>
>>
>> We have a couple of these already. What's missing?
>
> That's the good question. Lot of people using jQuery, but I don't see any
> framework beside ERJQueryMobile.
My Ajax experience begins and ends with AjaxFramework and MooToolsFramework.
JQuery seems to be the flavor of the day though and I am interested in pursuing
it. I'm intrigued by Johann's suggestion.
>>> - 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.
>>
>>
>> I read this as Java Client for mobile.
>
> I don't think you like this idea :-P
>
>>
>>
>>> - A "Project Wonder Cookbook". That book would contains, two pages max,
>>> solutions to common problems and questions about Project Wonder.
>>
>>
>> I often observe that the biggest problem WO devs have isn't solving a
>> problem with WO/Wonder. Instead, I see is WO devs reinventing wheels.
>> Writing solutions for problems already covered by WO/Wonder.
>>
>> The frameworks are so big, people just don't realize what's in there and
>> come up with one off solutions that aren't as robust in the end.
>>
>> Maybe we should have some WOCommunity highlights or something. A monthly
>> "Hey, check out this {framework | component | class}. Did you know ...?"
>> sort of thing. Validation is one of these things. WO offers validation.
>> Wonder improves it greatly. Everyone seems to make up their own anyway.
>
> +100.
This is a great idea. At this point I often find myself replacement prior
constructs of my own with better implementations in Wonder. It would also be
great if devs who are rolling redundant stuff in-house could find themselves
using Wonder instead and even using those hours to improve it where needed. The
highlights thing could promote that.
>
>>
>>> - Getting more people to understand and work on WOLips.
>>
>>
>> That'll be tough. Q is our lifeline right now. Without him, I don't think
>> anyone would have updated WOLips for 4.2.
>>
>>
>>> - A easy-to-install development environment, that would install not only
>>> WOLips and Eclipse, but also the core WO frameworks and Project Wonder.
>>
>>
>> I've given up on this happening. There's too much to do for an installer and
>> its painful work without any direct benefit for the author who would need to
>> provide ongoing maintenance and support. It would need to install:
>>
>> Eclipse
>> WOLips
>> eGit/git
>> jadclipse
>> WebObjects
>> clone and import Wonder
>> Set up the wolips.properties
>> Apache
>> mod_webobjects
>>
>> And lots of these pieces update independently of the others. The getting
>> started guide on the wiki is pretty good. It just needs to include the
>> apache setup. I had a guy showing interest in WO here at work and he gave
>> up at Apache. I'm hoping he will get a second wind.
>
> Well, I guess less people bugs you about development tools and deployment
> than me :-) Yes, I do have less questions about development tools once the
> new wiki page was up, but it's still a pain for some people. But I must say
> that the #1 problem is: the incremental builder vs Ant.
>
> I still think that we need that WOLips ships as a Eclipse RCP app, just like
> most other IDEs based on Eclipse.
I agree with Ramsey that this is a ball of wax. Although, in my own experience,
a big chunk of this gets addressed with Golipse. I use it every time with great
success for installing the toolchain. WO - I use woinstaller.jar. Works great.
With Apache - we deal in web-based apps. You kinda gotta know how to configure
it. If we keep Golipse updated, that could be a big help.
>
>>> - A easy to use deployment service. Having helped many people with
>>> deployment issues, it looks like deployment is still an issue.
>>
>>
>> The linux stuff you are working on sounds promising. I haven't had a chance
>> to try them out yet, but it would be nice to be able to stay up to date on
>> java monitor and wotaskd with a package manager.
>
> +1. And the OS X development package should be a .pkg so that it can be
> integrated in a workflow like ARD or other tools.
I've used the yum
Re: WOCommunity membership and goals
Am 07.02.2013 20:02 schrieb "Pascal Robert" :
>
>
> Le 2013-02-07 à 13:50, Ramsey Gurley a écrit :
>
> >
> > On Feb 7, 2013, at 5:59 AM, Pascal Robert wrote:
> >
> >> Hello everyone,
> >>
> >> Based on the feedback we have so far in the surveys (if you haven't
answered the 2013 surveys, please do it in the next 7 days), we established
a list of goals for 2013:
> >>
> >> - 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.
> >
> >
> > We have a couple of these already. What's missing?
>
> That's the good question. Lot of people using jQuery, but I don't see any
framework beside ERJQueryMobile.
>
> >
> >> - 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.
> >
> >
> > I read this as Java Client for mobile.
>
> I don't think you like this idea :-P
>
> >
> >
> >> - A "Project Wonder Cookbook". That book would contains, two pages
max, solutions to common problems and questions about Project Wonder.
> >
> >
> > I often observe that the biggest problem WO devs have isn't solving a
problem with WO/Wonder. Instead, I see is WO devs reinventing wheels.
Writing solutions for problems already covered by WO/Wonder.
> >
> > The frameworks are so big, people just don't realize what's in there
and come up with one off solutions that aren't as robust in the end.
> >
> > Maybe we should have some WOCommunity highlights or something. A
monthly "Hey, check out this {framework | component | class}. Did you know
...?" sort of thing. Validation is one of these things. WO offers
validation. Wonder improves it greatly. Everyone seems to make up their own
anyway.
>
> +100.
>
> >
> >> - Getting more people to understand and work on WOLips.
> >
> >
> > That'll be tough. Q is our lifeline right now. Without him, I don't
think anyone would have updated WOLips for 4.2.
> >
> >
> >> - A easy-to-install development environment, that would install not
only WOLips and Eclipse, but also the core WO frameworks and Project Wonder.
> >
> >
> > I've given up on this happening. There's too much to do for an
installer and its painful work without any direct benefit for the author
who would need to provide ongoing maintenance and support. It would need
to install:
> >
> > Eclipse
> > WOLips
> > eGit/git
> > jadclipse
> > WebObjects
> > clone and import Wonder
> > Set up the wolips.properties
> > Apache
> > mod_webobjects
> >
> > And lots of these pieces update independently of the others. The
getting started guide on the wiki is pretty good. It just needs to include
the apache setup. I had a guy showing interest in WO here at work and he
gave up at Apache. I'm hoping he will get a second wind.
>
> Well, I guess less people bugs you about development tools and deployment
than me :-) Yes, I do have less questions about development tools once the
new wiki page was up, but it's still a pain for some people. But I must say
that the #1 problem is: the incremental builder vs Ant.
>
> I still think that we need that WOLips ships as a Eclipse RCP app, just
like most other IDEs based on Eclipse.
>
> >> - A easy to use deployment service. Having helped many people with
deployment issues, it looks like deployment is still an issue.
> >
> >
> > The linux stuff you are working on sounds promising. I haven't had a
chance to try them out yet, but it would be nice to be able to stay up to
date on java monitor and wotaskd with a package manager.
>
> +1. And the OS X development package should be a .pkg so that it can be
integrated in a workflow like ARD or other tools.
>
Are people out there developing on Debian/Ubuntu?
> >> - Redesign of wocommunity.org.
> >
> >
> > I think wocommunity.org does the job just fine as is. What are you
wanting to redesign?
>
> It's so 2008. I see lots of comments on Twitter about how WO is outdated,
etc., and I don't think it helps that our site looks old too.
>
> >
> >> - 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.
> >
> >
> > Keeping my comments to myself :-)
> >
> >
> >> 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 mem
Re: WOCommunity membership and goals
Am 07.02.2013 20:02 schrieb "Pascal Robert" :
>
>
> Le 2013-02-07 à 13:50, Ramsey Gurley a écrit :
>
> >
> > On Feb 7, 2013, at 5:59 AM, Pascal Robert wrote:
> >
> >> Hello everyone,
> >>
> >> Based on the feedback we have so far in the surveys (if you haven't
answered the 2013 surveys, please do it in the next 7 days), we established
a list of goals for 2013:
> >>
> >> - 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.
> >
> >
> > We have a couple of these already. What's missing?
>
> That's the good question. Lot of people using jQuery, but I don't see any
framework beside ERJQueryMobile.
>
> >
> >> - 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.
> >
> >
> > I read this as Java Client for mobile.
>
> I don't think you like this idea :-P
>
> >
> >
> >> - A "Project Wonder Cookbook". That book would contains, two pages
max, solutions to common problems and questions about Project Wonder.
> >
> >
> > I often observe that the biggest problem WO devs have isn't solving a
problem with WO/Wonder. Instead, I see is WO devs reinventing wheels.
Writing solutions for problems already covered by WO/Wonder.
> >
> > The frameworks are so big, people just don't realize what's in there
and come up with one off solutions that aren't as robust in the end.
> >
> > Maybe we should have some WOCommunity highlights or something. A
monthly "Hey, check out this {framework | component | class}. Did you know
...?" sort of thing. Validation is one of these things. WO offers
validation. Wonder improves it greatly. Everyone seems to make up their own
anyway.
>
> +100.
>
> >
> >> - Getting more people to understand and work on WOLips.
> >
> >
> > That'll be tough. Q is our lifeline right now. Without him, I don't
think anyone would have updated WOLips for 4.2.
> >
> >
> >> - A easy-to-install development environment, that would install not
only WOLips and Eclipse, but also the core WO frameworks and Project Wonder.
> >
> >
> > I've given up on this happening. There's too much to do for an
installer and its painful work without any direct benefit for the author
who would need to provide ongoing maintenance and support. It would need
to install:
> >
> > Eclipse
> > WOLips
> > eGit/git
> > jadclipse
> > WebObjects
> > clone and import Wonder
> > Set up the wolips.properties
> > Apache
> > mod_webobjects
> >
> > And lots of these pieces update independently of the others. The
getting started guide on the wiki is pretty good. It just needs to include
the apache setup. I had a guy showing interest in WO here at work and he
gave up at Apache. I'm hoping he will get a second wind.
>
> Well, I guess less people bugs you about development tools and deployment
than me :-) Yes, I do have less questions about development tools once the
new wiki page was up, but it's still a pain for some people. But I must say
that the #1 problem is: the incremental builder vs Ant.
>
> I still think that we need that WOLips ships as a Eclipse RCP app, just
like most other IDEs based on Eclipse.
>
> >> - A easy to use deployment service. Having helped many people with
deployment issues, it looks like deployment is still an issue.
> >
> >
> > The linux stuff you are working on sounds promising. I haven't had a
chance to try them out yet, but it would be nice to be able to stay up to
date on java monitor and wotaskd with a package manager.
>
> +1. And the OS X development package should be a .pkg so that it can be
integrated in a workflow like ARD or other tools.
>
Are people out there developing on Debian/Ubuntu?
> >> - Redesign of wocommunity.org.
> >
> >
> > I think wocommunity.org does the job just fine as is. What are you
wanting to redesign?
>
> It's so 2008. I see lots of comments on Twitter about how WO is outdated,
etc., and I don't think it helps that our site looks old too.
>
> >
> >> - 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.
> >
> >
> > Keeping my comments to myself :-)
> >
> >
> >> 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 mem
Re: WOCommunity membership and goals
Le 2013-02-07 à 15:05, Johnny Miller 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 (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/jlmiller%40kahalawai.com >> >> This email sent to jlmil...@kahalawai.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/arc
Re: WOCommunity membership and goals
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). 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 (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/jlmiller%40kahalawai.com > > This email sent to jlmil...@kahalawai.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
Re: WOCommunity membership and goals
Le 2013-02-07 à 13:50, Ramsey Gurley a écrit :
>
> On Feb 7, 2013, at 5:59 AM, Pascal Robert wrote:
>
>> Hello everyone,
>>
>> Based on the feedback we have so far in the surveys (if you haven't answered
>> the 2013 surveys, please do it in the next 7 days), we established a list of
>> goals for 2013:
>>
>> - 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.
>
>
> We have a couple of these already. What's missing?
That's the good question. Lot of people using jQuery, but I don't see any
framework beside ERJQueryMobile.
>
>> - 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.
>
>
> I read this as Java Client for mobile.
I don't think you like this idea :-P
>
>
>> - A "Project Wonder Cookbook". That book would contains, two pages max,
>> solutions to common problems and questions about Project Wonder.
>
>
> I often observe that the biggest problem WO devs have isn't solving a problem
> with WO/Wonder. Instead, I see is WO devs reinventing wheels. Writing
> solutions for problems already covered by WO/Wonder.
>
> The frameworks are so big, people just don't realize what's in there and come
> up with one off solutions that aren't as robust in the end.
>
> Maybe we should have some WOCommunity highlights or something. A monthly
> "Hey, check out this {framework | component | class}. Did you know ...?" sort
> of thing. Validation is one of these things. WO offers validation. Wonder
> improves it greatly. Everyone seems to make up their own anyway.
+100.
>
>> - Getting more people to understand and work on WOLips.
>
>
> That'll be tough. Q is our lifeline right now. Without him, I don't think
> anyone would have updated WOLips for 4.2.
>
>
>> - A easy-to-install development environment, that would install not only
>> WOLips and Eclipse, but also the core WO frameworks and Project Wonder.
>
>
> I've given up on this happening. There's too much to do for an installer and
> its painful work without any direct benefit for the author who would need to
> provide ongoing maintenance and support. It would need to install:
>
> Eclipse
> WOLips
> eGit/git
> jadclipse
> WebObjects
> clone and import Wonder
> Set up the wolips.properties
> Apache
> mod_webobjects
>
> And lots of these pieces update independently of the others. The getting
> started guide on the wiki is pretty good. It just needs to include the apache
> setup. I had a guy showing interest in WO here at work and he gave up at
> Apache. I'm hoping he will get a second wind.
Well, I guess less people bugs you about development tools and deployment than
me :-) Yes, I do have less questions about development tools once the new wiki
page was up, but it's still a pain for some people. But I must say that the #1
problem is: the incremental builder vs Ant.
I still think that we need that WOLips ships as a Eclipse RCP app, just like
most other IDEs based on Eclipse.
>> - A easy to use deployment service. Having helped many people with
>> deployment issues, it looks like deployment is still an issue.
>
>
> The linux stuff you are working on sounds promising. I haven't had a chance
> to try them out yet, but it would be nice to be able to stay up to date on
> java monitor and wotaskd with a package manager.
+1. And the OS X development package should be a .pkg so that it can be
integrated in a workflow like ARD or other tools.
>> - Redesign of wocommunity.org.
>
>
> I think wocommunity.org does the job just fine as is. What are you wanting to
> redesign?
It's so 2008. I see lots of comments on Twitter about how WO is outdated, etc.,
and I don't think it helps that our site looks old too.
>
>> - 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.
>
>
> Keeping my comments to myself :-)
>
>
>> 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
>> log
Re: WOCommunity membership and goals
On Feb 7, 2013, at 5:59 AM, Pascal Robert wrote:
> Hello everyone,
>
> Based on the feedback we have so far in the surveys (if you haven't answered
> the 2013 surveys, please do it in the next 7 days), we established a list of
> goals for 2013:
>
> - 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.
We have a couple of these already. What's missing?
> - 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.
I read this as Java Client for mobile.
> - A "Project Wonder Cookbook". That book would contains, two pages max,
> solutions to common problems and questions about Project Wonder.
I often observe that the biggest problem WO devs have isn't solving a problem
with WO/Wonder. Instead, I see is WO devs reinventing wheels. Writing solutions
for problems already covered by WO/Wonder.
The frameworks are so big, people just don't realize what's in there and come
up with one off solutions that aren't as robust in the end.
Maybe we should have some WOCommunity highlights or something. A monthly "Hey,
check out this {framework | component | class}. Did you know ...?" sort of
thing. Validation is one of these things. WO offers validation. Wonder improves
it greatly. Everyone seems to make up their own anyway.
> - Getting more people to understand and work on WOLips.
That'll be tough. Q is our lifeline right now. Without him, I don't think
anyone would have updated WOLips for 4.2.
> - A easy-to-install development environment, that would install not only
> WOLips and Eclipse, but also the core WO frameworks and Project Wonder.
I've given up on this happening. There's too much to do for an installer and
its painful work without any direct benefit for the author who would need to
provide ongoing maintenance and support. It would need to install:
Eclipse
WOLips
eGit/git
jadclipse
WebObjects
clone and import Wonder
Set up the wolips.properties
Apache
mod_webobjects
And lots of these pieces update independently of the others. The getting
started guide on the wiki is pretty good. It just needs to include the apache
setup. I had a guy showing interest in WO here at work and he gave up at
Apache. I'm hoping he will get a second wind.
> - A easy to use deployment service. Having helped many people with deployment
> issues, it looks like deployment is still an issue.
The linux stuff you are working on sounds promising. I haven't had a chance to
try them out yet, but it would be nice to be able to stay up to date on java
monitor and wotaskd with a package manager.
> - Redesign of wocommunity.org.
I think wocommunity.org does the job just fine as is. What are you wanting to
redesign?
> - 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.
Keeping my comments to myself :-)
> 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.
A nice flyer or something I could hand to/forward to my boss would be good
here. We are suffering a shortage of WO devs currently, so maybe pitch it as a
way to get more exposure with developers might help. As someone else mentioned,
it would be even better if it were tax deductible and mentioned that
specifically.
>
> 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 (Webobjects-dev@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://list
Re: WOCommunity membership and goals
Speaking for my company, sometimes we are forced to use jQuery for some things. We try to do as much as possible with Ajax.framework (prototype) but some things are simply not feasible without jQuery. We generally have use the two mixed, which is sometimes a source for headaches. A nice thing would be to have a port of the prototype Ajax.framework to jQuery but that's way beyond our area of expertise, I can't even say if it's feasible. Matteo On 07/feb/2013, at 17:23, Pascal Robert wrote: > > Le 2013-02-07 à 11:21, Musall Maik a écrit : > >> >> Am 07.02.2013 um 16:58 schrieb Pascal Robert : >> >>> >>> Le 2013-02-07 à 10:44, Johann Werner a écrit : >>> Am 07.02.2013 um 16:12 schrieb James Cicenia : > I concur... a strong integration of WO with CoreData and Syncing, would > be a really nice marketing hook too. Which could translate into more > members! > > And yes, jQuery does have the momentum in the AJAX world. I see jQuery as an important option for Wonder though I am not sure if its the best way to have a separate AjaxPrototype, AjaxJQuery, AjaxMooTools, … framework which would make maintenance a nightmare if you want to keep those feature equal. If I remember correctly long time ago the idea to make some sort of Javascript API wrapper was already discussed / proposed on the list to have only one single Ajax framework and being able choose if you want to use prototype, jQuery or any other supported JS library. I already played with the thought to do some test code in that direction though had not enough time yet. What do you think, is that something the we should realize or does the community want a complete jQuery replacement of the prototype framework? >>> >>> I'm curious about this too, because looking at the surveys, looks like most >>> people use both jQuery and the Ajax framework: >>> >>> Ajax framework from Wonder 81% >>> jQuery 69% >>> >>> Last year: >>> >>> Ajax framework from Wonder 69% >>> jQuery 47% >> >> The survey was bit biased because it listed jQuery specifically but not moo >> tools. > > This is why we have a "Other" option, and two organizations listed MooTools > in "other". > >> I'm with Johann. We should have one server-side framework that supports the >> main JS libs, or we'll be seeing more frameworks eventually make their way >> into the "Archive" attic ;-) >> >> Maik >> >> >> ___ >> 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/probert%40macti.ca >> >> This email sent to prob...@macti.ca > > > ___ > 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/mcentro%40altera.it > > This email sent to mcen...@altera.it ___ 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
Re: WOCommunity membership and goals
Le 2013-02-07 à 11:21, Musall Maik a écrit : > > Am 07.02.2013 um 16:58 schrieb Pascal Robert : > >> >> Le 2013-02-07 à 10:44, Johann Werner a écrit : >> >>> >>> Am 07.02.2013 um 16:12 schrieb James Cicenia : >>> I concur... a strong integration of WO with CoreData and Syncing, would be a really nice marketing hook too. Which could translate into more members! And yes, jQuery does have the momentum in the AJAX world. >>> >>> I see jQuery as an important option for Wonder though I am not sure if its >>> the best way to have a separate AjaxPrototype, AjaxJQuery, AjaxMooTools, … >>> framework which would make maintenance a nightmare if you want to keep >>> those feature equal. If I remember correctly long time ago the idea to make >>> some sort of Javascript API wrapper was already discussed / proposed on the >>> list to have only one single Ajax framework and being able choose if you >>> want to use prototype, jQuery or any other supported JS library. >>> I already played with the thought to do some test code in that direction >>> though had not enough time yet. What do you think, is that something the we >>> should realize or does the community want a complete jQuery replacement of >>> the prototype framework? >> >> I'm curious about this too, because looking at the surveys, looks like most >> people use both jQuery and the Ajax framework: >> >> Ajax framework from Wonder 81% >> jQuery 69% >> >> Last year: >> >> Ajax framework from Wonder 69% >> jQuery 47% > > The survey was bit biased because it listed jQuery specifically but not moo > tools. This is why we have a "Other" option, and two organizations listed MooTools in "other". > I'm with Johann. We should have one server-side framework that supports the > main JS libs, or we'll be seeing more frameworks eventually make their way > into the "Archive" attic ;-) > > Maik > > > ___ > 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/probert%40macti.ca > > This email sent to prob...@macti.ca ___ 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
Re: WOCommunity membership and goals
Am 07.02.2013 um 16:58 schrieb Pascal Robert : > > Le 2013-02-07 à 10:44, Johann Werner a écrit : > >> >> Am 07.02.2013 um 16:12 schrieb James Cicenia : >> >>> I concur... a strong integration of WO with CoreData and Syncing, would be >>> a really nice marketing hook too. Which could translate into more members! >>> >>> And yes, jQuery does have the momentum in the AJAX world. >> >> I see jQuery as an important option for Wonder though I am not sure if its >> the best way to have a separate AjaxPrototype, AjaxJQuery, AjaxMooTools, … >> framework which would make maintenance a nightmare if you want to keep those >> feature equal. If I remember correctly long time ago the idea to make some >> sort of Javascript API wrapper was already discussed / proposed on the list >> to have only one single Ajax framework and being able choose if you want to >> use prototype, jQuery or any other supported JS library. >> I already played with the thought to do some test code in that direction >> though had not enough time yet. What do you think, is that something the we >> should realize or does the community want a complete jQuery replacement of >> the prototype framework? > > I'm curious about this too, because looking at the surveys, looks like most > people use both jQuery and the Ajax framework: > > Ajax framework from Wonder81% > jQuery69% > > Last year: > > Ajax framework from Wonder69% > jQuery47% The survey was bit biased because it listed jQuery specifically but not mootools. I'm with Johann. We should have one server-side framework that supports the main JS libs, or we'll be seeing more frameworks eventually make their way into the "Archive" attic ;-) Maik ___ 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
Re: WOCommunity membership and goals
Le 2013-02-07 à 10:44, Johann Werner a écrit : > > Am 07.02.2013 um 16:12 schrieb James Cicenia : > >> I concur... a strong integration of WO with CoreData and Syncing, would be a >> really nice marketing hook too. Which could translate into more members! >> >> And yes, jQuery does have the momentum in the AJAX world. > > I see jQuery as an important option for Wonder though I am not sure if its > the best way to have a separate AjaxPrototype, AjaxJQuery, AjaxMooTools, … > framework which would make maintenance a nightmare if you want to keep those > feature equal. If I remember correctly long time ago the idea to make some > sort of Javascript API wrapper was already discussed / proposed on the list > to have only one single Ajax framework and being able choose if you want to > use prototype, jQuery or any other supported JS library. > I already played with the thought to do some test code in that direction > though had not enough time yet. What do you think, is that something the we > should realize or does the community want a complete jQuery replacement of > the prototype framework? I'm curious about this too, because looking at the surveys, looks like most people use both jQuery and the Ajax framework: Ajax framework from Wonder 81% jQuery 69% Last year: Ajax framework from Wonder 69% jQuery 47% >> >> >> >> On Feb 7, 2013, at 7:49 AM, Jesse Tayler wrote: >> >>> >>> the future is mobile. >>> >>> getting a complete ERSync <---> iOS app with clearly readable demonstration >>> code is an essential part of the future as it relates to mobile or other >>> clients. >>> >>> I will certainly work with anyone to get to that point for all of us. >>> >>> JQuery, and continued AJAX and modern UI for the web is also a top priority >>> it seems to me, however I can't offer much help there outside of cheering >>> for those who can. >>> >>> here's to a WO 2013 everybody! >>> >>> >>> On Feb 7, 2013, at 8:11 AM, Markus Ruggiero >>> wrote: >>> On 07.02.2013, at 13:59, Pascal Robert wrote: > Hello everyone, > > Based on the feedback we have so far in the surveys (if you haven't > answered the 2013 surveys, please do it in the next 7 days), we > established a list of goals for 2013: > > - 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. +1 > - A "Project Wonder Cookbook". That book would contains, two pages max, > solutions to common problems and questions about Project Wonder. +10 > - Getting more people to understand and work on WOLips. +1 > - A easy-to-install development environment, that would install not only > WOLips and Eclipse, but also the core WO frameworks and Project Wonder. +10 > - A easy to use deployment service. Having helped many people with > deployment issues, it looks like deployment is still an issue. +1 Ken Ishimoto's script might be a start > - 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. I'll certainly buy a regular membership > - $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.
Re: WOCommunity membership and goals
Am 07.02.2013 um 16:12 schrieb James Cicenia : > I concur... a strong integration of WO with CoreData and Syncing, would be a > really nice marketing hook too. Which could translate into more members! > > And yes, jQuery does have the momentum in the AJAX world. I see jQuery as an important option for Wonder though I am not sure if its the best way to have a separate AjaxPrototype, AjaxJQuery, AjaxMooTools, … framework which would make maintenance a nightmare if you want to keep those feature equal. If I remember correctly long time ago the idea to make some sort of Javascript API wrapper was already discussed / proposed on the list to have only one single Ajax framework and being able choose if you want to use prototype, jQuery or any other supported JS library. I already played with the thought to do some test code in that direction though had not enough time yet. What do you think, is that something the we should realize or does the community want a complete jQuery replacement of the prototype framework? > > > > On Feb 7, 2013, at 7:49 AM, Jesse Tayler wrote: > >> >> the future is mobile. >> >> getting a complete ERSync <---> iOS app with clearly readable demonstration >> code is an essential part of the future as it relates to mobile or other >> clients. >> >> I will certainly work with anyone to get to that point for all of us. >> >> JQuery, and continued AJAX and modern UI for the web is also a top priority >> it seems to me, however I can't offer much help there outside of cheering >> for those who can. >> >> here's to a WO 2013 everybody! >> >> >> On Feb 7, 2013, at 8:11 AM, Markus Ruggiero >> wrote: >> >>> >>> On 07.02.2013, at 13:59, Pascal Robert wrote: >>> Hello everyone, Based on the feedback we have so far in the surveys (if you haven't answered the 2013 surveys, please do it in the next 7 days), we established a list of goals for 2013: - 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. >>> +1 >>> - A "Project Wonder Cookbook". That book would contains, two pages max, solutions to common problems and questions about Project Wonder. >>> +10 >>> - Getting more people to understand and work on WOLips. >>> +1 >>> - A easy-to-install development environment, that would install not only WOLips and Eclipse, but also the core WO frameworks and Project Wonder. >>> +10 >>> - A easy to use deployment service. Having helped many people with deployment issues, it looks like deployment is still an issue. >>> +1 Ken Ishimoto's script might be a start >>> - 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. >>> I'll certainly buy a regular membership >>> - $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 (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/mailinglists%40kataputt.com This email sent to mailingli...@kataputt.com >
Re: WOCommunity membership and goals
I concur... a strong integration of WO with CoreData and Syncing, would be a really nice marketing hook too. Which could translate into more members! And yes, jQuery does have the momentum in the AJAX world. On Feb 7, 2013, at 7:49 AM, Jesse Tayler wrote: > > the future is mobile. > > getting a complete ERSync <---> iOS app with clearly readable demonstration > code is an essential part of the future as it relates to mobile or other > clients. > > I will certainly work with anyone to get to that point for all of us. > > JQuery, and continued AJAX and modern UI for the web is also a top priority > it seems to me, however I can't offer much help there outside of cheering for > those who can. > > here's to a WO 2013 everybody! > > > On Feb 7, 2013, at 8:11 AM, Markus Ruggiero wrote: > >> >> On 07.02.2013, at 13:59, Pascal Robert wrote: >> >>> Hello everyone, >>> >>> Based on the feedback we have so far in the surveys (if you haven't >>> answered the 2013 surveys, please do it in the next 7 days), we established >>> a list of goals for 2013: >>> >>> - 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. >> +1 >> >>> - A "Project Wonder Cookbook". That book would contains, two pages max, >>> solutions to common problems and questions about Project Wonder. >> +10 >> >>> - Getting more people to understand and work on WOLips. >> +1 >> >>> - A easy-to-install development environment, that would install not only >>> WOLips and Eclipse, but also the core WO frameworks and Project Wonder. >> +10 >> >>> - A easy to use deployment service. Having helped many people with >>> deployment issues, it looks like deployment is still an issue. >> +1 Ken Ishimoto's script might be a start >> >>> - 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. >> I'll certainly buy a regular membership >> >>> - $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 (Webobjects-dev@lists.apple.com) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/mailinglists%40kataputt.com >>> >>> This email sent to mailingli...@kataputt.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/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/james%40jimijon.com > > This email sent to ja...@jimijon.com James Cicenia Founder / CEO Direct: (773) 398-4649 Mail: ja...@jimijon.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev m
Re: WOCommunity membership and goals
the future is mobile. getting a complete ERSync <---> iOS app with clearly readable demonstration code is an essential part of the future as it relates to mobile or other clients. I will certainly work with anyone to get to that point for all of us. JQuery, and continued AJAX and modern UI for the web is also a top priority it seems to me, however I can't offer much help there outside of cheering for those who can. here's to a WO 2013 everybody! On Feb 7, 2013, at 8:11 AM, Markus Ruggiero wrote: > > On 07.02.2013, at 13:59, Pascal Robert wrote: > >> Hello everyone, >> >> Based on the feedback we have so far in the surveys (if you haven't answered >> the 2013 surveys, please do it in the next 7 days), we established a list of >> goals for 2013: >> >> - 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. > +1 > >> - A "Project Wonder Cookbook". That book would contains, two pages max, >> solutions to common problems and questions about Project Wonder. > +10 > >> - Getting more people to understand and work on WOLips. > +1 > >> - A easy-to-install development environment, that would install not only >> WOLips and Eclipse, but also the core WO frameworks and Project Wonder. > +10 > >> - A easy to use deployment service. Having helped many people with >> deployment issues, it looks like deployment is still an issue. > +1 Ken Ishimoto's script might be a start > >> - 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. > I'll certainly buy a regular membership > >> - $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 (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/mailinglists%40kataputt.com >> >> This email sent to mailingli...@kataputt.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/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/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: WOCommunity membership and goals
On 07.02.2013, at 13:59, Pascal Robert wrote: > Hello everyone, > > Based on the feedback we have so far in the surveys (if you haven't answered > the 2013 surveys, please do it in the next 7 days), we established a list of > goals for 2013: > > - 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. +1 > - A "Project Wonder Cookbook". That book would contains, two pages max, > solutions to common problems and questions about Project Wonder. +10 > - Getting more people to understand and work on WOLips. +1 > - A easy-to-install development environment, that would install not only > WOLips and Eclipse, but also the core WO frameworks and Project Wonder. +10 > - A easy to use deployment service. Having helped many people with deployment > issues, it looks like deployment is still an issue. +1 Ken Ishimoto's script might be a start > - 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. I'll certainly buy a regular membership > - $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 (Webobjects-dev@lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/mailinglists%40kataputt.com > > This email sent to mailingli...@kataputt.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
WOCommunity membership and goals
Hello everyone, Based on the feedback we have so far in the surveys (if you haven't answered the 2013 surveys, please do it in the next 7 days), we established a list of goals for 2013: - 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 (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
