[albatross-users] New release?

[Sheila King]

--On Saturday, September 20, 2003 10:57 PM +1000 Dave Cole 
<djc at object-craft.com.au> wrote:

>>>>>> "Matt" == Matt Goodall <matt at pollenation.net> writes:
>
> Matt> Dave, Any chance of a new release soon or at least a snapshot of
> Matt> your source?
>
> Matt> It's getter harder and harder to send patches as my code base
> Matt> gets more and more out of sync with 1.10. I had to manually edit
> Matt> the patch I just sent (produced by Subversion) to remove other
> Matt> changes to these files, app.py in particular.
>
> I have spent most of today getting everything ready for a 1.20pre1
> release.

Sound exciting. And time consuming.

> I want to include your new PageModuleMixin as I think it is the right
> way to go.  It will break some code - probably a good thing though.  I
> want Andrew to have a look at the new code before a final decision is
> made.

Somehow I'm thinking the above remark doesn't apply to Matt's latest 
cookie-path patch? I've been meaning to post that I've been using it and it 
seems to have solved the problems I had been reporting regarding duplicate 
cookies and corrupted sessions that I could not re-establish.

Thanks again, Matt!

> Rather than import the page module you execfile() it.  This means that
> all classes defined in the page module look like they are defined in
> the __builtin__ module.  This causes problems if you ever place
> instances of these classes into the session...

The above is over my head, as I am not that intimate with the Albatross 
source and that level of development is beyond where I am personally 
comfortable. However, for me, the last Albatross upgrade set me back two 
weeks of trying to fix code that "broke" for me and allowed me to make no 
progress in my actual task at hand, just trying to scramble to get my code 
functioning again due to upgrading Albatross.

Certainly gives me pause in considering to upgrade Albatross further if it 
is going to break stuff each time. Especially since for me, I have no way 
to install an upgrade without overwriting my current install. I wish it 
were possible to do an alt-install switch, like one can do with Python, so 
that you can easily have more than one version installed.

> As we are trying to promote the use of an MVC approach, it might be a
> good idea to discourage people from placing more than the most basic
> glue code (no class definitions) in page modules.

I understand the reference to MVC approach, but I'm not sure what exactly 
is meant by trying to "discourage people from placing more than the most 
basic glue code (no class definitions) in page modules."

Are you referring to classes I might write myself? Or page classes? or 
what? How are the suggested changes expected to break code?

> I can think of at least a few programs I have written that this will
> break :-).

:\

-- 
Sheila King
http://www.thinkspot.net/sheila/
http://www.k12groups.org