[Fiware-wpa] D.2.4.2 Technical Roadmap - front page, open points and next steps

Sandfuchs, Thorsten thorsten.sandfuchs at sap.com
Fri Feb 1 09:30:36 CET 2013


Topic: producing tables where pages are oriented in landscape

Short answer: sort of "done" - at least semi-automatically.

What I did:

-          Introduce a word macro which handles layouting of the page orientation (which is attached below and attached to the manual created doc by me in order for you to copy)

How to use the macro:

-          place the cursor somewhere in the text before of a table, which breaks the page boundaries

-          Run the macro

-          Done :) (potentially check if you can still increase or decrease the font size)

Limitations:

-          only tested with MS word 2010

-          This does not address any of the content-related topics, raised within this thread :)

What the macro does:

-          It jumpts to the following table

-          Inserts a page break after and before of this table

-          Navigates again to the table at hand

-          Changes the page orientation to landscape

-          Decreases the size of the fonts within this table by 5 steps

With this macro, converting the complete "Technical Roadmap" took me around 5 minutes (max). It was applied to roughly 10-15 Tables (especially the WP9/Tools has a LOT of them - potentially this chapter should be layouted completely in landscape?!

For your convenience you can use my document, which I'm exposing with a link in the deliverable cockpit https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Deliverables_cockpit (linked as well below)

I would recommend to use this D242_v0_generated.docm for your reviews and check if I missed something in your chapter.
Progress Tracking and Links WP2 (skeleton)
Task

official
Deadline

Planned
submission

Deliverable Front Page Link

Link to generated .zip

related docx

2.4b

M21

2013-02-08

D.2.4.2 Technical Roadmap<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/D.2.4.2_FI-WARE_Technical_Roadmap_front_page>

generated: D242_v0_generated.zip<https://130.206.80.126/deliverables/D242_v0_generated.zip>

related doc: D242_v0_generated.docm<https://sapmats-de.sap-ag.de/download/download.cgi?id=343S2337FS1L9ME52THUHDUJ7C0WZ1H17UOX1U39AQ72IG03KV>


Best,
                                                                /Thorsten

And now comes the macro (you can easily bind this macro to a key on your quick-access bar and have the same functionality as I have in all of your documents):

Sub Macro1()
m
'
' Macro1 Macro
'
'
    Application.Browser.Target = wdBrowseTable
    Application.Browser.Next
    Selection.Tables(1).Select
    Selection.MoveRight Unit:=wdCharacter, Count:=1
    Selection.InsertBreak Type:=wdSectionBreakNextPage
    Application.Browser.Previous
    Selection.InsertBreak Type:=wdSectionBreakNextPage
    If Selection.PageSetup.Orientation = wdOrientPortrait Then
        Selection.PageSetup.Orientation = wdOrientLandscape
    Else
        Selection.PageSetup.Orientation = wdOrientPortrait
    End If
    Selection.Tables(1).Select
    Selection.Font.Shrink
    Selection.Font.Shrink
    Selection.Font.Shrink
    Selection.Font.Shrink
    Selection.Font.Shrink

End Sub


From: Juanjo Hierro [mailto:jhierro at tid.es]
Sent: Mittwoch, 30. Januar 2013 15:03
To: Sandfuchs, Thorsten
Cc: fiware-wpa at lists.fi-ware.eu; fiware-wpl at lists.fi-ware.eu
Subject: Re: [Fiware-wpa] D.2.4.2 Technical Roadmap - front page, open points and next steps


  What about producing the MS Word pages where tables are located in landscape orientation ?




On 30/01/13 14:48, Sandfuchs, Thorsten wrote:
Hi,
If this is the decision (not sticking to the DoW) - I'm fine with it - although I had to make everybody aware in order to come to that decision :)

The problem with the table layout is the following:
WE.HAVE.LONG.LISTS.OF.FEATURES :)
e.g.
FIWARE.Feature.Cloud.ResourceManager.APIs.EssentialManagement<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Cloud.ResourceManager.APIs.EssentialManagement> FIWARE.Feature.Cloud.ResourceManager.Placement.Scheduler<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Cloud.ResourceManager.Placement.Scheduler> FIWARE.Feature.Cloud.ResourceManager.Mobility.LiveMigration<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Cloud.ResourceManager.Mobility.LiveMigration>
Even if you break this, you end up with
FIWARE.Feature.Cloud.ResourceManager.APIs.EssentialManagement<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Cloud.ResourceManager.APIs.EssentialManagement>
FIWARE.Feature.Cloud.ResourceManager.Placement.Scheduler<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Cloud.ResourceManager.Placement.Scheduler>
FIWARE.Feature.Cloud.ResourceManager.Mobility.LiveMigration<https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FIWARE.Feature.Cloud.ResourceManager.Mobility.LiveMigration>

This character/point combination is broken down by MS word only if you really force it to.
In general this works if you have one column, but if there is another column in the table with similar "width", you are lost

Currently I managed to do it manually with:

-          Decrease the font size within the table to very small font

-          Drag & drop the borders of the table to the full width of the page

-          Slowly increase the font size again and hopefully then the table won't grow.

Unfortunately this didn't work for all of the tables, I tried it with and the behavior of resizing tables within MS word is non-deterministic. So obviously I'm not not knowledgeable enough in word to perform this task.

For this deliverable I would hope that one knowledgable person would manage to resize the ~25 tables in no time and we stick to the current wiki layout. But we need to nominate this person :)

In the cases I was successful, the table now looks like follows:



From: Juanjo Hierro [mailto:jhierro at tid.es]
Sent: Mittwoch, 30. Januar 2013 11:16
To: Sandfuchs, Thorsten
Cc: fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>
Subject: Re: [Fiware-wpa] D.2.4.2 Technical Roadmap - front page, open points and next steps

