Archive for March, 2007

Old Friend better then 3.2.2

Old Friend

Recently I tried to switch to latest Eclipse release 3.2.2. I perform ascetic setup - just Eclipse Platform + JDT + Subclipse 1.2.0. Have nothing bad to say about Eclipse itself, but new Subclipse from one side works faster, from the other unstable. Time to time I was getting errors, I have problems to switch between branches, and finally it start to say that “Client version is too old”. Ok, this was too much to me to checkout project again and I back to my old configuration, hope it wasn’t offended too much. At least Subclipse there stable slow.

No Comments »

Sharpshooter

over worked

When it is too much work TODO you may stuck with it only just because you switch too often from one task to other. In such situations I do the following thing, I just write all TODO items in a paper as a long list. Even things like “respond to email” or “copy file” will get there. So all the enemies became are good visible.

After that I select a strategy for the war. There are three obvious:

  • Kill smallest first
  • Kill higher priority first
  • Combination of first two.

After that the hunting begins. When the next task get finished I strikethrough it (or even rewrite the list) so list became noticeable shorter.

In most cases I select first strategy and when the list come shorter you get more courage to fight with the more complex and long-term task, so they became to look not so big sometimes they start to look even miserable.

No Comments »

Data Forest

Data Tree

From my experience there are two way to effectively organize supplemental information in Documentum and make it available as a data for the attributes.

The first and the simplest this is create and register table and in the Application Builder setup select from this table as a data source. Then WebTop and Desktop will display drop-down list with the values. This way is acceptable for the small amount of data and the second disadvantage that Documentum hasn’t an effective way to edit this information.

The second way is to create native Documentum document or folder and make a bit customization to populate it as a data for the attribute. I prefer folders because they allow to organize information in a tree, also Webtop has a native component to pickup a folder. So the general flowchart is:

  • create base folder/cabinet for the supplemental information
  • create a subfolder for each type of information
  • fill it

This way has many advantages. You may use folder structure to organize hierarchical data like your organization structure or products list, etc. Also Documentum provide a standard way to edit this information, all you need this is create a foder :). You may decide to create a separate type for each type of data; this will allow you easily link it with the specific icon (many capricious customers ask for this customization). To organize BIG amount of data you may add additional abstract layer to real folder tree. For example use leading letters as a subfolders or years or product category. So you may build your own data tree.

No Comments »

« Prev