Re: [Logicmail-devel] Developing
Brought to you by:
octorian
From: Derek K. <dko...@lo...> - 2010-01-04 02:55:27
|
If you haven't reviewed them recently, these are the full (up-to-date) setup instructions: http://www.logicprobe.org/proj/logicmail/wiki/development The most important part is that you have to use the BlackBerry Java Plug-in for Eclipse installed when doing all of this. The resource file its complaining about is code that is auto-generated behind the scenes by the plugin. FYI, the new 1.1 plugin makes the process *much* more straightforward than the old 1.0 plugin. You basically just checkout the whole thing, then import the projects into eclipse. -Derek On Sunday 03 January 2010 8:15:15 pm George Sexton wrote: > I'm taking a look at this now. > > I downloaded eclipse, and followed the instructions there. > > I used TortiseSVN to download the trunk from: > > https://logicmail.svn.sourceforge.net/svnroot/logicmail/trunk > > When I create a project for eclipse, the IDE shows errors. A class named > LogicMailResource doesn't resolve. > > I looked in the directory created by TortiseSVN and there are no files name > *resource*.* > > I'm the first to admit, I don't use Eclipse for Java development so I'm > kind of wandering around in the dark. Still, there are no files with that > name. I notice there are also no .properties files. I would have expected > to see some for captions and such. > > Am I missing something here? > > George Sexton > MH Software, Inc. > http://www.mhsoftware.com/ > Voice: 303 438 9585 > > > -----Original Message----- > > From: Derek Konigsberg [mailto:dko...@lo...] > > Sent: Wednesday, November 25, 2009 3:53 PM > > To: log...@li... > > Subject: Re: [Logicmail-devel] Developing > > > > George, > > I'm glad you wrote, since I can definitely use the help. Right now, I > > could > > divide the bulk of the work on the LogicMail code into the following > > categories: > > 1 - Death by a thousand papercuts > > - All these little nitpick issues that you're running into > > 2 - Development of major features > > - Offline message caching (active work-in-progress) > > - Network connection management (will be *much* easier in 5.0) > > 3 - UI cleanup and polish > > > > As someone trying to use the development version in a practical > > setting, #1 is > > the highest priority to you, followed sometimes by #3 (because you're > > on a > > Storm). > > > > As someone trying to make progress on the critical features for 2.0 to > > meet > > its goals, #2 is currently the highest priority to me, followed by the > > occasional bit of #3 (since its easier when I can't concentrate 110%). > > I > > basically put aside work on #1 for a while so I could make progress on > > #2. > > > > Now if you could help with all these nitpick issues and ironing out the > > kinks, > > that would be enormously helpful to me and the project. I actually > > have a > > fairly detailed TO-DO list on a lot of this, and I really should put it > > online > > for everyone here to see. (I normally keep it in Tomboy Notes, so I'll > > either > > export to HTML or see if they've made any progress with their web- > > service > > plans.) > > > > Now, as to how to get started... > > > > I've recently migrated the source tree to the 1.1 (beta) version of the > > BlackBerry Eclipse plugin. It works a lot better than the old one. > > You > > literally just open the workspace and import the projects, and that's > > it! > > None of the weird workarounds on my setup page for the 1.0 plugin. > > I'll be > > updating my development setup page sometime soon, but it really is that > > simple. > > > > So your first step is to grab the new Eclipse plugin: > > http://na.blackberry.com/eng/developers/devbetasoftware/javaplugin.jsp > > (The download includes a full Eclipse 3.5, so you just need the one > > file) > > > > Once you install it, run all the usual Eclipse updates. Then add the > > BlackBerry update site: > > http://www.blackberry.com/go/eclipseUpdate/3.5/java > > > > Finally, using that update site, install more BlackBerry SDK versions > > than > > just the 5.0 it comes with. I personally installed all of them, but > > the way > > my source tree is currently configured, I recommend the following: > > v4.2, v4.6, v4.7, v5.0 > > > > When you're all ready, set your workspace root to whereever you checked > > out > > trunk, and import all the projects. The new plugin lets you specify > > SDK/JDE > > version on a per-project basis, so I use 4.2.x for anything core, and > > newer > > versions for the platform support libraries. (anything ending in a "T" > > is > > touchscreen-specific) > > > > If you want to test on an OS 5.0 storm, use *all* the projects in your > > 9500 > > simulator configuration. (for an OS 5.0 Bold/Curve, everything but the > > projects ending in "T"... Just remember that all 5.0 simulators run > > from the > > same directory, so switching between them could have strange effects if > > you > > don't clean things out) > > > > (all this will find its way to the project website hopefully by this > > weekend) > > > > Finally, as far as contributing things back goes, the best way is to e- > > mail me > > a patch or just the changed source files, and I'll merge it in. As > > trunk > > stabilizes, I may eventually do this using tickets (like some of the > > 1.1 > > contributions), but I'm not quite there yet. > > > > P.S. The automated builds are currently disabled, since I haven't > > finished > > updating the build.xml file used for Ant. > > > > Ok, this e-mail has gone on long enough for now, so we'll continue the > > discussion in follow-up e-mails. > > > > -Derek > > > > On Wednesday 25 November 2009 1:42:35 pm George Sexton wrote: > > > I'm using Logic Mail 2.0 development snapshot on my Storm, running OS > > > version 5.0. (Not that the OS Version matters). > > > > > > Essentially, the 2.0 build is just horribly broken. Obvious > > > > functionality > > > > > just doesn't work. I mean things like deleting a message doesn't work > > > > at > > > > > all. Period. Not at all. > > > > > > Another MAJOR hassle is that the subscribed folders feature isn't > > > > present > > > > > in 2.0. > > > > > > I'm willing to pitch in here, and start trying to fix some of these > > > > things > > > > > but I want to make sure my changes go back into the source tree. > > > > > > I didn't see on the development page any information on how to > > > > contribute > > > > > changes that I make back to the source tree. > > > > > > How is this done? > > > > > > George Sexton > > > MH Software, Inc. - Home of Connect Daily Web Calendar > > > http://www.mhsoftware.com/ > > > Voice: 303 438 9585 > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > ------ > > > > > --- Let Crystal Reports handle the reporting - Free Crystal Reports > > > > 2008 > > > > > 30-Day trial. Simplify your report design, integration and > > > > deployment - > > > > > and focus on what you do best, core application coding. Discover > > > > what's > > > > > new with Crystal Reports now. http://p.sf.net/sfu/bobj-july > > > _______________________________________________ > > > Logicmail-devel mailing list > > > Log...@li... > > > https://lists.sourceforge.net/lists/listinfo/logicmail-devel > > > > -- > > --------------------------- > > Derek Konigsberg > > dko...@lo... > > --------------------------- > > > > ----------------------------------------------------------------------- > > ------- > > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > > 30-Day > > trial. Simplify your report design, integration and deployment - and > > focus on > > what you do best, core application coding. Discover what's new with > > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > _______________________________________________ > > Logicmail-devel mailing list > > Log...@li... > > https://lists.sourceforge.net/lists/listinfo/logicmail-devel > > --------------------------------------------------------------------------- > --- This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Logicmail-devel mailing list > Log...@li... > https://lists.sourceforge.net/lists/listinfo/logicmail-devel > -- --------------------------- Derek Konigsberg dko...@lo... --------------------------- |