Ross Gardler wrote:
> Tim Williams wrote:
> >Are pelt, tigris, and common the only current skins? The rest
> >(corium, forrest-site, krysalis-site, leather-dev, plain-dev) appear
> >to be either under development or deprecated. Also, is there a clear
> >way to determine which skins are deprecate
Message:
The following issue has been closed.
Resolver: David Crossley
Date: Fri, 27 May 2005 8:12 PM
Closing, because this was not the problem.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-507
Here
Tim Williams wrote:
I just added a simple patch but it got me thinking that maybe there
should be a little "skininfo.xml" in each skin directory where the
current status of the skin could be pulled vs. maintained in
skinlist2echo. I see the skin-1.xml hanging out with testskin1 and 2
but don't r
I just added a simple patch but it got me thinking that maybe there
should be a little "skininfo.xml" in each skin directory where the
current status of the skin could be pulled vs. maintained in
skinlist2echo. I see the skin-1.xml hanging out with testskin1 and 2
but don't really understand how t
The following issue has been updated:
Updater: Tim Williams (mailto:[EMAIL PROTECTED])
Date: Fri, 27 May 2005 11:17 AM
Comment:
Didn't get any more responses about the current state of skins so the
"available skins" output was changed to below.
--tim
Forrest provides the following
The following issue has been updated:
Updater: Tim Williams (mailto:[EMAIL PROTECTED])
Date: Fri, 27 May 2005 9:13 AM
Comment:
Unless I've oversimplified this, here's the change for this. "crust"
now goes to "pelt".
Skin aliasing for backwards compatability
0.5 => 0.6
Tim Williams wrote:
Is plain-dev really included by default?
Yes
plain-dev - success, but no resources found, images, script etc. and
they don't exist in the skins folder either.
Well it is in development :-))
Ross>
Tim Williams wrote:
Unless I've oversimplified this, here's the change for this. "crust"
now goes to "pelt".
Excellent, thanks for your contribution.
Please attach to the issue, it may get lost in the mail lists as I don;t
have time to apply it right now.
Ross
Unless I've oversimplified this, here's the change for this. "crust"
now goes to "pelt".
Skin aliasing for backwards compatability
0.5 => 0.6
krysalis-site => ... warn about future removal
forrest-site => ... warn about future removal
crust => pelt
forr
The following comment has been added to this issue:
Author: Pedro I. Sanchez
Created: Fri, 27 May 2005 8:54 AM
Body:
Sounds good. I will subscribe to the dev list and will open a new thread on
this topic. With your guidance I can put some time helping to implement
something. I'm
Is plain-dev really included by default? I just took a spin through
each of the skins and here's what I've found from a fresh svn.
pelt - success
tigris - success
common - success, but images not found even though they appear in the
skins folder
plain-dev - success, but no resources found, images
Tim Williams wrote:
Are pelt, tigris, and common the only current skins? The rest
(corium, forrest-site, krysalis-site, leather-dev, plain-dev) appear
to be either under development or deprecated. Also, is there a clear
way to determine which skins are deprecated?
The only officially support
Are pelt, tigris, and common the only current skins? The rest
(corium, forrest-site, krysalis-site, leather-dev, plain-dev) appear
to be either under development or deprecated. Also, is there a clear
way to determine which skins are deprecated?
I'd like to take on FOR-508 and FOR-509 as they a
The following issue has been updated:
Updater: Ross Gardler (mailto:[EMAIL PROTECTED])
Date: Fri, 27 May 2005 6:25 AM
Comment:
Reclassified to be fixed in the 0.7 release
Changes:
type changed from Task to Bug
priority changed from Minor to Major
The following issue has been updated:
Updater: Ross Gardler (mailto:[EMAIL PROTECTED])
Date: Fri, 27 May 2005 6:28 AM
Comment:
Scheduled for 0.7 release
Changes:
type changed from Task to Improvement
Version changed to 0.6
Component changed
[This discussion has migrated to dev issues, I've cc'd the dev list and
subsequent replies will go there, if you want to follow along you need
to join the dev list]
Maurice Lanselle wrote:
Ross Gardler said the following on 26/05/2005 22:07:
Thank you for taking the time to address my questio
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-509
Here is an overview of the issue:
-
Key
Thorsten Scherler wrote:
On Thu, 2005-05-26 at 18:20 -0400, Gregor J. Rothfuss wrote:
...
are you suggesting that it is easier to learn and use a DSL than to use
java? i don't buy that, sorry. the DSL is just a layer of indirection,
the real implementation (at least in lenya, dunno about for
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.cocoondev.org//browse/FOR-508
Here is an overview of the issue:
-
Key
On Thu, 2005-05-26 at 18:20 -0400, Gregor J. Rothfuss wrote:
> Thorsten Scherler wrote:
>
> > I do not like this expression 'programming in xml' it is more (like I
> > stated in other threads) 'configuring components with xml'.
>
> the crucial question will be where to draw the boundaries.
>
David Crossley wrote:
Antonio Gallardo wrote:
David Crossley dijo:
David Crossley wrote:
David Crossley wrote:
...
We would need either Tomcat or Jira so that we can test
our webapp in a servlet container. We also would run the
forrestbot webapp interface there, probably building the
"s
David Crossley wrote:
> We would need either Tomcat or Jira so that we can test
> our webapp in a servlet container.
Jira ---> jetty
Antonio Gallardo wrote:
> David Crossley dijo:
> > David Crossley wrote:
> >> David Crossley wrote:
>
> I saw the link, perhaps we can setup the default profile for all the users
> as stated in the link:
>
> PATH=/usr/bin:/usr/sfw/bin:/usr/sfw/sbin:/opt/sfw/bin: \
> /opt/sfw/sbin:/opt/SUNWspro/bi
On Vie, 27 de Mayo de 2005, 1:03, David Crossley dijo:
> David Crossley wrote:
>> David Crossley wrote:
>> > We have now been allocated a zone on the new server.
>> > So we need to define our goals and then start setting up
>> > some demo servers. We should get out of this RT thread
>> > and start
24 matches
Mail list logo
