Skip to content. | Skip to navigation

Sections

See also...

Hanno Schlichting: News from Plone trunk - November 2008

By hannosch@gmail.com (Hanno Schlichting) from Planet Plone. Published on Nov 20, 2008.

Some people following the developer mailing lists or blogosphere have noticed that Plone trunk has seen quite some interesting changes as of late.

Since I'm the current intermediate release manager for the upcoming Plone 4.0 release, I thought I might share some of those exciting news with you. The framework team for Plone 4.0 is currently being selected and will suggest a final release manager to the Plone Foundation board. I'm available as a candidate, but the decision is yet to be made.

Over the summer we have seen an amazing effort from some of our Google Summer of Code students and their mentor Sidnei who brought us Python 2.5 and 2.6 support for Zope trunk. This has been followed up by Sidnei and Matthew Wilkes and we can run Plone trunk with all Python versions from 2.4 up to 2.6 now.

In other news, we run Plone trunk based on the eggified Zope2 trunk as of last week. Thanks to David Glick for helping with some tough Acquisition related changes. This means we have moved our entire stack towards eggs. As a side effect of that move the amount of code we need to pull in from Zope2 has gotten a lot less. Instead of 105 zope and zope.app packages we only pull in 65 of them anymore. I'll post some current lines of code graphs soon.

The most amazing news has been unveiled by Malthe yesterday. I have been lucky enough to be in Copenhagen and cheer Malthe while he got Plone trunk running entirely based on Chameleon. While he posted some impressive numbers for the Chameleon versus ZPT comparison for Plone trunk, I thought I put this into perspective and compare it with Plone 3.2.



We have a 50% to more than 100% speed increase. And yes we get 16 requests per second out of a completely uncached front-page.

I included the number for the HTML filter control panel as an example of a somewhat complex formlib-based form. This gives you a hint, at what we can expect from a framework like dexterity when it comes to edit screens.

This is just the beginning of what we can do and I expect more performance improvements to come. We have seen a lot of improvements made to the content creation, catalog and search performance during the last year which still need to make it into Plone trunk.

With the next performance sprint in Bristol coming up in December, the future of Plone looks bright to me. And all of this just happens while we redefine the content editor and administration UI for Plone at the same time.

The future of Plone happens now,
Hanno

WebLion: GloWorm 1.0b1 Now Available

From Planet Plone. Published on Nov 20, 2008.

 I'm pleased to announce that Products.Gloworm is now an actual product and available for download from PyPi.

What's it do?

GloWorm is a theme inspection tool for Plone. Click on a part of the Plone interface to see what it is, where it came from, how it was generated, and what TAL statements are acting upon it. Show, hide, move, and customize viewlets through Plone. Get information about Archetypes widgets. See a tree-structured view of all viewlets and viewlet managers active on the page, including those in the html head.

 

What's new in this release?

  • Resizable panels. The GloWorm panel and navigation tree can now be drag-resized.
  • Better browser support. I've confirmed that it works in Firefox 3.0.3, Safari 3.2, Opera 9.62, and IE 7.0.5730.11. I'd appreciate it if you'd add any other versions, working or non-working, to this ticket. Yay crowdsourcing!
  • Inline display of template errors. No more hidden-in-the-traceback failures of template saves.
  • Display the results of a tal:attributes statement. Now see the variable name, expression, and result of tal:attributes calls.
  • Stability! The flakiness has been removed and I completely trust it on my own sites now.

 

Why the name change?

Er, I made a bad assumption about namespaces when I first started the project. Later, when I realized I what the old name implied, I felt a bit of a jerk and changed it to something more reasonable. Any chance we could get a best-practices doc for package naming?

Where's that move-a-viewlet-to-a-different-manager thingie?

Hidden, for now. I'm not yet convinced of the stability of that feature, so I've disabled it. It'll be back once I feel comfortable with it. (If you really, really want to use it, you can uncomment the button in browser/panel_inspect_viewlet.pt)

Is GloWorm going to have the ability to dump my customizations to a filesystem product?

I think every person I talked to at the conference asked the same thing and I'll give the same answer: Sure, when someone writes a product to do that, GloWorm will happily talk to it.

