Showing posts with label blog. Show all posts
Showing posts with label blog. Show all posts

Saturday, June 20, 2009

Clear space on blogger page

Practically, too much gadgets (much more than the height of web page) look very ugly.

The simplest way to save space is remove gadgets that actually never used by users.

For example, If you are really doesn't need followers, and satisfied with people, who found you through search engine, than you don't need funny followers gadget, that actually makes page ugly.

Another way is making some blocks invisible, until users really need them.

On the right of this blog, there is the string "[+]unhide my info".

If the reader of the blog really need info, he can click and unfold this information.
All information from list or text gadget could be packed there.

How to make existing text and list packed into html/javascript box foldable (hidden)?

For my case, I just enveloped the existing text in following HTML/javascript code:


<div id="div_contacts" onmouseover=
"javascript:div_contacts.style.cursor=pointer;"
style="color:#0000FF;cursor:pointer;cursor:hand" onclick=
"javascript:switch_direction()
"><b>[+] unhide my info and legal notice</b></div><
span id="my_contacts" style="display:none">
<pre>
<b>

your text/list/links there

</b>

</span>

<script type="text/javascript">
function switch_direction(direction)
{
var val = document.getElementById("div_contacts");
if(val.innerHTML=="<b>[+] unhide my info and legal notice</b>")
{
val.innerHTML="<b>[-] hide my info and legal notice<b>";
var val2=document.getElementById("my_contacts");
val2.style.display="";
}
else
{
val.innerHTML="<b>[+] unhide my info and legal notice</b>";
var val2=document.getElementById("my_contacts");
val2.style.display="none";
};
}
</script>


tested with firefox 3

Monday, March 30, 2009

Strategy for legacy software system code redesign

Basically, process of redesign of old existing software system can be presented as following sequence:

1) Define goal for redesign, and characteristics of system after redesign.

2) Cover by tests and measurements to measure degree of correspondence to characteristics defined.

3) Define methods for improvements.

4) Do redesign by methods defined in 3, keeping 2nd) tests and measurements.

5) If 1) goal of redesign achieved stop.


Other things, that should be kept during redesign, if you want to keep system live long after redesign done:

http://rgritsulyak.blogspot.com/2009/03/survivable-long-living-systems.html

Tuesday, April 15, 2008

refactoring

Appeared, that I have no suitable refactoring tool.

Started refactoring utility.
Platform is C, prototype in perl + postgres.

Perl appears great tool for prototyping of such tool(actually specific processor of set of files).
It provides you working prototype in times faster that it can be done in C.

First problems:

- Lack of time. I have only time when travelling between home and job, It takes about 1.5 hours, but not all time can be used for code input. That way version 1.0 only for Linux can take up to next new year. Actually it is possible that it would be never fixed because of changes in schedules, regime and load on paid job.

- Problem of platform choice. It have to be C because it is probably would be utility for GNU/Linux. Checked standards and appeared that C standard changed from last time I used pure C, but not C++. There is now C99 standard, and there is also draft standard with changes dated by this year.Also in GNU/Linux appeared used non standard GNU extensions of C. Decided to use C90, that way, because it is most commonly supported.

- Data structures. It is a lot of choices with pro's and con's. Decided to play with Perl prototype first. Using DS simple in implementation, with ability to change this to more fast but complex.

- Design questions. (sizes of structures, level of decomposition, libraries to use)

- License: GPL 2 (or 3?).

Wednesday, April 9, 2008

labels (Tags) in blog

Label cloud becomes trash label if put tags on fly, unique for each post.

I have cleaned my blog from rarely used tags and decided not create tags if they are used less than ones in blog.

Sunday, March 16, 2008

javascript for code highiliting, v0.3

Placed v.0.3 version.
It is more pretty.

Moved "<>" in the begining of keywords processing loop (by definition in basic.js).

Joined keywords by "|" symbol in basic.js to use as single expression without looping.

Further could be done improvements of comments, they are not working well in the version.
basic.js renamed to basic.js.txt, because it tried to be loaded from iframe.

Bothering alerts also removed.

Saturday, February 23, 2008

Thursday, February 21, 2008

Contact, about me, and disclaimer

Contact


My Blogger Profile

Write me e-mail

About me


My name is Roman Gritsulyak.

I am more than 10 years experienced in software development ( with Analytics, QA, and consulting as parts of this activities ) .

English is not first language for me, so there are possible errors in text of posts.
Please, feel free to write me, what I have to do to fix mistake in text. It will help me to made more useful staff.

Disclaimer


Use articles free, but put hypertext reference on original locations.

The code on this site distributed under MIT license

Most of hacks presented were produced and tested using Linux operational system,
and it is much less probable, that it will work under Cygwin on Windows.

Obey license agreement, when using code:


Copyright (c) 2008, Roman T. Gritsulyak

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

Sunday, April 22, 2007

Content

Thoughts, ideas and explorations that are of some interest
for me will be here.