BUG Community

Welcome! Log In

Forums Official Updates Application Cook Off

Subscribe to Application Cook Off  57 posts, 18 voices

Log in to reply to this topic
 
Oct 2, 2007 2:46pm
Medium Bug Labs team mcholerton 54 posts

With a solid week behind us, Heather's cocktail party a smashing success, and International Talk Like a Pirate Day all a faint memory, it's time now turn up the heat up with our first ever Bug Labs Beta challenge - the Application Bake Off. Any application of your own design/creation that is submitted to BUGnet before 11:59 pm EST on Friday, October 12th qualifies it's creator for a fun prize.

For example, we've created a recipe to get the camera module working with Flickr. Got a similar dish? GPS? Web service? Mashup?

Apps are judged based on flavor, productivity, fun, usability, and 'wow factor-ness', with points awarded through a somewhat unorganized and subjective panel process. This App Sizzle-a-thon includes the esteemed judging panel of beta email votes, Peter Semmelhack, Ken Gilmer, and Dorsey (the receptionist upstairs).

The Cook-off finalist wins a gift certificate from somewhere we love (a real place and real gift certificate), a one of a kind Bug Labs T-shirt, serious bragging rights, and the rights of the special Shiny Bug Badge of Honor (the details of which I could tell you, but then I'd have to kill you).

Good luck and let us know what we can do to help!
Oct 2, 2007 4:14pm
Medium Bug Labs team finsprings 268 posts

Any chance we’ll get an updated SDK with the fixes for LCD working on OS X and for not needing to run all apps in separate workspaces before Friday?

Oct 2, 2007 5:09pm
Medium Bug Labs team kgilmer 215 posts

The LCD issue on OS X is still ongoing. There seems to be some confusion regarding the viability of embedding AWT frames inside of SWT composites. Our internal tests have yet to work succesfully, but we are still trying. Worse case is that we have to rewrite the Virtual BUG UI in Swing. If this happens, we’ll be at least a week, maybe more out in terms of a release. Is it possible for you to use Ubuntu (via parallels, etc.) for BUG apps with LCD?

Oct 2, 2007 5:31pm
Medium Bug Labs team finsprings 268 posts

"kengilmer"
Is it possible for you to use Ubuntu (via parallels, etc.) for BUG apps with LCD?


I can definitely do that. I have an XP VM in Parallels and a knoppmyth box at home that I can repurpose. The problem with needing all apps loaded is also work-aroundable with separate workspaces.

With no status bar space, it's tough to imagine writing anything that wouldn't need the LCD module at this point.
Oct 3, 2007 11:27am
Medium Bug Labs team kgilmer 215 posts

finsprings,

Yes I see. The OS X/LCD fix is either going to be fairly quick or take some serious time. Once we know (hopefully today) we can either:
1. Provide a release that fixes both issues.
2. Provide a release that fixes the "closed project" issue only.

IRT the base LCD screen, yes it is pretty constrained :). We need to utilize the second line to provide more room to applications.

Oct 3, 2007 12:52pm
Medium Bug Labs team kgilmer 215 posts

There is a work around to defect #15 Project Explorer: Unable to launch Virtual BUG when a project has been set to closed (http://bugbeta.com/bugzilla/show_bug.cgi?id=15).

The fix is to install the development version of Concierge Tools for Eclipse (CTE). Using the Eclipse Update Manager, install CTE from this URL: http://bugbeta.com/cte/dev. The feature is entitled Concierge Tools for Eclipse 1.0.0.56. After restarting Eclipse, closing project should not cause the Virtual BUG to fail.

Oct 6, 2007 7:22pm
Img_missing_medium matt.gauger 15 posts

kengilmer
There is a work around to defect #15 Project Explorer: Unable to launch Virtual BUG when a project has been set to closed (http://bugbeta.com/bugzilla/show_bug.cgi?id=15).

The fix is to install the development version of Concierge Tools for Eclipse (CTE). Using the Eclipse Update Manager, install CTE from this URL: http://bugbeta.com/cte/dev. The feature is entitled Concierge Tools for Eclipse 1.0.0.56. After restarting Eclipse, closing project should not cause the Virtual BUG to fail.


This did fix the problem for me (Mac OSX, Eclipse 3.3, Java 1.5.0_07)

Is this a suggested download for all Beta Testers?
Oct 8, 2007 6:59am
Medium Bug Labs team kgilmer 215 posts

Matt,

I’d say if the multiple-application issue is causing you grief please use CTE 1.0.0.56, otherwise hold off until our next SDK release.

Oct 8, 2007 12:26pm
Medium Bug Labs team finsprings 268 posts

FWIW, I’m doing okay with having 2 workspaces, one for the app I’m working on and one with all the sample apps. I have 2 instances of Eclipse open and flip between them so I can look at the sample stuff and also work on my own app.

Oct 8, 2007 6:21pm
Img_missing_medium matt.gauger 15 posts

This is more of a request for a feature in the next SDK, but it’s something to do with my current work towards an entry for the Application Cook-off, so I thought I’d post it here.

It’s kind of pointless that the Hello World example on the wiki only shows up in ‘bundles’ on the console – it never writes to the "Hello World" line to stdout with System.out.println();
A lot of the example apps also have "Starting up" and "Shutting down" messages for their bundles going to System.out, but as far as I can tell, that isn’t writing to the console, or the PDE error log. That information pretty much goes no where.

Can we get a working System.out for the next SDK? It’d help out a lot with my development, strange as such a simple thing may sound. (Status bar is a little tiny to throw much information at, and I could be writing to the LCD but that’s a lot more code than simply System.out)

Thanks in advance guys! :D

Oct 8, 2007 9:59pm
Medium Bug Labs team finsprings 268 posts

