T.R | Title | User | Personal Name | Date | Lines |
---|
2188.1 | No Problems ! | QCAV01::RAVISHANKAR | NoExplainationsAreNecessary!! | Wed Apr 09 1997 10:24 | 34 |
| Hi Bjarne,
>> 1. We want to integrate the Office97 products as tools in LinkWorks.
MS Office tools are already integrated with LinkWorks. To integrate
Office 97 just the new Master Document Formats for the OFFICE 97
products have to be put to LinkWorks and made as defaults.
>> 2. We want the Office97 programs set up such that no local copies
>> of the objects are created on the client.
OLE ILockBytes is enabled so this functioanlity is available OOTB
>> 4. It should be possible to run Office97 both locally and from a
>> server.
Depends on the Office setup for the client. But YES !
>>5. If we create new object classes for documents, spreadsheets etc.,
>> is it possible to "move" an object from the old object class to the
>> new one, one by one? This would make it possible to run in
>> "parallel" with both tools (for instance Lotus 1-2-3 and Excel97) and
>> selectively bring the objects over to Office97.
For every user the tool can be specified. By Default all these
tools are associated with the object classes. So if a user has his/her
tool setup as Word and they click on a Document object which was
created using Word Perfect then on load office will request a
conversion (this is a functiality of Word). If they make changes to the
document then on exit they will be asked if they want to convert it to
Word format. This conversion does not mean a change in the object class
of the object. So the user has an option to save it as a Word Perfect
document or as a Word Document.
Hope this helps
Ravi
|
2188.2 | | elec5.uto.dec.com::maandag_j | | Wed Apr 09 1997 12:17 | 15 |
| Bjarne,
Regarding the integration of Outlook, how exactly do you want to see that integrated?
The mail part will be integrated the same way as the Exchange client mail integration.
In principle that means that you can send LinkWorks objects through Exchange and transfer
messages from the Exchange inbox on the client to LNX.
In version 3.2 drag and drop is fully supported as well between LNX and an open
Exchange/Outlook message.
Outlook is more then mail though. It has a Desk metaphore as well. I don't see ways
to integrate that with the Desk of LinkWorks.
Regards,
Jos
|
2188.3 | Something tried, but more questions from customer | OSL09::BJARNE | endless loop (n). See LOOP, ENDLESS. | Thu Apr 10 1997 09:07 | 41 |
| Thank you both for swift feedback! Here is some more input, directly from
the customer.
More help very welcome.
- Bjarne
---------------------------------------------------------------------------
1 Regarding Outlook integration I'm not quite sure myself, but I believe I
am thinking about the mail client!
2 I did as mentioned and used the already defined (Intel-NT) tools
in LinkWorks for MS-Excel and Word7.0 and changed the master documents.
(And path variable on NT as the tool are defined without a directory.
I can then see the option for running both on the server or locally
by just changing the path and keep the tools as they are)
It does work, but there is some strange behavior:
In particular saving is confusing: Say you are editing and object
called test. When you want to save you have the options to
use the "diskette" (save) ikon on the menu-bar or select "File-update"
or "File -Close and return to LinkWorks 'test'". The last option is
confusing for the users. They are already "in" LinkWorks test.
Whatever I do I always get the LinkWorks message afterwards:
Save "object-type" test? Still more confusing as it may have been saved
through various options "inside" the tool several times already.
Adding to that "Close and return...." also exits Excel,but Word stays open.
This is not a good.
3. When I use the MS-products as tools I cannot open any of the old objects
created in WP and Lotus. Excel (as an example) says it cannot start, because
it is looing for the old document in the 'temp' directory. Creating a new
object works (with the limitations mentioned in point 2).
4. The point I wanted to make was that for a (hopefully short!) period
a user should have both tools for the same object available.
(Or "move" an object to another object class if neccesary ,
but I do not really want to create too many object classes.)
Say you have an old document created in WP that tourns out horrible
in Word. The user have no time to go through the "clean up" in Word.
---------------------------------------------------------------------------
|
2188.4 | Update | OSL09::BJARNE | endless loop (n). See LOOP, ENDLESS. | Thu Apr 10 1997 13:16 | 9 |
| The last lines were somewhat cut, here is the correct ones:
>> Say you have an old document created in WP that tourns out horrible
>> in Word. The user have no time to go through the "clean up" in Word,
>> but may go back to WP, for that document only, to get the job done.
Any ideas of how we can support two tool types, in a parallel way?
- Bjarne
|
2188.5 | slightly roundabout way ! | QCAV02::RAVISHANKAR | NoExplainationsAreNecessary!! | Mon Apr 14 1997 07:58 | 13 |
|
Bjarne,
What your customer could do is derive the appropriate class from
the predefined LinkWorks Class and assign the other tool. Eg: Inherit
from Document a class called 'Document2' or something. For Document2
class assign the tool as Word. That way if the user creates a document
of class Document then they'll open Word Perfect but if they use
Document2 then the'll use Word97. In this scenario if they want to
convert documents then they'll have to export them convert them and
then import them as object in the new class.
Ravi.
|
2188.6 | | TAV02::YAKIR | Yakir Lavie, ISRAEL DTN 882-3327 | Tue Apr 15 1997 13:35 | 12 |
|
> Document2 then the'll use Word97. In this scenario if they want to
> convert documents then they'll have to export them convert them and
> then import them as object in the new class.
>
or else use the ChangeObjectClass() method to switch (back and forth)
between the old and new classes - easy to do with a button/menu option.
Yakir
|