Is there anyone out there that wants to step up and write such a thing? Several of the in-the-know developers I talked to said that the ability is there, it just needs to be tied together and polished. Great! When can you start?

  Special thanks to Alex, Alan, and many others for encouragement; Joel for evangelism and suggestions; and Mike and Christian for letting me run with this crazy idea.

 

Martin Aspeli: Blog post of the year?

From Planet Plone. Published on Nov 20, 2008.

Or at least the month

David Glick: call for PloneFormGen feature requests

From Planet Plone. Published on Nov 20, 2008.

ONE/Northwest is gearing up for building various “civic engagement features”–things like online fundraising, online advocacy, and event RSVP–on top of Plone and Salesforce.com. (You’ll be hearing more about this.) PloneFormGen will play a significant role in implementing several of these features, so we’ve invited its creator, the illustrious Steve McMahon, to come up to Seattle for a little PloneFormGen mini-sprint at the beginning of December.

As part of planning for this sprint and the future of PloneFormGen development, we’d like to get a sense of which outstanding feature requests are most desired by the community. So if you use PloneFormGen, please take a minute to go to http://ploneformgen.uservoice.com and vote for the improvements that would most ease your life when working with PloneFormGen. (The list is as of this writing heavily influenced by my own sense of what’s important — please feel free to add new items as well.)

Of course, our primary interest during the mini-sprint will be in scratching our own itches, but this may help us choose which of a number of minor itches to scratch if we have time, and I imagine the rating of priorities will come in handy in the future. (This is also a bit of a case study to see how well +/- voting works for prioritizing feature requests, to see if it’s something we should also consider doing for Plone itself.)

Plone.org: Plone Conference 2008 Video Offerings

From Planet Plone. Published on Nov 19, 2008.

Tune in to watch the conference!

Alex Clark: Naked Plone Theme

From Planet Plone. Published on Nov 19, 2008.

An installable theme for Plone 3.0 that does little but override default public stylesheets with empty ones.

Zea Partners: Plone replaces Sharepoint, Red Dot and Vignette

From Planet Plone. Published on Nov 19, 2008.

Open Source Content Management Solutions are generating more confidence as companies begin to realise the full potential of such software.

Mock It!: Speedup

By noreply@blogger.com (malthe) from Planet Plone. Published on Nov 19, 2008.

You can now have your cake and eat it, too.

Plone benchmark comparing Chameleon to ZPT

Disclaimer: Don't try this at home! Or actually, do try it, but only on Plone trunk. Simply pull in the five.pt egg and load its configuration. It's a whole-sale drop-in replacement of Zope Page Templates.

If you're interesting in sponsoring this on-going effort, there's an excellent sponsorship opportunity for the upcoming performance-sprint in Bristol. Please contact me by e-mail at mborch@gmail.com.

Rok Garbas: my plone wish list

By rok.garbas@gmail.com (Rok Garbas) from Planet Plone. Published on Nov 19, 2008.

