Hi Philipp!
Philipp von Weitershausen wrote:
yuppie wrote:
Some details:
- I'd like to keep the changes the extension profile makes as small as
possible. So I don't want to change the visible action targets. All we
need are some Method Aliases that point to the views.
- We need new names
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
Hi Philipp!
Philipp von Weitershausen wrote:
yuppie wrote:
Some details:
- I'd like to keep the changes the extension profile makes as small as
possible. So I don't want to change the visible action targets. All we
need
Hi Jens!
Jens Vagelpohl wrote:
- We need new names for the views. I'd like to use @@view.html,
@@edit.html and @@properties.html for the views that already exist. I
think 'metadata_edit_form' and 'folder_edit_form' are both in fact
properties views and 'folder_contents' is just a special
On 8 Mar 2006, at 16:52, yuppie wrote:
You could access the edit view with 'edit.html' instead of
'@@edit.html', but that has a major drawback: View names are not
protected in any way if used without '@@'. You can easily screw up
your site by adding content with the ID 'edit.html'.
Names
On 8 Mar 2006, at 17:36, yuppie wrote:
Hi Jens!
Jens Vagelpohl wrote:
But changing the visible names is not part of my proposal.
Well, I personally would love to change the visible names. The old
names are worse than the @@-prefixed new names ;)
I agree. But the old names are the status
On Wed, Mar 08, 2006 at 11:14:59PM +0100, yuppie wrote:
Paul Winkler wrote:
On Wed, Mar 08, 2006 at 10:52:09PM +0100, yuppie wrote:
You could access the edit view with 'edit.html' instead of
'@@edit.html', but that has a major drawback: View names are not
protected in any way if used
yuppie wrote:
Based on the discussion on the Five list I propose this solution:
1.) To become independent of the lookup order views are named different
than the corresponding skin methods.
2.) Skins *and* views are always enabled.
3.) A new extension profile hooks up the views instead
