From djlewis at acm.org  Sat Jan 20 12:55:36 2007
From: djlewis at acm.org (Deb Lewis)
Date: Sat, 20 Jan 2007 09:55:36 -0800
Subject: [Masterview-devel] Masterview experiment: packaging directives with
	a plugin
Message-ID: <20070120175535.JKUX15640.fed1rmmtao05.cox.net@fed1rmimpo01.cox.net>

fyi: I've been dabbling with a config service to make it simple to deliver a
directives dir as part of a plugin so that you can specify in your
masterview config "add all directives directories located in plugins I'm
loading in this app to the load path".  

I've been building several little plugins where I want to support directive
markup associated with the plugin facilities, and believe this is a nice way
to package and install/distribute the feature. For various reasons some of
the plugins I use in my app aren't installed in the standard rails
vendor/plugins dir in the app and the loc is diff in my dev setup than in
the deployed version of the site, so configuring my masterview directives
load path is kind of messy if I have to bolt down dir refs; thus the desire
for a config option asking to automatically add plugin directive dirs from
however the rails load path is set up for the current environment.

But I'm not sure I like the implementation yet of how we get hold of the
rails plugin load path, I kind of extracted and hacked from things done down
in the rails init code, so for the moment I'm patching it in on the side
from my app init.  Believe I should check out these hooks against rails 1.2
before committing.

Also haven't convinced myself I understand all the possible ramifications of
load time dependencies and the timing of when mv directive loading and
startup template processing occurs relative to rails framework, plugin, and
app loading.  Not sure we have quite the right set of hook points in either
masterview or rails itself to completely control some of the timing of
things that you might want.

~ Deb



From djlewis at acm.org  Sat Jan 20 12:44:23 2007
From: djlewis at acm.org (Deb Lewis)
Date: Sat, 20 Jan 2007 09:44:23 -0800
Subject: [Masterview-devel] We should get rid of unused top-level directives
	dir
Message-ID: <20070120174436.YYEU2628.fed1rmmtao06.cox.net@fed1rmimpo01.cox.net>

yes?  that was originally intended for stashing user's addon directives, but
we've now provided convention for std loc w/in app dir where users can
install additional directives; mv plugin dir itself is probably the wrong
place for this so we should drop if we don't have a purpose for it.

~ Deb



From jeff.barczewski at gmail.com  Sat Jan 20 14:19:15 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Sat, 20 Jan 2007 13:19:15 -0600
Subject: [Masterview-devel] We should get rid of unused top-level
	directives dir
In-Reply-To: <20070120174436.YYEU2628.fed1rmmtao06.cox.net@fed1rmimpo01.cox.net>
References: <20070120174436.YYEU2628.fed1rmmtao06.cox.net@fed1rmimpo01.cox.net>
Message-ID: <19cda190701201119p29e451fbv3d5ede45e16433cf@mail.gmail.com>

On 1/20/07, Deb Lewis <djlewis at acm.org> wrote:
> yes?  that was originally intended for stashing user's addon directives, but
> we've now provided convention for std loc w/in app dir where users can
> install additional directives; mv plugin dir itself is probably the wrong
> place for this so we should drop if we don't have a purpose for it.
>

Right, I think that would be less confusing. I am ok with dropping that.

From jeff.barczewski at gmail.com  Mon Jan 22 00:02:47 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Sun, 21 Jan 2007 23:02:47 -0600
Subject: [Masterview-devel] I added config.admin_check_auth_proc to allow
	configurable authorization for MasterView admin pages
Message-ID: <19cda190701212102t57c8472amc2808a5332aa4602@mail.gmail.com>

I added a configuration option to allow changing the proc used for
checking authorization for MasterView admin controller pages.

config.admin_check_auth_proc defaults to

lambda { |controller_instance| controller_instance.local_request? }

which restricts to local requests.

This can be overriden to a different block to check user permissions
or other things.

This is currently checked into the trunk.


-- 
Jeff Barczewski, MasterView project founder
Inspired Horizons Ruby on Rails Training and Consultancy
Next Ruby on Rails plus JRuby workshop Feb 22-24 St. Louis, MO
http://inspiredhorizons.com/training/rails
Limited seating, register now!