matt.gauger
This is more of a request for a feature in the next SDK, but it's something to do with my current work towards an entry for the Application Cook-off, so I thought I'd post it here.

It's kind of pointless that the Hello World example on the wiki only shows up in 'bundles' on the console - it never writes to the "Hello World" line to stdout with System.out.println();
A lot of the example apps also have "Starting up" and "Shutting down" messages for their bundles going to System.out, but as far as I can tell, that isn't writing to the console, or the PDE error log. That information pretty much goes no where.

Can we get a working System.out for the next SDK? It'd help out a lot with my development, strange as such a simple thing may sound. (Status bar is a little tiny to throw much information at, and I could be writing to the LCD but that's a lot more code than simply System.out)

Thanks in advance guys! :D


The output from System.out should be going to the Console pane in Eclipse, which by default will be in a tab toward the bottom of the screen along with Properties, Problems and so on. You should see messages in there from your app along with all the usual startup stuff. The first method that will be invoked in your bundle is Activator.start() so try putting a System.out call in there and see if you can see it.

Also, I posted about the status bar here: http://bugbeta.com/forums/viewtopic.php?t=30&highlight=status
Oct 11, 2007 9:46am
Img_missing_medium koolatron 52 posts

I can confirm that System.out works in eclipse 3.3 and a freshly updated Dragonfly installation. You may be missing your own outputs in the crush of information coming out of the BUG framework.. there are a lot of messages there to confound you.

A good place to stick your debug messages is after doStart() has been called in your application; it seems that is a pretty consistently quiet spot. If that fails (or is totally inconvenient), you could always stick your debug messages in an awt frame. That places an LCD dependency on your BUG, though, and the space is rather limited.

Oct 12, 2007 4:51pm
Img_missing_medium koolatron 52 posts

I really feel like this is in the same vein as groveling to a professor for a deadline extension, but I’ve got some great ideas that need hashing out and debugging before I can put them into BUGnet for the application bake-off.

I haven’t seen anything new creep into BUGnet in the past day or two – is it possible that the deadline for submissions could be extended to allow (at least my) ideas to congeal a little better?

Oct 12, 2007 5:01pm
Medium Bug Labs team finsprings 268 posts

Aw, I was looking forward to winning by default ;-)

Oct 12, 2007 5:17pm
Img_missing_medium koolatron 52 posts

Well, you’ll still probably win, since it’s your app that I’m working on anyhow ;)

I’m just putting some lipstick on it, heh

Oct 12, 2007 5:38pm
Medium Bug Labs team finsprings 268 posts

Yeah, but if you have to pick the pig, or the pig with lipstick, which would you choose?

:-)

Oct 12, 2007 5:47pm
Img_missing_medium koolatron 52 posts

I guess it all depends on what you’re into. :D

Oct 12, 2007 5:52pm
Medium Bug Labs team mcholerton 54 posts

Alright guys, take it easy. Starting to get hot in here! I don’t want to be forced to censor. :lol: oink

Oct 12, 2007 11:08pm
Medium Bug Labs team mcholerton 54 posts

As our first deadline for the Application Cook Off winds down, we’ve decided to put some more slack in the rope. QA and myself (sitting over here in our lawn chairs) didn’t anticipate the many issues that would come up when actual people working in all kinds of environments with all kinds of ideas were actually digging in.

Nonetheless, Fin got in there and posted an application! Wahooo. Great job! An early panel review has decided – and not by default, but rather by perseverance, he will be rewarded. Can’t reveal what it is at this time but I’ll give you warning when to check your mailbox.

However, all you other beta superstars will get a well deserved extension. (Kool, you can call me Professor Cholly – extension granted! Your lipstick pig and other ideas will live to see another day).

The Application Cook Off deadline will be pushed 2 weeks to October 26th. All current apps are still in the mix for consideration. The panel is licking their chops and gang here will continue to do their best to help whenever they can!

Oct 12, 2007 11:57pm
Img_missing_medium koolatron 52 posts

Oink!

Oct 13, 2007 12:16am
Medium Bug Labs team finsprings 268 posts

Nice. Thanks! I hope to get some time soon to keep working on GpsLogger. I’m looking forward to seeing Koolatron’s app and other folks’ too.

Oct 14, 2007 9:34pm
Img_missing_medium koolatron 52 posts

I’ve made some good progress tonight. Though it required reinventing some wheels that I knew already existed (and learning something along the way!).

I’ve currently got gpslogger calculating current heading, and panning the currently viewable tile so that the GPS position is in the center. Tomorrow or tonight I’ll goad it into downloading adjacent tiles and indicating heading on the main window…

Oct 14, 2007 9:52pm
Medium Bug Labs team finsprings 268 posts

koolatron
I've made some good progress tonight. Though it required reinventing some wheels that I knew already existed (and learning something along the way!).

I've currently got gpslogger calculating current heading, and panning the currently viewable tile so that the GPS position is in the center. Tomorrow or tonight I'll goad it into downloading adjacent tiles and indicating heading on the main window...

Nice!
Oct 22, 2007 9:17am
Img_missing_medium koolatron 52 posts

A new version of GpsLogger (I’m calling it 1.1) is on BUGnet waiting to be broken :)

I forwent the onscreen position/distance display until I can make it look pretty – the map tiles itself automatically to fill the available screen space and pans to keep the current GPS location in the center of the screen. I’m pretty sure that all this is done the "proper" way, given the partial AWT package included in PhoneME Personal Basis Profile.

Up next is visual heading indication and interactive zoom control!

Oct 23, 2007 9:09pm
Img_missing_medium koolatron 52 posts

Interactive zoom control is now available via buttons 1 (zoom in) and 2 (zoom out) on the BUGBase while GpsLogger_1.1 is running.