i just read hannosh's "News from trunk ..." before going to bed and as a result of this i woke up in the middle of the night (its 2:30am here) to write this blog post. i will just write things that i wish would be in plone4. some of this are unpolished ideas, some of this are just pain that i'm expiriencing.
  • everything is a folder (no folder content type)
    idea is not new, its taken from limi's blog, but everything (except File, Image) content types should be folderish.

  • no Image content type
    well Image is nothing more then extended File content type. what i saw in past was that users were confused that there are so many content types. by having only one content type it make plone even easier and close to file-like-system.

  • small/tiny/micro plonecore code base
    when plannning next release please also consider developers happiness not only end-users. we are ppl too you know :P. what i mean is that 90% time i work with plone i really dont need all those features that are builtin. 90% time i need only 2 content types (Document, File) which i extend, superclass, ... this is again subject to argue about, whether plone is framework or software. why it couldnt be both? having light plone core which developers could use to build on it, and end users ready packages like plonefor.community (curent plone), plonefor.getpaid, plonefor.goverment, plonefor.education, ...

  • link content types, wtf?@#$%
    maybe i should read some more end user doc but i just dont get what with link content types all about. just to store link to some page. i would expet form it to show content inside plone (like Windowz product), redirect to that link or even both options. but ofourse this is something that should not be in plonecore (menitoned above).

  • portlets+viewlets=widgets (or call it as you want)
    again idea is nothing knew. all i would ask from plone4 is that it provides rock solid UI to manipulate with them. draging and droping please.

  • no XML please
    i use genricsetup in day to day basis and writing all that xml is just not fun you know. we use perfect language - python - if you forgot. use it. it can do more then just magic. sonce XML is only computer friendly and if we really must use xml then an UI tool *must* be provided or if not next plone book should be "pistol for developers included - for self puprose only"

  • unified plone registry
    this has nothing to do with windows registry so dont panic. its just some centralized way of storing site configuration that can be also (ab)used by add-on products. now we have a mess. every configuration is stored in its own way and place.
    if i may dare this could also be next-generation of genericsetup (with no usage of XML ofcource).

  • no kss in plonecore, ship only with jquery
    50% of time i disable kss since it slows down the site. yes kss is usefull but not in all scenarios. make developers choose whether they would like to write javascript or use kss.

  • developer reference documentation
    this should be killer feature of plone4. currently there is no - or is really in bad shape - reference developer documentation. Christopher Warner few days ago wrote "If core code is undocumented it's broken". but who should be responsible for this? core developers. when there is new feature added/removed documentation should be alsoo updated. sphinx here offers a great way to document our code. it can be api, doctests, docstrings all in one. and can be done from the code ,so all those doctests, docstrings that are already there will be used.
--- after a while i found some more ---
  • plone theming
    deliverence promises a lot, but still plone itself must provide easier theming expirience. something as easy as old zope2 skins and scalable/reusable as zope3 resources.

  • wsgi out-of-the-box
    this is a must, repoze middleware that is availiable now looks so usefull i'm just wainting for some project to try it out.

well this is it, for now ... i'm exited with plone4 release and now its time for me to go back to bed. i think by the end of this night i'll come up with few more.

Rok Garbas: z3c.form in viewlets

By rok.garbas@gmail.com (Rok Garbas) from Planet Plone. Published on Nov 19, 2008.

i blame hannosch for not to be able to sleep tonight :P (previous post)

my obstacle today/tonight was z3c.form+viewlet coctail. after 2h of testing and optimizing i got quite nice peace of code:



and layout_viewlet.pt



now instead of wrapping with FormWrapper we wrap with our new ViewletFormWrapper, like:
OurViewletView = wrap_form(OurCustomZ3CForm, __wrapper_class=ViewletFormWrapper)

all that is left to do is register OurViewletView with browser:viewlet directive and form is ready.

i found this wrapper really usefull and i hope it can get into plone.z3cform. or is there any other way of doing this?

WebLion: Trac plugin makes checkouts easier

From Planet Plone. Published on Nov 18, 2008.

I finally got around to officially releasing the Trac Subversion Location Plugin. This fills a little hole in Trac’s UI wherein there was no easy way to go from spelunking around in the Browse Source tab to actually doing a checkout.

Subversion Location Plugin Screenshot

For a live demo, see the WebLion Trac. Enjoy!

EasyShop: It was never easier to install EasyShop

From Planet Plone. Published on Nov 18, 2008.

Now you can install EasyShop as easy as every other package:

Plone.org: Plone Conference 2009 Selection Process

From Planet Plone. Published on Nov 17, 2008.

Information about our Plone Conference 2009 proposals, and how Plone Foundation members can help select the location for Plone Conference 2009.

Lennart Regebro: Installing Linux on a MacBook without OS X

From Planet Plone. Published on Nov 16, 2008.


OK, so I have made up my mind. I’m switching back to Ubuntu. Why is a later post but in short I feel that Ubuntu is a better OS if you are a develope, at least a Python/Plone developer like me. This post is to explain some things about how MacBooks boot, and how to install Ubuntu on a MacBook without having OS X on it as well. Oh, and it’s for whining and ranting as well.

Firstly, you need OS X for your MacBook. OS X is the only OS you can use when updating the firmware of the MacBook, and firmware updates on MacBooks can be very useful. Earlier ones have for example increased the battery life significantly. Those things are nice to have. This means that most people who use Linux as the main OS will dual boot. There are several FAQs out there to do this, so I won’t touch on that. If you want OS X only to update the firmware, you can reinstall OS X on your hard disk skipping everything that is optional, and thus use up as little space as possible. Reportedly it should be possible to have a partition size of 10-15 GB for this. Quite a significant space waster just to keep the firmware updated, admittedly.