From jeff.barczewski at gmail.com  Mon Jan 22 10:31:08 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Mon, 22 Jan 2007 09:31:08 -0600
Subject: [Masterview-devel] From Rails list - Fwd: [Rails] "Safe" template
	engine with custom tags?
Message-ID: <19cda190701220731w273e507buc351348e3eeddacc@mail.gmail.com>

Here is a request that came on the Rails list along with my response.

I think eventually I'd like to take a closer look at doing non-evaling
or sandboxed directives to make this type of template editing safe for
untrusted users.

Jeff


Forwarded Conversation
Subject: [Rails] "Safe" template engine with custom tags?
------------------------

 From: goodieboy <goodieBoy at gmail.com>
Reply-To: rubyonrails-talk at googlegroups.com
To: "Ruby on Rails: Talk" <rubyonrails-talk at googlegroups.com>
Date: Fri, Jan 19, 2007 at 4:52 PM


I'm thinking about creating a CMS which stores templates, layouts and
page content in a database. This would allow me and the client to
update content from a browser. Not sure about the safety issues with
this though? Is it a bad idea to allow the rails template engine to be
manipulated from a browser? It'll all be password protected of course.
It would give me a ton of flecibility... but something smells weird...
If it's a *REALLY* bad idea then...

Does anyone know of a template engine that will that will:

1. integrate seamlessly
2. provide an easy syntax
3. give access to helpers just like the Rails template engine
4. provide ability to create custom tags

Anyone? Something like the Radius template engine with built in Rails
support would be fantastic I think.

- matt


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk at googlegroups.com
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe at googlegroups.com
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---


--------
 From: Russell Norris <sconds at gmail.com>
Reply-To: rubyonrails-talk at googlegroups.com
To: rubyonrails-talk at googlegroups.com
Date: Mon, Jan 22, 2007 at 7:42 AM

I sure hope it's safe 'cause I'm about to move one of my apps to the
same kind of thing. You might be interested in the theme_support
plugin, the liquid templating system, and looking over Mephisto's
source code. I think you'll find a lot of useful ideas there. I know I
have.

RSL
[Quoted text hidden]
--------
 From: Jeff Barczewski <jeff.barczewski at gmail.com>
To: rubyonrails-talk at googlegroups.com
Date: Mon, Jan 22, 2007 at 9:27 AM

On 1/19/07, goodieboy <goodieBoy at gmail.com> wrote:
>
> I'm thinking about creating a CMS which stores templates, layouts and
> page content in a database. This would allow me and the client to
> update content from a browser. Not sure about the safety issues with
> this though? Is it a bad idea to allow the rails template engine to be
> manipulated from a browser? It'll all be password protected of course.
> It would give me a ton of flecibility... but something smells weird...
> If it's a *REALLY* bad idea then...
>
> Does anyone know of a template engine that will that will:
>
> 1. integrate seamlessly
> 2. provide an easy syntax
> 3. give access to helpers just like the Rails template engine
> 4. provide ability to create custom tags
>

The MasterView template engine currently meets some of your goals.
http://masterview.org/

It will integrate seamlessly with Rails.

It provides an easy syntax (attribute based but very similar to the
native syntax for Rails helpers).

It provides full access to helpers, partials, layouts just like ERB.
The directives allow the content to inherit their style from the html
so that you can design with WYSIWYG editor.

It was designed from the ground up to be customizable and extensible
with custom directives (like tags but attribute based). The API was
refactored to use a DSL to simplify directive creation.

MasterView is designed to allow designers to WYSIWYG the templates,
while still allowing full power of ERB (partials, helpers). We are
developing some power attributes that simplify the creation of Ajax'd
tables.

The MasterView system has plugable IO framework allowing the templates
to exist anywhere (file system, DB, memory, etc.) however we have not
implemented the DB version yet. The hooks are there but just haven't
gotten to it yet.

As for the safety of doing things, here is my take:

If you are allowing your trusted developers to make changes to these
templates, then this is not much different than having it on the file
system. Assuming you secure it behind user authentication to access
these files, then it is not much different. Much more convenient than
requiring someone to scp or ftp the files up. However this is ruby
code with the same access as your code on the filesystem, so it should
be given the same respect and code reviews.

