You know the story - you start programming and you find yourself in need of a data store - place to keep and lately, hopefully, retrieve your precious data. You already know some Java, HTML, CSS, probably JavaScript as well and now you here comes the database. You've got several options so you start choosing - NoSQL, SQL or something else. Modern developers pick NoSQL for sure, they just want to save data and after us, the deluge. I'm going to skip it as I truly belief that NoSQL will eventually become a marginalized minority as it was several years back.
When it comes to SQL you start to have a dilemma. You'd like to access the database in an object way however there's this hairy old SQL language which doesn't do objects. So your first instinctive thought is to start using ORM - and nowadays Hibernate is a synonym for ORM.
It goes all so well. You define your data objects, you let Hibernate to generate your database schema - happy days. You can query for objects, create, modify and delete them and it's all so rosy.
But in a while - problems. Transactions not working as expected, relations are not propagated the way you want them to, database becomes slow and keeping the application running a chore. And after a bit longer you start to be more and more unhappy with your choice.
So what's wrong with ORM?
First of all ORM adds an extra level of complexity. You have to define stuff and obviously ORM brings in additional extra megabytes of code. And this comes at price. Application start up time up, performance down, scope for errors even higher. Hibernate uses black magic to get lots of things done so you find your object and method proxied, AOPed and intercepted. And that's not all.
ORM encourages bad practices and accesses database in an uncontrolled way - instead you taking control of the database you may not even know what tables there are!
Later you figure out that optimizing queries is next to impossible. Queries are generated by the ORM framework and you've got only limited way to influence their creation. So things like adding an index can be a nightmare.
And that's not all - ORM gets you more data than you need or you think you get. Not only you can’t specify columns you want to get, you may also find that you're fancy ORM goes to database for every detail object. I'm talking about this typical scenario where you iterate a collection of details. You either get all eagerly or nothing lazily. But ORM usually has no idea how you want to get the data (and neither do you) so if a detail for a master has 1000 elements you can end up going to database 1000 times. A real performance killer.
And even if you try to optimize that thing you may struggle - ORM makes it hard to optimize DB by adding indexes due to its unpredictability when it comes to construction of SQL queries. You can, normally, dump all the queries but there's no guarantee that the same queries will be generated all the time so it may be difficult to figure what to index and how. It's also a nightmare for your DBAs as generated queries are hard to read and thus optimizing can be a good fun for a couple of weeks.
So it's the old fashioned DAO where your handcrafted SQL lives still a way to go? May be. That's mostly up to you. But either way, you better master those SQL skills as that's the only way to get your database performance where you want it to be.
Tuesday, August 12, 2014
Friday, June 27, 2014
Is AngularJS the new Fat client?
It was year 2000. People survived Y2k, the dot com bubble was just about to burst and we were writing our shiny applications. Many people were already doing HTML based thin clients (with a bit Javascript and mostly on Internet Explorer because Netscape was crap with anything beyond basic form validation).
But at that time there were still people doing something called "Fat client".
So what exactly was (is) a Fat client application.
In a nutshell, fat client is a concept where the client holds the logic of the application and talks to database directly. Database in this case is the point of truth. Fat clients have certain advantages.
But there are certain drawbacks
And the list goes on.
Now, fast forward, year 2014. Here we are. We've got our servers but we try again to let our clients to do the heavy lifting. This time with a small twist. Instead of using native applications (we've been there, haven't we?) we use HTML/Javascript. So what exactly differs between the fat client v.1 (native application in year 2000) and fat client v. 2 (AngularJS application in year 2014)
So, is it all lost? I don't think so. Because there's already Fat client v. 3 here. Oh yes - the native smartphone/tablet applications! They install but keep themselves updated, they talk to APIs but in their own formats (although JSON is getting there as well). The applications still crash, allow you to save data and work offline. And now (*drumroll*) Google would like to allow these apps on their Chromebooks - eat that Angular!
And for those who want to see this side by side - here's the link!
But at that time there were still people doing something called "Fat client".
So what exactly was (is) a Fat client application.
In a nutshell, fat client is a concept where the client holds the logic of the application and talks to database directly. Database in this case is the point of truth. Fat clients have certain advantages.
- Fat client utilises the users CPU and resources - thus spares the company from buying (at that time) expensive servers.
- Fat client is pretty quick - unless you need something from the database (backend) and the database is busy.
- Fat client's look and feel is consistent. It is a native application so users are usually familiar with the UI.
But there are certain drawbacks
- Fat client needs to be installed and maintained locally. It's OK for several users, but thousands users can be a completely different story.
- Fat client runs on one platform only - it is a native application in the end! It means that upgrade to newer version Windows is risky not even thinking about porting that application to Unix/MacOS.
- Fat client can simply die or stop working and you don't know it until your users tell you (if they even bother to tell you).
And the list goes on.
Now, fast forward, year 2014. Here we are. We've got our servers but we try again to let our clients to do the heavy lifting. This time with a small twist. Instead of using native applications (we've been there, haven't we?) we use HTML/Javascript. So what exactly differs between the fat client v.1 (native application in year 2000) and fat client v. 2 (AngularJS application in year 2014)
- We dropped native applications, we now use HTML and Javascript. So the UI may be completely unfamiliar to our users. HTML builds a very thick layer on top of the hardware so our fat client v. 2 applications may be pretty slow on older computers.
- We ditch the installation process. Installing software is bad. Updating, maintaining it - no kudos there. Instead, we install the application over and over again as the user visits our site. But is the user really visiting our site that often? What the users just put his PC on stand by and have the page (application) running 24/7 for a days, months?
- We're smarter now - we don't talk to database. We talk to APIs. And because we're smarter we all use JSON. JSON is fine, everyone can read it, it's nicely structured and all the network sniffers are happy - listen or port 80 (443) and all the structured data is there.
- As the application is written in Javascript everyone can read the source code and tweak it. All these wannabe developers rejoice.
- We are more masochistic now. If something looks easy then everyone could do it, sure thing. So we make Angular difficult. Controllers, services, directives, dependancy injection. Who cares you only want to let user to input several parameters to get some output back, you still need to make it painful for the developers, they need to deserve their pay.
- We learn from experience and we know users hate error messages. That's why we don't give them any. If we're in a good mood we dump something on the console and we pray for the user not to press F12 (or CMD+ALT+J). Ideally we let to user in the dark by presenting a screen where things look working but the code behind them is long time zombie.
- Unfortunately the browser still has the reload and back button. We just hope the user will not press it or we try to come up with a smart way handling that. Users are confused but who cares about their feelings.
- Using browser has other nice advantages. No native printing, no access to the hardware, not working app if the user happen to lose his Internet connectivity. Some big companies allow you to continue using a crippled version of their application if you're offline but most people don't bother.
- And we all know that data is the king. So we don't allow the user to access the data. Fat client v. 1 would allow you to save data in various formats but v. 2 saves data in the Cloud and makes sure anything that even slightly resembles the save button is removed.
So, is it all lost? I don't think so. Because there's already Fat client v. 3 here. Oh yes - the native smartphone/tablet applications! They install but keep themselves updated, they talk to APIs but in their own formats (although JSON is getting there as well). The applications still crash, allow you to save data and work offline. And now (*drumroll*) Google would like to allow these apps on their Chromebooks - eat that Angular!
And for those who want to see this side by side - here's the link!
Tuesday, January 22, 2013
picoGal - tiny little js gallery for your website
Just finished a small (tiny, pico) JavaScript gallery jquery plugin.
Basically it takes a list of images (provided or loaded from DOM) and creates a gallery. Is't nowhere near to other comprehensive plugins but it's fast and lightweight.
Not everyone's cup of tea, I know.
For demo go here.
Source is in github.
Monday, November 21, 2011
Challenging week
What a week last week. Three project - three completely different technologies.
Anyway good times last week, this week it will be more about implementing more PoC and more, unfortunately, meetings ...
- I started the week bug fixing our Wheelchair portal written in Grails. Grails underpinned by my favorite language Groovy is by far framework of my choice and means that i had a pretty good time coding.
- Next one - PoC opening Oracle CRM (EBiz suite) custom form preloaded with data coming from our new out of the shelf leasing product. Normally we would pass this information in URL but that would mean customizing Oracle CRM which is expensive and no one wants to do it. Solution - Calling system will store input data in database and CRM will load this data on form load event. This event can be handled as personalization (not customization). Technologywise - Oracle SOA to store data into database (exposed as sync webservice) and Oracle forms on CRM side.
- Last one - creating MS Outlook tasks triggered by events in CRM. The CRM bit is outsourced but the Exchange bit is pure java witha hint of Apache Jackrabbit (client side only - no webDAV server) and composition of webDAV messages.
Anyway good times last week, this week it will be more about implementing more PoC and more, unfortunately, meetings ...
Friday, November 18, 2011
Multilevel clickable menu (tablet enabled)
My first component like project in jQuery. Why? In our internal application we use YUI menu and it works fine, but it's driven by mouse ins and outs. Normally that would be OK (and most of the time it is OK) but if you want to access such menu from tablets where you don't have a mouse connected (which renders mouse hovering useless) you've got a problem. There several solutions to it one which involves writing a mobile version of our application or rewriting the menu itself. Writing a mobile version was out of the question for us as we didn't have time and resources so the quickest solution was to replace the menu with one supporting mouse clicks (on tables taps).
To our surprise between the hundreds of html menus of all styles, shapes, all singing all dancing we could not find a single usable menu driven by clicks. And then I thought - right, if there's really nothing out there lets build something.
So I spent some time trying to stitch something together with mostly no luck but slowly learning how to display and hide and style a menu. My original idea was to render the menu from within jQuery and use HTML only to define the menu structure but later I had to change my mind as rendering in jQuery seemed to be slow and hard to debug. My final option was to delegate bulk of the job to HTML/CSS and use only small jQuery script to animate menu clicks.
If you want to see the menu just visit my github page https://github.com/defectus/mainmenu.js.
Thinks to note:
To our surprise between the hundreds of html menus of all styles, shapes, all singing all dancing we could not find a single usable menu driven by clicks. And then I thought - right, if there's really nothing out there lets build something.
So I spent some time trying to stitch something together with mostly no luck but slowly learning how to display and hide and style a menu. My original idea was to render the menu from within jQuery and use HTML only to define the menu structure but later I had to change my mind as rendering in jQuery seemed to be slow and hard to debug. My final option was to delegate bulk of the job to HTML/CSS and use only small jQuery script to animate menu clicks.
If you want to see the menu just visit my github page https://github.com/defectus/mainmenu.js.
Thinks to note:
- Menu doesn't display properly in IE6. It's usable but visually just not right.
- Menu looks somehow slow in IE. But what doesn't look slow in IE though.
- Menu supports on three levels. Any subsequent level needs to be handled individually.
Thursday, November 17, 2011
Creating an Outlook task in Java using webDAV
I've recently come across this interesting task. In Java, create MS Exchange tasks with assigned reminders and custom task body. I was told that PoC (proof of concept) had been successfully concluded and it was just a matter of integration. To be honest, the PoC came up with this idea - create a web application which would utilize jIntegra DCOM wrapper (as the web would be running in Linux so no COM there) and remotely access MS Outlook installed somewhere and from there it would create tasks in Exchange. As you can imagine, the level of complexity of this approach is enormous. This solution would do a round trip around the world just to access an Exchange server and create a task there. Still this solution would eventually fail because of Outlooks scripting protection (see it here) and would require someone permanently logged in Outlook so DCOM calls would be possible.
What other (if any) solutions are out there. One pretty straight forward and surprisingly Java friendly too. Long time ago someone invented this extension to HTTP called webDAV. Yes, it's still around - alive and kicking. As webDAV is generally speaking just a collection of additional HTTP verbs (methods) it can be easily invoked from any language as long as the program can access HTTP (i.e. all).
Below's how I did it. You only need to download Jackrabbit jar ( freely available from Apache) and run the code. It internally performs a webDAV call that creates a new Exchange task. Tested with Exchange 2003 SP2 but should work with any 2003+ version. Additional files can be found under the main one. It's just a small tweak to Jackrabbit's own PropPatch method (adding PropPatch call with the XML in a String) and HtmlEncode helper (not my invention!) class to allow html task body encoding.
More info and source can be found at these URLs:
What other (if any) solutions are out there. One pretty straight forward and surprisingly Java friendly too. Long time ago someone invented this extension to HTTP called webDAV. Yes, it's still around - alive and kicking. As webDAV is generally speaking just a collection of additional HTTP verbs (methods) it can be easily invoked from any language as long as the program can access HTTP (i.e. all).
Below's how I did it. You only need to download Jackrabbit jar ( freely available from Apache) and run the code. It internally performs a webDAV call that creates a new Exchange task. Tested with Exchange 2003 SP2 but should work with any 2003+ version. Additional files can be found under the main one. It's just a small tweak to Jackrabbit's own PropPatch method (adding PropPatch call with the XML in a String) and HtmlEncode helper (not my invention!) class to allow html task body encoding.
More info and source can be found at these URLs:
- webDAV PropPatch special fields in Exchange http://www.winserverkb.com/Uwe/Forum.aspx/exchange-2000-development/288/WebDAV-Tasks-A-Solution
- Visual Basic example of task creation http://objectmix.com/microsoft-exchange/268143-webdav-creating-task-exchange.html
- And a Java webDav example https://forums.oracle.com/forums/thread.jspa?threadID=2045070
package uk.co.mo.webDAV.utils; import org.apache.commons.httpclient.*; import org.apache.commons.httpclient.auth.AuthScope; import org.apache.commons.httpclient.params.HttpConnectionManagerParams; import java.util.Date; public class TaskCreator { public static void main(String[] args) throws Exception { // create a httpclient config String uri = "http://xxx.yyy.zzz/exchange/"; // String uri = "http://xxx.yyy.zzz/exchange/"; HostConfiguration hostConfig = new HostConfiguration(); hostConfig.setHost(uri); HttpConnectionManager connectionManager = new MultiThreadedHttpConnectionManager(); HttpConnectionManagerParams params = new HttpConnectionManagerParams(); int maxHostConnections = 20; params.setMaxConnectionsPerHost(hostConfig, maxHostConnections); connectionManager.setParams(params); HttpClient client = new HttpClient(connectionManager); client.setHostConfiguration(hostConfig); // set authentication (most exchange servers accept nt challenge-response) Credentials creds = new NTCredentials("admin_username", "password", "ip", "domain"); // Credentials creds = new NTCredentials("username", "password", "domain controller", "domain"); client.getState().setCredentials(AuthScope.ANY, creds); PropPatchMethodPro pPatch = new uk.co.mo.webDAV.utils.PropPatchMethodPro("http://xxx.yyy.zzz/exchange/user/Tasks/nameOfThetask" + new Date().getTime() + ".eml", getMessage()); // PropPatchMethodPro pPatch = new uk.co.mo.webDAV.utils.PropPatchMethodPro ("http://xxx.yyy.zzz/exchange/user/Tasks/nameOftheTask") new Date().getTime() + ".eml", getMessage()); pPatch.setRequestHeader("Content-type", "text/xml; charset=UTF-8"); // call exchange client.executeMethod(pPatch); // is everything OK if (!pPatch.isSuccess(pPatch.getStatusCode())) { // we've got a problem System.out.println("PROBLEM"); System.out.println(pPatch.getStatusCode()); System.out.println(pPatch.getStatusText()); System.out.println(pPatch.getStatusLine()); } else { // processed System.out.println("OK"); } } private static String getMessage() { return new StringBuilder("<?xml version=\"1.0\"?>\n") .append("<g:propertyupdate xmlns:g=\"DAV:\"\n") .append("xmlns:e=\"http://schemas.microsoft.com/exchange/\"\n") .append("xmlns:mapi=\"http://schemas.microsoft.com/mapi/\"\n") .append("xmlns:mapit=\"http://schemas.microsoft.com/mapi/proptag/\"\n") .append("xmlns:dt=\"urn:uuid:c2f41010-65b3-11d1-a29f-00aa00c14882/\"\n") .append("xmlns:h=\"http://schemas.microsoft.com/mapi/id/{00062003-0000-0000-C000-000000000046}/\"\n") .append("xmlns:i=\"http://schemas.microsoft.com/mapi/id/{00062008-0000-0000-C000-000000000046}/\"\n") .append("xmlns:header=\"urn:schemas:mailheader:\"\n") .append("xmlns:sql=\"urn:schemas-microsoft-com:mapping-schema\"\n") .append("xmlns:mail=\"urn:schemas:httpmail:\"\n") .append("xmlns:t=\"http://schemas.microsoft.com/exchange/tasks/\">\n") .append("<g:set>\n") .append("<g:prop>\n") .append("<g:contentclass>urn:content-classes:task</g:contentclass>\n") .append("<e:outlookmessageclass>IPM.Task</e:outlookmessageclass>\n") // we're creating a task .append("<mail:subject>Test Task</mail:subject>\n") //subject line of the task .append("<mail:htmldescription>") // html message - needs to html encoded .append(HtmlEncode.text("Task Test<br/><b>test bold</b><pre>test pre</pre><a href='www.google.com'>www.google.com</a>")) .append("</mail:htmldescription>\n") .append("<h:0x8104 dt:dt=\"dateTime.tz\">2011-11-20T01:00:00.00Z</h:0x8104>\n") //start date .append("<h:0x8105 dt:dt=\"dateTime.tz\">2011-11-21T01:00:00.00Z</h:0x8105>\n") //due date .append("<i:0x8516 dt:dt=\"dateTime.tz\">2011-11-20T01:00:00.00Z</i:0x8516>\n") //start date .append("<i:0x8517 dt:dt=\"dateTime.tz\">2011-11-21T01:00:00.00Z</i:0x8517>\n") //due date .append("<i:0x8502 dt:dt=\"dateTime.tz\">2011-11-20T15:50:00.00Z</i:0x8502>\n") // reminder date .append("<h:0x811C dt:dt=\"boolean\">0</h:0x811C>\n") // completed .append("<h:0x8101 dt:dt=\"int\">0</h:0x8101>\n") // status .append("<h:0x8102 dt:dt=\"float\">0</h:0x8102>\n") //completed % .append("<i:0x8503 dt:dt=\"boolean\">1</i:0x8503>\n") // reminder enabled .append("<header:to>apollosystem</header:to>\n") // task destination .append("</g:prop>\n") .append("</g:set>\n") .append("</g:propertyupdate>").toString(); } }
package uk.co.mo.webDAV.utils; import org.apache.commons.httpclient.methods.StringRequestEntity; import org.apache.jackrabbit.webdav.DavConstants; import org.apache.jackrabbit.webdav.DavMethods; import org.apache.jackrabbit.webdav.client.methods.DavMethodBase; import org.apache.jackrabbit.webdav.property.DavPropertyNameSet; import org.apache.jackrabbit.webdav.property.DavPropertyName; import org.apache.jackrabbit.webdav.property.DavPropertyNameIterator; import org.apache.jackrabbit.webdav.DavServletResponse; import org.apache.jackrabbit.webdav.MultiStatus; import org.apache.jackrabbit.webdav.MultiStatusResponse; import org.apache.jackrabbit.webdav.DavException; import org.apache.jackrabbit.webdav.Status; import org.apache.jackrabbit.webdav.xml.DomUtil; import org.apache.commons.httpclient.HttpState; import org.apache.commons.httpclient.HttpConnection; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import org.w3c.dom.Document; import org.w3c.dom.Element; import java.io.IOException; public class PropPatchMethodPro extends DavMethodBase implements DavConstants { private static Logger log = LoggerFactory.getLogger(PropPatchMethodPro.class); private final DavPropertyNameSet propertyNames = new DavPropertyNameSet(); private DavException responseException; /** * @param uri * @throws IOException */ public PropPatchMethodPro(String uri, Document document) throws IOException { super(uri); setRequestBody(document); } public PropPatchMethodPro(String uri, String document) throws IOException { super(uri); setRequestBodyText(document); } public void setRequestBodyText(String requestBody) { setRequestEntity(new StringRequestEntity(requestBody)); } private Element getPropElement(Element propUpdate, boolean isSet) { Element updateEntry = DomUtil.addChildElement(propUpdate, (isSet) ? XML_SET : XML_REMOVE, NAMESPACE); return DomUtil.addChildElement(updateEntry, XML_PROP, NAMESPACE); } //---------------------------------------------------------< HttpMethod >--- /** * @see org.apache.commons.httpclient.HttpMethod#getName() */ @Override public String getName() { return DavMethods.METHOD_PROPPATCH; } //------------------------------------------------------< DavMethodBase >--- /** * @param statusCode * @return true if status code is {@link DavServletResponse#SC_MULTI_STATUS 207 (Multi-Status)}. * For compliance reason {@link DavServletResponse#SC_OK 200 (OK)} is * interpreted as successful response as well. */ @Override protected boolean isSuccess(int statusCode) { return statusCode == DavServletResponse.SC_MULTI_STATUS || statusCode == DavServletResponse.SC_OK; } /** * @param multiStatus * @param httpState * @param httpConnection */ @Override protected void processMultiStatusBody(MultiStatus multiStatus, HttpState httpState, HttpConnection httpConnection) { // check of OK response contains all set/remove properties MultiStatusResponse[] resp = multiStatus.getResponses(); if (resp.length != 1) { log.warn("Expected a single multi-status response in PROPPATCH."); } boolean success = true; // only check the first ms-response for (int i = 0; i < 1; i++) { DavPropertyNameSet okSet = resp[i].getPropertyNames(DavServletResponse.SC_OK); if (okSet.isEmpty()) { log.debug("PROPPATCH failed: No 'OK' response found for resource " + resp[i].getHref()); success = false; } else { DavPropertyNameIterator it = propertyNames.iterator(); while (it.hasNext()) { DavPropertyName pn = it.nextPropertyName(); success = okSet.remove(pn); } } if (!okSet.isEmpty()) { StringBuffer b = new StringBuffer("The following properties outside of the original request where set or removed: "); DavPropertyNameIterator it = okSet.iterator(); while (it.hasNext()) { b.append(it.nextPropertyName().toString()).append("; "); } log.warn(b.toString()); } } // if build the error message if (!success) { Status[] st = resp[0].getStatus(); // TODO: respect multiple error reasons (not only the first one) for (int i = 0; i < st.length && responseException == null; i++) { switch (st[i].getStatusCode()) { case DavServletResponse.SC_FAILED_DEPENDENCY: // ignore break; default: responseException = new DavException(st[i].getStatusCode()); } } } } /** * @return * @throws IOException */ @Override public DavException getResponseException() throws IOException { checkUsed(); if (getSuccess()) { String msg = "Cannot retrieve exception from successful response."; log.warn(msg); throw new IllegalStateException(msg); } if (responseException != null) { return responseException; } else { return super.getResponseException(); } } }
package uk.co.mo.webDAV.utils; import java.io.UnsupportedEncodingException; import java.net.URLEncoder; /** * Encodes text and URL strings in various ways resulting HTML-safe text. * All methods are <code>null</code> safe. */ public class HtmlEncode { protected static String EMPTY_STRING = ""; protected static final char[][] TEXT = new char[64][]; protected static final char[][] BLOCK = new char[64][]; protected static final char[][] URL = new char[256][]; /** * Creates HTML lookup tables for faster encoding. */ static { for (int i = 0; i < 64; i++) { TEXT[i] = new char[]{(char) i}; } for (char c = 0; c < 256; c++) { try { URL[c] = URLEncoder.encode(String.valueOf(c), "ISO-8859-1").toCharArray(); } catch (UnsupportedEncodingException ueex) { ueex.printStackTrace(); } } // special HTML characters TEXT['\''] = "'".toCharArray(); // apostrophe (''' doesn't work - it is not by the w3 specs) TEXT['"'] = """.toCharArray(); // double quote TEXT['&'] = "&".toCharArray(); // ampersand TEXT['<'] = "<".toCharArray(); // lower than TEXT['>'] = ">".toCharArray(); // greater than // text table System.arraycopy(TEXT, 0, BLOCK, 0, 64); BLOCK['\n'] = "<br>".toCharArray(); // ascii 10, new line BLOCK['\r'] = "<br>".toCharArray(); // ascii 13, carriage return } // ---------------------------------------------------------------- encode public static String text(Object object) { if (object == null) { return EMPTY_STRING; } return text(object.toString()); } /** * Encodes a string to HTML-safe text. The following characters are replaced: * <ul> * <li>' with ' (' doesn't work)</li> * <li>" with "</li> * <li>& with &</li> * <li>< with <</li> * <li>> with ></li> * </ul> * * @see #block(String) */ public static String text(String text) { int len; if ((text == null) || ((len = text.length()) == 0)) { return EMPTY_STRING; } StringBuilder buffer = new StringBuilder(len + (len >> 2)); for (int i = 0; i < len; i++) { char c = text.charAt(i); if (c < 64) { buffer.append(TEXT[c]); } else { buffer.append(c); } } return buffer.toString(); } // ---------------------------------------------------------------- enocde text public static String block(Object object) { if (object == null) { return EMPTY_STRING; } return block(object.toString()); } /** * Encodes text into HTML-safe block preserving paragraphes. Besides the {@link #text(String) default * special characters} the following are replaced, too: * <ul> * <li>\n with <br></li> * <li>\r with <br></li> * </ul> * <p/> * <p/> * Method accepts any of CR, LF, or CR+LF as a line terminator. */ public static String block(String text) { int len; if ((text == null) || ((len = text.length()) == 0)) { return EMPTY_STRING; } StringBuilder buffer = new StringBuilder(len + (len >> 2)); char c, prev = 0; for (int i = 0; i < len; i++, prev = c) { c = text.charAt(i); if ((c == '\n') && (prev == '\r')) { continue; // previously '\r' (CR) was encoded, so skip '\n' (LF) } if (c < 64) { buffer.append(BLOCK[c]); } else { buffer.append(c); } } return buffer.toString(); } // ---------------------------------------------------------------- encode text strict public static String strict(Object object) { if (object == null) { return EMPTY_STRING; } return strict(object.toString()); } /** * Encodes text int HTML-safe block and preserves format using smart spaces. * Additionaly to {@link #block(String)}, the following characters are replaced: * <p/> * <ul> * <li>\n with <br></li> * <li>\r with <br></li> * </ul> * <p/> * This method preserves the format as much as possible, using the combination of * not-breakable and common spaces. */ public static String strict(String text) { int len; if ((text == null) || ((len = text.length()) == 0)) { return EMPTY_STRING; } StringBuilder buffer = new StringBuilder(len + (len >> 2)); char c, prev = 0; boolean prevSpace = false; for (int i = 0; i < len; i++, prev = c) { c = text.charAt(i); if (c == ' ') { if (prev != ' ') { prevSpace = false; } if (prevSpace == false) { buffer.append(' '); } else { buffer.append(" "); } prevSpace = !prevSpace; continue; } if ((c == '\n') && (prev == '\r')) { continue; // previously '\r' (CR) was encoded, so skip '\n' (LF) } if (c < 64) { buffer.append(BLOCK[c]); } else { buffer.append(c); } } return buffer.toString(); } }Enjoy while it lasts!
Subscribe to:
Posts (Atom)