One of the common tasks of a LablZ server administrator is to re-index resources. Till now it was possible to submit this operation online running
a url /text/index/resources?... in browser and waiting for a result. But allowing to start indexing tasks outside of scheduler control can potentially create a havoc.
To amend this it is now required to prefix the url with "/job" , for indexing it will become /job/text/index/resources?.... . Effect  of this would be replacement of a direct immediate indexing task invocation for a user job submission controlled by the scheduler.  Any attempt to invoke indexing using old url will be rejected.

.

 

I have added @hideControlPanelInView from some classes which prevents newbie guest from seeing powerful but alas confusing parts.

Could you always show parent in the create dialog?  

Editing in RTE is very good as long as you can stretch the edit box to the width your final resource will show on a blog view resource list or ROP.

The recent work on many aspects of lablz are making it easy to create a stunning looking site!

image resource already has description property.  Would it be possible to include this text directly below an image if the property is not null?

widgets and tabs on a dashboard would benefit from a tool tip at times, such as "click here to see the whole list of features" or "click here to see the dashboard".

relatedTo is a great tool with all manner of uses but could do with some controls.  Here are some examples related to a site such as Floordata:

Not a request for now, but thought I'd share this nice implementation by Ikea of showing more detail while in grid mode.

Would it be possible to create a widget that can refresh and show new content as either a resource list or a single resource?

some words such as All, Product, Service, etc are common in company names and can spoil the Related list of resources.

need for performance analysis

The need. Declarative nature of Lablz Web Apps requires better debugging tool. We currently trace into error.log and this file gets huge and hard to read. In the past we added indispensable Dev zone menu to see only the log for the last HTTP request, sql log for the last HTTP request and stats for queries that hit or missed the cache. But we need better a much way to assess the performance, discover slow and inefficient queries, analyze cache effectiveness, discover exceptions and debug the DAV to SQL mapping.

performance as a standard data source

We have recently cleaned up the Profiling tool which shows WebDAV queries grouped by class. We redesigned Profiling tool from being a custom made HTML generator to producing normal DavResources and utilize the standard resource list painter. This cleaned up the presentation and the code so much that it gave us the idea of fully transforming the unstructured source of data (error.log) into a structured data source using Lablz core DavServlet plugin architecture. Thus MonitorDavServlet was born. New monitoring tool will add the ability to analyze XHR (Ajax) requests, ability to see previous N
HTTP requests, drill down to an individual WebDAV query level and even the ability to re-execute the last WebDAV query collecting the resulting SQL log.

QA, support and other uses

What is amazing is that as performance data becomes structured data the other possibilities instantly open up. These are a couple we thought up:

1. testing framework can use monitoring stats to discover bugs automatically. Initial ideas: execute all bookmarks on every host and compare the number of SQL queries, number of cache hist and misses with the baseline. Also compare the execution time to timely discover performance regression.
2. instant problem indicators. We will place a couple of icons in a visible place (near Home menu or as a badge icon on top of it) to indicate an error which might otherwise be invisible, a presence of a slow query and other exceptions.
   
3. automatically collect current state of the system at the bug submission time. This can be done by producing .csv backup of monitoring resources and attached to the Bug resource in Lablz CRM. This can be further automated much like Ubuntu bug submission tool which collects system info on behalf of the user. The developer can then load these .csv files into his system for analysis.

Most of the initial development has been done and Dev Zone menu already contains a link to Monitoring. Please review and submit your comments and ideas.

Implementation notes:

1. we begin collecting monitoring info on the first request to /monitor location. That means the stats will start accumulating only after your first click on Monitoring link in the Dev zone.
2. we collect info on an HTTP session. This means you will see only your own requests.
   
3. data on the last 10 requests are kept in memory, no extra disk operations are performed
   

It is hard to distinguish between color scheme resources just by their names. Imagine we will have dozens and even thousands of them. When ColorScheme resource is added we can generate an image that shows its primary and secondary colors. We can create a small image as a pie chart and larger images like a colorschemedesigner preview square that shows all primary and secondary colors.

Implementation details:

1. ColorScheme class must implement ResourceImage interface
2. create a GenColorSchemeImageServlet that generates png (or jpeg) images for a given ColorScheme resource URI. This servlet should then issue PUT to upload generated images to the ColorScheme resource and after that set its originalImage, mediumImage, etc. properties.
3. add NotificationPhase handler that will submit GenColorSchemeImageServlet as a delayed job.
   

Initially I was thinking of this for layout changes; you delete a widget accidentally or save over a bookmark by mistake (all pilot errors), or you are simply experimenting with a specific layout.  In traditional html tools you might save a version or the tool will generally have undo history.  Making small layout changes are a one way process in Lablz unless you keep a copy set of bookmarks; there's no going back.

The ability for the user to change the backlinked resource properties shown would on ROP would be useful.

Would it be possible to remove the widget flip and grabber for users without the rights to make changes?

Lablz continues with its strategic direction of making Search a center of user experience in any Lablz App. Many changes were pushed to current 3.4 build, others will show up in 4.0.New Search featuresWe have added spell checking (language independent), word stemming (English only for now), autocomplete in Mobile mode (soon will show up in desktop mode as well), and word pairs for autocomplete (shingles in Lucene-speak). A day ago we enhanced each autocomplete word with icons of related classes. We continue to optimize the Search (just shaved 200ms by reader caching) and improving the presentation layer. We are also fine tuning Filter after Search so that novice users have a way to drill down after a simple text search. 

At least this is whatJohn Herlihy of Google Europe says . See an interesting article on a platform shift to Mobiles by former startup evangelist at Microsoft and now Google's Developer Advocate Don Dodge.Things are heating up in Mobile space. Google recently announced the change in strategy called Mobile first . Google will now release new products first for the smartphones and only later for desktops.

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

Sometimes papinet message was not generated because of some errors in Order (for example transshipment point should have been Verbrugge, but instead it is something that was not recognized as Verbrugge). When Order is fixed papinet message should be generated anew in order to sent it to the client.

In order to do that:

1. Login to Verbrugge host
2. execute the following URL:
   [verbruggeHostUrl]/export/edi/import/[newpl]/fileName?name=PapinetContainerTransport&target=papinet