However, I want to be able to boot into OS X so that I can test things. Sometimes I get reports that things doesn’t work in Safari, and I quite often gets bug reports on Plone4ArtistsCalendar together with iCal. It’s going to be nice to be able to test those reports myself. So I need more than these 10GB, probably around 40GB. And of course, I need to be able to test websites in Internet Explorer as well. I have done that with a Windows machine I have at home so far, but to be able to do it when I’m at a customers place would be a nice bonus. And of course, there goes another 40GB, and then I suddenly don’t have much space left for Ubuntu. Especially since I want separate root and home partitions (this has saved me once earlier, when an upgrade went pear-shaped).

So, I yesterday bought an external HD. The My Passport Studio has faster transfer rates, so I picked that one, even though it’s MacBook Pro silvery, and not MacBook white. (Wester DIgital has Macbook white external drives too, but only of their cheaper, slower model). Turns out the faster choice was good because it also has Firewire, and I later read that MacBooks won’t reliably boot from USB drives, so that was a lucky choice. I’m hoping this has been changed in the new model MacBooks that doesn’t have Firewire.

Anyway, I then proceeded to try to get Mac OS X onto the external HD (easy) and Ubuntu onto the internal HD. That later part was not so easy. OK, if you let Ubuntu take over the whole HD, by default, it’s going to work, but there will be a long delay for about 30 seconds where the MacBook will seem to not do anything. And if you have an external drive connected or a bootable CD in the drive, it will boot from that, no options. What the heck was going on here?

