Re: [Radiant] Drop down menus?

2008-05-27 Thread [EMAIL PROTECTED]
On Tue, 2008-05-27 at 10:20 -0500, Sean Cribbs wrote:
 Nate,
 
 It depends on how you want to generate those menus.  r:navigation is 
 best for single list navigation menus that have highlighting, not nested 
 menus.  However, assuming you'll be generating the navigation from the 
 page structure, you could do something like this:
 
 r:find url=/
 ul
 r:children:each
   lir:link/
 r:if_children
 ul
   r:children:eachlir:link //li/r:children:each
 /ul
 /r:if_children/li
 /r:children:each
 /ul
 /r:find
 
 That will generate a list based on the homepage's children and 
 grandchildren pages.

OMG! Are you kidding me? It's that easy? I am really loving the switch
to Radiant.

One question though, I am using r:navigation to show the current page
with :here and :selected methods(?), so how would this work with the
markup you described?


~Nate

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] gallery extension

2008-05-27 Thread Steven Southard
I am, great job of moving it to git.  Very easy to get and install.  I  
thought maybe there are some requirements like imagemagick and  
rmagick.  I don't have those gems installed so if they're needed it  
makes sense, I guess.  If they are needed seems like it would be a  
good idea to add that to the readme file.



On May 27, 2008, at 2:46 AM, Andrea Franz wrote:


On Mon, May 26, 2008 at 10:16 PM, Steven Southard
[EMAIL PROTECTED] wrote:
I installed .6.7 and then I tried to use the gallery extension with  
some
difficulties.  It all seemed to install properly but uploaded  
images aren't
added to the gallery.  The images are uploaded, It's just that my  
gallery
says 0 files and of course there's nothing in the gallery.  Anyone  
else have

this problem?


It's strange, are you using the latest version of the gallery?

--
Andrea Franz
http://gravityblast.com - http://nimboo.net
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Drop down menus?

2008-05-27 Thread Anton Aylward
Given that nested list, there are a number of sites that show how to do
the 'suckerfish' pull-downs using ONLY CSS.

Sean Cribbs said the following on 27/05/08 11:20 AM:
 Nate,
 
 It depends on how you want to generate those menus.  r:navigation is 
 best for single list navigation menus that have highlighting, not nested 
 menus.  However, assuming you'll be generating the navigation from the 
 page structure, you could do something like this:
 
 r:find url=/
 ul
 r:children:each
   lir:link/
 r:if_children
 ul
   r:children:eachlir:link //li/r:children:each
 /ul
 /r:if_children/li
 /r:children:each
 /ul
 /r:find
 
 That will generate a list based on the homepage's children and 
 grandchildren pages.
 
 Sean
 
 [EMAIL PROTECTED] wrote:
 I am new to Radiant and using radiant tags, and I am having trouble
 finding a solution for drop-down menus using r:navigation. What I want
 to do is this, similar to the suckerfish dropdowns from alistapart.com
 (http://www.alistapart.com/articles/dropdowns) :

 ul
  liMenu Item 1/li
  ul
  ?liSub Menu Item 1/li
  ?liSub Menu Item 2/li
  ?liSub Menu Item 3/li
  /ul
  ?liMenu Item 2/li
  ?liMenu Item 3/li
 /ul

 Are there any facilities for this in r:navigation or do I need to cobble
 this together by hand? Thanks in advance.


-- 
Many of life's failures are people who did not realize how close they
were to success when they gave up.
Thomas A. Edison
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] RailsConf plans

2008-05-27 Thread Victor Cosby
I'm trying to find a room share for Thursday thru Sunday. Anyone have  
a spare bed that would like to split the cost?


Thanks,
Victor

Sent from my iPhone


Victor Cosby
Independent Software Consultant and Web Developer
Cosby Ventures LLC
t. 206.399.0971
e. [EMAIL PROTECTED]
http://www.cosbyventures.com

