Happy New Year, everyone!

 

RTF is hardly the way of the future; nor is HTML. Neither of them permit the full expressiveness that a writer needs. As an example, most of us use InfoQube in part or in whole because of its outlining capabilities. Neither RTF nor HTML version 4 support outlining. HTML5 does – although for the moment very few HTML5 editor's make much use of it.

I do not use the HTML pane in InfoQube (which uses HTML version 4). That is because any work that I put into formatting text in the HTML pane is wasted because I cannot export it in order to publish it. For now, the work that I publish is created in Microsoft PowerPoint and in Microsoft Word - as it has been for many years. Once there is a good HTML5 editor, I may jump ship towards that. As Pierre hints, HTML 5 support within InfoQube is and must remain a low priority. I too would like to have RTF support… But that would be a distraction.

 

Instead, we all want to see InfoQube version 1.0 on the market and making money for Pierre in 2015.

 

Let's use InfoQube for what it's good at: structuring information, primarily in the outline view. That can, somewhat painfully, be exported into Word or PowerPoint via Excel. And that is good enough.

On my wall, I have a motto in large print. It reads:

"Distraction is a deadly enemy. Flee it."

 

Mark GREGORY, Redon, France - GMT +1/+2; EST +6

That will always be a challenge in my opinion. Google can be capricious at times and Microsoft provides updates which break things for some software. This is why I either would keep the calendar local in IQ or do a Onedrive dance and be done with reliance on other parties. But that's just me.

 

Jon

 

--

Sony Vaio Z, Intel Core i7, 8 GB RAM, 800 GB SSD

Windows 7 Professional 64 bit