[
https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592561#action_12592561
]
David Nuescheler commented on SLING-367:
----------------------------------------
let me try from a slightly different angle:
my point is the following... when you are writing the content in the very first
form
you will have to let sling do a redirect. hence you will have to use the
redirect
instruction... from a users perspective it is simple to understand that "sling"
stuff
is prefixed with sling: have some special meaning in sling.
that's the first simple case... now i would like to make that as simple as
possible.
since i am trying to streamline the simple first steps to lower the entry
barrier
(and i know that i am going to extremes here, but i think i am doing it for the
right
reasons) i think it is of a great importance that we do not have to teach the
user
for the very simple case a lot of the complexities of either jcr or sling. as
much as i
don't want the user to need to understand things like nodetypes or workspaces
to get started with sling i think he should also not need to make the
distinction
between sling "instructions" that are persisted in content and others that
aren't...
> change sling:post: to sling: for "command" prefixes in form names
> -----------------------------------------------------------------
>
> Key: SLING-367
> URL: https://issues.apache.org/jira/browse/SLING-367
> Project: Sling
> Issue Type: Bug
> Components: Post Servlets
> Reporter: David Nuescheler
>
> I think it is fair to also prefix the form elements that express certain
> "commands"
> with "sling:" since they are sling related.
> i see it more as a side effect that the "sling:resourceType" also gets
> persisted.
> generally, i think everything that has something to with "sling" should be
> prefixed
> with "sling".
> I think we need to make sure that we don't complicate the most simple cases
> just
> to a avoid possible collisions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
