Re: [Plone-UI] Plone 5 Theme

Quoting Nathan Van Gheem (2013-11-18 16:54:07)
> 
> 
> 
> On Mon, Nov 18, 2013 at 9:44 AM, Timo Stollenwerk <[email protected]> wrote:
> 
>     Am 18.11.2013 16:23, schrieb Ramon Navarro Bosch:
>     > Mainly for two reasons:
>     >
>     > * In most of our use cases the client prefers no modals ( there is a lot
>     > of content edition and they love to see the edit and the view with the
>     > same skin )
> 
>     + 100
> 
> ...
>  
> 
> 
>     Not having a separation between backend and frontend has always been one
>     of the biggest selling points of the Plone UI. As far as I can tell
>     other CMSes are trying to get rid of that separation for a good reason.
> 
> which ones? Others are doing the contextual editing finally but, if they mix
> editing, they'll just end up getting the same theming nightmare we have.
>  
> 
> 
>     We are about to go into the opposite direction "to make theming easier"
>     (which was the original point of p.a.toolbar if I recall correctly).
>     Though, according to Ramon and what I saw so far theming will become
>     more complicated with p.a.toolbar.
> 
> It's not more complicated to theme with plone.app.toolbar. It might be more
> difficult to theme the backend...
> 
> 
> 
>     > * In most of our use cases the client needs specific edit forms (skinned
>     > and layout) so it's common that we need to skin also the backend and the
>     > edit forms layout.
> 
>     Same here. Right now I can't imaging to use p.a.toolbar/modals (again)
>     for my customer projects (for UI as well as technical reasons that I
>     pointed out before) and I would really like to see a Plone 5 where I'm
>     not forced to use overlays.
> 
> Wow, yikes. Are you sure these customers just aren't too used to the old plone
> way of doing things? Have you tested this on new customers?
> 
> So what you're saying is that we should maintain backend css in our themes
> still and then also maintain all the toolbar, modals, etc. Sounds like a really
> bad idea.
>  
> 

just to calm down the discussion a bit.

 - nothing really changed in the plan of having plone.app.toolbar in plone 5.

 - it is possible (it always was) to have same toolbar without modals, but this
   will require a bit of work from developer side to make it happen. and when
   i say little i mean you'll have to provide css/js for your theme compiled
   from mockup.

 - plone will still ship with plone.app.toolbar and it is going to be super
   easy to theme it. plone.app.toolbar release is waiting for
   plone.app.contenttypes to be released then you'll have a chance to try
   latest work being done, should happen in matter of days.

 - plonetheme.barceloneta is also rewrite of clientside javascript with
   patterns from mockup (same javascript that is going to be used in
   plone.app.toolbar) and its a nice middle step before we get
   plone.app.toolbar into coredev.

 - plone.app.widgets/toolbar is coming to coredev piece by piece since its
   quite some change and we surely dont want to break tests. this slow
   integration was holding back development of front end theme,
   plonetheme.baceloneta puts us back into track doing work in paralel.

 - if some ppl are confused, please dont be there is no reason. it was just
   comunicated baddly from our side.



--
Rok Garbas - http://www.garbas.si

------------------------------------------------------------------------------
DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________
Plone-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-developers