Rép : Ajax Update Link not working on one server
Hi Jeff,Can I know which component of wonder did you used for our datagrid?Thanks a lotEnvoyé depuis iCloudLe 06 fév 2013 à 05:04, Jeffrey Schmitz j...@netbrackets.com a écrit :Hi all, I'm using the Wonder Ajax constructs and on one of my servers my AjaxUpdateLinks have stopped working. Comparing the same page on two different servers, one that works and one that doesn't. Texamples of working vs not working, can be found at the following links. First, choose 5 Entries per page, and then click the next page button.Doesn't work:http://208.52.189.43/cgi-bin/WebObjects/netBrackets.woa/wa/demoPoolStatusworks:http://24.217.161.112/cgi-bin/WebObjects/netBrackets.woa/wa/demoPoolStatusThe html being generated on each machine is as follows:Doesn't work:a href="" _onclick_="AUL.update('tableBody', {onComplete:function(request) { }}, '3.0.19.13.41.9');" class="right" img src="" width="16" height="16" alt="First Page" /aworks:a href="" _onclick_="AUL.update('tableBody', {onComplete:function(request) { }}, '3.0.19.13.41.9');" class="right" img src="" width="16" height="16" alt="First Page" /aThis is the code being used to generate the above...webobjectname="NextBatch"imgsrc="/Images/TinyTable/next.gif"width="16"height="16"alt="First Page"//webobjectNextBatch:AjaxUpdateLink{action=nextBatch;updateContainerID="tableBody";evalScripts=true;onComplete="function(request) { }";}Note that the below AjaxObserveField construct is still working correctly on both machines.AOF html:div id="perpage"select id="EntriesPerPageID" name="0.19.29.1.1.25"option selected="selected" value="0"5/optionoption value="1"10/optionoption value="2"20/optionoption value="3"50/optionoption value="4"100/option/select spanEntries Per Page/span/divAOF code: divid="perpage" webobjectname="EntriesPerPage"/ webobjectname="EntriesPerPageObserveField"/ spanEntries Per Page/span /divEntriesPerPage:WOPopUpButton{id="EntriesPerPageID";list=numEntriesList;item=repetitionNumEntries;selection=selectedNumEntries;displayString=repetitionNumEntries;}EntriesPerPageObserveField:AjaxObserveField{observeFieldID="EntriesPerPageID";updateContainerID="tableBody";fullSubmit=false;}Any ideas where I might look to track this down?Thanks,Jeff___ 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/rnaneon%40me.com This email sent to rnan...@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: 2dim excel for 1:m relationship problem
On 06.02.2013, at 19:38, Ramsey Gurley rgur...@smarthealth.com wrote: May I begin by saying: That design sucks :-P If there's one really big 'n' and a bunch of really small 'n's, the customer going to waste a ton of paper. Plus, long text in a narrow column? Srsly?? ZOMG, I want to die noa! Well, no, it doesn't. This is actually a n by m matrix and being able to see this matrix is a very good thing. And it is certainly not my job to tell the customer not to print. But you have not seen the rest of the model, THAT is crap all over. This started out as a D2W app created by some JEE folks combining raw JDBC calls with what they thought is WebObjects and D2W. While I have taken over this baby it started to grow almost uncontrollably. I have already thrown out the JEE and JDBC stuff and about 30 custom D2W page components. Anyway. I have to deal with this and slowly try to fix and clean up things. Don't let them design. They don't know what they're doing. Let them tell you the requirements and you do the design ;-) I know they don't - and what they know changes by the hour. There are no requirements, they just work with the stuff and then marketing comes up with some new ideas and terminologies and legal has ideas and while working with the app the user sees some potential and so on. And there are tons of interfaces to other systems where a simple change request would take some 2 months and cost you an arm and a leg - Oh, did I mention that you would have to send your request via Poland to India, to have it re-evaluated in Belgium, then sent out to all parties in Europe and the US for eventual implementation of the changes in Bangalore and tested in Romania Oh the wonders of globalization. But I digress... I haven't used the excel generator before, so I don't know if it can handle this, but ERD2W has a grouping list page. With that, you should be able to get a table that looks something like product 1 statement 1.1 statement 1.2 product 2 statement 2.1 statement 2.2 statement 2.3 statement 2.4 statement 2.5 statement 2.6 product 3 statment 3.1 product 4 ... and so on. If the xls generator can't handle the markup ERD2W produces, but you could customize your own grouping list repetition component. If they really Really demand columns per statement, I'd just dump the text to a csv file and let them open that in excel. This may be the easiest route. probably the best idea. Thanks Ramsey (and hey, your name is masculine enough...) ---markus--- Ramsey On Feb 6, 2013, at 10:13 AM, Markus Ruggiero wrote: Folks, I need some good ideas. I have basically the following model: PRODUCT (code, name, some other attrs) -- STATEMENTREF (status) -- STATEMENT(text) STATEMENTREF is a join table that has one attribute (so it is not a simple m:n join). The customer wants an excel file looking like this heading line: product code | product name | statement 1 text | statement 2 text | ... | statement n text data line 1 : 2345 | name of this | ref status 1 | ref status 2 | ... | ref status n data line 2 : 8976 | name of this | ref status 1 | ref status 2 | ... | ref status n etc The columns are the statements, the rows one per product and the cells hold the status for the reference from product to statement text. Any idea how to do such a thing? This is pretty urgent and I am at a loss. The whole thing is a D2W project in Neutral Look. Creating Excel stuff with ERExcelLook is no problem under normal conditions. But here? I am pulling my hair but I have not made any progress so far. Thanks a lot for any help ---markus--- ___ 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/rgurley%40smarthealth.com This email sent to rgur...@smarthealth.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 Association is now a non-profit corporation
On 30 jan. 2013, at 17:03, Pascal Robert prob...@macti.ca wrote: FYI, I got confirmation that the WOCommunity Association is now a non-profit corporation! We still have to open a bank account and write the by-laws, but at least the first part is done. It might be an idea for the United States people to hook up with this: http://spi-inc.org/projects/associated-project-howto/ It seems to be a nice way to combine tax deduction, and giving money. (I found this when looking for libreoffice 4.0 which was announced at FOSDEM 2013) If someone wants to contribute or comment the by-laws, I wrote a draft in the wiki: http://wiki.wocommunity.org/display/WOCOM/Organization+Incorporation Please be aware that we defined two classes of members: « The corporation is authorized to establish Class A members and Class B members as follows : (1) The Class A members shall be entitled to receive notice of and to attend all meetings of the members of the Corporation and each Class A member shall have one (1) vote at each such meeting, except for meetings at which only members of another class are entitled to vote separately as a class. (2) Except as otherwise provided by the Canada Not-for-Profit Corporations Act, S.C. 2009, c.23 the Class B members shall not be entitled to receive notice of, attend or vote at meetings of the members of the Corporation. » The by-laws needs to define who is going in each class. ___ 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/johan%40netsense.nl This email sent to jo...@netsense.nl Johan Henselmans jo...@netsense.nl ___ 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
Re: WOCommunity membership and goals
On 07.02.2013, at 13:59, Pascal Robert prob...@macti.ca 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
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 mailingli...@kataputt.com wrote: On 07.02.2013, at 13:59, Pascal Robert prob...@macti.ca 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
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 jtay...@oeinc.com 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 mailingli...@kataputt.com wrote: On 07.02.2013, at 13:59, Pascal Robert prob...@macti.ca 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 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
Re: WOCommunity membership and goals
Am 07.02.2013 um 16:12 schrieb James Cicenia ja...@jimijon.com: 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 jtay...@oeinc.com 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 mailingli...@kataputt.com wrote: On 07.02.2013, at 13:59, Pascal Robert prob...@macti.ca 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:
Re: WOCommunity membership and goals
Le 2013-02-07 à 10:44, Johann Werner j...@oyosys.de a écrit : Am 07.02.2013 um 16:12 schrieb James Cicenia ja...@jimijon.com: 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 jtay...@oeinc.com 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 mailingli...@kataputt.com wrote: On 07.02.2013, at 13:59, Pascal Robert prob...@macti.ca 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:
ERMODQueryPage help
I am trying to understand the ERMODQueryPage in my D2W app. to that end, I
cloned it to TPMODQueryPage and I am screwing around to see what does what.
I see that the list for the popup might be being generated in
ERD2WQueryStringOperator extends D2WQueryStringOperator.
The end result is that I want to limit the list in the popup on a QueryPage to
Contains, Starts With, Like (although Contains and Like sound like the
same thing).
Is there a property that I can set to give me the list I want or do I have to
clone the stringOperator?
on a java style question, I see this a lot:
_stringQualifierOperators = new NSArrayString(new String[]{starts with,
contains, ends with, is, like});
would it be more better to use
_stringQualifierOperators = new NSArrayString(starts with, contains,
ends with, is, like);
are they the same?
___
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 prob...@macti.ca: Le 2013-02-07 à 10:44, Johann Werner j...@oyosys.de a écrit : Am 07.02.2013 um 16:12 schrieb James Cicenia ja...@jimijon.com: 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 à 11:21, Musall Maik m...@selbstdenker.ag a écrit : Am 07.02.2013 um 16:58 schrieb Pascal Robert prob...@macti.ca: Le 2013-02-07 à 10:44, Johann Werner j...@oyosys.de a écrit : Am 07.02.2013 um 16:12 schrieb James Cicenia ja...@jimijon.com: 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: ERMODQueryPage help
100 : propertyKey = 'abstract' = qualifierOperators = (contains)
[com.webobjects.directtoweb.Assignment]
On 2013-02-07, at 7:59 AM, Theodore Petrosky tedp...@yahoo.com wrote:
I am trying to understand the ERMODQueryPage in my D2W app. to that end, I
cloned it to TPMODQueryPage and I am screwing around to see what does what.
I see that the list for the popup might be being generated in
ERD2WQueryStringOperator extends D2WQueryStringOperator.
The end result is that I want to limit the list in the popup on a QueryPage
to Contains, Starts With, Like (although Contains and Like sound like
the same thing).
Is there a property that I can set to give me the list I want or do I have to
clone the stringOperator?
on a java style question, I see this a lot:
_stringQualifierOperators = new NSArrayString(new String[]{starts with,
contains, ends with, is, like});
would it be more better to use
_stringQualifierOperators = new NSArrayString(starts with, contains,
ends with, is, like);
are they the same?
___
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/programmingosx%40mac.com
This email sent to programming...@mac.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
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 prob...@macti.ca wrote: Le 2013-02-07 à 11:21, Musall Maik m...@selbstdenker.ag a écrit : Am 07.02.2013 um 16:58 schrieb Pascal Robert prob...@macti.ca: Le 2013-02-07 à 10:44, Johann Werner j...@oyosys.de a écrit : Am 07.02.2013 um 16:12 schrieb James Cicenia ja...@jimijon.com: 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: ERMODQueryPage help
thanks with that info I found:
public NSArrayString qualifierOperatorsOverrideFromRules(){
return (NSArrayString)d2wContext().valueForKey(qualifierOperators);
}
but the rule isn't firing:
100 : propertyKey = 'abstract' = qualifierOperators = (contains, starts
with, like) [com.webobjects.directtoweb.Assignment]
I don't understand where the LHS is coming from and the rule is still not
firing.
Ted
--- On Thu, 2/7/13, David Holt programming...@mac.com wrote:
From: David Holt programming...@mac.com
Subject: Re: ERMODQueryPage help
To: Theodore Petrosky tedp...@yahoo.com
Cc: WebObjects Development webobjects-dev@lists.apple.com
Date: Thursday, February 7, 2013, 11:51 AM
100 : propertyKey = 'abstract' =
qualifierOperators = (contains)
[com.webobjects.directtoweb.Assignment]
On 2013-02-07, at 7:59 AM, Theodore Petrosky tedp...@yahoo.com
wrote:
I am trying to understand the ERMODQueryPage in my D2W
app. to that end, I cloned it to TPMODQueryPage and I am
screwing around to see what does what.
I see that the list for the popup might be being
generated in ERD2WQueryStringOperator extends
D2WQueryStringOperator.
The end result is that I want to limit the list in the
popup on a QueryPage to Contains, Starts With, Like
(although Contains and Like sound like the same thing).
Is there a property that I can set to give me the list
I want or do I have to clone the stringOperator?
on a java style question, I see this a lot:
_stringQualifierOperators = new
NSArrayString(new String[]{starts with,
contains, ends with, is, like});
would it be more better to use
_stringQualifierOperators = new
NSArrayString(starts with, contains, ends
with, is, like);
are they the same?
___
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/programmingosx%40mac.com
This email sent to programming...@mac.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: quick pwd hash?
Just wanted to remind you to Salt your passwords. If you don't you might as well not message digest them. ___ 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: quick pwd hash?
Thank you sir! Have you read over this godawful looking web page from Ramsey on the subject? http://codahale.com/how-to-safely-store-a-password/ He suggests this approach which I _THINK_ seems to work quite well as a basic authentication crypt. Maybe others have thoughts on the subject? On Feb 7, 2013, at 12:55 PM, Jeffrey Simpson simp...@yfu.org wrote: Just wanted to remind you to Salt your passwords. If you don't you might as well not message digest them. ___ 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: quick pwd hash?
A very interesting and ugly page. I am not a security expert by any means but what he says makes a lot of sense. On 2/7/13 1:27 PM, Jesse Tayler jtay...@oeinc.com wrote: Thank you sir! Have you read over this godawful looking web page from Ramsey on the subject? http://codahale.com/how-to-safely-store-a-password/ He suggests this approach which I _THINK_ seems to work quite well as a basic authentication crypt. Maybe others have thoughts on the subject? On Feb 7, 2013, at 12:55 PM, Jeffrey Simpson simp...@yfu.org wrote: Just wanted to remind you to Salt your passwords. If you don't you might as well not message digest them. ___ 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.co m 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 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:
Re: WOCommunity membership and goals
Le 2013-02-07 à 13:50, Ramsey Gurley rgur...@smarthealth.com 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
logo on the WOWODC site.
- $1500 for Gold Sponsorship. You get membership + your company logo on
wocommunity.org for 12
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 à 15:05, Johnny Miller jlmil...@kahalawai.com 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/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: WOCommunity membership and goals
Am 07.02.2013 20:02 schrieb Pascal Robert prob...@macti.ca:
Le 2013-02-07 à 13:50, Ramsey Gurley rgur...@smarthealth.com 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 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
Re: WOCommunity membership and goals
Am 07.02.2013 20:02 schrieb Pascal Robert prob...@macti.ca:
Le 2013-02-07 à 13:50, Ramsey Gurley rgur...@smarthealth.com 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 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
Re: WOCommunity membership and goals
On Feb 7, 2013, at 11:01 AM, Pascal Robert prob...@macti.ca wrote:
Le 2013-02-07 à 13:50, Ramsey Gurley rgur...@smarthealth.com 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 stuff on CentOS. Awesome - worked fabulously!
- Redesign of wocommunity.org.
I think wocommunity.org does the job just fine as is. What are you wanting
to
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
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 prob...@macti.ca wrote: Le 2013-02-07 à 15:05, Johnny Miller jlmil...@kahalawai.com 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
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 increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/gvc/practical_webobjects
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 prob...@macti.ca wrote: From: Pascal Robert prob...@macti.ca Subject: Re: WOCommunity membership and goals To: Bastian Triller bastian.tril...@gmail.com Cc: WebObjects Development webobjects-dev@lists.apple.com 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
Le 2013-02-07 à 15:24, Theodore Petrosky tedp...@yahoo.com 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 prob...@macti.ca wrote: From: Pascal Robert prob...@macti.ca Subject: Re: WOCommunity membership and goals To: Bastian Triller bastian.tril...@gmail.com Cc: WebObjects Development webobjects-dev@lists.apple.com 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
Le 2013-02-07 à 15:17, Johnny Miller jlmil...@kahalawai.com 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 prob...@macti.ca wrote: Le 2013-02-07 à 15:05, Johnny Miller jlmil...@kahalawai.com 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:
Re: WOCommunity membership and goals
On Feb 7, 2013, at 10:19 AM, Chuck Hill ch...@global-village.net 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/jlmiller%40kahalawai.com This email sent to jlmil...@kahalawai.com ___ Do not post admin requests to the list. They will be ignored. Webobjects-dev
Re: WOCommunity membership and goals
On Feb 7, 2013, at 10:26 AM, Pascal Robert prob...@macti.ca wrote: Le 2013-02-07 à 15:17, Johnny Miller jlmil...@kahalawai.com 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 prob...@macti.ca wrote: Le 2013-02-07 à 15:05, Johnny Miller jlmil...@kahalawai.com 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
Re: WOCommunity membership and goals
On 2013-02-07, at 10:44 AM, Johann Werner j...@oyosys.de wrote: Am 07.02.2013 um 16:12 schrieb James Cicenia ja...@jimijon.com: 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 jtay...@oeinc.com 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 mailingli...@kataputt.com wrote: On 07.02.2013, at 13:59, Pascal Robert prob...@macti.ca 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
Re: WOCommunity membership and goals
Hi David, Am 08.02.2013 um 03:48 schrieb David LeBer dleber_wo...@codeferous.com: On 2013-02-07, at 10:44 AM, Johann Werner j...@oyosys.de wrote: Am 07.02.2013 um 16:12 schrieb James Cicenia ja...@jimijon.com: 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 jtay...@oeinc.com 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 mailingli...@kataputt.com wrote: On 07.02.2013, at 13:59, Pascal Robert prob...@macti.ca 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
Re: WOCommunity membership and goals
Hi Ramsey,
Am 07.02.2013 um 19:50 schrieb Ramsey Gurley rgur...@smarthealth.com:
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
row number in direct2web ERMDSimpleListPageRepetition?
Hey, has anybody displayed a row number in direct2web ERMDSimpleListPageRepetition? ___ 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
