Quick update

[Scott Elcomb]

Sorry for the delay.

I did find an old Pine image that works, but it has some issues. I was
about to start work on manual build docs when it occurred to me that I
hadn't checked for any potential finds regarding running Raspbian in
qemu in several months...

I'm happy to report that the critical issues with auto-pine are now
fixed and (mostly) builds using the most recent (December) Raspbian
release. =D

In order to make it work I had to build a fresh qemu from source (it's
not too difficult) and change my system's date before running
auto-pine. This allows us to use an arm 1176 kernel instead of an
1136-r2 kernel, fixing some graphics issues among others.

There's still a couple small things that need to be corrected and I
expect to have it all fixed up & committed this weekend. (I'll try to
get mongodb into this image as well.)

While I really do want to provide a pre-built image (it would save
dev's an hour or two of build & prep time), I don't have the bandwidth
to support many downloads, around 5-7 per month... This might sound a
little strange coming from a "pirate" but anyone know how to seed new
torrents? (I've downloaded maybe a dozen files [Linux distros &
albums released under CC licenses] since bt was originally developed.)

Also, does anyone have a preferred build system? The current set of
bash scripts work, but it's pretty finicky. To make it a little more
robust I'm thinking it might be best to start using makefiles, ant, or
a custom build-tool in node.js

--
Scott Elcomb
@psema4 on Twitter / Identi.ca / Github & more

Atomic OS: Self Contained Microsystems
http://code.google.com/p/atomos/

Member of the Pirate Party of Canada
http://www.pirateparty.ca/

[Alex Wilson]

Wow, that's awesome! Can't wait to start testing stuff out.

I think that it will be a good idea to start using a build tool, but having scripts that work is the best place to start. I don't know much about torrenting, but I can do some research. 

--
You received this message because you are subscribed to the Google Groups "Pine" group.
To post to this group, send email to pine-d...@googlegroups.com.
To unsubscribe from this group, send email to pine-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Jeremy Kahn]

Sweet, great job Scott!  

I would vote for a Node build tool.  I say that because it would be more consistent with rest of the project.  Otherwise I don't have much of an opinion on build tools.  I've had good luck with that approach for other projects (they were much simpler, however).

Instead of torrenting, could we just upload a file to Dropbox and share the link?  It looks like their limit for free accounts is 20GB a day - it should be enough to get us started.  How big are the images?

[Scott Elcomb]

On Thu, Jan 3, 2013 at 11:18 PM, Jeremy Kahn <jerem...@gmail.com> wrote:
> Sweet, great job Scott!
>
> I would vote for a Node build tool. I say that because it would be more
> consistent with rest of the project. Otherwise I don't have much of an
> opinion on build tools. I've had good luck with that approach for other
> projects (they were much simpler, however).

Started looking into jake <https://github.com/mde/jake> which appears
to be a pretty good fit and rather simpler than trying to reinvent
this particular wheel.

> Instead of torrenting, could we just upload a file to Dropbox and share the
> link? It looks like their limit for free accounts is 20GB a day - it should
> be enough to get us started. How big are the images?

Another service I've never used - but certainly looks like it'll fit
the bill for our current needs. =D

Without compression the image size 1.9G. So at a minimum, we should
be able to support ~10 downloads/day using a free account. Plenty for
now.

Turns out there is some trouble with the latest image - despite adding
a rather substantial swap partition, I can't (yet) prevent this image
from running out of memory when running X & Chrome under qemu. I'm
investigating but in the meantime this means I need to write the image
to an SD card and boot physical hardware for almost every issue I run
into. Each iteration is currently running me between 30 and 120
minutes depending on which build steps are required.

That said, I'm fairly certain that I'm close to a useful image. As
soon as I have one that works I'll get it into dropbox and post a link
here. Hoping for tonight. Regardless, I'll commit my recent changes
to github (~ 6 hours from now) in case anyone else wants to have a go.

[Jeremy Kahn]

Each iteration is currently running me between 30 and 120
minutes depending  on which build steps are required.

That sounds painful.  Be brave! 

--
You received this message because you are subscribed to the Google Groups "Pine" group.
To post to this group, send email to pine-d...@googlegroups.com.
To unsubscribe from this group, send email to pine-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
Jeremy Kahn

jerem...@gmail.com

https://github.com/jeremyckahn

[Scott Elcomb]

Got it, but we need to expand the image to 4G. There isn't any free
space in this raspbian image; we have to add some (expand rootfs in
raspi-config) in order for X to launch it and Chrome.

There's a new branch "fixautopine" in the repo; it doesn't contain the
expandfs portion as it hasn't been automated yet. Need to:

- copy do_expand_rootfs() from raspi-config into auto-pine's
first_build.sh script
- after unpacking the raspbian archive but before running the first build:
- create a blank 4G file and overwrite it with the 1.9G image (w/o truncating)
- during first build, use do_expand_rootfs() to resize the root
partition on next boot

I've got another branch to cleanup the pine.js launch, but it's
untested as yet... coming soon
- Move the dev-server from ui/ into pine-user's home directory (as the
default pine.js server)

Almost there...

[Jeremy Kahn]

Sweet!  Most of this is over my head, but it sounds promising!

If you have questions about anything in the ui/ directory, let me know.  I'm happy to help.

[Alex Wilson]

Hi, everyone. I'm not sure if anyone else has been able to put much work into Pine over the last month, but I just wanted to let you know that I haven't given up! I'm working on a library for multi-player functionality in webpages, which I plan to have cleaned up and usable by Monday, and playing with some user interface ideas for the console.

[Jeremy Kahn]

Awesome, I can't wait to see what you've been working on!  Please post a link when you've got something to show.

