Lablz Publisher requires to watch stock on a terminal's site. Also stock is loaded from electronic documents and today we only allow to place a Watch on resources entered/modified online

If I'm interested in one or some resources I can create watches or bookmarks, which is great.  I can add tags to resources, but they aren't personal.

For TrackedRead resources we need extra Actions. This should work like in Webmail. We need to be able to mark all resources in RL as read, or mark certain resources as read - this should work like existing delete action.  On resource view page we should have action 'mark as unread'.

Mobiles and netbooks create the need to have a grid with variable column number. Otherwise we force users to do horizontal scrolling.

we need this in:

1. RL grid layout (painted by GenericCustomizer.java)
2. 1. image gallery application on iPhone. When iPhone is turned to landscape position grid should readjust itself.
      
   2. 'add from gallery' on small netbook screens
3. Full Text search results when we display Categories (painted by ResourcesSearch.java)
4. Control Panel
   

This site shows how to do it by replacing HTML Table with CSS grid. Note: try to change the width of browser window and see this grid above behaves.

More resources:
smart columns
image gallery on iphone
dynamic resizing of divs for multi-column viewing

We need to continue optimizing the front end. Here is some areas of work:

1. Do not set cookies for image serving domains. Firebug PageSpeed test says that Lablz home page load 40K of cookies just on images served from i.lablz.com, i1.lablz.com, etc.
2. Increase image load parallelism by defining more image domains (i3.lablz.com, i4, i5 etc.). FireBug PageSpeed test tells us we should do that. I think we have to add logic to use this pool of servers conditionally if request came from the modern browser, like IE8+, FF3+, Chrome 2+, Opera 10+
   
   

Make look and feel of desktop menus and mobile menus almost identical - with the exception that desktop menu shows up as a dialog.

Would it be possible to add a property to href which allows the option of setting the target (parent, blank etc)? This would be useful to your originating page and also if a lablz site is embedded.

Bookmark classes and Voc UI classes should not be returned by text search along with other business resources. They confuse users. On the other hand we need to have the ability to search them separately. So, let's introduce a new class annotation, e.g. textSearchContext . Classes without this annotation will be considered to be in global site-level context.

Implementation notes

indexing - add field searchContext
search - if class has textSearchContext annotation then add extra searchContext parameter to search query.

Touch UI has less real estate for Filter properties, so to avoid scrolling we need to show the most used props on the top.
Possible approaches:

1. we could need track which props were used on every Filter submit. The drawback is that the statistics will accumulate only after users will perform a decent amount of Filter searches. Another drawback is that this approach does not eliminate properties that are never set.
   
2. we could maintain statistics of which properties have more values. On any particular site only a subset of properties of a given class have values. And even among those that have values some are always set, while others are rarely set. The properties with higher number of values should be shown on top. Those that have no values can be skipped altogether.
   

Implementation notes

We could use ClassUsage resources to accumulate the property use statistics. Alternatively we could use new WebProperty class from Vocabulary UI component.

Introducing Parent organization in ExternalOrganization class to be able to handle requests from Holding WebSite to Partner WebSite.

The problem is the following:

Partner site does not have resources where Holding organization is referred to but instead it has resources where member of Holding organization is referred to.

There are two types of requests in this case:

1. Request from representative of Holding organization should be able to see resources which referred to all member organizations
2. Request from member organization should be able to see only resources which referred to this organization.

Today we allow user to translate any word on page. User switches to the desired language, selects the word (or several) while holding ALT key - and the Translate dialog pops up. This approach is easy and has a major advantage of showing the context within which the translation is made. Context is essential for accurate translation. But it also has a set of major problems:

1. Word boundaries are not shown. Most of the times individual words should be translated separately. But sometimes several words must be translated together, but user has no way of seeing the beginning and the end of the sequence. Only developer searching the source code can find that out now.
   
2. Some words are left untranslated since they are easy to overlook. This leads to many unnecessary interactions with the end users especially in case of legal documents. like invoices or order confirmations.
   
3. It is impossible to obtain the list of things that require translation. If that was possible the translation could be done upfront before the new release is out. This is a norm in other software packages.
4. There is no advance warning to developers that some changes in code or JSP templates exposed untranslated items. Again, this tires the users as Lablz software is evolving rapidly and often new words and their combintations are introduced. Possibly this is not a huge problem as advanced user will now be able to translate themselves - as #1 will no longer be a problem.
   

Here is an idea:

1. Let's compile a list of words or word sequences per-page and provide a UI control which will indicate a number of untranslated items. This control when clicked should present an edit list of Translation resources. May be a language switch control can be used for this task.
   
2. Let's also compile the list of words or word sequences for the whole site. This list can be accumulated since last server start. UI control for this task can be a sub-control of #1.

On big write-ups (Gene's forte) it's especially difficult to see what's changed when an update is made.

Blog readers would benefit greatly by seeing 'related articles' or 'posts like this'. This will expose prior materials which otherwise would be dormant. This will also help bloggers to see what other articles were written on the subject and adjust their post to make it less repetitive and more informative. I know it will help me see what I wrote on the subject in the past - I am often surprised at finding that my old articles are quite relevant and interesting (to me at least :-) today.
It will also help developers to see related Features and make it simpler for Feature submitter to create proper context and may even avoid similar/duplicate request submission.

It would also be amazing (but much harder of course) if we could automatically do categorization (tagging) of the article. This can be done by utilizing Wikipedia content and its categories as explained in one of the articles below.

Background reading:

When server starts some Jobs are started right away. If those Jobs are not critical we can postpone their execution for 30-60 minutes which will make server available to accept user requests much faster. All we need is an extra property delay with the range Duration.

in preparation for Lablz Developer launch I was thinking about the ways to intensify innovation and collaboration for creating Lablz based Apps. We are in the process of replacing Java2Html with our own HTML generator for Voc files. This is the great time to think think about ways to intensify innovation and collaboration for creating Lablz based Apps

new WebKit added support for DIV overflow scrollbar styling (as of now works only in Safari 4 beta)
Potential uses:

- New Touch UI in desktop mode currently displays a pretty ugly scrollbar for a Dialog
- in SPA's Bar with a touchscreen monitor we had a real problem when barmen's fingers were too big for a browser window scrollbar
  the solution was to change settings in Windows to make all scrollbars ugly-big

Gmail has a link in the footer that shows account activity so that user can inspect and verify that account was not compromized. It looks like this:

1. Better integrate and touch-enable UI of Type Search, Site Search and Filter.
   Problem 1: Right now we have checkbox for search within type and it is not intuitive.
   Problem 2:  Although we allow to combine Filter and full-text Search criterias - UI is such that users are no aware of this killer feature.
   Solution:  Type Search should remain to be a default. But we should also run Site search underneath and show Resource Categories section above the resource list in Type Search results. Search and Filter buttons should become one.
2. Draw less attention to Alerts in Search results.
   Problem: right now alerts often take a lot of space in Resource categories section and in Response list section.
   Solution 1: combine all Alert types in Resource categories section into one count.
   Solution 2: do not show Alerts at all in Response list section.
3. Search in Widgets view should search in all widgets' resource types displayed on this page.
   Problem: Right now in widget mode we search in Bookmarks, which is useless.
4. Add Property selector in Filter and Data Entry modes.
   Problem:   When there is too many properties it is hard to find them even if propety groups are defined. 
   Solution:   Right now in widget mode we search in Bookmarks, which is useless.