Hi,

  Let's discuss all these points during the confcall this afternoon.

  Of course, any discussion to make progress in the meantime is welcome !

  My two cents in the meantime:

 *   We shouldn't stick so much to what is said in the DoW
 *   The Technical Roadmap has been communicated in the AB meeting so that works as a "sign off" somehow ... nevertheless, again don't stick to the DoW (this was a legacy somehow from the very initial times at which the EC was concerned that FI-WARE was going to be too much "technology push" and there may be conflicts at the AB ... but practice demonstrated this was not the case)
 *   I believe you can break lines within a cell using the standard <br/>.   I remind doing so ... check the cell that describes features of the BigData Analysis GE in the Data/Context Management Chapter.   would that solve the problem you raise with the tables layout ?

  Cheers,

-- Juanjo

-------------

Product Development and Innovation (PDI) - Telefonica Digital

website: www.tid.es<http://www.tid.es>

email: jhierro at tid.es<mailto:jhierro at tid.es>

twitter: twitter.com/JuanjoHierro



FI-WARE (European Future Internet Core Platform) Chief Architect



You can follow FI-WARE at:

  website:  http://www.fi-ware.eu

  facebook: http://www.facebook.com/pages/FI-WARE/251366491587242

  twitter:  http://twitter.com/FIware

  linkedIn: http://www.linkedin.com/groups/FIWARE-4239932
On 30/01/13 10:32, Sandfuchs, Thorsten wrote:
Dear colleagues,
Perhaps to emphasize this - in order to come up with reasonable good and consumable information on what v2 of FI-WARE will provide, the pure list of features, as delivered by every chapter currently, does not help very much.

To add to the points, already listed below I would like to propose a point 5:

   5.   Every chapter to come up with a list of "highlights" provided by "their" v2 - this can be "better"/"some"/"major" integration between A and B - a set of new EPICs which will be supported and was previously not - or a set of "major" functionality, which will be provided, after the release of this particular version.

Subsequently this can be exploited in the executive summary, the FI-WARE Technical Roamap -page and your personal chapter-introduction pages.

... again this is just my 5 cents. So what do you think?

Best,
                                                                /Thorsten

From: fiware-wpa-bounces at lists.fi-ware.eu<mailto:fiware-wpa-bounces at lists.fi-ware.eu> [mailto:fiware-wpa-bounces at lists.fi-ware.eu] On Behalf Of Sandfuchs, Thorsten
Sent: Dienstag, 29. Januar 2013 15:58
To: fiware-wpa at lists.fi-ware.eu<mailto:fiware-wpa at lists.fi-ware.eu>; fiware-wpl at lists.fi-ware.eu<mailto:fiware-wpl at lists.fi-ware.eu>
Subject: [Fiware-wpa] D.2.4.2 Technical Roadmap - front page, open points and next steps


Dear colleagues,

as discussed in Rome, I prepared the submission of the technical roadmap via a related "front page" - within the fi-ware wiki: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/D.2.4.2_FI-WARE_Technical_Roadmap_front_page and the related "zip" here: https://130.206.80.126/deliverables/D242_v0_generated.zip



Please bear in mind, that the DoW foresees content, which is yet - to my knowledge -  NOT persisted in any of the wiki pages:

Part B, page 125 "Releases b) and c) will also comprise proposals for potential evolutions beyond the project completion. Releases of this deliverable will be reviewed and signed off by the PPP Architecture Board."



1.       Who will contribute this perspective on "potential evolutions beyond the project completion" in time?

2.       Furthermore it is unclear to me if there is this "sign-off" from the architecture board currently planned.

3.       In the zip file you see that the layout of the "wide"-tables, provided by the chapters 3-8 the column "Epics under analysis" is often layouted out of the page-range. This is the case, as the content of the table-cells is really humengeous and there are no usable spaces or other means of breaking lines within these tables. The options are as follows:

a.       Somebody layout the related tables in this deliverable prior to submission by hand (I thinks this has to do with hyphenation on  the paragraph format level - but I'm not sure)

b.      We change the layout of these tables to something which is rendering fine in wiki and doc

4.       And lastly, I think the content provided by https://forge.fi-ware.eu/plugins/mediawiki/wiki/fiware/index.php/FI-WARE_Technical_Roadmap is very poor and definitely not up to date - e.g. it says that a "major release is planned for ... Q3 2012" which obvious is already done...

So another open point where we need content-wise improvements prior to submission of this document!



If I remember it correctly, the submission was planned by the end of this week - so we have to quickly decide on who is contributing to the content in this short period of time.

What do you think?



Best regards,

                                                               /Thorsten



PS: related links and deadlines are as always persisted in the deliverable cockpit: https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/D.2.X.submission_cockpit#Progress_Tracking_and_Links_WP2_.28skeleton.29

--



Thorsten Sandfuchs



SAP AG



SAP Research Center Karlsruhe



Vincenz-Priessnitz-Strasse 1

D - 76131 Karlsruhe

www.sap.com<http://www.sap.com>





Pflichtangaben/Mandatory Disclosure Statements: http://www.sap.com/company/legal/impressum.epx



Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.



This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.


Please consider the environment before printing this mail!


_______________________________________________

Fiware-wpa mailing list

Fiware-wpa at lists.fi-ware.eu<mailto:Fiware-wpa at lists.fi-ware.eu>

http://lists.fi-ware.eu/listinfo/fiware-wpa

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20130201/5e07e161/attachment.html>


More information about the Fiware-wpa mailing list

You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy   Cookies policy