On May 27, 2008, at 5:19 AM, Sean Cribbs [EMAIL PROTECTED] wrote:

I posted on the Radiant blog various things that are happening at  
RailsConf this week in Portland for Radiant people.  I look forward  
to meeting some more of you there.  I had a great time last year and  
this year promises to be just as fun.  If you want to meetup, come  
to the code drive, BoF or ping me via IRC or IM.  Here's some  
contact info:


Skype/GoogleTalk: seancribbs
IRC: seancribbs in #radiantcms on Freenode

Of course, you can always email me at this address.

Sean

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] gallery extension

2008-05-27 Thread Keith Bingman
Is Spring a BSD Server or a shared accelerator? Don't take my word  
about mini_magick, it worked when I was still on a BSD server.


On May 27, 2008, at 6:30 PM, Steven Southard wrote:

That's sad news about mini_magick not working at Joyent even if you  
freeze it in.  I guess the available gems depends on what server  
you're on.  I'm on Spring and here is the list of gems:


*** LOCAL GEMS ***

actionmailer (2.0.2)
actionpack (2.0.2)
activerecord (2.0.2)
activeresource (2.0.2)
activesupport (2.0.2)
BlueCloth (1.0.0)
capistrano (2.2.0)
cgi_multipart_eof_fix (2.5.0)
daemons (1.0.10)
extensions (0.6.0)
fast_xs (0.6)
fastthread (1.0.1)
ferret (0.11.6)
filesystem (0.1.0)
gem_plugin (0.2.3)
gruff (0.3.1)
highline (1.4.0)
hoe (1.5.1)
hpricot (0.6)
log4r (1.0.5)
mime-types (1.15)
mongrel (1.1.4)
mongrel_cluster (1.0.5)
needle (1.3.0)
needle-extras (1.0.0)
net-sftp (1.1.1)
net-ssh (1.1.2)
postgres (0.7.9.2008.01.28)
rails (2.0.2)
rake (0.8.1)
RedCloth (3.0.4)
ruby-json (1.1.2)
ruby-openid (2.0.4)
ruby-yadis (0.3.4)
rubyforge (0.4.5)
rubygems-update (1.0.1)
syntax (1.0.0)
tzinfo (0.3.8)



On May 27, 2008, at 11:19 AM, Keith Bingman wrote:


Are you sure Joyent doesn't have RMagick?

I have a couple of Radiant sites there using both my own extensions  
and Sean's page_attachments with RMagick. Mini_magick does not work  
there, even if you freeze the gem.


I just discovered Paperclip, http://www.thoughtbot.com/projects/paperclip 
. It resizes images without RMagick or Mini_magick, just using the  
image_magick library itself. I have a prototype extension based on  
it, though it is not a full fledged gallery like Andrea's.

_
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] gallery extension

2008-05-27 Thread Steven Southard
Shared accelerator.  Seems like the BSD servers were loaded with  
almost every gem out there.  Not sure why but the new servers are more  
bring your own.



On May 27, 2008, at 11:35 AM, Keith Bingman wrote:

Is Spring a BSD Server or a shared accelerator? Don't take my word  
about mini_magick, it worked when I was still on a BSD server.


On May 27, 2008, at 6:30 PM, Steven Southard wrote:

That's sad news about mini_magick not working at Joyent even if you  
freeze it in.  I guess the available gems depends on what server  
you're on.  I'm on Spring and here is the list of gems:


*** LOCAL GEMS ***

