Jetpack 0.8 and the Road Ahead
Daniel
We are nearing the release of Jetpack 0.8, which will feature both the
Toolbar and Places APIs. Jetpack 0.8 is a particularly important
release because it marks the last release based on the experimental
prototype we started with last year. As we wrote about last week, we
have concurrently been working on a new production-quality iteration
of Jetpack, with a revamped architecture that takes inspiration from
all of the feedback about the prototype.
In the coming week we will be publishing more information about the
new architecture, but currently, we need your feedback on our draft
roadmap: https://wiki.mozilla.org/Labs/Jetpack/Reboot_Roadmap. We are
looking at roughly a four month time-frame for completion of this
feature roadmap. During this four month span, there are three major
releases scheduled. Each will add targeted, essential features and
APIs to the rebooted platform. The first of these three releases will
be live about 6 weeks from today.
As we near this transition, expect an increase in communication from
the team. It's an exciting time for Jetpack!
- Daniel Buchner, on behalf of the Jetpack team.
M.Terada
I tried seeing https://wiki.mozilla.org/Labs/Jetpack/Reboot/Getting_Started
on Ubuntu
but "jpx run" occurs an error
---------------------------------------------
$ jpx run
Traceback (most recent call last):
File "/home/teramako/var/jetpack/jep-28/bin/jpx", line 8, in <module>
packaging.call_cmdline_tool(os.environ['CUDDLEFISH_ROOT'], 'jetpack')
File "/home/teramako/var/jetpack/jep-28/python-lib/cuddlefish/packaging.py",
line 207, in call_cmdline_tool
module.run()
File "/home/teramako/var/jetpack/jep-28/packages/atul-packages/packages/jetpack/python-lib/jetpack.py",
line 47, in run
usage=usage)
File "/home/teramako/var/jetpack/jep-28/python-lib/cuddlefish/__init__.py",
line 111, in parse_args
group.add_option(*names, **opts)
File "/usr/lib/python2.6/optparse.py", line 1020, in add_option
self._check_conflict(option)
File "/usr/lib/python2.6/optparse.py", line 995, in _check_conflict
option)
optparse.OptionConflictError: option -r/--use-server: conflicting
option string(s): -r
---------------------------------------------
It seems "-r" option conflicts.
Please apply following patch:
---------------------------------------------
diff -r c2f02b47d179 python-lib/cuddlefish/__init__.py
--- a/python-lib/cuddlefish/__init__.py Tue Jan 26 13:28:54 2010 -0800
+++ b/python-lib/cuddlefish/__init__.py Thu Jan 28 11:11:12 2010 +0900
@@ -58,7 +58,7 @@
"firefox, or thunderbird"),
metavar=None,
default="xulrunner"),
- ("-r", "--use-server",): dict(dest="use_server",
+ ("-u", "--use-server",): dict(dest="use_server",
help="use task queue server",
action="store_true",
default=False),
---------------------------------------------
Best regards
----
teramako
http://twitter.com/teramako/
http://d.hatena.ne.jp/teramako/
2010/1/28 Daniel <dani...@gmail.com>:
> --
> You received this message because you are subscribed to the Google Groups "mozilla-labs-jetpack" group.
> To post to this group, send email to mozilla-la...@googlegroups.com.
> To unsubscribe from this group, send email to mozilla-labs-jet...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mozilla-labs-jetpack?hl=en.
>
>
Hernan Rodriguez Colmeiro
"HTML5 Simple Storage". I wonder how this would work with firebug for
the debugging, since currently there's no functionality (or extension)
in firebug to debug HTML5 offline storage.
Also, I don't clearly understand what are the "packs". Are they just a
way to summarize certain features that will be present on the release?
Am I getting I comletely wrong?
Besides that all seems fine to me :)
Hernan
Brian King
The roadmap is not very clear on whether current features such as
slidebars will be still be available in the reboot. It could be nice for
the items to link back to JEPs at
https://wiki.mozilla.org/Labs/Jetpack/JEPs.
- Brian
Daniel
more usable ui mechanisms. As for JEPs, they already exist in the
reboot context, see: Labs/Jetpack/Reboot/JEP on the wiki, all the 0.1
Reboot release JEPs will be filled out by end of day Friday.
- Daniel
On Jan 28, 7:31 am, Brian King <briks...@gmail.com> wrote:
> Hi,
>
> The roadmap is not very clear on whether current features such as
> slidebars will be still be available in the reboot. It could be nice for
> the items to link back to JEPs athttps://wiki.mozilla.org/Labs/Jetpack/JEPs.
Brian King
> Actually, we intended to depricate slidebars in favor of a few slicker
> more usable ui mechanisms.
That will pull the rug from under a lot of Jetpacks. Many in the Jetpack
for Learning Design Challenge use them. But as early-adopters, I guess
we signed up for change and breakage!
- Brian
*** Birddog ***
Daniel
calls that establish extensions in the slidebar to another UI type,
such as panels (door hangers). We would likely be doing something
like this, so that they don't just break ;)
- Daniel
Daniel
yet, nothing is 'decided', we are just stating our feelings and
experiences. We will definitely be providing something even more
awesome if it was to happen, and trying our best to auto-convert your
current stuff!
- Daniel
Marcio Galli
m
--
You received this message because you are subscribed to the Google Groups "mozilla-labs-jetpack" group.
To post to this group, send email to mozilla-la...@googlegroups.com.
To unsubscribe from this group, send email to mozilla-labs-jet...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/mozilla-labs-jetpack?hl=en.
--
blog.taboca.com
Drew
http://hg.mozilla.org/users/avarma_mozilla.com/jep-28/rev/fa2f0197c80d
Drew
johnjbarton
On Jan 27, 2:11 pm, Daniel <daniel...@gmail.com> wrote:
> In the coming week we will be publishing more information about the
> new architecture, but currently, we need your feedback on our draft
> roadmap:https://wiki.mozilla.org/Labs/Jetpack/Reboot_Roadmap.
Ok then, my first feedback: publish something about the new
architecture now so we can make sense of the roadmap ;-).
The current roadmap lists disconnected and unexplained features. With
an architecture outline, the roadmap could be more like "build X,
build Y on X, Y provides features A, B, C.
As jetpack is a tool for developers, the design should include a
solution for the issues facing developers. They need API (check), edit
(check), compile (check), load (check), and debug (ooops). So what's
the story for jetpack debug?
So far we have heard from mozilla platform that jetpack will provide a
migration story for extensions. But I can't find any information on
that. Starting that discussion would engage extension developers.
Otherwise you are missing the primary source of criticism that can
make the system better.
Some concrete suggestions for architectural elements that would
support a migration story:
* Common JS based shared object loader to replace mozilla modules and
js components for extensions,
* purpose-focused sandbox toolkit layer, without jetpack content, as
a basis for jetpack sandboxes,
* undo library, outside of jetpack, as basis for jetpack undo,
* packaging, load, unload solution
jjb