I'll be honest, I haven't touched Pine in a while, and I'm not planning on getting back into it unless there is something specifically you guys would like me to do.  I'm happy to help where I can, but at the moment I am focusing on other projects.

Sorry to take the wind out of the sails, I guess I just lost motivation for the project.  That being said, feel free to assign bugs or feature requests to me on Github - I'm happy to work on them. 

On Sat, Feb 9, 2013 at 1:01 PM, Alex Wilson <arex...@gmail.com> wrote:

Hi, everyone. I'm not sure if anyone else has been able to put much work into Pine over the last month, but I just wanted to let you know that I haven't given up! I'm working on a library for multi-player functionality in webpages, which I plan to have cleaned up and usable by Monday, and playing with some user interface ideas for the console.

--

You received this message because you are subscribed to the Google Groups "Pine" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pine-discuss...@googlegroups.com.

To post to this group, send email to pine-d...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msg/pine-discuss/-/60r-WdMdfs0J.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Scott Elcomb]

Sounds good - looking forward to checking it out.

It's been rather a whirlwind start to 2013 here. The linux image is
*almost* ready (just need to integrate the UI server). Unfortunately,
the next version of CCS (<http://www.ti.com/tool/ccstudio>) went into
feature freeze just recently and with only a couple weeks left until
the next iteration, I've been really pressed for time.

I broke down and grabbed a dedicated display
(<https://www.adafruit.com/products/1033>) a bit earlier than expected
so I can avoid scheduling HD TV & Monitor access with the family. ;-)
Delivery was expected this past Friday but was delayed due to a fairly
decent winter storm. I expect it'll be in tomorrow and to have the
distro ready within the next week or so.

Additionally, I've ordered a RoBo 3D printer
(<http://www.robo3dprinter.com/>) which should arrive mid-summer; I'll
be looking to design & print a case for Pine consoles by late
summer/early fall. My intention is to share the design on Thingverse
under an open or creative commons license. I'll post a new thread on
this in a few weeks to flesh out the details.

[Alex Wilson]

I'm glad to hear the linux image is coming along! I have a start on that multi-player library (https://github.com/arextar/link.js), but the server-side still needs some work. The plan for it is to have a flexible server that can facilitate multiple kinda of connections depending on what the client can do. I'm hoping to dive into WebRTC soon, and, once I do, I'll work on integrating it.

[Alex Wilson]

I have the next few months off from school, so I'd like to put some work into Pine. I think that, if people are still interested, this project could benefit from putting some sort of a roadmap together. It'd be nice to know exactly what we want and be able to see progress as we go.

[Jeremy Kahn]

Hi Alex,

I'm glad you're still enthusiastic about the project.  I have personally moved on from Pine — there's nothing wrong with the project, it doesn't fit with my current goals.  As you may recall, I have transferred ownership of the project to Scott, and he is leading the project.  Certainly feel free to put together a roadmap, I agree that Pine would benefit from it.

On Tue, Jun 4, 2013 at 3:47 PM, Alex Wilson <arex...@gmail.com> wrote:

I have the next few months off from school, so I'd like to put some work into Pine. I think that, if people are still interested, this project could benefit from putting some sort of a roadmap together. It'd be nice to know exactly what we want and be able to see progress as we go.

--

You received this message because you are subscribed to the Google Groups "Pine" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pine-discuss...@googlegroups.com.

To post to this group, send email to pine-d...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pine-discuss/ae5a12c7-4257-481f-a547-7ab123c1fe8d%40googlegroups.com?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Scott Elcomb]

On Tue, Jun 4, 2013 at 9:42 PM, Jeremy Kahn <jerem...@gmail.com> wrote:
> Hi Alex,
>
> I'm glad you're still enthusiastic about the project.

+1! =D

Actually Alex and I have been holding a bit of a discussion off-list
and I'll be able to provide a more useful update later this week.

I now have a working dev image (just needs to be cleaned up before
sharing) that includes a boot screen and a startup sound. I've also
been investigating the possibility of using AngularJS in the front-end
which has a number of benefits; for anyone interested, you can find a
quick test in the repo, under the 'angular' directory on the 'angular'
branch.

More soon & best regards,
- Scott.

[Alex Wilson]

Hey, just want to make a quick update. I've been looking at Angular-JS and I'm really enjoying it. I plan on looking at some design stuff this weekend and also looking back over my API specs and cleaning them up. After the OS is working, the next step will probably be to look at the game packaging and API.

[Scott Elcomb]

I had yet another wrench thrown into my plans for last week but come
Saturday I'll have a couple of weeks to dedicate to Pine.

Alex - I'll ping you with a link to the OS image as soon as I can.
I'd also like to set aside an hour or so Sunday or Monday to discuss
design decisions and hammer out the roadmap. Based on that
discussion, I'll go through and reorganize the repo/wiki on github.

Once again, thanks for your patience!

- Scott

PS: Quick question - any suggestions for a domain name to host the
game packages and community API's (ie. gamer profiles) on? I know we
don't have these yet, but I'd like to get that sorted out soon. In my
imagination, I'm seeing this central site as the Pine equivalent to
Steam or the Ouya Store.

The only domain that's popped into my head yet is "pinegaming.org".

[Alex Wilson]

As soon as you can get it done; I understand how much life can throw at you. As for the domain, I would prefer something like pinegames.org (mostly because it's slightly shorter).

--
You received this message because you are subscribed to the Google Groups "Pine" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pine-discuss...@googlegroups.com.
To post to this group, send email to pine-d...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/pine-discuss/CAEx-jsOsmRZfnHYg_rX5ba1Q3Ywj5zE830bwb2NApPWt3FZuDg%40mail.gmail.com.