Well, after many tried, lots of reading on different sites and many retries (today I have installed Mac OS X three times, which takes an hour or more each time, and Ubuntu I think five (maybe more) times, which takes some 15-20 minutes or so, all in efforts to get the right combination of partition tables and software and I don’t know what. And here finally is the explanations.

The MacBook 3,1 and 4,1 will only load from HFS+ partitions. If there are none available, it will sit around for 20-30 seconds while waiting for you to insert one. Yeah, really. Only then will it go on to boot from non-GFS partitions. This is to be honest quite astounding, and completely incomprehensible. It’s yet again one of these “It Just Works (If You Do Exactly What We Tell You To) ™” attitudes from Apple. This means that the primary partition has to be HFS+. Obviously, you can’t install Ubuntu to HFS+. Neither, it seems, can you install GRUB to it. You can of course install OS X on it, which is why this all works if you dualboot, but that takes 10GB of space, see above. But despair not, there is something you can install to an HFS+ partition, which is not a big fat OS and will boot, and it’s called rEFIt. It’s a boot menu for EFI machines, specifically MacBooks. It can be installed on pretty much any filesystem, and since it’s designed to be a multi boot system for MacBooks, it works well in this case. After installation of Ubuntu, rEFIt will see the Ubuntu and you can boot it, without having to wait for half a minute.

Here are the rough steps you need to do (I didn’t do it in this order, as I was experimenting heavily, but this ordet should work, I think). Again, this has been tested on a MacBook 4,1. It seems to NOT be necessary on MacBook swith Intel CoreDuo (1,1 and 2,1). But it seems to be necessary on MacBooks with Core2Duo (3,1, and 4,1. I don’t know about the new 5,1).

  1. Install Mac OS X on the external HD.
  2. Boot from the Ubuntu Live CD, start Partition Editor (Under System->Administration). If you can figure out a way to remove, add and control partitions in detail in Mac OS X, you can do that instead, but Diskutils in OS X doesn’t seem to have the necessary control to do this.
  3. Remove the HFS+ partition from the internal HD (/dev/dsa)
  4. Create a new unformatted partition (we’ll format it from OS X). rEFIt will use up 14MB, so probably 20 MB is enough. Yes, MB, not GB. I have a 50MB partition for rEFIt.
  5. Reboot into OS X from the External HD. Format the new partition as “Mac OS Extended” (That’s HFS+). Mount the newly formatted partition.
  6. Download rEFIt, and follow the instructions to install it on an external HFS+ Volume. At this point you probably want to change the refit.config to have a lower timeout than 20 seconds. 2 seconds is good IMO. You should now be able to boot into rEFIt from the internal HD. If not, something is wrong. You still don’t have any OS installed to boot from though, but if you get the rEFIT menu up, your good.
  7. Reboot from the Ubuntu LiveCD, and install as usual. Do NOT select “Use entire HD” as this would delete your rEFIt volume. Largest free space should work (although I always use manual, and have separate root and home volumes).
  8. Done!

This is all and well, and works. The only minor stupidity with this, is that you now have a two-step boot. And to explain why, we must talk about EFI. EFI is the new successor to the BIOS that has been around since the original IBM PC. But of course, not all software that needs to support EFI does that, so therefore there is also a BIOS compatibility mode. EFI also uses a new sort of boot procedure, based on something called GUID Partition Table, or GPT instead of the old MBR one. The booting will revert to MBR if there is no GPT, and in this case it will also enter BIOS compatibility mode (I think).

Now, GRUB is a MBR type loader that uses BIOS compatibility mode. And you have to have it. Because although there is an EFI boot loader from Linux, ELILO, if you boot the machine completely in EFI mode and not in BIOS compatibility mode, you won’t have a BIOS, and lo, the graphics drivers require this, so you can’t run the proper graphics drivers, so graphics performance will suck. And the reason the graphics drivers require this, seems to be that Apple refuse to tell the driver developers how to support the cards without a BIOS.

This sucks, Apple. This, really, really, sucks. I was told that now the MacBook is an open platform where you can run any OS. Well, that is still, unfortunately, bullshit. Apple and their platforms are still not open. Sure, when it comes to the iPhones they have blamed the carriers. I don’t believe that anymore. Help the Linux people write proper ELI drivers for your machines, if you are serious about this. I understand you don’t want OS X running on normal PC’s. You are using OS X as an argument for buying your hardware. If you sold OS X separately your machines would be cheaper and your upgrades more expensive, and that would probably not be good for business. But making it hard to run OTHER things on Macs doesn’t make any sense.

All in all, I can not recommend you to buy MacBooks unless you intend your main OS to be OS X. And I can’t recommend OS X to a developer. Yes, this buy was a mistake.

Posted in linux, mac, plone, python, ubuntu   Tagged: ELILO, grub, macbook, rEFIt, single boot   

Karl Horak: World Plone Day After-Action Report

By noreply@blogger.com (Schlepp) from Planet Plone. Published on Nov 16, 2008.

As regular readers of this blog know, 7 Nov. was World Plone Day. If you hosted a WPD event, but haven't sent in your summary results, please go over to the spreadsheet at Google Docs and fill in your data. Thanks in advance.

Below is a draft press release that captures what we've learned so far from self-reported events.
With 66% of the event sites reporting in, the first World Plone Day can claim success. Friday 7 November was World Plone Day, a coordinated worldwide series of meetups, seminars, and workshops. Events were scheduled from Buenos Aires, Argentina to Hanoi, Viet Nam with a healthy representation in North America and Europe. Truly an international day of Plone, 30 countries on five continents were involved.

Plone is a ready-to-run, open source content management system that is built on the powerful and free Zope application server. Plone is easy to set up, extremely flexible, and provides you with a system for managing web content that is ideal for project groups, communities, web sites, extranets and intranets.

Forty of the 61 registered venues have reported in, showing a total of 982 participants who listened to 107 presenters. Extrapolating to those sites that have yet to record their guest count, perhaps 1500 participants world wide were engaged in learning about Plone. Over 40 companies sponsored events throughout the globe, which were sanctioned by the not-for-profit Plone Foundation, the legal owner of the Plone codebase, trademarks, and domain names.

Activities ranged from small, informal gatherings with ad hoc presentations to large, formal sessions with a half dozen presentations, refreshments, and door prizes. Brasilia, Brazil had the largest event with 128 attendees. Events were tied together in more than enthusiasm for Plone--live blogging, Twitter, and streaming video were all used to interconnect participants.

World Plone Day is anticipated to become an annual event to advocate the benefits of using Plone in education, government, non-profit/non-governmental organizations, and business. For more information, contact the Plone support lists.
Thanks to everyone for their participation and enthusiasm.


Document Actions