Jan 03 04:37:51 <destinal> ooh
Jan 03 04:38:17 <destinal> I think appinfo.json
Jan 03 04:38:26 <destinal> and I think we want a type of "game"
Jan 03 04:38:46 <destinal> strings on LunaSysMgr has the two keywords near each other and the other appinfo stuff
Jan 03 04:39:39 <destinal> I still don't know how we get the binary path in there though

then a set-back:

Code:

Jan 03 04:47:40 <destinal> ok trying type of game with a main of the binary name
Jan 03 04:47:44 <destinal> let's see what happens
Jan 03 04:54:38 <destinal> hmm, it doesn't care about type
Jan 03 04:54:51 <destinal> or seemingly not anyway

It means that we can now install a native Linux application on the Pre (e.g. DOOM! or Quake or Need For Speed or OpenVPN) and launch it without any need for the Upstart Manager Service that I spent 4 solid hours creating the other day.

This has significant implications, not just for games, but for any type of advanced homebrew application.

We'll let the reader ponder on what those implications may be - we've thought of quite a few in the last hour ...

It means that we can now install a native Linux application on the Pre (e.g. DOOM! or Quake or Need For Speed or OpenVPN) and launch it without any need for the Upstart Manager Service that I spent 4 solid hours creating the other day.

-- Rod

I had to chuckle at that one. Thems the "breaks" as it were in app development. I'm not a raw coder per say but do enough that this "gotcha" has gotten me many times. (Work all weekend on a solution and Monday an epiphany is realized that shortcuts 19 hours of Sunday Game time sacrifice!)

Excellent work tho! Does this mean you will rework the DOOM! port and is there any performance benefit to the native call over the upstart manager other than easier launching?

I had to chuckle at that one. Thems the "breaks" as it were in app development. I'm not a raw coder per say but do enough that this "gotcha" has gotten me many times. (Work all weekend on a solution and Monday an epiphany is realized that shortcuts 19 hours of Sunday Game time sacrifice!)

Excellent work tho! Does this mean you will rework the DOOM! port and is there any performance benefit to the native call over the upstart manager other than easier launching?

As a software developer (not on the pre) This is business as usual and doesn't bother me. All my best work starts out large and complicated and then the more I work on it the smaller it gets. By the time I call it "done" it's often 1/4 or 1/10th the size and complexity of the first working version. Some of my stuff that's grown over time, even though it's functional and robust, I stiull consider somewhat of a failurte because I just know I'm missing some way to simplify it by at least 50%.

Consider the earlier larger work which you "threw away" or "obsoleted" instead of thinking of it as wasted, think of it as prototyping. Before you can make the nice optimized widget, you first have to make a big ugly hand made bolted together prototype to figure out all the ins & outs.

Could you install preware with just a single ipk that could be distributed through the palm app catalog or fileCoaster?

Yep.

Originally Posted by cobrakon

I had to chuckle at that one. Thems the "breaks" as it were in app development. I'm not a raw coder per say but do enough that this "gotcha" has gotten me many times. (Work all weekend on a solution and Monday an epiphany is realized that shortcuts 19 hours of Sunday Game time sacrifice!)

Excellent work tho! Does this mean you will rework the DOOM! port and is there any performance benefit to the native call over the upstart manager other than easier launching?

Don't worry, the upstart service is still very useful in it's own right (e.g. for an OpenVPN GUI to be able to start and stop an OpenVPN backend service). It's absolutely not wasted at all, and I'll be continuing work on it to add more features.