the new internal pages structure...

[jens]

One of most important requests is the restructuring of the internal pages. Two points:
-The data should not stored into the database.
-The additional Stylesheet/JavaScript content should not included directly into the html page. The Server should handle these files, as normal static file requests (Include with <link href=...> and <script src=...>)

I started implementing this. There is more changes necessary than I thought.

I moved any internal page files into the directory ./media/PyLucid/internal_page/ (In a subdirectory named as the plugin name).
If a user will customize a internal page, he must made a copy of the html,css and js files into ./media/PyLucid/customized_internal_page/ (Also in a subdir)

I need to tidy up some path settings. So this changes are bigger than small updates.

I think i can commit the changes tomorrow...
_________________

http://www.jensdiemer.de | http://www.htfx.de | http://www.python-forum.de

[rantaaho]

Great!

But "customized_internal_page" is a quite horrible name for a directory, could it be that default templates are under ./media/PyLucid/internal_pages and customized under./media/internal_pages?

[jens]

Yes, the name is very long. But i think the customized files should be stored in ./media/PyLucid/ together with the rest of PyLucid related media files. Do you think that is not so important?
_________________

http://www.jensdiemer.de | http://www.htfx.de | http://www.python-forum.de

[rantaaho]

Well my logic was that under ./media/PyLucid/ would be the files which are shipped with PyLucid and any customized files would be "user's own" outside PyLucid-directory.

But maybe it is clearer if all PyLucid related file are under ./media/PyLucid. One solution could be that all customized files are under ./media/PyLucid/local/ or ./media/PyLucid/custom/. It may seems as unnecessary step folder, but IMHO it is clearer that way.

[jens]

First step commited: http://trac.pylucid.net/changeset/1449

More info here: http://trac.pylucid.net/ticket/132#comment:1

I did not test the changes thoroughly. Probably there still exists some bugs.
_________________

http://www.jensdiemer.de | http://www.htfx.de | http://www.python-forum.de

[jens]

btw. Now there is no need to put "meta information" about the internal pages into the plugin manager config anymore.

But if we remove all internal page info from the config files we lost all meta information. But that's not bad, I think.

EDIT: Next step is done: http://trac.pylucid.net/ticket/132#comment:2
Now, all big things about these changes are done. Very nice.
_________________

http://www.jensdiemer.de | http://www.htfx.de | http://www.python-forum.de

[jens]

Ha! I have a great new Idea related to this. I have implement it quick, see: http://trac.pylucid.net/changeset/1452

Why not save the global Stylesheet into the media dir, too? So the webserver can handle this file, too.

There exist a fall back, if PyLucid can't save the file in the filesystem (Run as CGI with user 'nobody'). In this case, everything remains the same: PyLucid handle the fake-file reuqest via _command -> two request for one page...
_________________

http://www.jensdiemer.de | http://www.htfx.de | http://www.python-forum.de

[jens]

I add a unitest for the new global Stylesheet handling: http://trac.pylucid.net/changeset/1456

I would like to test the performance between the old and the new handlings, with my old simple_web_bench.py. I am strained whether the difference is measurable.

EDIT: I added a unitest for the new internal page API: http://trac.pylucid.net/changeset/1460
And i commit some bugfixes...
_________________

http://www.jensdiemer.de | http://www.htfx.de | http://www.python-forum.de

[jens]

I create a docu page, here: http://pylucid.org/_goto/142/internal-pages/
_________________

http://www.jensdiemer.de | http://www.htfx.de | http://www.python-forum.de