Tim, - Sounds as if the text needs to be changed - tell me where it sounds like I am on permanent sabbatical.
- When everyone decides on the future of the WO web portals, I'll happily comply where I can to the group mentality. - That being said, there ARE parts (maybe just one part...have to recheck) of the installer which cannot be shared with the group - I will ask the party responsible since we had an agreement on not sharing information related to those components. Let's just say it was a very nice benefit of the installer. Yeah. - So...if I made everything public then we'd have to consider forking the package...I'll have to see what can be done there. I'm still considering the future of the installer, and how it would ideally work given the multiple versions that have been requested. Otherwise, say hello to half-a-dozen jumbled installers. Not me fav idea. - What this boils down to - when I ask for feedback, I'm serious there. I get little to no information except when things don't work. There should be a wish list somewhere...somehow. Then I could focus on priority features. Thanks, jeremy On Dec 6, 2009, at 6:28 PM, Tim Worman wrote: > +1 > > Jeremy: > > I'm just a guy reading messages and I took it as true that you may not be > maintaining the installer anymore. Obviously, you're completely capable of > keeping the installer working and it benefits the community if you do. A > bullet proof all-in-one installer is really beneficial. I don't think anyone > meant anything as an indictment of your work. > > I do think the organizational observations are good ones - making everything > downloadable directly from the wiki or some other central site. I like > Kieran's idea of putting the code for (whatever) installers under version > control for community contribution - might even help keep it versioned for > different OS X versions. > > Tim Worman > UCLA GSE&IS > > On Dec 6, 2009, at 2:36 PM, Joe Little wrote: > >> Let me apologize for the group, and hope you stay with us a little longer. >> We all tend to use the mailing list as the official conduit of >> communications and forget that direct email may be preferred when reporting >> a problem for some. Worse yet, bringing up such issues over a weekend can be >> a recipe for more disastrous fun. The only bit I agree on is making it even >> more obvious to new users whatever the group preffered methods are. Anything >> to limit confusion is _usually_ best. >> >> On Dec 6, 2009, at 12:20 PM, Jeremy Matthews <jeremymatth...@mac.com> wrote: >> >>> Clearly broken, eh? >>> I suppose after seeing more than a dozen messages no one thought of >>> actually talking to me? >>> Sigh...so many assumptions, so little meaningful conversation.... >>> >>> I'm not sure what the issue is, since we test it routinely, and this is the >>> first time we've heard in MONTHS that there was a problem. And now there's >>> talk of abandoning it entirely - within an hour. >>> Nice. >>> >>> So, seems everyone wants to talk AROUND me and not TO me, let me make a few >>> things clear: >>> 1) I regularly test and maintain the installer. >>> 2) Whenever we hear there is an issue we FIX it. Usually pretty damn fast. >>> Ask around. >>> 3) I do not build WO Apps _ROUTINTELY_ anymore - this does not mean I care >>> less about the tools or the installer, or the great people in the >>> community. I still develop too, I just don't advertise it. Usually the >>> opposite since there are tons of talented people here. >>> >>> That being said, if someone wants to take the installer over, fine by me. >>> I've had fun working with some really cool people, and being able to create >>> something a lot of people thanked me for. >>> >>> I've been fortunate to work with this great community, and am sincerely >>> thankful for that. But...if people will not communicate with me, then there >>> is nothing I can do (to help this community). I wish everyone the absolute >>> best of luck. >>> >>> So long, and thanks for all the fish! >>> >>> -jeremy >>> >>> P.S. - There have a been more than a few people along the way who said they >>> owed me a beer. If I see you at WWDC, I'll be collecting those! >>> >>> >>> ##### >>> I was setting up a new SL dev environment, and just to see what the >>> initial installation and setup procedure would be like for a complete >>> newbie on SL, I looked on the wiki for instructions for the simplest >>> possible path to new installation on a virgin Snow Leopard. >>> >>> It seems that really, a newbie would probably be confused and would >>> probably struggle. :-( >>> >>> >>> After installing WebObjects 5.4.3 using Apple's dmg installer and then >>> installing the "All In One" Eclipse/WOLips installer from >>> Jeremy's .mac page (since the sisu download was slow as molasses with >>> an est time of 1 day+!), I then hit a roadblock, getting an error when >>> launching Eclipse after running Jeremy's installer. >>> " An Error has occurred" >>> " See the log file ~/.eclipse/...../blahblah.log" >>> >>> That error log file is full of "missing required bundle" messages. >>> >>> Anyway, just FYI, I don't have time for troubleshooting this now .... >>> I am doing my usual 3.4.2 download and install/setup the manual way. >>> >>> Since Jeremy is not working in WO anymore and this is AIO (All In One) >>> installer is clearly broken for install on a virgin OS X Snow Leopard >>> box, we might want to just discontinue the all-in-one installer and >>> just go write a concise "WebObjects Developer Quick Start Guide" for >>> newbies .......so I started a wiki page on this and will work on >>> completing it as I get time. Any thoughts on that? Should I wipe all >>> references on the wiki to the AIO? >>> >>> If we are ever going to get new devs to come to WebObjects, we need to >>> have a working quick start. Any dev worth his salt should be >>> comfortable on the command line, so maybe a bash install script that >>> downloads and installs various bits and configures everything might be >>> the better route. Any opinions on that? >>> >>> BTW, I went to use the WOInstaller.jar initially and thinking that a >>> newbie would want standard install paths, I set the WOInstaller.jar >>> target as "/", but got an error saying System directory already >>> exists. Should the WOInstaller.jar's CPIO class be changed to just >>> overwrite existing files? Does that "overlay" directory paths (aka >>> merge eith existing files if named differently, or does it realyl >>> "replace" existing directories (ie., wiping them out)? >>> >>> Anyway, this is just some meandering thoughts / discussion before I >>> leave off the "How would a newbie WO dev fare on getting started" for >>> now and go do some work. >>> >>> Regards, Kieran >>> _______________________________________________ >>> 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: >>> http://lists.apple.com/mailman/options/webobjects-dev/jmlittle%40gmail.com >>> >>> This email sent to jmlit...@gmail.com >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> http://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com >> >> This email sent to li...@thetimmy.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: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
