Personal tools
You are here: Home Eggs wildcard.excel

wildcard.excel

interpret excel files into content

Current release

No stable release available yet.

Project Description

  • excel file required
  • on save, convert excel file into something meaningful
  • render converted as html table
  • allow some sort of table editing? later maybe...

System Message: WARNING/2 (<string>, line 6)

Bullet list ends without a blank line; unexpected unindent.

Change history

Changelog

1.2rc4 (2011-06-13)
  • fix number check
1.2rc3 (2011-06-08)
  • fix jquery $ ref
  • respect the excel styles at all costs
1.2rc2 (2011-05-25)
  • remove back arrow on "return to table"
  • add render format
  • fix online editor
  • allow breaks to be entered in online editor of excel
  • provide way to ignore, and headerize a cell with table editor
1.2rc1 (2011-05-25)
  • fixed view references in fti
  • fix download view to set filename and such
1.2b2 (2011-02-22)
  • add blob migration
1.2b1 (2011-02-22)
  • using new version of xlrd that supports inline styles
  • use blob storage if available
1.1b2 (2010-12-09)
  • remove subscripts from jump links
  • add ability to replace text with other text so you can customize the output
1.1b1 (2010-12-08)
  • provide ability for jump links
  • previous page link on table page
1.0b1 (2010-12-07)
  • fixed superscript numbers not formatting correctly.
  • fixed dark tan table padding
  • added italics and underline styles
1.0a3 (2010-11-14)
  • fixed formatting of 1st, 2nd, 3rd, etc..
  • fixed footers not getting grabbed correctly
  • added referenced data declaration
  • added headers and changed some formatting
  • add validation and give error message if problem with parsing excel file
  • fixed issue where data was getting corrupted
1.0a2 (2010-11-11)
  • fix issue where extra rows would show for some tables
1.0a1 (2010-11-09)
  • initial release

Detailed Documentation

Introduction

This is a full-blown functional test. The emphasis here is on testing what the user may input and see, and the system is largely tested as a black box. We use PloneTestCase to set up this test as well, so we have a full Plone site to play with. We can inspect the state of the portal, e.g. using self.portal and self.folder, but it is often frowned upon since you are not treating the system as a black box. Also, if you, for example, log in or set roles using calls like self.setRoles(), these are not reflected in the test browser, which runs as a separate session.

Being a doctest, we can tell a story here.

First, we must perform some setup. We use the testbrowser that is shipped with Five, as this provides proper Zope 2 integration. Most of the documentation, though, is in the underlying zope.testbrower package.

>>> from Products.Five.testbrowser import Browser
>>> browser = Browser()
>>> portal_url = self.portal.absolute_url()

The following is useful when writing and debugging testbrowser tests. It lets us see all error messages in the error_log.

>>> self.portal.error_log._ignored_exceptions = ()

With that in place, we can go to the portal front page and log in. We will do this using the default user from PloneTestCase:

>>> from Products.PloneTestCase.setup import portal_owner, default_password

Because add-on themes or products may remove or hide the login portlet, this test will use the login form that comes with plone.

>>> browser.open(portal_url + '/login_form')
>>> browser.getControl(name='__ac_name').value = portal_owner
>>> browser.getControl(name='__ac_password').value = default_password
>>> browser.getControl(name='submit').click()

Here, we set the value of the fields on the login form and then simulate a submit click. We then ensure that we get the friendly logged-in message:

>>> "You are now logged in" in browser.contents
True

Finally, let's return to the front page of our site before continuing

>>> browser.open(portal_url)

-- extra stuff goes here -- The ExcelFile content type ===============================

In this section we are tesing the ExcelFile content type by performing basic operations like adding, updadating and deleting ExcelFile content items.

Adding a new ExcelFile content item

System Message: WARNING/2 (<string>, line 175)

Title underline too short.

Adding a new ExcelFile content item
--------------------------------

We use the 'Add new' menu to add a new content item.

>>> browser.getLink('Add new').click()

Then we select the type of item we want to add. In this case we select 'ExcelFile' and click the 'Add' button to get to the add form.

>>> browser.getControl('ExcelFile').click()
>>> browser.getControl(name='form.button.Add').click()
>>> 'ExcelFile' in browser.contents
True

Now we fill the form and submit it.

>>> browser.getControl(name='title').value = 'ExcelFile Sample'
>>> browser.getControl('Save').click()

And we are done! We added a new 'ExcelFile' content item to the portal.

Updating an existing ExcelFile content item

System Message: WARNING/2 (<string>, line 197)

Title underline too short.

Updating an existing ExcelFile content item
---------------------------------------

Let's click on the 'edit' tab and update the object attribute values.

>>> browser.getLink('Edit').click()
>>> browser.getControl(name='title').value = 'New ExcelFile Sample'
>>> browser.getControl('Save').click()

We check that the changes were applied.

>>> 'Changes saved' in browser.contents
True
>>> 'New ExcelFile Sample' in browser.contents
True
Removing a/an ExcelFile content item

System Message: WARNING/2 (<string>, line 213)

Title underline too short.

Removing a/an ExcelFile content item
--------------------------------

If we go to the home page, we can see a tab with the 'New ExcelFile Sample' title in the global navigation tabs.

>>> browser.open(portal_url)
>>> 'New ExcelFile Sample' in browser.contents
True

Now we are going to delete the 'New ExcelFile Sample' object. First we go to the contents tab and select the 'New ExcelFile Sample' for deletion.

>>> browser.getLink('Contents').click()
>>> browser.getControl('New ExcelFile Sample').click()

We click on the 'Delete' button.

>>> browser.getControl('Delete').click()
>>> 'Item(s) deleted' in browser.contents
True

So, if we go back to the home page, there is no longer a 'New ExcelFile Sample' tab.

>>> browser.open(portal_url)
>>> 'New ExcelFile Sample' in browser.contents
False
Adding a new ExcelFile content item as contributor

System Message: WARNING/2 (<string>, line 243)

Title underline too short.

Adding a new ExcelFile content item as contributor
------------------------------------------------

Not only site managers are allowed to add ExcelFile content items, but also site contributors.

Let's logout and then login as 'contributor', a portal member that has the contributor role assigned.

>>> browser.getLink('Log out').click()
>>> browser.open(portal_url + '/login_form')
>>> browser.getControl(name='__ac_name').value = 'contributor'
>>> browser.getControl(name='__ac_password').value = default_password
>>> browser.getControl(name='submit').click()
>>> browser.open(portal_url)

We use the 'Add new' menu to add a new content item.

>>> browser.getLink('Add new').click()

We select 'ExcelFile' and click the 'Add' button to get to the add form.

>>> browser.getControl('ExcelFile').click()
>>> browser.getControl(name='form.button.Add').click()
>>> 'ExcelFile' in browser.contents
True

Now we fill the form and submit it.

>>> browser.getControl(name='title').value = 'ExcelFile Sample'
>>> browser.getControl('Save').click()
>>> 'Changes saved' in browser.contents
True

Done! We added a new ExcelFile content item logged in as contributor.

Finally, let's login back as manager.

>>> browser.getLink('Log out').click()
>>> browser.open(portal_url + '/login_form')
>>> browser.getControl(name='__ac_name').value = portal_owner
>>> browser.getControl(name='__ac_password').value = default_password
>>> browser.getControl(name='submit').click()
>>> browser.open(portal_url)

Contributors

"", Author