However if you are wanting to allow generic users (not just your
developers) to be able to change the templates, then you will want to
either prevent them from using evaling code or to use some sort of
sandboxing. We are planning to add some non-evaling or sandboxed
directives to MasterView but that is still a little ways off. Doing
this today, you might consider using Liquid for that aspect of things
if you need to allow users to edit templates and not simply content.
Liquid can be used in conjunction with MasterView as well. Hendy
Irawan has done this for his site.


If it were me, I would take the approach of trying to limit the end
users from being able to directly change templates. Provide them a way
to change the content all they want. Give them a way to change the
CSS. If you have the right hooks into the content for CSS you would be
suprised about the layouts you can get just be changing this. Check
out http://www.csszengarden.com/ to see how drastically sites can be
changed with CSS alone. This should get you most of the way there and
it can be made be totally safe. Then if this doesn't meet all your
needs, you might provide several canned template layouts that you
created and they can choose one of them. Beyond that check out using
Liquid possibly with MasterView depending on your needs.

If you have any questions about this, I will do my best to help. If
you would like to know more how MasterView works we have some
illustrations and screencasts on the site. http://masterview.org/ as
well as mailing lists, etc. (We are preparing a new release that fixes
some smaller issues with Rails 1.2, should be out in the next few
days, trunk already has fixes).

Blessings,

--
Jeff Barczewski, MasterView project founder
Inspired Horizons Ruby on Rails Training and Consultancy
Next Ruby on Rails plus JRuby workshop Feb 22-24 St. Louis, MO
http://inspiredhorizons.com/training/rails
Limited seating, register now!

--------

From jeff.barczewski at gmail.com  Sat Jan 27 13:39:13 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Sat, 27 Jan 2007 12:39:13 -0600
Subject: [Masterview-devel] I will be speaking about MasterView at the
	MountainWest Ruby conference March 16th in Salt Lake City UT
Message-ID: <19cda190701271039i1021949ej66f06d59a3fcc884@mail.gmail.com>

FYI. I will be speaking about MasterView at the MountainWest Ruby conference
March 16th in Salt Lake City UT
http://mtnwestruby.org/speakers/

I believe I am scheduled to talk at 2pm on Friday Mar 16.

If any of you will be there, I would love to meet you in person and discuss
how you have been using MasterView, and ideas you might have for the
project.

Blessings,

-- 
Jeff Barczewski, MasterView core team
Inspired Horizons Ruby on Rails Training and Consultancy
Next Ruby on Rails plus JRuby workshop Feb 22-24 St. Louis, MO
http://inspiredhorizons.com/training/rails/index.html
Limited seating, register now!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070127/9b7768bd/attachment.html 

From djlewis at acm.org  Mon Jan 29 00:53:50 2007
From: djlewis at acm.org (Deb Lewis)
Date: Sun, 28 Jan 2007 21:53:50 -0800
Subject: [Masterview-devel] White space blues
Message-ID: <200701290553.l0T5rlV7002571@mail.authsmtp.com>

ok, tired of getting tripped by this...

The editors I use aren't fussy about trailing white space on lines - esp. in
comments, there are often 1 or 2 trailing blanks on lines in files I've
worked on.  Conversely whatever you're using aggressively strips line-ending
white space on any file you touch.

This totally destroys ability to do reasonable change compares between
versions, which I rely on utterly.  I can't identify relevant changes when
90% of the compare delta is blank-stripping.  This is bad.

We need some approach so we both commit with consistent formatting.  Some
combo of text editor settings or a formatter we both like, dunno what's
going to be best, but let's see if we can find solution.  thx

~ Deb


From djlewis at acm.org  Mon Jan 29 00:47:17 2007
From: djlewis at acm.org (Deb Lewis)
Date: Sun, 28 Jan 2007 21:47:17 -0800
Subject: [Masterview-devel] I added config.admin_check_auth_proc to
	allowconfigurable authorization for MasterView admin pages
In-Reply-To: <19cda190701212102t57c8472amc2808a5332aa4602@mail.gmail.com>
Message-ID: <200701290547.l0T5lE6F000290@mail.authsmtp.com>

weeeeelllll.... I don't like it.

The awkwardness you ran into even with the simple local_request? predicate
may well recur on user-supplied impl's as well; having to write
"controller.send :foo" is just unnatural.