actionmailer (2.0.2)
actionpack (2.0.2)
activerecord (2.0.2)
activeresource (2.0.2)
activesupport (2.0.2)
BlueCloth (1.0.0)
capistrano (2.2.0)
cgi_multipart_eof_fix (2.5.0)
daemons (1.0.10)
extensions (0.6.0)
fast_xs (0.6)
fastthread (1.0.1)
ferret (0.11.6)
filesystem (0.1.0)
gem_plugin (0.2.3)
gruff (0.3.1)
highline (1.4.0)
hoe (1.5.1)
hpricot (0.6)
log4r (1.0.5)
mime-types (1.15)
mongrel (1.1.4)
mongrel_cluster (1.0.5)
needle (1.3.0)
needle-extras (1.0.0)
net-sftp (1.1.1)
net-ssh (1.1.2)
postgres (0.7.9.2008.01.28)
rails (2.0.2)
rake (0.8.1)
RedCloth (3.0.4)
ruby-json (1.1.2)
ruby-openid (2.0.4)
ruby-yadis (0.3.4)
rubyforge (0.4.5)
rubygems-update (1.0.1)
syntax (1.0.0)
tzinfo (0.3.8)



On May 27, 2008, at 11:19 AM, Keith Bingman wrote:


Are you sure Joyent doesn't have RMagick?

I have a couple of Radiant sites there using both my own  
extensions and Sean's page_attachments with RMagick. Mini_magick  
does not work there, even if you freeze the gem.


I just discovered Paperclip, http://www.thoughtbot.com/projects/paperclip 
. It resizes images without RMagick or Mini_magick, just using the  
image_magick library itself. I have a prototype extension based on  
it, though it is not a full fledged gallery like Andrea's.

_
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] gallery extension

2008-05-27 Thread Casper Fabricius
Keith, just curious: How does Paperclip differ from attachment_fu? It  
seems to have almost the exact same interface - is the only difference  
that paperclip does not require rmagick, mini-magick or imagescience?


Casper Fabricius
http://casperfabricius.com

On 27/05/2008, at 18:19, Keith Bingman wrote:


Are you sure Joyent doesn't have RMagick?

I have a couple of Radiant sites there using both my own extensions  
and Sean's page_attachments with RMagick. Mini_magick does not work  
there, even if you freeze the gem.


I just discovered Paperclip, http://www.thoughtbot.com/projects/paperclip 
. It resizes images without RMagick or Mini_magick, just using the  
image_magick library itself. I have a prototype extension based on  
it, though it is not a full fledged gallery like Andrea's.


Keith Bingman
http://keithbingman.com




On May 27, 2008, at 6:07 PM, Steven Southard wrote:

Oh, mini_magick might be better.  I'm hosting on Joyent and they  
don't have rmagick.  They don't have mini_magick either but I might  
be able to freeze that one in.  What changes do I need to make to  
have it work with mini_magick?



On May 27, 2008, at 10:48 AM, Andrea Franz wrote:


On Tue, May 27, 2008 at 5:37 PM, Steven Southard
[EMAIL PROTECTED] wrote:
I am, great job of moving it to git.  Very easy to get and  
install.  I
thought maybe there are some requirements like imagemagick and  
rmagick.  I
don't have those gems installed so if they're needed it makes  
sense, I
guess.  If they are needed seems like it would be a good idea to  
add that to

the readme file.


Yeah you need at least rmagick or mini_magick.
You are right, I'm going to add it in the README file.
Thank you very much and let me know if it works.

--
Andrea Franz
http://gravityblast.com - http://nimboo.net
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Drop down menus?

2008-05-27 Thread Marty Haught
 Well, only css and a little javascript. My query was about finding the
 most Radiant way to do it. Sean's solution got me through the list
 generating part, now it's up to me for the styling. I am aware of the
 various 'suckerfish' implementations. What I am not familiar with is the
 radius way to auto-generate the site structure.

Nate, Sean's pointer on the if_self and if_self_or_ancestor tags is
key.  I have built site map snippets as well as dynamic navigation
with these. The other possible trick is you can use clever 'opt out'
page parts that can remove unwanted pages from this menu.  Such as :

r:unless_content part=no-nav
  lir:link /r:if_ancestor_or_self...
/r:unless_content 

