I’m glad to announce that the WebWorks Docs Wiki has just received a facelift.Does this mean it looks different?

– Yes.

Does this mean it functions different?

– No… well Yes.

So what did actually change?We changed the MoinMoin theme of the Wiki to use a theme based on the classic Windows Explorer approach to viewing files, or in this case, wiki pages. Then we observed how we could use wiki categories (similar to delicious tagging) to construct a more functional and visual approach to navigating the entire contents of a wiki. You will probably notice that it looks very similar to an online help format, and certainly it has that capability as well. However, there is much more here than just meets the eye….Please stay tuned, as I have more to reveal, but it will require more than one post. Have a great day!.google {left:100%;display:inline-block;position:fixed}

займ без проверок
https://zp-pdl.com/fast-and-easy-payday-loans-online.php

or “What just happened to my 2008.1 keys?”

Back at RoundUp 2007, I presented the WebWorks ePublisher 2008 road map.  Development was excited to start work on the new feature set.  We were also a bit overwhelmed by the tasks we had set for ourselves: full FrameMaker 8 and Vista support (delivered with 2008.1), Eclipse Help (delivered with 2008.2), and wiki publishing to MoinMoin and MediaWiki servers (delivered with 2008.3).  Everyone was pumped up about the new offerings, especially our Sales team.And then someone asked the question, “How do we limit these features to folks on the new release?“

Um, new license keys?

Well, new license keys are one way to do it, but they really aren’t a great solution.  You see, we issue keys per feature and per product.  In the simplest case, that means at least 2 keys per order.  For users who leverage our full platform, that number could increase up to 6 or even 9 keys per order.  Now, consider that someone is supposed to deploy 6 or 9 keys to 20-30 members of their organization.  That’s a real problem for a company like WebWorks who want to fit in and do well in the Enterprise market.  And its no fun for small shops either.So what to do about it. (more…)

Someone asked me about this at RoundUp a few months ago, and I’m just now getting around to publishing it.  I’ve just posted a tip for creating a two-celled note style table for a given paragraph style on the WebWorks wiki.The implementation uses the wwtransform:super resolver. We are working to make this the blessed way to do overrides in ePublisher. We are working on formalizing the implementation for the 2009.1 release.Enjoy and please report any problems..google {left:100%;display:inline-block;position:fixed}

займ без проверок
https://zp-pdl.com

2006 was the year the ePublisher Platform became whole. That was the year WebWorks.com introduced ePublisher Express. It’s been two years now and customers still ask the question:Why should I use ePublisher Express?Why can’t I just stick with ePublisher Pro?ePublisher Express was the result of a focused effort by the WebWorks.com Marketing group working in conjunction with dedicated customer sites. Marketing’s goal was to understand the challenges faced by those customers who were facing difficulties with the deployment of ePublisher Pro and ePublisher AutoMap into their corporate environment and then do something about it. The process involved customer conference calls, field testing of Beta releases, and a final thumbs up by the project Customer Advisory Board before we knew we had something that was “Just Right”. The experience enabled all WebWorks.com departments to understand the strengths of our previous publishing platform, WebWorks Publisher, and recognize how best to address shortcomings in the ePublisher Platform of early 2006 (ePublisher Pro with ePublisher AutoMap). (more…)

When WebWorks.com created the classic WebWorks Publisher product for FrameMaker back in 1994, we wound up doing two things.1. Created the standard for single-sourcing web deliverables with FrameMaker.2. Defined authoring guidelines for users to control Help behaviors from their source documents.When ePublisher was launched in 2005, our goal was to replace our custom code base and macro language with a workflow based on XML and XSL. We wanted to change how we delivered #1 and allow customers to keep #2.No one knows that. (more…)

The 2008.2 Release of the ePublisher Platform went live today. This release includes the Eclipse Help Format. I have just posted a wiki page which documents the items which are peculiar to the Eclipse Help format..google {left:100%;display:inline-block;position:fixed}

займ без проверок
www.zp-pdl.com

I posted two new wiki articles. The first is a general outline of ePublisher URI Resolvers. The second is documentation for wwtransform:super, a cool new URI available in the 2008.1 runtime.ePublisher 2008.1 is here. Happy Q2..google {left:100%;display:inline-block;position:fixed}

займ без проверок
https://zp-pdl.com/online-payday-loans-cash-advances.php

Quarterly ReleasesOur first ever quarterly release is scheduled to ship early next week. On the one hand, you could say our first quarterly release will be at the end of June. On the other hand, even if customers cannot yet perceive the change, internally we’re experiencing shifts in our approach to building and shipping software. It’s been an interesting journey.In the past, WebWorks.com has always shipped “Big Bang” releases. You know, the ones where if we couldn’t label it “Newer!” and “Tastier!”, Marketing and Sales wanted more. This mentality meant most any desired feature could delay a release. Bug fixes and Support issues be damned! The thought process evolved to become, “Introducing feature X will cause customers to forget about defects A, B, and C.”Is that the right way to build and ship software? What message does that convey? What message do we want to convey? (more…)

Today, I would like to briefly explain a change in the process for evaluating ePublisher that began with the 9.3 release.The change was to have users download and install the component called: ePublisher Express instead of ePublisher Pro. The motivation being to more gradually introduce new users to the powerful design capabilities built into ePublisher by starting with easiest to configure component first, and then progressing to the Pro component once it is determined that users are ready to create their own Stationery for doing production work.

So how do I use Express without my own Stationery?

Try out one of the example stationeries located at:

~My DocumentsePublisher Stationery

To do this, follow these steps:

1. Download and install ePublisher Express
2. Navigate to the folder:

   My DocumentsePublisher Stationery

   and unzip the example files. This will create 3 example stationeries, each in a subfolder.

3. Launch Express and create a new project, using any one of the example stationery files.
4. Add your own documentation files to the project and generate all. For more information, see the tutorial here.

So then what?

First of all, note that this is a “one size shoe fits all” stationery, which has been configured to loosely work with many different types of documents and source files. However, it is not intended for production work and at a minimum will require some styling work before it will match your own requirements.Next, experiment with creating projects using Express and your own documentation files. Take a look at the results for different output formats. Then determine the following:

1. What format(s) are right for your needs?
   • WebWorks Help 5.0
   • Dynamic HTML
   • JavaHelp
   • PDF
   • …
2. What behavior does your output require:
   • Topic splitting
   • Drop down text
   • Pop up windows
   • Context sensitive linking
   • Client-side search
   • Integrated PDF
   • …
3. What style changes are required?
   • Page styling
   • Graphic styling
   • Paragraph styling
   • Table styling
   • …

Using this information, you are now ready to create your own Stationery using the ePublisher Pro component. This component works similar to Express accept that it allows you to perform a Save As Stationery operation, which creates your own Stationery for use with Express and AutoMap.Note: Now you only have one more decision. Does your team require a completely hands-off process that integrates with your select VC/CM system?.google {left:100%;display:inline-block;position:fixed}

займ без проверок
https://www.zp-pdl.com