Paul Bolger wrote:
> I think the appropriate time to do this would be immediately after the
> official dispatcher release. Anyone interested in collaborating?
Since I understand the JavaScript of the menu system now I'd be happy
to help.
--
Ferdinand Soethe
> El lun, 16-01-2006 a las 17:05 +0100, Gavin (JIRA) escribió:
>> [
>> http://issues.apache.org/jira/browse/FOR-790?page=comments#action_12362854
>> ]
>>
>> Gavin commented on FOR-790:
>> ---
>>
>> This can be avoided by using onFocus inline for Form values instead of
(After answers i will put this into the Howto Structurer.)
I wanted to quickly see how an existing site goes
with the new Dispatcher.
1) added structurer and themer plugins to forrest.properties
2) deployed structurer plugins with etc/structurer.sh
3) localhost:/index.html ... fantastic.
Now
Remove the view prototype
-
Key: FOR-791
URL: http://issues.apache.org/jira/browse/FOR-791
Project: Forrest
Type: Task
Components: Dispatcher (aka views)
Reporter: Thorsten Scherler
Remove all view (v1 - prototyp) releated resources
El lun, 16-01-2006 a las 17:51 +1300, Paul Bolger escribió:
> Hi Thorsten, I've been trying to digest your replies before answering.
> Not easy when I understand about 20% of it...
Ok, please keep on asking questions to bring you closer to 100%. ;-) If
I can get you to this all other future user/d
El lun, 16-01-2006 a las 17:05 +0100, Gavin (JIRA) escribió:
> [
> http://issues.apache.org/jira/browse/FOR-790?page=comments#action_12362854 ]
>
> Gavin commented on FOR-790:
> ---
>
> This can be avoided by using onFocus inline for Form values instead of
> calling
[ http://issues.apache.org/jira/browse/FOR-787?page=all ]
Cyriaque Dupoirieux updated FOR-787:
Summary: Migrate themer contracts to dispatcher v3 (was: Migrate pelt
theme from themer to dispatcher v3)
> Migrate themer contracts to dispatcher v3
> -
[
http://issues.apache.org/jira/browse/FOR-790?page=comments#action_12362854 ]
Gavin commented on FOR-790:
---
This can be avoided by using onFocus inline for Form values instead of calling
the getBlank.js script.
A generic e.g to adapt :-
Username
Head part is included as many times a contract is used
--
Key: FOR-790
URL: http://issues.apache.org/jira/browse/FOR-790
Project: Forrest
Type: Improvement
Components: Dispatcher (aka views)
Versions: 0.8-de
Ross Gardler wrote:
> David Crossley wrote:
> >Thanks for the thoughts on the other aspects - very helpful.
> >
> >Ross Gardler wrote:
> >
> >>In use cases like this one, the locationmap would map *.xml to something
> >>like *.anakia.xml.
> >
> >
> >This sounds interesting.
> >
> >There is another
David Crossley wrote:
Thanks for the thoughts on the other aspects - very helpful.
Ross Gardler wrote:
In use cases like this one, the locationmap would map *.xml to something
like *.anakia.xml.
This sounds interesting.
There is another problem. To get the xml output happening
for the whol
Cyriaque Dupoirieux wrote:
Whaaaooouu !
Thx to Ross and David for this wonderfull feature (indeed !)
Actually that is one of the features of Jira, we did nothing other.
Ross
Thanks for the thoughts on the other aspects - very helpful.
Ross Gardler wrote:
>
> In use cases like this one, the locationmap would map *.xml to something
> like *.anakia.xml.
This sounds interesting.
There is another problem. To get the xml output happening
for the whole site in 'forrest s
Can someone with enough rights change the type of this FOR into Bug
please...
Cyriaque,
Cyriaque Dupoirieux (JIRA) a écrit :
Problem chaining hooks with the same name with dispatcher v3
Key: FOR-788
URL: http://iss
default variable filename is always set to 'index.html' in dispatcher v3
Key: FOR-789
URL: http://issues.apache.org/jira/browse/FOR-789
Project: Forrest
Type: Bug
Components: Dispatcher (aka v
Problem chaining hooks with the same name with dispatcher v3
Key: FOR-788
URL: http://issues.apache.org/jira/browse/FOR-788
Project: Forrest
Type: New Feature
Components: Dispatcher (aka views)
Vers
Whaaaooouu !
Thx to Ross and David for this wonderfull feature (indeed !)
Cyriaque,
Cyriaque Dupoirieux a écrit :
Thx, I already have tried with the FOR-787 and two commits, now I am
waiting to see ;-)
Salutations
Cyriaque,
Ross Gardler a écrit :
Cyriaque Dupoirieux wrote:
I don't
David Crossley wrote:
Ross Gardler wrote:
David Crossley wrote:
I have a partially working output plugin to generate a
plain xml document type solely to be consumed by Anakia. [1]
They can it "xdoc".
However, i have an issue at the moment. Can you help?
I want the output to be .xml filename
Cyriaque Dupoirieux wrote:
>
> Hi Ross,
>
>I don't know how you've linked the submits in the FOR-726.
>I would be pleased to do the same for the pelt contracts migration...
>
When you do the 'svn commit' then add the FOR-XXX number
to your commit message. See the example messages down t
Thx, I already have tried with the FOR-787 and two commits, now I am
waiting to see ;-)
Salutations
Cyriaque,
Ross Gardler a écrit :
Cyriaque Dupoirieux wrote:
I don't know how you've linked the submits in the FOR-726.
I would be pleased to do the same for the pelt contracts migratio
Cyriaque Dupoirieux wrote:
I don't know how you've linked the submits in the FOR-726.
I would be pleased to do the same for the pelt contracts migration...
Create an issue and add the issue number (FOR-*) to the commit message
in SVN - that's it.
Ross
Ross Gardler wrote:
> David Crossley wrote:
> >I have a partially working output plugin to generate a
> >plain xml document type solely to be consumed by Anakia. [1]
> >They can it "xdoc".
> >
> >However, i have an issue at the moment. Can you help?
> >
> >I want the output to be .xml filename exte
Migrate pelt theme from themer to dispatcher v3
---
Key: FOR-787
URL: http://issues.apache.org/jira/browse/FOR-787
Project: Forrest
Type: New Feature
Components: Dispatcher (aka views)
Versions: 0.8-dev
Repo
Hi Ross,
I don't know how you've linked the submits in the FOR-726.
I would be pleased to do the same for the pelt contracts migration...
Cyriaque,
[EMAIL PROTECTED] wrote:
Author: cdupoirieux
Date: Fri Jan 13 07:55:50 2006
New Revision: 368762
URL: http://svn.apache.org/viewcvs?rev=3
Cyriaque Dupoirieux wrote:
Hi,
I wonder why theFOR-urgency-blocker filter of JIRA only returns one
FOR and not 6 (There are 6 blockers FOR in the JIRA portal)
5 of those "blockers" are on plugins not core. The FOR-urgency-blocker
filter is showing us blockers for core, i.e. blockers on ou
David Crossley wrote:
I have a partially working output plugin to generate a
plain xml document type solely to be consumed by Anakia. [1]
They can it "xdoc".
However, i have an issue at the moment. Can you help?
I want the output to be .xml filename extension, but of
course Forrest uses that fo
Cyriaque Dupoirieux wrote:
>
>I wonder why theFOR-urgency-blocker filter of JIRA only returns one
> FOR and not 6 (There are 6 blockers FOR in the JIRA portal)
Because we have a new field called "urgency" and we
have only declared one issue as blocker.
There is 6 listed on the default Jira
Hi,
I wonder why theFOR-urgency-blocker filter of JIRA only returns one
FOR and not 6 (There are 6 blockers FOR in the JIRA portal)
--
Salutations,
Cyriaque,
I have a partially working output plugin to generate a
plain xml document type solely to be consumed by Anakia. [1]
They can it "xdoc".
However, i have an issue at the moment. Can you help?
I want the output to be .xml filename extension, but of
course Forrest uses that for its internal format. I
29 matches
Mail list logo