In this example any page with a no-nav page part will be ignored.  You
can add these at the top level for things that you don't want to
appear in your menu but still be visible in other spaces.  You can
then make a sub-nav snippet that continues to refer to itself so that
you can nest down many levels.  Hopefully that gives you enough to go
on.

Cheers,
Marty
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] gallery extension

2008-05-27 Thread Keith Bingman
It is actually pretty different than attachment_fu. It doesn't require  
it's own model, just a few columns. It is a lot lighter weight. I  
actually like attachment_fu a lot, but it is a bit slow and it  
requires either RMagick, Mini_magick or Image Science, all of which  
are problematic. So I thought I would give it a try. So far, it seems  
nice, but I haven't really tried it in production yet.


Keith Bingman
http://keithbingman.com


On May 27, 2008, at 6:57 PM, Casper Fabricius wrote:

Keith, just curious: How does Paperclip differ from attachment_fu?  
It seems to have almost the exact same interface - is the only  
difference that paperclip does not require rmagick, mini-magick or  
imagescience?


Casper Fabricius
http://casperfabricius.com

On 27/05/2008, at 18:19, Keith Bingman wrote:


Are you sure Joyent doesn't have RMagick?

I have a couple of Radiant sites there using both my own extensions  
and Sean's page_attachments with RMagick. Mini_magick does not work  
there, even if you freeze the gem.


I just discovered Paperclip, http://www.thoughtbot.com/projects/paperclip 
. It resizes images without RMagick or Mini_magick, just using the  
image_magick library itself. I have a prototype extension based on  
it, though it is not a full fledged gallery like Andrea's.


Keith Bingman
http://keithbingman.com



___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


[Radiant] [ANN] Styles 'n Scripts Extension v0.3 Release

2008-05-27 Thread Chris Parrish
Based on some feedback that I've gotten from the list (thanks all!), 
I've added some new functionality and improved the existing.


NEW FEATURES

  1. Added  r:stylesheet and r:javascript tags for use in pages. 
 Based on the attributes, these tags will render:

 * The url to a css or js file
 * The content of a css or js file
 * The content of a css or js file wrapped in the appropriate
   style or script html tags.

  2. Added r:stylesheet and r:javascript tags for use in your
 stylesheets or javascripts -- and here's were it gets interesting
 -- so that you can do asset packaging (reference all of your
 javascripts or stylesheets in one main file to reduce server
 requests and speed page load time).

 What's really cool here is that the stylesheets and javascripts
 now track their own dependencies so your files all report an
 accurate LAST-MODIFIED date/time.  This keeps your server from
 having to re-serve your css and js files unless their content has
 truly changed.

 Fast page loads for visitors, reduced bandwidth and server
 requirements for you!


