[Framework-Team] Re: The big 3.0 ;)
Martin Aspeli wrote: - Search: "only in this section" checkbox Needs to happen soon or becomes 3.5 material. Trivial, though, if someone has cycles. I was looking at this template anyway, so I've done it. Florian has promised to hook it into livesearch. Martin ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: The big 3.0 ;)
Alec Mitchell wrote: On 4/3/07, Martin Aspeli <[EMAIL PROTECTED]> wrote: Wichert Akkerman wrote: >> - Wicked >> - Needs to use createObject?type_name=Document — the way it is >> set up now, anything spidering the site with credentials will >> create objects, and any object clicked will create objects >> (this change will make it invoke portal_factory) > > Hasn't happened. Am I right in thinking this should be considered a seriousish bug? I don't see why this should be considered any better/worse than the content add menu which uses the exact same links and will be shown on all such pages as well. From a spiders point of view, it's not different, AFAIK. Not that this isn't an important issue, but we've lived with it for a long time. who spiders with credentials? The real issue is clicky users creating content they don't actually edit. This is more of an annoyance than a barn-burner considering it's a wiki convention that most of the time people use the syntax so they can rapidly create and populate a link. this is like 3-4 line fix unless you wanted to create a proper add view (ie less effort than has been expended in writing emails about it). might have time this weekend to do it. an kss inline of the add item page would be by far the best solution overall(still need above as a fallback). -w -- -- d. whit morriss -- - senior engineer, opencore - - http://www.openplans.org - - m: 415-710-8975 - "If you don't know where you are, you don't know anything at all" Dr. Edgar Spencer, Ph.D., 1995 begin:vcard fn:D. Whitfield Morriss n:Morriss;D. Whitfield org:The Open Planning Project;OpenPlans adr:;;1309 Ashwood Ave;Nashville;TN;37212;USA email;internet:[EMAIL PROTECTED] title:Lead Developer tel;home:615 292-9142 tel;cell:415 710-8975 x-mozilla-html:FALSE version:2.1 end:vcard ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: The big 3.0 ;)
Alec Mitchell wrote: On 4/3/07, Martin Aspeli <[EMAIL PROTECTED]> wrote: Wichert Akkerman wrote: - Wicked - Needs to use createObject?type_name=Document — the way it is set up now, anything spidering the site with credentials will create objects, and any object clicked will create objects (this change will make it invoke portal_factory) Hasn't happened. Am I right in thinking this should be considered a seriousish bug? I don't see why this should be considered any better/worse than the content add menu which uses the exact same links and will be shown on all such pages as well. From a spiders point of view, it's not different, AFAIK. Not that this isn't an important issue, but we've lived with it for a long time. True. So what's it using now? In any case, if it's not using createObject it probably should (if feasible) just to standardise on that API. Note that the add menu can make use of z3 add views now. I don't think there's an immediate need for wicked to do the same, but if it uses createObject, then we could make createObject support addviews as well in the future, again through a common interface. Martin ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: The big 3.0 ;)
On Tue, 03 Apr 2007 20:21:06 +0200, Martin Aspeli <[EMAIL PROTECTED]> wrote: Wichert Akkerman wrote: - Move sendto/print/whatever to bottom of page, use text representation Needs to happen soon or becomes 3.5 material. Bear in mind this probably has an impact on third party products' view templates if they need to change to be consistent with the "new" standard. That's why we switched to viewlets. 3rd party products need to adapt anyway now. The change itself is then transparetn to 3rd party products. Regards, Florian Schulze ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] Re: The big 3.0 ;)
On 4/3/07, Martin Aspeli <[EMAIL PROTECTED]> wrote: Wichert Akkerman wrote: >> - Wicked >> - Needs to use createObject?type_name=Document — the way it is >> set up now, anything spidering the site with credentials will >> create objects, and any object clicked will create objects >> (this change will make it invoke portal_factory) > > Hasn't happened. Am I right in thinking this should be considered a seriousish bug? I don't see why this should be considered any better/worse than the content add menu which uses the exact same links and will be shown on all such pages as well. From a spiders point of view, it's not different, AFAIK. Not that this isn't an important issue, but we've lived with it for a long time. Alec ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] Re: The big 3.0 ;)
Wichert Akkerman wrote: some comments on this list, based on current status. Previously Alexander Limi wrote: Fix before RCs: - KSS: - Reduce file size, it's currently way too heavy I'll make a seperate post on that. - Get a basic UI on ÜberSelectionWidget It has a basic UI, just no ajax interface. Nobody appears to be doing that either, so we're going to have to postpone that until 3.5. It really needs to be made to look a bit less amateurish (no offense!) though, even if it's just HTML. :) - Wicked - Needs to use createObject?type_name=Document — the way it is set up now, anything spidering the site with credentials will create objects, and any object clicked will create objects (this change will make it invoke portal_factory) Hasn't happened. Am I right in thinking this should be considered a seriousish bug? - Don't install the following by default: - Content Rules Needs a toggle somewhere. Consider this issue resolved. There is a switch. Content rules is not really "installable" as such. - Move sendto/print/whatever to bottom of page, use text representation Needs to happen soon or becomes 3.5 material. Bear in mind this probably has an impact on third party products' view templates if they need to change to be consistent with the "new" standard. - Combine delete confirmation page with integrity checking (having to say yes/no on two separate pages sucks :) Needs to happen soon or becomes 3.5 material. I'd say this is a usability bug that could be 3.0 or 3.0.x even, if someone can fix it. - Only show the Display/Add/WF pulldowns on the View screen - Possibly remove the border on initial creation forms (ie. keep the actual green border, but remove everything clickable on it, since it causes errors) Done at the sprint. Actually before the sprint. :) - Other - Users seem to be listed twice in the control panel Fixed at the sprint, not merged yet. - "You are adjusting the sharing privileges for a default view, to adjust them for the entire container, go here." Fixed at the sprint I think, may not be merged yet. - WF history and versioning history should be shown in the same table Probably too late for 3.0. - We need a way to ping us (image with some info about OS, version etc) when you install Plone — checkbox on install screen Too late for 3.0 And also of debatable merit if you ask me. - Fix up Table-of-Contents styling - Fix up presentation mode styling Needs to happen soon or becomes 3.5 material. These are UI/CSS bugs and should be considered as part of the usual bug fixing process. - Search: "only in this section" checkbox Needs to happen soon or becomes 3.5 material. Trivial, though, if someone has cycles. Martin ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] NuPlone and Plone 3.0
Franco Carinato, and to a lesser extent Rosario Di Somma, looked at it a bit during the sprint. I'm not sure how feasible it would be for them to help get it into a usable state in the near future though. We really missed spliter at the sprint. Alec On 4/3/07, Wichert Akkerman <[EMAIL PROTECTED]> wrote: I'm wearing my release manager hat today and was looking at NuPlone. At the moment there are still a lot things that do not work or look bad in NuPlone (IE support, form styling and control panel styling are easy to find examples). That means that it is currently not in a state where I want it to even ship with Plone 3. So, what can we do about it? From what I gather: - Cornelis does not have the time to work on NuPlone, but does not mind if others work on it. He does want to be consulted for any stylistic changes. - Denis is willing to work on IE support for it - Danny has a made a fair number of improvements on the Informaat NuPlone-based intranet design, which might be mergable into NuPlone directly. But he has no time to work on that. This does not make me very optimistic for NuPlone's chances of staying in. Unless something magic happens quickly I think we need to take it out of the bundle and reconsider it for inclusion in Plone 3.5. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] The big 3.0 ;)
On 4/3/07, Wichert Akkerman <[EMAIL PROTECTED]> wrote: some comments on this list, based on current status. ... > - Combine delete confirmation page with integrity checking > (having to say yes/no on two separate pages sucks :) Needs to happen soon or becomes 3.5 material. I'm pretty sure you can't do this while maintaining post protection for the delete action without adding some tremendous hack to delay the deletion until a second post request, or by making the original delete link a POST form submit. Neither of these is really 3.0 material IMO. Alec ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] The big 3.0 ;)
some comments on this list, based on current status. Previously Alexander Limi wrote: > Fix before RCs: > > - KSS: > - Reduce file size, it's currently way too heavy I'll make a seperate post on that. > - Get a basic UI on ÜberSelectionWidget It has a basic UI, just no ajax interface. Nobody appears to be doing that either, so we're going to have to postpone that until 3.5. > - Archetypes > - After we removed JS from checkboxes, they no longer "stick" > (really!). Might have to put that back, even though it sucks > - There's something strange going on with enabling comments, it > only works on the initial view of the page after saving, > possibly related Fixed. > - NuPlone theme > - Be complete and functional by RCs, tested in IE6 too > - Be the default in RCs if the above is the case ;) See my other post. > - Kupu > - Make sure the control panel removes stuff that is no longer > relevant with the HTML Filtering control panel > - Make sure you can't insert images that are bigger than > Preview size by default > - Include additional default styles (highlight, table > variations) Nobody worked on this to my knowledge. > - Wicked > - Needs to use createObject?type_name=Document — the way it is > set up now, anything spidering the site with credentials will > create objects, and any object clicked will create objects > (this change will make it invoke portal_factory) Hasn't happened. > - Support both (()) and [[]] syntax by default, so we can > remove this preference from the control panel (exclusively > using either is still supported behind the scenes, of course > — just not in the standard control panel) > - Wiki control panel can be removed, only needs wiki syntax > on/off switch in the control panel Hasn't happened and can just as easily be postponed until 3.5, if ever. > - Fieldsets > - Do we still support fieldsets that require something on > fieldset #1 to be filled out before you can access fieldset > #4? > - Next button shows up in the Save/Cancel area when using the > inline fieldsets? > - Fieldset code: if more than N (N=6?) fieldsets, turn into > pulldown These need to be fixed still. > - Sensible defaults: > - Make sure the WFs are sensible and default WF decided All the unittests still require our old default workflow and nobodu has the resources to fix that, so we're going to have to stick with our old default. > - Members folder gets created even though it's turned off? Bug, should be fixed. > - Only HTML available as format by default, everything else > assumes knowledge of markup > - But make sure it supports loading existing documents that > are in other formats already > - Enable wiki support by default on most types? it's unlikely > to trigger accidentally anyway All behavioural changes very late in the release process, probably 3.5 stuff now. > - Both the Navigation and Search control panel does not show > the "Friendly types" list, but uses the full list instead, > should be fixed (user does not know what a ChangeSet or > Relative Path Criterion type is ;) Debatable. > - Remove personal prefs from the global prefs section > - Don't install the following by default: > - Content Rules Needs a toggle somewhere. > - Can the old-style Add-on products support TITLE.txt to match > the new style products' ability to have a "friendly name"? Behavioural change this very late in the release process, probably 3.5 stuff now. > - Preferrably move the Collections (Smart Folder) control panel > to a ZMI version, since it is very complex and not something > site admins are likely to need Behavioural change this very late in the release process, probably 3.5 stuff now. > - Put back autofocus behaviour now that we have ondomload (make > sure tabindex is correct) Already done I think > - Move sendto/print/whatever to bottom of page, use text > representation Needs to happen soon or becomes 3.5 material. > - Combine delete confirmation page with integrity checking > (having to say yes/no on two separate pages sucks :) Needs to happen soon or becomes 3.5 material. > - Only show the Display/Add/WF pulldowns on the View screen > - Possibly remove the border on initial creation forms (ie. > keep the actual green border, but remove everything > clickable on it, since it causes errors) Done at the sprint. > - Other > - Users seem to be listed twice in the control
Re: [Framework-Team] PloneErrorReporting
Previously Alexander Limi wrote: > Hi, > > Could we please remove PloneErrorReporting from Plone 3.0? It's gone now. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] NuPlone and Plone 3.0
I'm wearing my release manager hat today and was looking at NuPlone. At the moment there are still a lot things that do not work or look bad in NuPlone (IE support, form styling and control panel styling are easy to find examples). That means that it is currently not in a state where I want it to even ship with Plone 3. So, what can we do about it? From what I gather: - Cornelis does not have the time to work on NuPlone, but does not mind if others work on it. He does want to be consulted for any stylistic changes. - Denis is willing to work on IE support for it - Danny has a made a fair number of improvements on the Informaat NuPlone-based intranet design, which might be mergable into NuPlone directly. But he has no time to work on that. This does not make me very optimistic for NuPlone's chances of staying in. Unless something magic happens quickly I think we need to take it out of the bundle and reconsider it for inclusion in Plone 3.5. Wichert. -- Wichert Akkerman <[EMAIL PROTECTED]>It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
