On Nov 14, 2008, at 7:46 PM, Jim Gay wrote:
Have you first run
rake db:bootstrap
That was it. I hadn't created the development database yet. I'll
have to be more careful next time.
Thank you very much.
Jose
...
Jose Hales-Garcia
UCLA Department of Statistics
[EMAIL PROTECTED]
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Adam van den Hoven wrote:
Possibly but I find
">
not just unaesthetic, its offensive. If you're using a tag paradigm to
encapsulate functional bits, then mixing those tags into attribute
values are only confusing and you will not be able to leverage an
existing tool (like an extensible XML base WYSIWIG component... not
that there are many but I can dream). IMO, if you're following this
paradigm you should be thinking in terms of extending HTML not doing
something independent of HTML.
I agree. I'm not offended per se, but I do find it really hard to
follow visually.
In fact I find myself wondering whether radius could easily be tweaked
to parse something different (I mean, we can easily change it to accept
instead of using 'r' could we also do {{title}} or content (part => 'sidebar') !> or [insert your idea here].
Of course, once I open that door, I start wondering about languages like
liquid -- some sort of more well-rounded tool. I created the
conditional_tags extension to address one of these needs but you'll
never make radius pull off stuff like if/else if/else behavior.
But I'm way off topic now.
Sorry. I jumped to a new idea. I should have signaled that better ;)
I mean that I want to use jQuery and the Metadata plugin. JQuery comes
from a public CDN so I can use it externally (unless I'm behind HTTPS)
but even if there is a public copy of the meta plugin, I probably
shouldn't be stealing someone else's bandwidth. So I need to import
that into my machine. Right now, I have to download then upload it.
But if I can just point to the tarball or bare code, on the
originating server ( and easily update to the latest version) I can
save a lot of time.
But there is no maintaining lists. I give you the URL of some file or
GIT repository which you then download, decompose and copy the
contents into the appropriate asset
I'd love to see that -- but I'm not sure I'd build it. From the average
user's perspective, not much time is spent with radiant mucking around
with css and js. For a brief period of time during each project, we're
really focused there, then it's off to the "important" stuff. I guess
that makes my threshold for pain is higher for those elements.
So on this one I'd probably pull out the "we're accepting patches" card ;-).
Actually it would probably be better as an extension -- SnS is fully
extendable, you know. I worked shards into it so you can override
elements, insert partials, the whole bit.
-Chris
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Have you first run
rake db:bootstrap
?
The first error says that the 'extension_meta' table does not exist.
The second says that the 'pages' table does not exist
On Nov 14, 2008, at 9:58 PM, Jose Hales-Garcia wrote:
Hello Radiant list,
I'm going through the online tutorial on creating extensions and am
getting errors. I've tried creating the extension with a project
using the Sqlite3 adaptor (project_1) and with another project using
the PostgeSQL adaptor (project_2). Both give errors, albeit
different ones. Project 1 gives errors when I try to run the
migration. Project 2 gives errors when I attempt to generate the
extension. Below are the error messages. (I'm doing this on a
Leopard system.)
Any advice would be much appreciated.
Thank you,
Jose
The Sqlite3 error:
[mb2:CMS/radiant/project_1] hg% rake db:migrate:extensions --trace
(in /Users/hg/Sites/Rails/CMS/radiant/project_1)
** Invoke db:migrate:extensions (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:migrate:extensions
rake aborted!
Could not find table 'extension_meta'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/connection_adapters/sqlite3_adapter.rb:29:in
`table_structure'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/../../activesupport/lib/active_support/core_ext/object/misc.rb:
28:in `returning'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/connection_adapters/sqlite3_adapter.rb:28:in
`table_structure'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/connection_adapters/sqlite_adapter.rb:189:in
`columns'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1080:in `columns'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1093:in `column_names'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1106:in `column_methods_hash'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1555:in `all_attributes_exists?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/../../activesupport/lib/active_support/inflector.rb:257:in `all?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1555:in `each'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1555:in `all?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1555:in `all_attributes_exists?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1506:in `method_missing'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/extension.rb:
56:in `meta'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/extension.rb:
27:in `meta'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:38:in `current_version'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/migration.rb:414:in `irrelevant_migration?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/migration.rb:345:in
`migrate_without_extension_support'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/migration.rb:339:in `each'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/migration.rb:339:in
`migrate_without_extension_support'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:33:in `migrate'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:6:in `migrate_extensions'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:5:in `each'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:5:in `migrate_extensions'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/tasks/extensions.rake:8
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `call'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `execute'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `execute'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:578:in
`invoke_with_call_chain'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
1.8/monitor.rb:242:in `synchronize'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:571:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:564:in `invoke'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:2019:in
`invoke_task'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level'
/Library/Ruby/Gem
Hello Radiant list,
I'm going through the online tutorial on creating extensions and am
getting errors. I've tried creating the extension with a project
using the Sqlite3 adaptor (project_1) and with another project using
the PostgeSQL adaptor (project_2). Both give errors, albeit different
ones. Project 1 gives errors when I try to run the migration.
Project 2 gives errors when I attempt to generate the extension.
Below are the error messages. (I'm doing this on a Leopard system.)
Any advice would be much appreciated.
Thank you,
Jose
The Sqlite3 error:
[mb2:CMS/radiant/project_1] hg% rake db:migrate:extensions --trace
(in /Users/hg/Sites/Rails/CMS/radiant/project_1)
** Invoke db:migrate:extensions (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:migrate:extensions
rake aborted!
Could not find table 'extension_meta'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/connection_adapters/sqlite3_adapter.rb:29:in
`table_structure'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/../../activesupport/lib/active_support/core_ext/object/misc.rb:
28:in `returning'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/connection_adapters/sqlite3_adapter.rb:28:in
`table_structure'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/connection_adapters/sqlite_adapter.rb:189:in `columns'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1080:in `columns'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1093:in `column_names'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1106:in `column_methods_hash'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1555:in `all_attributes_exists?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/../../activesupport/lib/active_support/inflector.rb:257:in `all?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1555:in `each'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1555:in `all?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1555:in `all_attributes_exists?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/base.rb:1506:in `method_missing'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/extension.rb:
56:in `meta'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/extension.rb:
27:in `meta'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:38:in `current_version'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/migration.rb:414:in `irrelevant_migration?'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/migration.rb:345:in
`migrate_without_extension_support'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/migration.rb:339:in `each'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/
lib/active_record/migration.rb:339:in
`migrate_without_extension_support'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:33:in `migrate'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:6:in `migrate_extensions'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:5:in `each'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/radiant/
extension_migrator.rb:5:in `migrate_extensions'
/Library/Ruby/Gems/1.8/gems/radiant-0.6.9/lib/tasks/extensions.rake:8
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `call'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:617:in `execute'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:612:in `execute'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:578:in
`invoke_with_call_chain'
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/
1.8/monitor.rb:242:in `synchronize'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:571:in
`invoke_with_call_chain'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:564:in `invoke'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:2019:in `invoke_task'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `each'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:1997:in `top_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:2036:in
`standard_exception_handling'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:1991:in `top_level'
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake.rb:1970:in `run'
/Library/Ruby/Ge
Jay Levitt said the following on 11/14/2008 06:19 PM:
> Sean Cribbs wrote:
>> I have decided to extend the Template Contest deadline to January 1,
>> 2009. Sadly, we received no entries by the October 31 deadline.
>
> [...]
>
> So I could contribute that. BUT: It won't be a full "template", in the sense
> that there's no art, and not much graphic design; it's really an
> infrastructure thing, not a ready-to-use template. It should make it easier
> for someone to create a nicely-done theme, though. (In fact, I was thinking
> that if I released it, it should have some godawful hideous colors to force
> users to change them...)
Are we actually artists? I'm not.
I've taken one of Andreas Viklund's 'free' designs, isolated areas,
factored out snippets, dug out a logo from years ago, stuff and stuff an
stuff...
The trouble is that a lot of the snippets are being made obsolete as new
stuff gets written (like 'siblings' and other ways of doing navigation).
Assets or paperclips?
But the result isn't something I think could be submitted as its too
geared towards the one site, too may things like the logo and navigation
not 'generalized'.
But it does raise another question. There are some good basic templates
out there. Andreas Viklund also has some excellent models of two and
three panel layouts with various arrangements. Perhaps we should look
to packaging those - with permission and acknowledgement of course.
--
My definition of a free society is a society where it is safe to be
unpopular.
Adlai E. Stevenson Jr., Speech in Detroit, 7 Oct. 1952
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Thanks for the update. I've just installed import_export and
super_export for some testing this weekend and will look at them.
On the same note, I've been emailing back and forth with Anton Aylward
about an issue he had with SnS when he copied and pasted db tables from
one sqlite3 db into another (using sqliteman). In his case the
effectively_updated_at fields were also set to null. And this crashes
the app when caching. I figured it was just the way he copied and
pasted but if import-export is doing it too then I'm not sure what's up.
Anybody out there know why a table with values in it would wipe out
datetime values during an export or import?
-Chris
Nate Turnage wrote:
On Wed, Nov 12, 2008 at 11:32 PM, Chris Parrish <
[EMAIL PROTECTED]> wrote:
I'm getting ready to roll out a new SnS version this weekend with some bug
fixes and a column name change (requested and implemented by Andrew Neil to
help it work with his file_system extension).
I am having problems using files uploaded/created with the import_export
extension. I create my apps on my laptop then use import_export to pull the
db content into the file system and add that to my subversion repo.
The problem is that when I cap deploy the app to the production server and
use import_export to rake the db content into the production server the
class info for the css and js files is set as null which means that they
don't show up in the admin portion of the app. The "effectively_updated_at"
fields are also null in the text_asset_dependencies table. I don't know if
that's a SnS issue or an import_export issue, but I thought I would mention
it as long as you are asking for requests.
Thanks,
Nate
___
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
On 14-Nov-08, at 3:01 PM, Chris Parrish wrote:
Adam van den Hoven wrote:
support for external libraries
I really just want 1 tag to use for all these assets
they can be always "as link"
If you really want to be cool, "know" ahead of time all the
important libraries and their versions (kinda like how the google
Ajax Libraries API works -- http://code.google.com/apis/
ajaxlibs/) so I can do version="2.6" minimized='true' />
But also just http://scriptsite.com/
somelibrary" />
Sounds neat -- though I'm *positive* you don't want me anywhere
near any project that requires constant maintenance to keep up-to-
date with the latest libraries.
Couple of questions, though:
* If you know the url, what's the benefit of using the
/> tag? I mean sure, it renders the link for you but that's not
so bad to type manually.
* How would it be helpful for SnS to have it's own list of
libraries
when the Google api you offered already does this?
I'm really not trying to beat the "you can already do this" drum,
but why not just type:
http://www.google.com/jsapi";>
google.load("prototype", "1.6");
google.load("scriptaculous", "1.8.1");
Perhaps I'm over doing it. I generally like having on way to do
things, so using and together violates my
sense of aesthetics.
Ah. Makes sense. Actually I lean towards John and Sean's
suggestions that tags not render markup (that way you can use them
safely with filters or in pages that aren't html). That's why my
tags just render the content by default and offer an as="url" to
render that property. Whereas the as="inline" and as="link" are
viewed more as "bonus" or "convenience" tools.
Possibly but I find
">
not just unaesthetic, its offensive. If you're using a tag paradigm to
encapsulate functional bits, then mixing those tags into attribute
values are only confusing and you will not be able to leverage an
existing tool (like an extensible XML base WYSIWIG component... not
that there are many but I can dream). IMO, if you're following this
paradigm you should be thinking in terms of extending HTML not doing
something independent of HTML.
But maintaining a list of libraries is probably bad.
How about importing from remote URL so we don't have to download
then up load?
Hmm. If you already have a URL why not point your browser there and
copy the contents from your browser window (not download into a
file). Then paste the body of a new javascript in the Radiant UI?
Or do you mean SnS keeping a catalog of URLs so you wouldn't have to
know that off-hand? But that's beginning to sound like maintaining
a list again.
Sorry. I jumped to a new idea. I should have signaled that better ;)
I mean that I want to use jQuery and the Metadata plugin. JQuery comes
from a public CDN so I can use it externally (unless I'm behind HTTPS)
but even if there is a public copy of the meta plugin, I probably
shouldn't be stealing someone else's bandwidth. So I need to import
that into my machine. Right now, I have to download then upload it.
But if I can just point to the tarball or bare code, on the
originating server ( and easily update to the latest version) I can
save a lot of time.
But there is no maintaining lists. I give you the URL of some file or
GIT repository which you then download, decompose and copy the
contents into the appropriate asset
Or, if you want to keep your list of google.load's in their own
javascript file (named, say, "google.loads"), you could just:
http://www.google.com/jsapi";>
I want to make sure I'm understanding your ideas. (Thanks for the
tip on google, BTW. I've never used that and think that it'd be a
nice addition -- looks like they even minify stuff for us).
I tend to toss ideas out to see what's good or not. This was
probably not.
No worries. I'm the same actually. Sometimes things get clearer in
the communicating.
It's challenging on my end too because I can come across as beating
down all your ideas which can be discouraging. In my book if I
throw out 200 dumb ideas and come up with one really usable one,
that's a win.
So keep 'em coming.
What about interacting paperclipped? Not the bucket, per se, but
the tags for sure are useful.
Big on my list. Same with Page Attachments.
So this is brings up something similar to what I just said previously.
There are some javascript plugins that you are going to download that
have some skinning. So you have javascript, css and images all in one
tarball (or something similar)... when you explode the tarball, if you
could present a tree view of the data and allow the user to select
which bits to import, rewrite URLs in the CSS... Ok. maybe thats WAY
too compl
Sean Cribbs wrote:
I have decided to extend the Template Contest deadline to January 1,
2009. Sadly, we received no entries by the October 31 deadline.
I've been thinking that as I finish up^h^h^h^hstart my blog, it would be
nice to have a DRY blogging template for Radiant. I started with Sean's,
which he so nicely pastied for us, but I keep getting confused; the layouts
render the pages which render their children which inherit the thing which
has its own layout which... at the moment, I've got all the templates
printed out and sitting on my kitchen table.
So I could contribute that. BUT: It won't be a full "template", in the sense
that there's no art, and not much graphic design; it's really an
infrastructure thing, not a ready-to-use template. It should make it easier
for someone to create a nicely-done theme, though. (In fact, I was thinking
that if I released it, it should have some godawful hideous colors to force
users to change them...)
Any interest?
Jay Levitt
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Adam van den Hoven wrote:
support for external libraries
I really just want 1 tag to use for all these assets
they can be always "as link"
If you really want to be cool, "know" ahead of time all the
important libraries and their versions (kinda like how the google
Ajax Libraries API works -- http://code.google.com/apis/ajaxlibs/)
so I can do minimized='true' />
But also just http://scriptsite.com/somelibrary"; />
Sounds neat -- though I'm *positive* you don't want me anywhere near
any project that requires constant maintenance to keep up-to-date
with the latest libraries.
Couple of questions, though:
* If you know the url, what's the benefit of using the tag? I mean sure, it renders the link for you but that's not
so bad to type manually.
* How would it be helpful for SnS to have it's own list of libraries
when the Google api you offered already does this?
I'm really not trying to beat the "you can already do this" drum, but
why not just type:
http://www.google.com/jsapi";>
google.load("prototype", "1.6");
google.load("scriptaculous", "1.8.1");
Perhaps I'm over doing it. I generally like having on way to do
things, so using and together violates my
sense of aesthetics.
Ah. Makes sense. Actually I lean towards John and Sean's suggestions
that tags not render markup (that way you can use them safely with
filters or in pages that aren't html). That's why my tags just render
the content by default and offer an as="url" to render that property.
Whereas the as="inline" and as="link" are viewed more as "bonus" or
"convenience" tools.
But maintaining a list of libraries is probably bad.
How about importing from remote URL so we don't have to download then
up load?
Hmm. If you already have a URL why not point your browser there and
copy the contents from your browser window (not download into a file).
Then paste the body of a new javascript in the Radiant UI?
Or do you mean SnS keeping a catalog of URLs so you wouldn't have to
know that off-hand? But that's beginning to sound like maintaining a
list again.
Or, if you want to keep your list of google.load's in their own
javascript file (named, say, "google.loads"), you could just: