Ticket #9313 (closed PLIP: wontfix)

Opened 7 years ago

Last modified 7 years ago

Mobile View with Mobile Image selection options

Reported by: pigeonflight Owned by:
Priority: minor Milestone: 4.0
Component: Unknown Version:
Keywords: Cc: plip-advisories@…

Description

Proposer: David "pigeonflight" Bain
Seconder: None as yet

Motivation

Plone needs a mobile view that provides a sensible default for mobile devices. There are many mobile devices that don't respect standard mobile stylesheets, the best approach is to provide a mobile version of pages.

Assumptions

Key assumptions made. What is being covered by and what is intentionally left out of the scope of the proposal.

Proposal & Implementation

The mobile system should allow a content manager to specify a mobile version of images found in the page. A content manager should be able to select an image and provide the mobile alternative. They should also be able to preview the mobile version.

Deliverables

Required code:

  • a mobile view (@@mobile) which adapts the normal plone view
  • a mobile edit view (@@mobile_edit) which makes it possible to customize the mobile version, including the images.
  • Unit tests
  • Localization
  • Documentation

Risks

I don't know enough to be sure of the risks, hopefully someone else can add notes here.

Participants

?

Progress

I know of the Mobilize Product from Weblion, I'm not sure how similar that is see:  https://weblion.psu.edu/trac/weblion/wiki/MobilizeProduct

Change History

comment:1 Changed 7 years ago by MatthewWilkes

Your participants section is just "?" at the moment, does this mean you're unwilling to be a participant?

comment:2 Changed 7 years ago by erikrose

Clearing Owner field of 4.0 PLIPs so we can use it to mean "implementor". (Many of these owners were automatically assigned from choosing a Component that had a default owner.)

comment:3 Changed 7 years ago by alecm

This PLIP would, IMO, need significantly more detail to be considered for Plone 4.0. Providing a mobile skin out of the box could be very useful, but it doesn't appear that this PLIP provides a realistic outline of that feature. The lack of participants is also not encouraging.

comment:4 Changed 7 years ago by smcmahon

  • Cc plip-advisories@… added

comment:5 Changed 7 years ago by MatthewWilkes

This PLIP is incomplete, and what I can see of the implementation appears to be a Bad Way of doing things, i.e. using named views rather than layers.

FWT Vote: -1

comment:6 Changed 7 years ago by rossp

FWT vote: -1. Incomplete.

comment:7 Changed 7 years ago by davisagli

FWT vote: -1. I am +1 on the general concept of a mobile view, but I think a successful PLIP needs more detail including a consideration of which mobile devices actually should see a special view and how that determination is made during traversal; as well as a consideration of different options for registering mobile views and why a particular one was chosen.

I think an improved version of this PLIP could probably be submitted for a later release in the 4.x series.

comment:8 Changed 7 years ago by raphael

FWT vote: -1

I see this as a feature request more than anything else

comment:9 Changed 7 years ago by calvinhp

FWT Vote: -1 incomplete

comment:10 Changed 7 years ago by esteele

  • Status changed from new to closed
  • Resolution set to wontfix

Rejected for Plone 4.0 by FWT vote.

comment:11 Changed 7 years ago by miohtama

No need to add this to core. This is "fixed" by add on product:  http://pypi.python.org/pypi/gomobile.mobile

Note: See TracTickets for help on using tickets.