Layout: maybe add links to the skins of the default layout of the installation? #138

Open
opened 2015-04-04 16:14:07 +00:00 by GoogleCodeExporter · 5 comments
GoogleCodeExporter commented 2015-04-04 16:14:07 +00:00 (Migrated from github.com)
Without macro documentation or seeing the current skins as reference, users 
have no chance to repair layouts gone dysfunctional any more. 

Well, they could request another blog or export their old layout, reset it to 
get the new skins, export the new skins, re-import the old layout and compare 
the skins of the old layout with their new counterparts. 

Or would it be better to promote AntClick as a sandbox for layout-maintenance? 
I'm not sure. 

cf http://help.antville.org/stories/2041353/

Original issue reported on code.google.com by kinomu.w...@gmail.com on 20 Jan 2011 at 2:54

``` Without macro documentation or seeing the current skins as reference, users have no chance to repair layouts gone dysfunctional any more. Well, they could request another blog or export their old layout, reset it to get the new skins, export the new skins, re-import the old layout and compare the skins of the old layout with their new counterparts. Or would it be better to promote AntClick as a sandbox for layout-maintenance? I'm not sure. cf http://help.antville.org/stories/2041353/ ``` Original issue reported on code.google.com by `kinomu.w...@gmail.com` on 20 Jan 2011 at 2:54
GoogleCodeExporter commented 2015-04-04 16:14:07 +00:00 (Migrated from github.com)
I correct myself: in this case, the "diff" would have shown the needed macro, 
too. But if the old layout had been importet, it wouldn't. 

Original comment by kinomu.w...@gmail.com on 20 Jan 2011 at 4:51

``` I correct myself: in this case, the "diff" would have shown the needed macro, too. But if the old layout had been importet, it wouldn't. ``` Original comment by `kinomu.w...@gmail.com` on 20 Jan 2011 at 4:51
GoogleCodeExporter commented 2015-04-04 16:14:07 +00:00 (Migrated from github.com)

Original comment by interf...@p3k.org on 20 Jan 2011 at 11:17

  • Added labels: Milestone-Release-1.3
Original comment by `interf...@p3k.org` on 20 Jan 2011 at 11:17 - Added labels: **Milestone-Release-1.3**
GoogleCodeExporter commented 2015-04-04 16:14:07 +00:00 (Migrated from github.com)

Original comment by interf...@p3k.org on 29 May 2011 at 9:08

  • Added labels: Milestone-Release-1.4
Original comment by `interf...@p3k.org` on 29 May 2011 at 9:08 - Added labels: **Milestone-Release-1.4**
GoogleCodeExporter commented 2015-04-04 16:14:07 +00:00 (Migrated from github.com)

Original comment by m...@tobischaefer.com on 28 Jul 2013 at 8:50

  • Added labels: Milestone-Release-1.5
  • Removed labels: Milestone-Release-1.4
Original comment by `m...@tobischaefer.com` on 28 Jul 2013 at 8:50 - Added labels: **Milestone-Release-1.5** - Removed labels: **Milestone-Release-1.4**
github-actions[bot] commented 2021-05-17 02:38:25 +00:00 (Migrated from github.com)

Stale issue message

Stale issue message
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: antville/antville#138
No description provided.