I expect to hook up authentication and authorization mechanisms in my sites
very soon which have a user model, where logged in user is marked in
session, and a roles/permissions mechanism for expressing the rights granted
to a user.  So the check I'm going to want to write is essentially the
predicate "is there a logged-in user and do their perms include admin
rights?"

And I don't know whether I'd necessarily declare those as public methods
(have to think about that, anyway, but don't know that it's a good
assumption that people necessarily would)

Don't want to have to write tricky/slimy block code which has to poke at its
controller arg using send to get around protected access.  (and you flat
can't get at private, I think - tho I avoid those)

Allowing developer to plug in this access check functionality as a mixin
might be a better approach.  Allows you to write the code in a fairly
natural style.  Then we break our default impl out into the default mixin
impl; ref to that class is the default value of the admin_check_auth config
setting (name appropriately...).  App developer can set the config option
with the name of their version of the auth check mixin class.  Initializer
is responsible for installing when activating the admin controller feature.

Something like that, anyway, perhaps some mildly tricky details to work out
to get this running.  But something like this might be better than using a
block if access control is going to get in the way.

~ Deb 

  # Default implementation of authorization check
  # to restrict access to administrative services
  def allow_access?
    # backstop: only allow for developer testing on local machine
    local_request?
  end

  # authorization check to restrict access to administrative services
  # (app-specific implementation)
  def allow_access?
    current_user && user_has_perm?(:admin)
  end

-----Original Message-----
From: masterview-devel-bounces at rubyforge.org
[mailto:masterview-devel-bounces at rubyforge.org] On Behalf Of Jeff Barczewski
Sent: Sunday, January 21, 2007 9:03 PM
To: masterview-devel at rubyforge.org
Subject: [Masterview-devel] I added config.admin_check_auth_proc to
allowconfigurable authorization for MasterView admin pages

I added a configuration option to allow changing the proc used for checking
authorization for MasterView admin controller pages.

config.admin_check_auth_proc defaults to

lambda { |controller_instance| controller_instance.local_request? }

which restricts to local requests.

This can be overriden to a different block to check user permissions or
other things.

This is currently checked into the trunk.


--
Jeff Barczewski, MasterView project founder Inspired Horizons Ruby on Rails
Training and Consultancy Next Ruby on Rails plus JRuby workshop Feb 22-24
St. Louis, MO http://inspiredhorizons.com/training/rails
Limited seating, register now!
_______________________________________________
Masterview-devel mailing list
Masterview-devel at rubyforge.org
http://rubyforge.org/mailman/listinfo/masterview-devel


From jeff.barczewski at gmail.com  Mon Jan 29 08:13:56 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Mon, 29 Jan 2007 07:13:56 -0600
Subject: [Masterview-devel] White space blues
In-Reply-To: <200701290553.l0T5rlV7002571@mail.authsmtp.com>
References: <200701290553.l0T5rlV7002571@mail.authsmtp.com>
Message-ID: <19cda190701290513l758b2439w3ee4b476cea1abc3@mail.gmail.com>

I was wondering what was going on here.

I had to remove some white space in the one test file so that it matched.

Have you ever used "beyond compare"? We use it on windows and it does a
fabulous job. It shows you side by side the changes and color codes the
chars in a line that changed. You can have it ignore whitespace etc. It will
do files, and directories of files.

It is just a wonderful comparison and merge tool.

Not that this is what we need to do here, just mentioning it to you since it
saves me tons of time diffing and merging in my java projects for work.

So on every file I touch, you are seeing white space changes on the whole
file? I'm sure I can turn this off in emacs now that I know it is happening.
Let me check into it.

Jeff



On 1/28/07, Deb Lewis <djlewis at acm.org> wrote:
>
> ok, tired of getting tripped by this...
>
> The editors I use aren't fussy about trailing white space on lines - esp.
> in
> comments, there are often 1 or 2 trailing blanks on lines in files I've
> worked on.  Conversely whatever you're using aggressively strips
> line-ending
> white space on any file you touch.
>
> This totally destroys ability to do reasonable change compares between
> versions, which I rely on utterly.  I can't identify relevant changes when
> 90% of the compare delta is blank-stripping.  This is bad.
>
> We need some approach so we both commit with consistent formatting.  Some
> combo of text editor settings or a formatter we both like, dunno what's
> going to be best, but let's see if we can find solution.  thx
>
> ~ Deb
>
> _______________________________________________
> Masterview-devel mailing list
> Masterview-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-devel
>



-- 
Jeff Barczewski, MasterView core team
Inspired Horizons Ruby on Rails Training and Consultancy
Next Ruby on Rails plus JRuby workshop Feb 22-24 St. Louis, MO
http://inspiredhorizons.com/training/rails/index.html
Limited seating, register now!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070129/ef14dd58/attachment.html 

From jeff.barczewski at gmail.com  Mon Jan 29 08:19:21 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Mon, 29 Jan 2007 07:19:21 -0600
Subject: [Masterview-devel] White space blues
In-Reply-To: <19cda190701290513l758b2439w3ee4b476cea1abc3@mail.gmail.com>
References: <200701290553.l0T5rlV7002571@mail.authsmtp.com>
	<19cda190701290513l758b2439w3ee4b476cea1abc3@mail.gmail.com>
Message-ID: <19cda190701290519j79cff90fl52eb6b224c30b69b@mail.gmail.com>

Are we sure it is actually stripping white space or possibly changing new
line chars? Like instead of \r\n it is saving just \n? This might also show
up as all lines changed.

On 1/29/07, Jeff Barczewski <jeff.barczewski at gmail.com> wrote:
>
> I was wondering what was going on here.
>
> I had to remove some white space in the one test file so that it matched.
>
> Have you ever used "beyond compare"? We use it on windows and it does a
> fabulous job. It shows you side by side the changes and color codes the
> chars in a line that changed. You can have it ignore whitespace etc. It will
> do files, and directories of files.
>
> It is just a wonderful comparison and merge tool.
>
> Not that this is what we need to do here, just mentioning it to you since
> it saves me tons of time diffing and merging in my java projects for work.
>
> So on every file I touch, you are seeing white space changes on the whole
> file? I'm sure I can turn this off in emacs now that I know it is happening.
> Let me check into it.
>
> Jeff
>
>
>
> On 1/28/07, Deb Lewis <djlewis at acm.org> wrote:
> >
> > ok, tired of getting tripped by this...
> >
> > The editors I use aren't fussy about trailing white space on lines -
> > esp. in
> > comments, there are often 1 or 2 trailing blanks on lines in files I've
> > worked on.  Conversely whatever you're using aggressively strips
> > line-ending
> > white space on any file you touch.
> >
> > This totally destroys ability to do reasonable change compares between
> > versions, which I rely on utterly.  I can't identify relevant changes
> > when
> > 90% of the compare delta is blank-stripping.  This is bad.
> >
> > We need some approach so we both commit with consistent
> > formatting.  Some
> > combo of text editor settings or a formatter we both like, dunno what's
> > going to be best, but let's see if we can find solution.  thx
> >
> > ~ Deb
> >
> > _______________________________________________
> > Masterview-devel mailing list
> > Masterview-devel at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/masterview-devel
> >
>
>
>
> --
> Jeff Barczewski, MasterView core team
> Inspired Horizons Ruby on Rails Training and Consultancy
> Next Ruby on Rails plus JRuby workshop Feb 22-24 St. Louis, MO
> http://inspiredhorizons.com/training/rails/index.html
> Limited seating, register now!




-- 
Jeff Barczewski, MasterView core team
Inspired Horizons Ruby on Rails Training and Consultancy
Next Ruby on Rails plus JRuby workshop Feb 22-24 St. Louis, MO
http://inspiredhorizons.com/training/rails/index.html
Limited seating, register now!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070129/6c4253cb/attachment.html 

From jeff.barczewski at gmail.com  Mon Jan 29 08:44:25 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Mon, 29 Jan 2007 07:44:25 -0600
Subject: [Masterview-devel] I added config.admin_check_auth_proc to
	allowconfigurable authorization for MasterView admin pages
In-Reply-To: <200701290547.l0T5lE6F000290@mail.authsmtp.com>
References: <19cda190701212102t57c8472amc2808a5332aa4602@mail.gmail.com>
	<200701290547.l0T5lE6F000290@mail.authsmtp.com>
Message-ID: <19cda190701290544s2d2fc6bdj445f3d4482306d5@mail.gmail.com>

I'm thinking possibly we could just substitute the code in for the
local_request anyway into our default check. Then we wouldn't have to call
any private methods and in case they change things we won't break since they
can change private methods at any time. We can just put that line of code in
our default check.

However it is always safer to not make controller methods public unless you
want Rails to expose them, because people can type in the appropriate url
and usually invoke them directly. So everything that is not supposed to be
exposed needs to be protected or private. (Actually I think current version
of send can get at any method, though they are changing this in Ruby 2 and
you have to use some other method)

All that being said, I am fine with doing something else like a mixin
assuming it won't have issues where it can be called from Rails. There might
be an additional way to protect what methods rails exposes.

Do you think we should try to get a release up that fixes the issues with
Rails 1.2 quickly (maybe even backing out this auth change) and then follow
up with these other changes?

The not being able to debug compile errors is one thing I want to get out to
users as soon as possible so that any new users who download the gem and try
it with Rails 1.2 don't have a blank screen when they hit a compile error
(misspelling something). It is fixed in trunk.

So let me know what you think regarding what we have on the table. I haven't
yet made the changes to link_to either.

Jeff

On 1/28/07, Deb Lewis <djlewis at acm.org> wrote:
>
> weeeeelllll.... I don't like it.
>
> The awkwardness you ran into even with the simple local_request? predicate
> may well recur on user-supplied impl's as well; having to write
> "controller.send :foo" is just unnatural.
>
> I expect to hook up authentication and authorization mechanisms in my
> sites
> very soon which have a user model, where logged in user is marked in
> session, and a roles/permissions mechanism for expressing the rights
> granted
> to a user.  So the check I'm going to want to write is essentially the
> predicate "is there a logged-in user and do their perms include admin
> rights?"
>
> And I don't know whether I'd necessarily declare those as public methods
> (have to think about that, anyway, but don't know that it's a good
> assumption that people necessarily would)
>
> Don't want to have to write tricky/slimy block code which has to poke at
> its
> controller arg using send to get around protected access.  (and you flat
> can't get at private, I think - tho I avoid those)
>
> Allowing developer to plug in this access check functionality as a mixin
> might be a better approach.  Allows you to write the code in a fairly
> natural style.  Then we break our default impl out into the default mixin
> impl; ref to that class is the default value of the admin_check_auth
> config
> setting (name appropriately...).  App developer can set the config option
> with the name of their version of the auth check mixin class.  Initializer
> is responsible for installing when activating the admin controller
> feature.
>
> Something like that, anyway, perhaps some mildly tricky details to work
> out
> to get this running.  But something like this might be better than using a
> block if access control is going to get in the way.
>
> ~ Deb
>
>   # Default implementation of authorization check
>   # to restrict access to administrative services
>   def allow_access?
>     # backstop: only allow for developer testing on local machine
>     local_request?
>   end
>
>   # authorization check to restrict access to administrative services
>   # (app-specific implementation)
>   def allow_access?
>     current_user && user_has_perm?(:admin)
>   end
>
> -----Original Message-----
> From: masterview-devel-bounces at rubyforge.org
> [mailto:masterview-devel-bounces at rubyforge.org] On Behalf Of Jeff
> Barczewski
> Sent: Sunday, January 21, 2007 9:03 PM
> To: masterview-devel at rubyforge.org
> Subject: [Masterview-devel] I added config.admin_check_auth_proc to
> allowconfigurable authorization for MasterView admin pages
>
> I added a configuration option to allow changing the proc used for
> checking
> authorization for MasterView admin controller pages.
>
> config.admin_check_auth_proc defaults to
>
> lambda { |controller_instance| controller_instance.local_request? }
>
> which restricts to local requests.
>
> This can be overriden to a different block to check user permissions or
> other things.
>
> This is currently checked into the trunk.
>
>
> --
> Jeff Barczewski, MasterView project founder Inspired Horizons Ruby on
> Rails
> Training and Consultancy Next Ruby on Rails plus JRuby workshop Feb 22-24
> St. Louis, MO http://inspiredhorizons.com/training/rails
> Limited seating, register now!
> _______________________________________________
> Masterview-devel mailing list
> Masterview-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-devel
>
> _______________________________________________
> Masterview-devel mailing list
> Masterview-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-devel
>



-- 
Jeff Barczewski, MasterView core team
Inspired Horizons Ruby on Rails Training and Consultancy
Next Ruby on Rails plus JRuby workshop Feb 22-24 St. Louis, MO
http://inspiredhorizons.com/training/rails/index.html
Limited seating, register now!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070129/f6878ad9/attachment-0001.html 

From djlewis at acm.org  Mon Jan 29 23:16:36 2007
From: djlewis at acm.org (Deb Lewis)
Date: Mon, 29 Jan 2007 20:16:36 -0800
Subject: [Masterview-devel] I added config.admin_check_auth_proc to
	allowconfigurable authorization for MasterView admin pages
In-Reply-To: <19cda190701290544s2d2fc6bdj445f3d4482306d5@mail.gmail.com>
Message-ID: <200701300416.l0U4GX9f084422@mail.authsmtp.com>

not sure how fast people are switching to 1.2, but certainly blank screen on
compile error would be good to fix!
 
I think we should back out the access check change if we want to get a
release out for other reasons; I think we shouldn't change that until we
think we've got the right solution.  Would rather document workaround in the
meantime if necessary.
 
~ Deb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070129/ef9a8205/attachment.html 

From djlewis at acm.org  Mon Jan 29 23:16:36 2007
From: djlewis at acm.org (Deb Lewis)
Date: Mon, 29 Jan 2007 20:16:36 -0800
Subject: [Masterview-devel] White space blues
In-Reply-To: <19cda190701290513l758b2439w3ee4b476cea1abc3@mail.gmail.com>
Message-ID: <200701300416.l0U4GX9g084422@mail.authsmtp.com>

For general use, I use a compare tool called UltraCompare, which is pretty
good; I gave it try because I settled on UltraEdit for my Windows text
editor (when not in eclipse, that is) after hunting around and trying
several.  It's a really programmer editor, you can plug in syntax hightlight
definitions so I've added ruby, python, etc to the stock set of basic rules
it ships with.
 
Believe UltraCompare has options for ignoring white space.  But.. trouble is
I'm running into this running sync tools for subclipse in Eclipse, and I
dont' think that's very configurable.  (I'll re-check, though)
 
I'll check out your "beyond compare", always useful to know about good
tools.
 
>> you are seeing white space changes on the whole file
 
believe so, at any rate I periodically get something with a ton of changes
reported which are just a bunch of trailing-black strippers.
 
>> maybe its newlines
 
I don't think so, because even when I got a lot of hits it does seem to be
selective, not *every* line in the file.
 
But checking a couple random files we do seem to be inconsistent about
svn:eol-style props - i find native, LF, and not set.  Seems like that
should be set to native on .rb files (and probably .html as well), then
subversion generally just does the right thing at checkout time.
 
~ Deb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070129/daf4c663/attachment.html 

From jeff.barczewski at gmail.com  Tue Jan 30 11:22:25 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Tue, 30 Jan 2007 10:22:25 -0600
Subject: [Masterview-devel] White space blues
In-Reply-To: <200701300416.l0U4GX9g084422@mail.authsmtp.com>
References: <19cda190701290513l758b2439w3ee4b476cea1abc3@mail.gmail.com>
	<200701300416.l0U4GX9g084422@mail.authsmtp.com>
Message-ID: <19cda190701300822s4d1b9384h1b27240b654a6b0a@mail.gmail.com>

On 1/29/07, Deb Lewis <djlewis at acm.org> wrote:
>
>
> But checking a couple random files we do seem to be inconsistent about
> svn:eol-style props - i find native, LF, and not set.  Seems like that
> should be set to native on .rb files (and probably .html as well), then
> subversion generally just does the right thing at checkout time.
>


So maybe if we get this straightened out, then that may fix our issues? I
guess we can try to get that resolved how it needs to be and then see if it
still occurs.

Hard for me to get my head around this stuff, since I haven't had to deal
with it before and have pretty much only needed to know the basics to get by
in svn so far. I'll read up on the setting the props properly.

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070130/7f1f154b/attachment.html