On Wed, Mar 24, 2010 at 1:16 PM, Markus Weimar
<[email protected]> wrote:
> Didn't see your reply.
>
> Keeping site.language changes to a minimum is good, but till 4.x we
> should free ourselves and improve as much as we can.

Still, I would prefer to make the transition to 4.x as painless as
possible. A lot of forms are going to have to be redone. I'd like to
keep it to that for the most part...

> 1) The name "backup" let's you expect everything but not what the
> action actually is. I would strongly prefer action.package instead.

Yes and no. It is a backup of files, and it **could** be done for a
whole site, it's just not efficient for that.  So there's nothing
wrong with 'backup'.

And since the command is called backup, and the folder they are stored
in is called backups, I don't want to change the action to "package".
It should all be the same.

I like the semantic feel of 'package', but like 'looks', I wonder if
that semantic advantage outweighs the familiarity of a more common
term like skin/theme, or backup...  Others could chime in on this
point...

The more I think about it, the more I agree. (Still not sure about
'looks' though!) But we need to go the whole way and change everything
to package, if we are going to do that. That means all our online
.backup files need to be renamed, etc. And the time to do that would
be 4.xx not now.

Actually, it might be a nice way to tell whether or not a
backup/package has been upgraded to 4.xx... On the other hand, I would
do a simple search and replace and rename everything on the server
repository...  :)  Kind of thinking out loud...

> 2) I attached the two pages as it was a bad idea to upload them to the
> group. I changed the order and user interaction for action."backup".

Do we need a list of other dir's? The only one things would be loaded
from should be the files folder. I think it would be better to have a
button that you could click to list your files just like the pages.
And then you select any pages and graphics you need. That would be
quite cool...

If a skin were designed using local files, it could be easily
installed as a simple package. I think I'd like to move that direction
even more in 4.xx. Maybe make that the exclusive system for skin
installation.

Cheers,
Dan

-- 
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/boltwire?hl=en.

Reply via email to