Hi all, I think the point is still valid. We shouldn’t invest in WOLips development without first discussing the option of creating similar plugins for alternative IDEs.
So, who has enough insight into and experience with IntelliJ, Netbeans and the like to offer some thoughts on this? Maik P.S. Meanwhile, another Eclipse plugin developer has offered his services, and not just to to plain dev work but also do training to enable other community members to take over. A similar thing is probably possible with other IDEs. > Am 08.07.2020 um 03:37 schrieb Tim W via Webobjects-dev > <webobjects-dev@lists.apple.com>: > > Well said, Aaron. WOBuilder was great. That said, I haven’t hated WOLips - > I’ve actually really liked some aspects of the workflow. > > Also, I’ll add secondarily that I find it unlikely that anyone will move to > Xcode from Eclipse. > > Tim > UCLA GSE&IS > >> On Jul 4, 2020, at 8:46 AM, Aaron Rosenzweig via Webobjects-dev >> <webobjects-dev@lists.apple.com <mailto:webobjects-dev@lists.apple.com>> >> wrote: >> >> Thanks OC for sharing your experience and your code for the EOModeler on >> OSX. (I realize that is jvanek’s link; however, it was you who cobbled >> together the first version). >> >> Eclipse does two things well: >> 1) Refactoring >> 2) Cross platform (Macs, PCs, Linux - mixed environment) >> >> I use Eclipse today mainly because my team-mates chose it… and it’s ok, it >> has issues, but it’s alright for me. If we were honest, IntelliJ does those >> two things better than Eclipse but it doesn’t have the WOLips plugin. That >> plug-in is good but it is a never-ending struggle where Eclipse keeps >> breaking it in strange ways and nobody enjoys figuring out that useful >> friend in a foreign land. We’ve never fit in with the Eclipse community. >> >> It was nice in the days when you could double-click install WebObjects with >> tooling on a Mac. I enjoyed ProjectBuilder, WOBuilder, EOModeler, it all >> worked very nice for the most part. It had some issues too… there are always >> issues, but that was the heyday and when I enjoyed working with WO the most. >> If it were up to me I’d run MacOS Tiger in a VM with all that tooling when >> doing WO. But to be the lone wolf when others prefer getting rid of the .wod >> file and not using the same IDE setup it’s more like fighting than being >> productive. >> >> There was something guttural, tangible, enjoyable, with dragging member >> variables into component bindings. I enjoyed WOBuilder immensely and even >> created my member variables there. Whatever I do today I do in a trance >> where I imagine I was doing things that way. It’s like channelling an >> ancient codex to do my bidding in the modern age. >> >> I’m fortunate that much of what I loved I do today in Ares / Enyo but it too >> is dead. Why is it that the flame that burns Twice as bright burns half as >> long? >> AARON ROSENZWEIG / Chat 'n Bike <http://www.chatnbike.com/> >> e: aa...@chatnbike.com <mailto:aa...@chatnbike.com> t: (301) 956-2319 >> >> >>> On Jul 3, 2020, at 3:29 PM, OCsite via Webobjects-dev >>> <webobjects-dev@lists.apple.com <mailto:webobjects-dev@lists.apple.com>> >>> wrote: >>> >>> ... well, myself, I have found Eclipse next-to-unuseable (WOLips itself >>> looked good, but it's, alas, Eclipse-based). In case there's more people >>> similarly Eclipse-incompatible, let me just remind that the good ole XCode >>> (with a couple of build scripts added) is considerably more convenient than >>> Eclipse, and the only thing it can't do reasonably is EOmodelling. >>> >>> Which is why there's a stand-alone EOModeller application, freely available >>> at https://github.com/jvanek/EOModeler-OSX >>> <https://github.com/jvanek/EOModeler-OSX> >>> >>> (There's no graph view: for graph view you can use OmniGraffle, which still >>> supports EOModels very nicely.) >>> >>> All the best, >>> OC >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com >>> <mailto:Webobjects-dev@lists.apple.com>) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/aaron%40chatnbike.com >>> >>> <https://lists.apple.com/mailman/options/webobjects-dev/aaron%40chatnbike.com> >>> >>> This email sent to aa...@chatnbike.com <mailto:aa...@chatnbike.com> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list (Webobjects-dev@lists.apple.com >> <mailto:Webobjects-dev@lists.apple.com>) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com >> <https://lists.apple.com/mailman/options/webobjects-dev/lists%40thetimmy.com> >> >> This email sent to li...@thetimmy.com <mailto:li...@thetimmy.com> > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list (Webobjects-dev@lists.apple.com > <mailto:Webobjects-dev@lists.apple.com>) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/maik%40selbstdenker.ag > <https://lists.apple.com/mailman/options/webobjects-dev/maik%40selbstdenker.ag> > > This email sent to m...@selbstdenker.ag <mailto:m...@selbstdenker.ag>
_______________________________________________ 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
