Tim Williams wrote:
I personally like a stable trunk -- builds and runs without
hoop-jumping.
I think it is critical to keep the hoops required to an absolute
minimum for two simple reasons:
- even well documented hoops take time each time I set up a new
instance of Forrest (ok, this
Ross Gardler wrote:
I hadn't thought of that, but it triggered another requirement in my
mind, which happens to provide a solution.
I might add the need for a simple minimum seed for people who want to
start a fresh site w/o having to move all our demo junk out of it
first
AND
perhaps some
Ross Gardler wrote:
Personally, I think the current state of views is good enough for Trunk
(if we address the fresh-site issue). I've started to use it for a new
project, that's what I usually use as my yardstick. Lets see what others
say.
Playing with the default implementation it looks
for them.
Some of these questions are different for skins than they are for views
(skins = what skin? Which search box? where put it? etc., views = which
default view? which CSS? etc.)
Now look what you made me do, I almost created this already, I may as
well copy it into the locationmap
David Crossley wrote:
Ferdinand Soethe wrote:
Ross Gardler wrote:
I hadn't thought of that, but it triggered another requirement in my
mind, which happens to provide a solution.
I might add the need for a simple minimum seed for people who want to
start a fresh site w/o having to move all
Ferdinand Soethe wrote:
Ross Gardler wrote:
Personally, I think the current state of views is good enough for Trunk
(if we address the fresh-site issue). I've started to use it for a new
project, that's what I usually use as my yardstick. Lets see what others
say.
Playing with the default
Ferdinand Soethe wrote:
Ross Gardler wrote:
Furthermore, in my work on versioned plugins for the 0.7 release I took
us nearly all the way to having plugins used from the plugins directory
if they are present there. That would remove the need for a download or
a local-deploy for people using
bringing this up but in the current locationmap branch, we
have locationmap functionality==trunkable and
views==just-a-hair-shy-of-trunkable; the result is that it's difficult
to merge lcoationmap now even thought it's mature enough to be merged.
Granted the hurdles we're facing there are trivial but it's
With 0.7 finally out (congratulations everyone by the way, great work).
I'd like to take a vote on merging the locationmap branch with trunk.
The changes over there are:
Locationmap
---
This is pretty much functional, but not in any way complete. There are a
couple of outstanding
Obviously, my enthusiastic, [non-binding] +1
...
Views
-
Lots of work has been happening on views over there. These are totally
optional as they are whiteboard plugins.
I think I'd take out references to Views from the fresh-site prior
because right now we have to locally-deploy the
On 6/24/05, Ross Gardler [EMAIL PROTECTED] wrote:
Tim Williams wrote:
Obviously, my enthusiastic, [non-binding] +1
...
Views
-
Lots of work has been happening on views over there. These are totally
optional as they are whiteboard plugins.
I think I'd take out references to
this already, I may as
well copy it into the locationmap branch now. What do you think?
Ross
Ross Gardler wrote:
Tim Williams wrote:
I thought I'd read that views weren't going to get deployed until you
guys had a chance to review them at ApacheCon? If they're in fact
ready, then that would make things simpler.
Did we say that? I can't remember. I'd be willing to revisit that
As requested I have set up a branch with my experiments with the
locationmap. This branch is *not* to be used for any real work as I have
done little testing. It is merely for experimentation right now.
However, I do need the locationmap working in order to properly develop
the Daisy plugin.
There's obviously a good chance I'm doing something wrong but when I
build a seeded site based on the branch, i get:
* [129/4] [1/28]0.27s 7.8Kb /samples/usemap.html
* [130/3] [0/0] 0.151s 4.1Kb /samples/usemap.pdf
X [0]
Tim Williams wrote:
There's obviously a good chance I'm doing something wrong but when I
build a seeded site based on the branch, i get:
There's an equally good chance that in my experiments I have overlooked
important things, as is the (partly) the case here.
For the part that is not my
16 matches
Mail list logo