WHY USE STYLES 'N SCRIPTS
John originally suggested this extension so that should be good enough 
for you.  But in case you're still wondering, this extension offers:


   * Administrator or Developer permissions for accessing CSS or JS files

   * Better caching for these files (their cache isn't flushed every 5
 minutes like pages but, instead only when updates occur).  So your
 user's browser cache can go to work -- speeding page loads and
 minimizing server hits.

   * Separation of concerns - lets extensions that work with pages not
 get tripped up by CSS and JS files (examples include keyword
 searches that don't find text in your stylesheets, adding meta
 keyword or descriptions to pages but not stylesheets, using
 WYSIWYG or WYSIWYM editors like TinyMCE or FCKEditor to edit your
 pages but not your css or js files.  This also opens the door to
 extensions aimed at working just with css or js files (look for
 css  js minification coming soon).

   * Declutter the Pages tree view.  Now it only needs to show the
 content - not the assets.


WHERE TO GET IT
https://secure.svnrepository.com/s_swanki/open/radiant/extensions/styles_n_scripts/tags/v0.3

Requirements: Radiant 0.6.6+
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension

2008-05-27 Thread Chris Parrish

nurilized wrote:

is there any way to call js/css files from anywhere of the page/layout?
suppose, i use one template and many subpages?
 but i use different/extra css/js files on subpages (and also common), for
example i will use accordion script on a subpage and putting this on
template or on header snippet is nonsense
so i am looking for a way to call these files from inside page/layout
  
I just released version 0.3 of this extension and you will now find tags 
to do just this. For instance:


 r:stylesheet name=my_stylesheet /

produces:

 your stylesheet content

Or, if you want to be more fancy, try:

 r:stylesheet name=my_stylesheet as=inline /

and get:

 style type=text/css
 !--
 your stylesheet content
 --
 /style

The same works with the r:javascript tag.

-Chris
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension

2008-05-27 Thread Steven Southard
I just tried out your extension.  Nice idea.  I've always liked how  
the css file was exposed under pages but I really hadn't thought of it  
having it's own section either.  Also, I've always wondered where to  
put my js files.  I usually just tucked them in the javascript folder  
and referenced them. This gives them a proper place.   I mostly only  
use one stylesheet per website so it seems a bit overkill.  Not to be  
stingy with my tabs, but I think I'd like it better if the css and js  
pages were both under one tab.   I'm looking forward to seeing what  
becomes of this extension.


Thanks,

Steven



On May 27, 2008, at 1:28 PM, Chris Parrish wrote:


nurilized wrote:
is there any way to call js/css files from anywhere of the page/ 
layout?

suppose, i use one template and many subpages?
but i use different/extra css/js files on subpages (and also  
common), for

example i will use accordion script on a subpage and putting this on
template or on header snippet is nonsense
so i am looking for a way to call these files from inside page/layout

I just released version 0.3 of this extension and you will now find  
tags to do just this. For instance:


r:stylesheet name=my_stylesheet /

produces:

your stylesheet content

Or, if you want to be more fancy, try:

r:stylesheet name=my_stylesheet as=inline /

and get:

style type=text/css
!--
your stylesheet content
--
/style

The same works with the r:javascript tag.

-Chris
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Authentication again

2008-05-27 Thread Dan and Norine Simpson
Thanks, Josh!


On Tue, May 27, 2008 at 3:16 PM, Josh French [EMAIL PROTECTED] wrote:

 does Radiant plays well with rails
 plugins?  I recall something about differences in the file structures
 creating incompatibilities.


 Dan,

 Rails plugins (or the majority of them) work just fine under Radiant. You
 can place them in vendor/plugins or vendor/extensions/.../vendor/plugins. I
 like to keep a single copy of commonly used plugins such as attachment_fu,
 will_paginate, c in the main vendor dir; plugins that only apply to
 specific extensions get bundled with that extension. This way I don't have
 multiple copies of the common plugins, and the weird one-offs don't get left
 behind when I'm moving custom extensions between projects.

 Josh

 ___
 Radiant mailing list
 Post:   Radiant@radiantcms.org
 Search: http://radiantcms.org/mailing-list/search/
 Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Drop down menus?

2008-05-27 Thread Chris Parrish

Anton Aylward wrote:

There __ARE__ pure CSS pull-downs.
  


Anton, I couldn't get to the link you provided so just in case I wanted 
to make sure you and others were aware that you do need a bit of 
javascript with suckerfish menus if you plan to support IE 6 or lower 
(they only support the pseudo classes (like :hover) on a tags so you 
can have javascript add attributes to your DOM so the older IE's can 
play along).


If your requirements are only for newer browsers, then you can get by 
with true css-only drop down menus.


-Chris


I've always preferred them to the javascript ones for a  variety of
reasons, not least of which is that the ones I've used (go google) are
portable across browsers and work when javascript is turned off, as many
people do thinking that this makes them immune to things like XSS.


Her, for example, is a CSS generator with which you can even customize
the CSS

http://pixopoint.com/suckerfish_css/

  


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Error installing

2008-05-27 Thread Sean Cribbs

Ruslan,

Chances are unless it's a VPS, they won't let you update rubygems.  
Otherwise, try 'sudo gem update --system'.


Sean

Ruslan Gomez wrote:

I'm installing Radianr CMS on Mediatemple.

Everything had turn out perfect until:

RAILS_ENV=production rake db:bootstrap
which gave me
Radiant requires RubyGems = 0.9.4 (you have 0.9.2). Please `gem update
--system` and try again.

I've been trying to update the gems but I'm unsuccessful and after gem
update --system it will keep saying 0.9.2 on gem -v
  


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension

2008-05-27 Thread Chris Parrish
Thanks for the feedback Steven.  I'm really interested in making this a 
usable extension for all.


I always used pages for my js and css files too and, like you, never had 
more than a handful of each -- it wasn't much of a bother to do.  So, 
when John first mentioned the idea to me I really only saw one or two 
valid reasons for such an extension (for instance, I found it difficult 
to explain to users why they had to create a blank layout for a 
stylesheet just to set the content-type).


Now that I've been working on it, I see *many* good reasons to go this 
route (my current favorite is the server and browser caching benefits -- 
I *love* the idea of not having to expire and reserve all stylesheets 
and javascripts every 5 minutes).


As to the multiple tabs, yeah, I'm with you.  Originally I think John 
envisioned something like an Assets tab where CSS, JS and image files 
could all reside but Radiant hasn't settled on an image asset approach 
just yet.  And without images, what do you call the tab -- Text Assets?  
CSS  JS?  Assets-That-Don't-Happen-To-Include-Images?  Actually, my 
original mock-up for this extension had one tab (called Files) but I 
still kind of choked on that vague name.


Anyway, for now, John just suggested keeping two tabs and waiting to see 
how things progressed.  In the interest of minimizing tab space, I did 
choose to name them CSS and JS instead of Stylesheets and Javascripts.  
Plus, your standard-level users never see the tabs anyway so it looks 
clean to them.


I certainly welcome any ideas/suggestions here. Its a fairly 
straightforward design but nothing's set in stone.


-Chris


Steven Southard wrote:
I just tried out your extension.  Nice idea.  I've always liked how 
the css file was exposed under pages but I really hadn't thought of it 
having it's own section either.  Also, I've always wondered where to 
put my js files.  I usually just tucked them in the javascript folder 
and referenced them. This gives them a proper place.   I mostly only 
use one stylesheet per website so it seems a bit overkill.  Not to be 
stingy with my tabs, but I think I'd like it better if the css and js 
pages were both under one tab.   I'm looking forward to seeing what 
becomes of this extension.


Thanks,

Steven



On May 27, 2008, at 1:28 PM, Chris Parrish wrote:


nurilized wrote:

is there any way to call js/css files from anywhere of the page/layout?
suppose, i use one template and many subpages?
but i use different/extra css/js files on subpages (and also 
common), for

example i will use accordion script on a subpage and putting this on
template or on header snippet is nonsense
so i am looking for a way to call these files from inside page/layout

I just released version 0.3 of this extension and you will now find 
tags to do just this. For instance:


r:stylesheet name=my_stylesheet /

produces:

your stylesheet content

Or, if you want to be more fancy, try:

r:stylesheet name=my_stylesheet as=inline /

and get:

style type=text/css
!--
your stylesheet content
--
/style

The same works with the r:javascript tag.

-Chris
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension

2008-05-27 Thread Steven Southard
I must admit that assets that don't happen to include images  is a  
bit long.  I kind of like text assets.  That kind of opens it up to  
include other types of files that people may want to put there  
like .xml or maybe even a .as file.  One thing that would be nice  
about putting them together is that you could then make use of a file  
type combo box.  That would fill out the page a bit and give a person  
a little more to do.  Also those lovely icons would have a chance to  
help you sort out your file types.


-Steven

On May 27, 2008, at 8:50 PM, Chris Parrish wrote:

Thanks for the feedback Steven.  I'm really interested in making  
this a usable extension for all.


I always used pages for my js and css files too and, like you, never  
had more than a handful of each -- it wasn't much of a bother to  
do.  So, when John first mentioned the idea to me I really only saw  
one or two valid reasons for such an extension (for instance, I  
found it difficult to explain to users why they had to create a  
blank layout for a stylesheet just to set the content-type).


Now that I've been working on it, I see *many* good reasons to go  
this route (my current favorite is the server and browser caching  
benefits -- I *love* the idea of not having to expire and reserve  
all stylesheets and javascripts every 5 minutes).


As to the multiple tabs, yeah, I'm with you.  Originally I think  
John envisioned something like an Assets tab where CSS, JS and  
image files could all reside but Radiant hasn't settled on an image  
asset approach just yet.  And without images, what do you call the  
tab -- Text Assets?  CSS  JS?  Assets-That-Don't-Happen-To-Include- 
Images?  Actually, my original mock-up for this extension had one  
tab (called Files) but I still kind of choked on that vague name.


Anyway, for now, John just suggested keeping two tabs and waiting to  
see how things progressed.  In the interest of minimizing tab space,  
I did choose to name them CSS and JS instead of Stylesheets and  
Javascripts.  Plus, your standard-level users never see the tabs  
anyway so it looks clean to them.


I certainly welcome any ideas/suggestions here. Its a fairly  
straightforward design but nothing's set in stone.


-Chris


Steven Southard wrote:
I just tried out your extension.  Nice idea.  I've always liked how  
the css file was exposed under pages but I really hadn't thought of  
it having it's own section either.  Also, I've always wondered  
where to put my js files.  I usually just tucked them in the  
javascript folder and referenced them. This gives them a proper  
place.   I mostly only use one stylesheet per website so it seems a  
bit overkill.  Not to be stingy with my tabs, but I think I'd like  
it better if the css and js pages were both under one tab.   I'm  
looking forward to seeing what becomes of this extension.


Thanks,

Steven



On May 27, 2008, at 1:28 PM, Chris Parrish wrote:


nurilized wrote:
is there any way to call js/css files from anywhere of the page/ 
layout?

suppose, i use one template and many subpages?
but i use different/extra css/js files on subpages (and also  
common), for
example i will use accordion script on a subpage and putting this  
on

template or on header snippet is nonsense
so i am looking for a way to call these files from inside page/ 
layout


I just released version 0.3 of this extension and you will now  
find tags to do just this. For instance:


r:stylesheet name=my_stylesheet /

produces:

your stylesheet content

Or, if you want to be more fancy, try:

r:stylesheet name=my_stylesheet as=inline /

and get:

style type=text/css
!--
your stylesheet content
--
/style

The same works with the r:javascript tag.

-Chris
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


[Radiant] ajax call for save and continue editing and style changes

2008-05-27 Thread Steven Southard
I've been using this interface a lot lately and one thing that would  
make it much better for me is not having the page refresh when I hit  
save and continue editing.  This is especially true when I'm editing  
a long CSS file, I hate to image how much time I wasted looking for  
the place I was just editing.  A couple of other default style changes  
I think would help are to make the text area height about 600px also a  
bit skinnier and over to the right so I can grab the side easier and  
get to the save changes button.  Having to scroll down the page like  
that to get to the save button is kind of a pain as well.  I think the  
save button would be more useable if it were in that blank space to  
the right above the text area.


Regards,

-Steven
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant


[Radiant] admin page titles

2008-05-27 Thread Steven Southard
I've also noticed that all the admin pages have the same title so when  
I'm working on multiple pages in tabs I can never tell which is  
which.  If the admin pages were titled what they were it would make it  
easier to keep track of them.


Regards,

Steven
___
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant